IP address family not supported problem

Posted:
in Genius Bar edited January 2014











I'm trying to connect to my router (Vizio xwr100 with openwrt installed), but can't because its IP address is out of range. The previous configuration got messed up and its address is set to 224.0.0.251. When I try to access it using the browser interface, I get the following error: "Safari can't open the page "http://224.0.0.251/". The error is: "The operation couldn't be completed. Address family not supported by the protocol family" (NSPOSIXErrorDomain:47)".

 

In addition, I tried to change the address on my computer to 224.0.0.250 so I would be on the same subnet in order to ssh into it, but got the error: "Invalid IP Address. The first quad of the value entered is out of range and cannot be used as the router address for this computer." And ssh to that address returns: "Address family not supported by protocol family".

 

I also tried the command:

sudo arp -s 192.168.0.2 1:0:5e:0:0:fb temp && ssh [email protected]

to see if I could ssh into it from its MAC address, but the attempt just times out.

 

And, I can't reset it to the factory default because the firmware's been flashed. Any ideas on how to access this router?



 

Comments

  • Reply 1 of 10
    MarvinMarvin Posts: 14,548moderator
    Are you sure that your router is running an SSH server? Try using telnet after your arp command instead. Also, are you sure the main user is root and not admin?
  • Reply 2 of 10

    Yes, I'm sure it's running ssh server and that the main user is root rather than admin. I tried telnet and got the same error as ssh.

  • Reply 3 of 10

    Are you trying to connect wirelessly? Can you connect to it via ethernet?

  • Reply 4 of 10

    No, I'm not connecting wirelessly. It's connected to one of the LAN ports by ethernet.

  • Reply 5 of 10
    muppetrymuppetry Posts: 3,331member

    Yes - your problem is that somehow the router accepted an address that is outside IPv4 address space. I'm surprised that it did not refuse it in the same way that your computer does. I can't see any way out of that if a factory reset doesn't work.

  • Reply 6 of 10
    MarvinMarvin Posts: 14,548moderator
    Does Safari not let you use the temporary IP once you use the arp command?
  • Reply 7 of 10

    Safari times out and doesn't load anything after setting the temporary IP, the same result after trying ssh and telnet.

     

    Muppetry, actually the router assigned the address to itself. I had changed the configuration of the LAN from static to dhcp, but realized I wanted it to be static so I changed it back but didn't set the address. I left and came back later to finish configuring it but couldn't get back in because the address had been set to 224.0.0.251.

     

    I think there may be a system file telling the OS which addresses are out of range. If I could temporarily disable that file then I could access the router. Any idea of which file that would be?

  • Reply 8 of 10
    muppetrymuppetry Posts: 3,331member
    Quote:

    Originally Posted by Tipton View Post

     

    Safari times out and doesn't load anything after setting the temporary IP, the same result after trying ssh and telnet.

     

    Muppetry, actually the router assigned the address to itself. I had changed the configuration of the LAN from static to dhcp, but realized I wanted it to be static so I changed it back but didn't set the address. I left and came back later to finish configuring it but couldn't get back in because the address had been set to 224.0.0.251.

     

    I think there may be a system file telling the OS which addresses are out of range. If I could temporarily disable that file then I could access the router. Any idea of which file that would be?


     

    That was most unsporting of it. 224.0.0.251 is reserved for local multicast DNS I think, and so that would make it a fairly core function in IPv4. I don't know of any system files that define it as reserved. You can address packets (e.g. ping) to that address without being on that (pseudo) subnet, but they will be treated as a multicast broadcast to all machines. I don't think that there is any way you can make a peer-to-peer connection, but that is definitely beyond my knowledge or direct experience.

     

    Just curious - how did you discover that it had set that address if  you couldn't talk to it?

  • Reply 9 of 10

    Glad you asked that question, I had to backtrack what I did.

    At first I disconnected the computer from the Internet, connected it to just the router, and entered "ping 255.255.255.255" from the terminal, entered "cntrl-c" to stop it, and then "arp -a" to see the results. The result was:

     

    ? (17.171.4.35) at (incomplete) on en0 ifscope [ethernet]

    ? (192.168.0.2) at (incomplete) on en0 ifscope [ethernet]

    ? (224.0.0.251) at 1:0:5e:0:0:fb on en0 ifscope permanent [ethernet]

    broadcasthost (255.255.255.255) at ff:ff:ff:ff:ff:ff on en0 ifscope [ethernet]

     

    At this point I had thought the address of the router was 224.0.0.251. My computer is 192.168.0.2. But, after you asked the question I changed my computer's address to 17.171.4.34 to put it on the same subnet as one of the results, entered the sequence of commands again and got this:

     

    ? (17.171.4.35) at (incomplete) on en0 ifscope [ethernet]

    ? (188.37.11.137) at (incomplete) on en0 ifscope [ethernet]

    ? (192.168.0.2) at (incomplete) on en0 ifscope [ethernet]

    ? (224.0.0.251) at 1:0:5e:0:0:fb on en0 ifscope permanent [ethernet]

    broadcasthost (255.255.255.255) at ff:ff:ff:ff:ff:ff on en0 ifscope [ethernet]

     

    I then changed my netmask from 255.255.255.0 to 255.0.0.0, did the sequence again, and got this:

     

    ? (17.171.4.35) at (incomplete) on en0 ifscope [ethernet]

    ? (91.121.72.224) at (incomplete) on en0 ifscope [ethernet]

    ? (122.149.249.116) at (incomplete) on en0 ifscope [ethernet]

    ? (188.37.11.137) at (incomplete) on en0 ifscope [ethernet]

    ? (192.168.0.2) at (incomplete) on en0 ifscope [ethernet]

    ? (224.0.0.251) at 1:0:5e:0:0:fb on en0 ifscope permanent [ethernet]

     

    I'm now thoroughly confused.

  • Reply 10 of 10
    muppetrymuppetry Posts: 3,331member
    Quote:
    Originally Posted by Tipton View Post

     

    Glad you asked that question, I had to backtrack what I did.

    At first I disconnected the computer from the Internet, connected it to just the router, and entered "ping 255.255.255.255" from the terminal, entered "cntrl-c" to stop it, and then "arp -a" to see the results. The result was:

     

    ? (17.171.4.35) at (incomplete) on en0 ifscope [ethernet]

    ? (192.168.0.2) at (incomplete) on en0 ifscope [ethernet]

    ? (224.0.0.251) at 1:0:5e:0:0:fb on en0 ifscope permanent [ethernet]

    broadcasthost (255.255.255.255) at ff:ff:ff:ff:ff:ff on en0 ifscope [ethernet]

     

    At this point I had thought the address of the router was 224.0.0.251. My computer is 192.168.0.2. But, after you asked the question I changed my computer's address to 17.171.4.34 to put it on the same subnet as one of the results, entered the sequence of commands again and got this:

     

    ? (17.171.4.35) at (incomplete) on en0 ifscope [ethernet]

    ? (188.37.11.137) at (incomplete) on en0 ifscope [ethernet]

    ? (192.168.0.2) at (incomplete) on en0 ifscope [ethernet]

    ? (224.0.0.251) at 1:0:5e:0:0:fb on en0 ifscope permanent [ethernet]

    broadcasthost (255.255.255.255) at ff:ff:ff:ff:ff:ff on en0 ifscope [ethernet]

     

    I then changed my netmask from 255.255.255.0 to 255.0.0.0, did the sequence again, and got this:

     

    ? (17.171.4.35) at (incomplete) on en0 ifscope [ethernet]

    ? (91.121.72.224) at (incomplete) on en0 ifscope [ethernet]

    ? (122.149.249.116) at (incomplete) on en0 ifscope [ethernet]

    ? (188.37.11.137) at (incomplete) on en0 ifscope [ethernet]

    ? (192.168.0.2) at (incomplete) on en0 ifscope [ethernet]

    ? (224.0.0.251) at 1:0:5e:0:0:fb on en0 ifscope permanent [ethernet]

     

    I'm now thoroughly confused.


     

    Since you changed IP address and 192.168.0.2 is still replying, are you sure that router isn't using that address - the same as your original computer IP address?

Sign In or Register to comment.