can not conect to linksys router

[ranmaaaron]

i have a Linksys wirelsee accesspoint router with 4 port switch all conectons talked about are wired in the switch. the model number of the router is befw11s4

i am trying to my router with both a dell and an emachines computer both do not conect while using knoppix the dell is a dimension 8200 using a cnet pro 200wl fast ethernet adapter and the emachines uses an nvidian force networking controller

i get no internet so i have no clue what to do while in linux any help would be great.

I am vary new to linux just got it this week.

[Harry Kuhman]

We need the output of ifconfig. Also, try running netcardconfig and say yes to the dhcp question and tell us what happens. Do this for each computer. And I'm assuming that you don't have dhcp disabled in the router or have any strange security feature like MAC address filtering turned on.

[ranmaaaron]

here is the output from ifconfig


knoppix@1[knoppix]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:17:79:D4:8F
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::216:17ff:fe79:d48f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1890 (1.8 KiB) TX bytes:1920 (1.8 KiB)
Interrupt:5 Base address:0xa000

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:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:700 (700.0 b) TX bytes:700 (700.0 b)

knoppix@1[knoppix]$


and the dhcp failed

[ranmaaaron]

my router's ip is 192.168.1.1 also

[Harry Kuhman]

and the dhcp failed
Why do you say it failed? It looks like you have a good dhcp setup to me. Or did you manually make these settings?

What does "I get no Internet" mean?

What error messages do you get (exact words)?

I'm wondering if you have an ip6/ip4 type problem as has recently been discussed in another thread. But there is still too little information to diagnose what is happening. Can you ping the router? Can you ping 72.36.188.40 ? Can you ping knoppix.net?

[ranmaaaron]

ok to clear things up a bit i was trying to state that i only have internet while in windows not i linux.
now here is a ifconfig before i run the network card config


knoppix@1[knoppix]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:17:79:D4:8F
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::216:17ff:fe79:d48f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2201 (2.1 KiB) TX bytes:1990 (1.9 KiB)
Interrupt:5 Base address:0xa000

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:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:700 (700.0 b) TX bytes:700 (700.0 b)

knoppix@1[knoppix]$

once i try to do the netcard config i get this message


Sending DHCP broadcast from device eth0 operation failed.
failed.
Hit return to exit.

after the netcard config i try ifconfig again and get this


knoppix@1[knoppix]$ ifconfig
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:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:800 (800.0 b) TX bytes:800 (800.0 b)

knoppix@1[knoppix]$

[ranmaaaron]

oops for got to ping ill do that her in a min

[ranmaaaron]

ok here is the ping resolts for each on you sugested

router


knoppix@1[knoppix]$ ping -c5 168.192.1.1
PING 168.192.1.1 (168.192.1.1) 56(84) bytes of data.
From 192.168.1.101 icmp_seq=2 Destination Host Unreachable
From 192.168.1.101 icmp_seq=3 Destination Host Unreachable
From 192.168.1.101 icmp_seq=4 Destination Host Unreachable
From 192.168.1.101 icmp_seq=5 Destination Host Unreachable

--- 168.192.1.1 ping statistics ---
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4000ms
, pipe 3
knoppix@1[knoppix]$

72.36.189.40


knoppix@1[knoppix]$ ping -c5 72.36.189.40
PING 72.36.189.40 (72.36.189.40) 56(84) bytes of data.
From 192.168.1.101 icmp_seq=2 Destination Host Unreachable
From 192.168.1.101 icmp_seq=3 Destination Host Unreachable
From 192.168.1.101 icmp_seq=4 Destination Host Unreachable
From 192.168.1.101 icmp_seq=5 Destination Host Unreachable

--- 72.36.189.40 ping statistics ---
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3999ms
, pipe 3
knoppix@1[knoppix]$

knoppix.net


knoppix@1[knoppix]$ ping -c5 knoppix.net
ping: unknown host knoppix.net
knoppix@1[knoppix]$

[Harry Kuhman]

I'm at a huge loss to understand what is going on here. Normally what one sees when booting Knoppix on a computer attached to a router is that during the boot process Knoppix does a DCP discovery with the router and gets assigned a local IP address in the same IP range as the router, and has the broadcast address, Domain Name Sever and network mask set. From there they can access the Internet as soon as the boot process finsihes, no setup at all needed.

The thing is, you show that your system (at least one of them) is assigned 192.168.1.101, the broadcast address and the network mask are right. This isn't something that Knoppix ever does on it's own, this information must be coming from the router by DHCP. I'm not at all clear on why you couldn't access the Internet at that point, although we had seem some setup issues that deal with DNS servers that apparently don't treat IP6 properly. But then you do another DHCP setup by running netcardconfig and somehow the system no longer can recognize it's ethernet connection. That's a huge mystery to me and I can't make any sense of it.

Nor can I understand the ping to the router at 192.168.0.1 failing. I had expected the ping to knoppix.net to fail and the ping to the IP address here to work, but I didn't expect there would be any problem pinging the router, I just put that in because it's a logical first step in testing. Once that ping failed the others were sure to, but why it failed is strange.

I'm guessing that you tried the pings after trying the manual netcardconfig. And at that point, for some strange reason, the system no longer thinks it has an ethernet interface. The first test I would suggest is, if I'm correct above, trying the ping to the router right after rebooting, before trying a netcardconfig. You can do an ifconfig first, and that should confirm that the eth0 interface is still functional and that the computer has been assigned an IP address from the Linksys, but don't force a DHCP setup before doing the ping.

I also would suggest making sure that you try all of this from both systems and reporting the result from each.

As I said before, I would also check all of the settings of the router to be sure that there were no "security" features enabled that might muck you up, such as MAC filtering or IP address filtering.

We have on more than one occasion seen a router get into a strange state and do very unexpected things. I can't quite explain the eth0 vanishing from your ifconfig if that's what is happening, but it would be wise to try this:
Power down all computers, leave the CD in the disk drive.
Cycle power on the Linksys, give it a minute to fully restart.
Boot a computer directly into Knoppix without lettiing Windows boot first.
Try the ping test again.
And just to be sure, we are talking about Knoppix running from CD or DVD, right? You're not one of those who thinks it can be installed and then fails to mention that, are you?

[ranmaaaron]

no i am runing all test from the cd i have done a poor mans install on the dell but all test so far have been from the emachines
i also tested to see if i can get a conection directly form the cable modem i was able to access web pages for about a min then i could get no pages to come up if that helps any i will try you others tests and post what i get.
edit
also i had to restart to do the ping test becase i forgot so that is from start up.

[ranmaaaron]

did the ping test this time from the dell after powercycling the router and shuting down all computer and still got this for the ping


knoppix@1[knoppix]$ ping -c5 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.101 icmp_seq=2 Destination Host Unreachable
From 192.168.1.101 icmp_seq=3 Destination Host Unreachable
From 192.168.1.101 icmp_seq=4 Destination Host Unreachable
From 192.168.1.101 icmp_seq=5 Destination Host Unreachable

--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4003ms
, pipe 3
knoppix@1[knoppix]$

will test the the network card config again on the dell now after restart.

[ranmaaaron]

doing what i did before with the net card config i got the same thing this time with the dell. i get this


knoppix@1[knoppix]$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:80:AD:77:F8:7C
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::280:adff:fe77:f87c/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:5 dropped:0 overruns:0 carrier:5
collisions:0 txqueuelen:1000
RX bytes:1890 (1.8 KiB) TX bytes:300 (300.0 b)
Interrupt:18 Base address:0xe800

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:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:700 (700.0 b) TX bytes:700 (700.0 b)

knoppix@1[knoppix]$

then the failed message from the dhcp broadcast and ifconfig give me this


knoppix@1[knoppix]$ ifconfig
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:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:700 (700.0 b) TX bytes:700 (700.0 b)

knoppix@1[knoppix]$

[ranmaaaron]

it seem the knoppix does not like my networkcards because if i conect direct to the router i can conect for about one webpage then if i do an ifconfig i drops my eth0 for some reason if any knows why this is and how to bypass it it would be great if there is none then thanks all for your help.

[Harry Kuhman]

it seem the knoppix does not like my networkcards.....
No, I don't believe that's it, I'm using a CNET PRO200WC PCI FastEthernet Adapter and have no problems with it. Of course, card makers are famous for slip-streaming different chipsets into cards so I can't say with 100% certainty that it's not your NICs, but to see this with two different brand of NICs, both presumably simple 10/100 basic NICs, makes this extremely unlikely to be the issue.

I'm at a real loss to explain why the DHCP setup at first works though and then later you don't show an eth0 interface in ifconfig. This is completely in conflict with no only my experience but with everything else I've seem people here report about networking under Knoppix in the last three years.

[ranmaaaron]

is there any way to change the mac address that knoppix uses because i know that my isp will only alow one mac address out and i read in another post that it is posible but not common for knoppix to change the mac address by it self.

[Harry Kuhman]

is there any way to change the mac address that knoppix uses because i know that my isp will only alow one mac address out and i read in another post that it is posible but not common for knoppix to change the mac address by it self.
The MAC address is dtermined by a EEROM on the NIC, all NICs are made with a unique MAC addres. Knoppix should be using the exact same MAC address as when the same NIC is used under windows. There was one report a couple of years ago where this was said to not happen, but I've never seen it fail to work properly myself, particularly on my CNet NIC.

To answer your question, yes, Linux (and Knoppix) can tell the stack to use a different MAC address than what is assigned to the NIC by the EEROM. I'm not sure of the exact command to use to do it though, but you should be able to find it with a little searching on Google faster than waiting for someone to give it to you here.

But if, as I have speculated, there is a router built into your modem, then the ISP only sees the MAC address of the router, not of any of your computers. MAC addresses are not routable across the Internet, they apply only to the local network and are stopped at the first router. If you have determined that the modem does not include a router then something really nasty is going on. Maybe you ISP is doing NAT on his end and giving you a non-routable IP address. That would not be good, it would greatly limit what you could do with your Internet connection. But it really doesn't look like that is happening in your case.

[ranmaaaron]

Update Ok I finaly got the time to download knoppix 4.0.2 i am able to conect to the internet and my router with this verson i have no idea what would make a diference but obvisly some thing is diffrent some one may want to look in to this. i am fine for now using the older verson as it works about the same.

[Ironfighter]

It seems I am having the same problem as you (see me post of a couple of days ago) - same symptons exactly. I can reach the internet from Knoppix 4.0.2 Live CD but not from Knoppix 5.0.1 Live DVD. Doesn't it bug you? :(