Author
Topic: internet unreachable by core/hybrid (Read 3109 times)

INTRODUCTION=========Howdy folks! -- I'm in about 3 months since my real interest in LinuxMCE; lots of research reading all your comments and watching the video over and over before I committed to get started. It's had its rough spots so far including multiple incompatible capture cards and IR remotes and gyro remote, getting a couple VAIO jukes over e-bay, and adding an additional SATA TB drive (I'll be writing an article on that later). I'm still hopeful that it'll all turn out in the end. I'm hopeful about getting it working and then helping friends do theirs; also hopeful for an iPhone 3G orbiter! This is my first post here. But enough of the introduction...

PROBLEM======Despite my best efforts, I cannot for the life of me get the core/hybrid itself to connect to the internet. The givens:

--2 NICs (one external, one internal);--DHCP at DSL router is ON. I allow wireless connections to the external network, --DHCP-enabled DSL router goes straight to the external NIC on MCE and provides a 192.168.0.x IP to eth0;--DHCP at LinuxMCE is ON. Devices hardwired to the internal hub get their 192.168.80.x from eth1 (192.168.80.1);--internal network does great; I attach my Ubuntu Hardy lappy to an internal hub and I can get to the Net fine.--external network does great; I attach my WinXP lappy over wireless and reach the Net fine.

!! But, no Internet directly from the core/hybrid.

--on install eth1 was external and eth0 was internal, I used the UI to switch these and their cables.

I reverified all network settings from KDE and it makes me wonder if I have to do some kind of core/hybrid configuration so that its own apps do some kind of BIND TO ALL NICs or something?

Konqueror browser shows google.com, but chokes on cnn.com. cnn.com shows looking up address, then connecting to server, but never gets there. I think I'm very close now. Aha! sudo /etc/init.d/networking restart yielded the following:DHCPRELEASE on eth0 to 192.168.0.1 port 67There is already a pid file /var/run/dhclient.eth0.pid with pid 134519120I can get to cnn.com now, but not other addresses. Weird!I can reach linuxmce.org, but not others. I don't get it.

SOLUTION========See below for the process to reach this solution, but I had to "hard code" the ip address:-- From the orbiter, advanced>kde desktop.-- Then from the "K" menu at lower left, choose System Settings.-- In kubuntu>system settings>network settings.-- switch to administrator mode (at bottom) and enter your linuxmce password from installation.-- Select the eth0 from the list and click [configure interface].-- Switch from Automatic to Manual and OK.-- Under the Domain Name Server list, moved the main DSL modem's address (in my environment 192.168.0.1) to the second position in the list. The first position shows the ISP's primary nameserver.

From a shell on your core (not on your internal or externally connected PCs)

Ping google.com

Does it resolve to an IP address? Yes - then your core is able to access your router for DNS, so that's good! No - troubleshoot the interactions between core and router, as if DNS isn't getting through, then....

Does it actually ping after resolving? No - try traceroute and see where it stops...

Take a look at the routes on the core as well - but assuming if your internal devices are getting through then this should be fine.

Oh, also check that arp is working between core and router - if it is trying to ARP the DNS server on your router and it can't convert IP to MAC then it won't be able to get any further even though it can router perfectly fine (although that would seem to affect your internal network as well... worth checking)

Dave and Mark -- Thanks very much for your input. I tried some of this and believe I have a better idea now. My lack of knowledge of ubuntu networking and conf files is the biggest stumbling block right now.

Konqueror browser shows all of google.com, but chokes on cnn.com. cnn.com shows looking up address, then connecting to server, but never gets there. I think I'm very close now. Aha! sudo /etc/init.d/networking restart yielded the following:DHCPRELEASE on eth0 to 192.168.0.1 port 67There is already a pid file /var/run/dhclient.eth0.pid with pid 134519120I can get to cnn.com now, but not other addresses. Weird!I can reach linuxmce.org, but not others. I don't get it.

Domodude

nslookup cnn.comYou SHOULD get the ip address. It should certainly work for google.com, since you can ping it.If you do not get a good ip address, doublecheck if the DNS address is correct (should be your ISP DNS, or any other that you have access to).

If you have a working windows machine using the same router/ISP connection, check its DNS entry. Use that entry in LMCE, just use a manual configuration to test it all.

This may seem obvious, but I have this issue with my cable modem connection whenever I switch the box that is connected to it out. Unplug the cable modem for 30 seconds and plug it back in, mine has to have the connection refreshed whenever the MAC of the device it's connected to changes. For some reason DHCP on the cable modem gets hosed up and while it will work somewhat DNS gets really flakey and until the connection is refreshed I will continue to see strange issues. Give it a shot if you haven't already done so.

Ugh. Thanks to everyone for your ideas. I though I almost had it tonight. I compared a lappy on the external network to the eth0 DNS list on the core/hybrid, and realized that the secondary DNS entry on the core/hybrid was pointing at the secondary DNS for my ISP. Corrected it. I still have the DSL router listed first (192.168.0.1) and the ISP primary DNS listed second.

I also tried the DSL router power-bounce... no change.

Verified the MAC address in the client list on the DSL router's web portal for the core/hybrid. It's correct.

The core's default gateway is the DSL router (192.168.0.1) on eth0. I almost want to manually change it to the actual DSL gateway at the ISP to see what happens, but I know that won't do it.

I wonder if there is some kind of permissions issue for the linuxmce user

rodercot

Not sure if you did this but what network cards (codecs) are you using for the system more-so the eth0 nic controller and which driver is that nic using.

go to shell to the core (or ctl-alt-F2 at the core itself) and use ifconfig look for tx or rx errors or Frame Drops and then ethtool -i eth0 and then ethtool eth0 and post the reports here.

I change my router address to 192.168.1.1 not sure if it matters and the gateway at the core is the same but the DNS address for me never seem to propogate properly anyhow. My primary on the core usually is never the primary on the router and vice versa. It updates or should update this everytime the PPOE connection is refreshed and with mine that is usually once or twice per week.

Not sure if you mentioned this but what router are you using is it a modem/router or a modem wlan out to a router. Sorry if you mentioned this.

Not many Modem/Routers work right as a router but fine as a modem. I have a couple of Unlocked Speedstars for Bell and both of them have router features. I ended up turning off the router features and using the wlan port out to a Dlink 655 Gb wired and wireless. But do not go spending extra $$ just yet, let's look at those settings.

If you are getting inconsistent DNS lookups, then that can easily be because one DNS server is working/accessible and the other is not. The way the client chooses which one will determine whether your lookup works. Using NSLOOKUP is a client in its own right, so doesn't necessarily do the same thing as the Linux client and may confuse matters. Try configuring your core with only 1 DNS server (primary) either statically or be reconfiguring the DHCP settings on your DSL router. Make that DNS server your DSL router and test extensively. Then change it to your ISP and do the same thing (perhaps your router's statefulness on UDP packets is dodgey - that would cause the returning DNS answers to be blocked at the router). However, looking at your original problem, it looks to be more than just DNS....

Eliminate DNS using this method first, and doing lots of pings (as Zaerc pointed out, just look for the resolution, not the actual returning packets as most sites block ICMP packets, so ping doesn't work) - if one setting gives you reliable lookups, leave it at that and move onto the connectivity issue...

And late to the fray (thanks to colinjones), I tried removing the ISP as the secondary last night, and everything broke. No more Net connectivity from Internal at all. Will try removing the DSL modem as primary after I post this; will modify with my results shortly.

Thanks again for your support. I am encouraged by your additional recommendations. Be back shortly.

We're very close now. Removed the DSL modem and forced manual/static on external from the kubuntu system settings>network settings panel. If left on dhcp, the networking restart repopulated the 192.168.0.1 as primary, so I had to switch to static. Now, how can I make this workable?

-- From 192.168.0.9 (external lappy), I still want to ssh in to the server, so don't want to disable dhcp on the dsl modem.-- going to set "static" assignment of ip to core/router to the mac address.-- answering my own question, i've re-added the dsl modem to the now static configuration kubuntu for eth0, but as a _secondary_ dns. still works.

WHOOPS. The MAC authentication I remembered in the DSL modem webadmin is for wireless access allow/deny only. I'll have to set up a static routing, but don't know how to do that. Will do a bit of research to see if that is the answer. Is that how to avoid switching the kubuntu ip if the modem assigns a different ip?

rodercot

You should not be port forwarding port 22. It should be a core input not a port forward. Also your core should Be seeing TWO DNS addresses from the router/modem not one gateway and one DNS. That is likely your problem. My router sends three all the time when connected to PPOE. I am telling you use that modem as a modem and get a router only - The D-link under 90$ now works out of the box other than some simple setup. But make sure you can shut off the router portion in that modem.

your port 22 line should be TCP - 22 to 22 no port /no ip / core input then add. right now you are opening port 22 and then telling it to forward port 22 to the internal lan.

I have to agree with Thom and why this is so hard to setup up i am not sure. but I was here not too long ago so we'll see ya through this.

OOPS I did not see colin post, I would not try and set anything manually. I tried that with mine and no dice. It should be simple though.

ADSL - Modem/Router - PPOE/or connected all the time (DNS addresses resolved at the modem DHCP clients set on subnet 255.255.255.0 on gateway address 192.168 0 or 1. 1. Dhcp client list in the router, I make this only as many as I need) I have 10 open spots. I force the core to 192.168.1.100 from the router (not really force I just reserve that address to the core's mac address) - Then the core - Get IP address automatically eth0, it does and sets up eth1 at 80.1.

Have you checked the DHCP client listing in your modem as well. the core will setup a client named Ubuntu upon install but should change to dcerouter upon completion and reboot. Sometimes it does not.