Unable to connect to the Internet

[ddichiera]

Hi everyone,

I have just received my new Joggler and am enjoying playing with it, but I can't get it to connect to the internet.

I have a Cisco RV220W small business router which the Joggler connects to via Wireless (I also tried wired) and can see all my other devices including the Squeezebox server, DVBViewer server and can interact with those, but it cannot connect to the internet.

I'm not sure what thee problem is, but given that all my other devices including five PCs can see the wan, I suspect an issue with the Joggler.

Can anyone help?

Dominic

[dwl99]

I assume you're using the stock OS & WPA encryption?

Your router is probably set to use mixed TKIP/AES encryption. Go to the Joggler's Network Settings, select Advanced & change the encryption to WPA AES. If that does not work then try WPA TKIP. If still no success change the router's & the Joggler's settings to AES only. If still no success change the router's & the Joggler's settings to TKIP only.

It's a real pig to do the initial setup but after that it works fine. The Joggler really needs a good, strong signal to work.

[ddichiera]

Thanks for the reply dwl99.

How do I get to Advanced Network Settings?

BTW it has exactly the same problem if I connect wired.

Software version is 26635.53 (Jun 25 2010)

[gegs]

If the Joggler can see and interact with devices on the LAN, the problem may be with your business router settings. You may have to specifically allow the device to connect to the internet.

I do this, but in reverse, every evening at home. I disallow internet access for my children's web enabled devices (by MAC address) when I think they should be asleep. I could also restrict internet access to a set of MAC addresses that I specify and no other devices, which could be the case with your router.

[dwl99]

Thanks for the reply dwl99.

How do I get to Advanced Network Settings?

BTW it has exactly the same problem if I connect wired.

Software version is 26635.53 (Jun 25 2010)

It'll not be an encryption problem if it cannot connect via ethernet. As gegs said, it will probably be a router setting. Check that the system time & date are correct, this can sometimes prevent connection.

[ddichiera]

I bought it into work and it connected up to the internet via our private ADSL line immediately (wirelessly), so I guess there must be an issue with the Cisco Small Business router (RV220W).

Does anyone have any experience with these? I put it in a few months ago to replace a knackered Netgear DG832GT and all my PCs and devices connected to the internet straight away. It is set to DHCP.

[gegs]

You should check your router administration tool to see if any settings can be changed to allow the Joggler to access the internet.
DHCP will assign your devices IP numbers on the network. An IP number is not a guaranteed gateway to the internet.

[ddichiera]

Hi everyone,

I finally got to talk to Cisco support today. In short it does seem as though the router isn't passing requests from my Joggler (BTW I now have three of them). I produced some logs which he examined with Wireshark indicating the dns requests aren't being answered, but the engineer is unable to help much further because he can't connect remotely to the Joggler.

In short he suggested I add the external DNS address to the /etc/resolv.conf file of the joggler.

I ssh'd into the Joggler and added a test DNS (8.8.8.8) as nameserver and saved the file, but when I rebooted it had lost the edit.

I've doublechecked that I'm saving the edit by looking back at the contents after saving, but to no avail.

I don't know enough about Linux to know if I'm doing something wrong, or even if I'm putting the info in the correct file. Can anyone advise?

[pete]

I would say that its more related to your Cisco box than your Jogglers; especially if you brought one Joggler to work and it worked fine.

Getting a DNS address is part of DHCP.

Try calling Cisco again; tell them that you have three devices not getting their DNS from the DHCP in the their box; and that you have validated the their devices to be fully functional. Ask them for a service ticket number and that you want the issue resolved in a reasonable amount of time. Tell them to leave the ticket open until its resolved. (they will work dilligently for short MTR).

Before calling them; try shutting off the rest of the devices connected to your Cisco router and then booting up one of the Jogglers. It could be a setting relating to the DHCP scope configured. If you have a keyboard connected and you can do SSH to the Joggler just type in IFCONFIG to see your hw address settings. Then just type in ping www.google.com to see if you DNS resolution is working. Try also changing the resolv.conf and before rebooting try doing the ping to www.google.com and see if it works. It really shouldn't be anything that you set on the Jogglers unless for whatever reason there is a mess up with the DHCP configuration; which I doubt if its working in the office. My firewalls/routers have manual and automatic DHCP DNS configurations in the configs on the box. I've never looked at your specfic Cisco model; but all/most are the same. One side connects to the internet and the side connects to your home network. Typically your one internet address is NATed to multiple internal addresses. By default these are assigned via a DHCP configuration. If you know what the subnet is and what the gateway IP address is then manually configure one Joggler for a static IP address, put in the gateway address and use the same gateway address for the DNS piece on your Joggler configuration and see if that works.

[Mevi]

(BTW I now have three of them)

ONE OF US! ONE OF US!

Edit: Sorry, that wasn't at all helpful.

[ddichiera]

Thanks for the advice pete_c.

I tried all the options you suggested. I turned off DHCP and disconnected all other devices incl. wireless from router, in various combinations, all to no avail.

I'm definitely going to pursue with Cisco as I have time during their office hours, but I'm seeing very strange behaviour from my Joggle.

I still cannot change the parameters for resolv.conf without it resetting. I have since discovered if I change it and check back, it's ok. Then after a few minutes, the resolv.conf reverts to the original setting - actually it reverts back to the first change I made which is with the google nameserver (8.8.8.8) as the second line.

If you have a keyboard connected and you can do SSH to the Joggler just type in IFCONFIG to see your hw address settings

That suggests I can open a terminal session on the Joggler itself. If so, how do I do that?

[roobarb!]

That suggests I can open a terminal session on the Joggler itself. If so, how do I do that?

http://www.jogglerwiki.com/wiki/Ssh will tell you all you need. I recommend 'Easy Way (New Version)'.

[pete]

With SSH you can utilize both Putty and WinSCP to edit files etc; whichever you feel comfortable with. Google nameserver is good.

Can you ping the address 8.8.8.8?
Here I see (via XP)

\Pete>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:

Reply from 8.8.8.8: bytes=32 time=23ms TTL=52
Reply from 8.8.8.8: bytes=32 time=22ms TTL=52
Reply from 8.8.8.8: bytes=32 time=23ms TTL=52
Reply from 8.8.8.8: bytes=32 time=22ms TTL=52

Can you trace the IP to the source?

Here I see:

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms MyROUTERGATEWAYIP
2 30 ms 10 ms 19 ms MYFIRSTHOP
3 10 ms 9 ms 8 ms te-1-2-ur03.romeoville.il.chicago.comcast.net [6
8.86.118.221]
4 9 ms 8 ms 9 ms te-8-4-ur04.romeoville.il.chicago.comcast.net [6
8.86.187.166]
5 11 ms 12 ms 11 ms te-2-7-0-5-ar01.area4.il.chicago.comcast.net [68
.87.230.121]
6 15 ms 14 ms 12 ms pos-3-6-0-0-cr01.350ecermak.il.ibone.comcast.net
[68.86.95.9]
7 16 ms 27 ms 13 ms pos-1-6-0-0-pe01.350ecermak.il.ibone.comcast.net
[68.86.87.130]
8 13 ms 11 ms 11 ms 66.208.228.202
9 12 ms 13 ms 12 ms 209.85.254.120
10 13 ms 14 ms 12 ms 72.14.237.133
11 24 ms 23 ms 23 ms 209.85.241.22
12 24 ms 23 ms 23 ms 216.239.43.217
13 23 ms 31 ms 35 ms 216.239.47.189
14 23 ms 25 ms 22 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

If you can then your name resolution should be OK.

When you first do an SSH do a "cat /etc/resolv.conf".

What does that show?

There should also be an option on your Cisco router to manually assign a DNS server(s). So what will happen is that when it resolves the DNS from DHCP then it'll just utilize what you have manually assigned. Typically the other side of your router also does DHCP to the ISP. There it gets an IP and DNS to the internet; your router just changes the IP via NAT to something usable inside of your network; like maybe the gateway address.

[ddichiera]

Ok, here's what I found out since my last post.

The resolv.conf file is being overwritten by the OS based on the data in the Settings>About screen which in itself can be changed from Settings>Network>Edit>Advanced screen.

You have to change DHCP to off to activate the option for DNS server.

I took one of the Jogglers with me to work and can now see that it has the external DNS servers listed for both primary and secondary whereas the Joggler at home had my router as the first dns server [192.168.1.1] and initially nothing for the second.

Setting the secondary to the external address got some things working, but not all. Weather and News widgets worked, but BBC Iplayer didn't.

When I get home, I'll try and change the primary to the external address and see how that goes.

[pete]

Good News there!

Addicting these Jogglers eh?

[ddichiera]

That works.

Put both primary and secondary DNS servers manually and all seems to have come good.

Iplayer now works (BBC Live), the Opera icons have re-appeared, as has the Screen Off icon.

Now to update Squeezeplay before hitting the sack.

[pete]

While looking at your home configuration you may want to address (pun here) changing your subnet to something smaller at home. Maybe creating a section of just static IPs and making the DHCP scope a little bit smaller. Here my DHCP scope is really small; IE: just 5-6 clients with the rest of the network using static addressing.

[ddichiera]

Thanks for that tip, I'll look into it, and thanks to everyone for their help.

I have a few other queries, so I'll post a new thread.

Cheers,
Dominic