• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Can't connect to mythbackend

Scheduled Pinned Locked Moved General pfSense Questions
3 Posts 2 Posters 1.5k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    johnvan
    last edited by Mar 3, 2010, 2:21 PM

    This morning I turned on my mythfrontend and couldn't connect to the server. I also can't connect to it through mythweb. I'm a little lost here (and relatively new)
    The only strange thing I see is this:
    Mar 3 09:02:47 kernel: arp: 192.168.2.10 moved from 00:26:bb:d8:82:2a to 00:1c:25:3c:b7:be on xl0
    Mar 3 09:03:05 kernel: arp: 192.168.2.10 moved from 00:1c:25:3c:b7:be to 00:26:bb:d8:82:2a on xl0
    Mar 3 09:03:44 kernel: arp: 192.168.2.10 moved from 00:26:bb:d8:82:2a to 00:1c:25:3c:b7:be on xl0
    Mar 3 09:04:48 kernel: arp: 192.168.2.10 moved from 00:1c:25:3c:b7:be to 00:26:bb:d8:82:2a on xl0
    Mar 3 09:04:49 kernel: arp: 192.168.2.10 moved from 00:26:bb:d8:82:2a to 00:1c:25:3c:b7:be on xl0
    Mar 3 09:04:49 kernel: arp: 192.168.2.10 moved from 00:1c:25:3c:b7:be to 00:26:bb:d8:82:2a on xl0
    Mar 3 09:05:44 kernel: arp: 192.168.2.10 moved from 00:26:bb:d8:82:2a to 00:1c:25:3c:b7:be on xl0
    Mar 3 09:07:10 kernel: arp: 192.168.2.10 moved from 00:1c:25:3c:b7:be to 00:26:bb:d8:82:2a on xl0
    Mar 3 09:07:11 kernel: arp: 192.168.2.10 moved from 00:26:bb:d8:82:2a to 00:1c:25:3c:b7:be on xl0
    Mar 3 09:07:11 kernel: arp: 192.168.2.10 moved from 00:1c:25:3c:b7:be to 00:26:bb:d8:82:2a on xl0
    Mar 3 09:07:12 kernel: arp: 192.168.2.10 moved from 00:26:bb:d8:82:2a to 00:1c:25:3c:b7:be on xl0
    Mar 3 09:07:12 kernel: arp: 192.168.2.10 moved from 00:1c:25:3c:b7:be to 00:26:bb:d8:82:2a on xl0
    Mar 3 09:07:23 kernel: arp: 192.168.2.10 moved from 00:26:bb:d8:82:2a to 00:1c:25:3c:b7:be on xl0
    Mar 3 09:07:23 kernel: arp: 192.168.2.10 moved from 00:1c:25:3c:b7:be to 00:26:bb:d8:82:2a on xl0
    Mar 3 09:07:24 kernel: arp: 192.168.2.10 moved from 00:26:bb:d8:82:2a to 00:1c:25:3c:b7:be on xl0
    Mar 3 09:07:24 kernel: arp: 192.168.2.10 moved from 00:1c:25:3c:b7:be to 00:26:bb:d8:82:2a on xl0
    Mar 3 09:07:25 kernel: arp: 192.168.2.10 moved from 00:26:bb:d8:82:2a to 00:1c:25:3c:b7:be on xl0
    Mar 3 09:07:25 kernel: arp: 192.168.2.10 moved from 00:1c:25:3c:b7:be to 00:26:bb:d8:82:2a on xl0
    Mar 3 09:07:32 kernel: arp: 192.168.2.10 moved from 00:26:bb:d8:82:2a to 00:1c:25:3c:b7:be on xl0
    Mar 3 09:07:53 kernel: arp: 192.168.2.10 moved from 00:1c:25:3c:b7:be to 00:26:bb:d8:82:2a on xl0
    Mar 3 09:08:26 kernel: arp: 192.168.2.10 moved from 00:26:bb:d8:82:2a to 00:1c:25:3c:b7:be on xl0

    192.168.2.10 is the IP address of my mythtv backend.
    Any help would be appreciated, thanks!

    1 Reply Last reply Reply Quote 0
    • E
      EddieA
      last edited by Mar 3, 2010, 2:57 PM

      That looks like you have 2 machines, both configured to use 192.168.2.10.

      Is the myth configured with a static, or dynamic address.  Is 192.168.2.10 within a DHCP range.

      Cheers.

      1 Reply Last reply Reply Quote 0
      • J
        johnvan
        last edited by Mar 3, 2010, 3:18 PM

        Thanks, that's exactly what it was. My static mapping wasn't setup properly. I left 192.168.2.10 in the range of the DHCP pool and it was assigned to my IPOD touch.
        It's all setup properly now.
        Thanks!

        1 Reply Last reply Reply Quote 0
        3 out of 3
        • First post
          3/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received