I am SOOO close - ping router, but no internet

[MrDuck]

Howdy!

I'm not a noob to Linux, but I've just tried out Knoppix for the first time...on an Apple Mac Mini (Intel DuoCore). Boots and runs fine from CD. However, I cannot get the networking right. I can get eth1 "active", I can ping myself, I can ping my DSL's router, but I cannot get to the internet in general. (Cannot open a browser window to a site, or even PING a site like www.cnn.com.) I know I'm close, I even tried following a FAQ, I show the loopback and my local address of 192.168.1.40. The router is 192.168.1.1. I just can't get PAST the router.

So I know I'm VERY close, I just need a little push. Any suggestions?

TIA.

MrDuck

:mrgreen:

[Harry Kuhman]

Can you ping knoppix.net ? If not, can you ping 72.232.180.133 ? If the first fails but the second works, you have a DNS issue.

Posting the result of ifconfig might help. Also, you might try to do a netcardconfig , assuming you understand what values to use. What make and model router? Is the firmware flashed to the most recent version available?

[MrDuck]

I'll have to boot back over to Knoppix later to get some of the other answers, but:

1) I cannot ping knoppix.net.
2) I don't know yet if I can ping 723.232.180.133, I'll have to try that.
3) The router is a Westell Model 327W supplied through Verizon, that runs perfectly right now (I'm posting this reply to you now from booting back over to Mac OS X). It connects fine and automatically through the supplied Mac OS X and connects 3 other computers in the house right now (3 Windows PC's).

That's why I'm saying I'm so close. I just cannot figure how to tell Knoppix "to go look" beyond the router for the net.

I'll boot back over to Knoppix and reply back.

But thank you for the VERY quick reply!


MrDuck

[MrDuck]

Okay, I'm back from booting over to Knoppix.

1) I CANNOT ping knoppix.net.
2) I CAN ping 72.232.180.133.

So that basically means I have "a DNS issue". ifconfig shows my eth1 information and my loopback information.

Tried netcardconfig both DHCP auto, and by trying it manually, local IP 192.168.1.40, mask 255.255.240.0, gateway IP is 192.168.1.1, and nameservers I've tried both 192.168.1.1 (default) and 208.67.222.222 208.67.220.220 (OpenDNS dns servers), no difference.

I can still ping addresses, but not by name.

I'm going to be off for the next five hours, I'll be back after that. But again, thank you VERY much for your prompt response!!!


MrDuck

[Harry Kuhman]

.... local IP 192.168.1.40, mask 255.255.240.0, gateway IP is 192.168.1.1, and nameservers I've tried both 192.168.1.1 (default) and 208.67.222.222 208.67.220.220 (OpenDNS dns servers), no difference.
Yup, some sort of DNS issue.

I don't know that router, but I have seen an old Belkin router that would DHCP fine with Windows but not with Linux. It was a router issue, not a Linux issue. I have also seen reports here of problems with DNS servers and ipv6 vs. ipv4, but since you have tried using both the gateway as a DNS server and some open DNS servers I doubt that is your issue.

I quoted the above because it doesn't look right. I don't know that router, but does it really support 4094 devices (4096 addresses based on the mask)? Most home devices support far fewer, 256 addresses or less. If it's correct then great, but if it's wrong it would throw off ARP pretty bad.

By the way, you should be able to get to this site by putting the above ip address in a browser. More interesting than just pinging it. But you'll still want DNS services working.

Good Luck.

[MrDuck]

Harry,

For some reason, this morning, everything works now. I feel sorry that I had to bug you a few hours ago. It all configured itself without an issue, I didn't have to run netcardconfig or anything. I opened up a terminal window and was able to ping both knoppix.net and the IP address. So I went to a browser and everything works like it should.

But for your info, here's what ifconfig looks like at the moment:


ath0 Link encap:Ethernet HWaddr 00:16:CB:BA:6E:5A
inet addr:10.0.1.2 Bcast:255.255.255.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:576 Metric:1
RX packets:11 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2223 (2.1 KiB) TX bytes:2053 (2.0 KiB)

eth1 Link encap:Ethernet HWaddr 00:16:CB:A4:EE:8B
inet addr:192.168.1.40 Bcast:255.255.255.255 Mask:255.255.255.0
inet6 addr: fe80::216:cbff:fea4:ee8b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4323 errors:0 dropped:0 overruns:0 frame:0
TX packets:5103 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2419383 (2.3 MiB) TX bytes:898397 (877.3 KiB)
Interrupt:17

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:41 errors:0 dropped:0 overruns:0 frame:0

Just for your information. Thanks for your help, but I don't know how it "fixed itself".


MrDuck

[Harry Kuhman]

Thanks for your help, but I don't know how it "fixed itself".
We have, on rare occasions, seen routers give unexpected results when the previous OS didn't give up it's lease when shutting down. I don't know the full cause or the proper technical fix, but powering down or even resetting the router sometimes fixes things like this, just in case it keeps happening.