intel pro/100 ve & backtrack2. IP but no connection
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
route -n from my Suse 10 on the same lan has this extra line
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
>tail -f /var/log/messages . shows the card is up ok.
The card works ok with suse 10.2 , kubuntu & windoze thru dhcp .
>ping 192.168.0.1 - Destination host unreachable - I can see the router lights flashing , so the card and router are connected , same when I try through dhcp.
I disabled ipv6 in backtrack , no result.
I assigned a fixed ip in the router to the card & disabled dhcp,no result.
I'm completely stumped here , the router is netgear 834dg , BT kernel is 2.6.20-BT-Pwnsauce-NOSMP.
Can anyone give me some idea as to what to try next ?
1. iptables rules are as for new install.
"iptables-save" just returns me to the prompt.-where am I saving to ?
I think with backtrack the firewall is disabled by default , you have to bring it up manually.
2.Dhcp client is my router , configured to allocate addresses with dhcp. -This works ok on the same network card with suse10.2 & xp on this laptop.
3.I tried "dhcpcd eth0" before & after the command "ifconfig eth0 up"
I can see the light flashing on the router for a minute but it's not giving me an ip.
I'm going to try the backtrack live cd on my other box to see if it works with a d-link card.
Edit:
Tried the live cd & dhcp works during the loading of the kernel automatically -so the router works ok.
By “What dhcp client do you use?” I meant which program(s) have you used for a dhcp client. I see you already mentioned dhcpcd. Have you tried dhclient, pump, or udhcpc? Also, with dhcpcd, have you tried the “-d” flag (which should produce debugging output in syslog)? Also, is there any weird stuff in /etc/dhcpc/dhcpcd-eth0.cache?
I upgraded Linux Mint Bianca through the ubuntu repos to 7.04. All was well until the latest kernel upgrade to 2.6.20. Then I started to lose my wifi connection, getting brief "blips" of connectivity until it completely lost connection. Like you, I could detect the wireless access point/router, get an IP, but no data passing through.
This laptop (Dell 510m)using an intelpro 2100 card is on a dual boot with XP. I used xp to check the card. It worked fine. After a LOT of messing around, I did a clean install of the linux mint 2.2 Bianca. It now works perfectly again.
I haven't done anything to check it, but I immediately suspected that latest kernel.
In terms of kernel parameters to debug the situation further (to figure out if the problem actually is in the e100 module), you can use the e100’s debug parameter at module loading time. To do this, do something like “sudo modprobe -r e100” to remove the module, and then “sudo modprobe e100 debug=16”. This will give you extra debugging output in dmesg. Now you probably will want to use a number less than 16 (since it might give too much irrelevant output). The default is 3, so you might try experimenting with values in-between 3 and 16 until you get the kind of output you want.
P.S., I still think the problem is outside of the kernel, this is just another desperate attempt to find the problem.
thanks for the suggestions osor , I'll 'borrow' a usb stick tomorrow & put pump, dhclient etc on it & try them out.
I'll Post back when I got anything new .
I found a few bug reports with 2.6.20 kernel & this card (pro/100)with google , I'll be happier if I don't have to mess around changing kernels but if that's the only way to get it working ...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.