No Internet access after power loss

Arcatus · Post by **Arcatus** » 26 Apr 2011, 12:05

Hi!

I have a Bubba 2 with Wlan that is not able to access Internet after a power loss.

It is used as a wireless access point, and is connected after a router that assigns my public IP to it. This system has worked fine for moths, but after I flipped the power switch and left the router and bubba unpowered for a few days Internet is no longer detected.

The router is able to detect bubba, and everything seems normal in that end...

I am able to connect to the bubba using WLAN, (where it's using the default 192.168.10.1 address, the router is 10.0.0.1... is this ok...?)
Network profile is automatic, and under bubba network settings; "network/WAN" the correct public IP address is shown, so there is some DHCP communication going on between the router and bubba...

However; when pinging my hostname the old IP address is used, so the DNS is not updated.

The new public IP does not reply on ping.

So; the above is perhaps not enough to find a solution; but if you need me to paste some logs or write some commands over telnet I can do that, I just don't know what commands to use...

Ubi · Post by **Ubi** » 26 Apr 2011, 13:18

Arcatus wrote:I am able to connect to the bubba using WLAN, (where it's using the default 192.168.10.1 address, the router is 10.0.0.1... is this ok...?)

no this is very much not ok. It's actually nearly impossible to get traffic across when the router and the client do not have compatible network settings. You need to address this first.

Personally I'd log onto the SSH terminal of bubba to see what's really going on, but that might not be you r cup of tea. For the rest I have difficulty fully understanding your situation as it contains ambiguous references that make it hard to interpret (please try to avoid phrases like "the correct public IP address" or "the old IP address ". I don't know what you mean !).

If you don't want to SSH, I think your first stop is the network settings of the bubba interface (which, strangely, you do seem able to reach)

good luck

RandomUsername · Post by **RandomUsername** » 26 Apr 2011, 14:29

I'm not familiar with the wifi enabled Bubba 2 but could this be related to this post - http://forum.excito.net/viewtopic.php?f ... +Localhost ? Seems to be similar.

Binkem · Post by **Binkem** » 26 Apr 2011, 15:20

You might want to outline your network setup more elaborately, i.e. how is the bubba connected to the router/internet using what post (wan/lan) and how is the rest of your network connected: wifi only?

Arcatus · Post by **Arcatus** » 26 Apr 2011, 15:47

Sorry, it was not intentional to be unclear. But I have no idea where the problem is, so it's all rather generalized...

First; this illustrates my system:

If I disconnect the cable between the computer and the router and I loose Internet access and access to the router configuration pages.
If I disconnect the wireless I loose contact with bubba.

The router is setup to assign the public IP to bubba, so the router should be "completely" transparent when seen from bubba. Is it still an issue that different network IP's are involved?

Anyway; by having a cable to my router and activating my WLAN I am able to connect to the Internet and the bubba at the same time. I can connect to the router @ 10.0.0.1 and Bubba @ 192.168.10.1.

The 84.48.xx.xx IP address shown is my public IP and it is updated and correct. (so at some point after I restarted this address was sent from my router to bubba)

Pinging 84.48.xx.xx does nothing.
pinging myhostname.bubbserver.com and I ping the wrong IP -> so bubba has not updated the DNS service.

10.0.0.1 is my router.

For the record I've tried forcing the bubbas address to 10.0.0.20 and my computer to 10.0.0.60. That didn't work...

Cheeseboy · Post by **Cheeseboy** » 26 Apr 2011, 16:11

Hi Arcatus,

So if I understand you correctly, everything worked fine with your diagram (without the dotted line) before your B2 lost power, but now it doesn't.
Correct?

It worries me that your "Default gateway" in your screen pic above is NOT your router's 10.0.0.1, because it should be (if I understand you correctly).
And is your router's DHCP configured to deal out IPs starting with 84?
And why isn't your netmask the more normal 255.255.255.0?

If B2 is really talking to your DHCP server in your Router to get these values, your router is messed up.
But perhaps the B2 is messed up too, I don't know, but it doesn't surprise me nothing works.

Perhaps you should give your router and B2 both a half hours poweroff time?

Cheers,

Cheeseboy

EDIT:
And I recommend setting them both up manually

Ubi · Post by **Ubi** » 26 Apr 2011, 16:19

Kudos for the screenshots. I don't understand that, when the router is completely transparent to bubba, that you can still connect to the router and get internet access from the desktop. That should be impossible. Unless some more exotic setup is present. What happens if you set the router to non-transparent? Does it give bubba a 10.0.0. address on the wan and allow it internet access?

Binkem · Post by **Binkem** » 26 Apr 2011, 16:26

Try setting the lan side to fixed IP for the Bubba and DHCP for other computers (unless you have another DHCP service on the lan-side)

ryz · Post by **ryz** » 26 Apr 2011, 17:41

I think that you should ssh into the Bubba and do the following as the root user
Run the command

Code: Select all

ifconfig eth0

This will show you the current setting on the WAN port.If this seems incorect you could run

Code: Select all

ifdown eth0

to take down the WAN port wait a bit and the run

Code: Select all

ifup eth0

To enable the WAN port once more.

IF you still have problems you could try to run

Code: Select all

dhclient -r

to explicity release the IP followed by an

Code: Select all

dhclient

To get a new IP.

Cheeseboy · Post by **Cheeseboy** » 26 Apr 2011, 18:04

Heavily edited for horrible spelling (if I ever get my internet connection back):

Hi again,

Please ignore most of what I wrote before, it was rubbish (I scrolled my mouse up and down and didn't realise I was looking at two pics at once). Now I will write some of it again.

Now what I look in your WAN settings, they are quite strange.
It looks like you have the play of the whole NextGenTel AS IP-range (according to RIPE whois) with that netmask.

This is strange in it self, but also your ISP does not give you (or your router does not pass through) other basic stuff like default gateway via DHCP, but still it picks up your local 10.x IP as DNS?
This must mean you diagram was inaccurate, or did you have the temporary cable attached directly to the bubba so it could act as DHCP sever?

I would oppose Blinkem and suggest that you can disconnect everything but your router and connect a PC over a network cable, then connect to the router's web interface and make a note of what values it gets from the ISP DHCP server in there (gateway, DNS, netmask, etc).

OR:
Just do what ryz said in the post he was posting when I was writing this first.

Ubi · Post by **Ubi** » 26 Apr 2011, 18:18

well spotted on the WAN settings. These are completely wrong.
could we please see the output of

Code: Select all

ifconfig

and

Code: Select all

route

thanks

Arcatus · Post by **Arcatus** » 27 Apr 2011, 17:48

Thanks allot for great assistance so far

As this is a public forum iv've masked out parts of the IP's with x'es, as well as the HW addresses, but if any forum users want them I can send it as a PM...

Ifconfig:

Code: Select all

br0       Link encap:Ethernet  HWaddr xxxxxxxxxxx
          inet addr:192.168.10.1  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::222:xyz:xyz:xyz/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3182 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2906 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:409161 (399.5 KiB)  TX bytes:895246 (874.2 KiB)

eth0      Link encap:Ethernet  HWaddr xxxxxxx
          inet addr:84.48.xx.xyz  Bcast:84.255.255.255  Mask:255.0.0.0
          inet6 addr: fe80::222:xyz:xyz:xyz/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:14174 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4348 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:958955 (936.4 KiB)  TX bytes:190830 (186.3 KiB)
          Base address:0xc000

eth1      Link encap:Ethernet  HWaddr xxxxxxx
          inet6 addr: fe80::222:xyz:xyz:xyz/64 Scope:Link
          UP BROADCAST PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:557 errors:0 dropped:0 overruns:0 frame:0
          TX packets:479 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:80877 (78.9 KiB)  TX bytes:140475 (137.1 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:811 errors:0 dropped:0 overruns:0 frame:0
          TX packets:811 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:140412 (137.1 KiB)  TX bytes:140412 (137.1 KiB)

mon.wlan0 Link encap:UNSPEC  HWaddr xxxxxxxxxx
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:85 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6151 (6.0 KiB)  TX bytes:0 (0.0 b)

wlan0     Link encap:Ethernet  HWaddr xxxxxx
          inet6 addr: fe80::280:xyz:xyz:xyz/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9605 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13181 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1252221 (1.1 MiB)  TX bytes:5396329 (5.1 MiB)

route:

Code: Select all

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.10.0    *               255.255.255.0   U     0      0        0 br0
84.0.0.0        *               255.0.0.0       U     0      0        0 eth0

I've not masked anything in the above return from route.. so there it is allot of 0's there. is that normal?

I also checked on the tread suggested by randomusername, and indeed my hosts file looked like this:

Code: Select all

127.0.0.1       localhost.localdomain   localhost
::1     ip6-localhost   ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
127.0.0.1       bubba   bubba.localdomain

I corrected it to this:

Code: Select all

192.168.10.1    localhost.localdomain   localhost
::1     ip6-localhost   ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
192.168.10.1    bubba   bubba.localdomain

I rebooted, but that didn't fix anything.. My guess is that when I was poking around in the web interface I also triggered the bug described by randomusername.

So, the above doesn't make much sense to me; but hopefully it can be an assistance to you guys...

forum.excito.org

No Internet access after power loss

No Internet access after power loss

Re: No Internet access after power loss

Re: No Internet access after power loss

Re: No Internet access after power loss

Re: No Internet access after power loss

Re: No Internet access after power loss

Re: No Internet access after power loss

Re: No Internet access after power loss

Re: No Internet access after power loss

Re: No Internet access after power loss

Re: No Internet access after power loss

Re: No Internet access after power loss