Im using a DELL Latitude D600, and I was able to get the broadcom wireless networking card to work. I can connect through the wireless network at school, and it works great!

My problem happens when I want to switch to another interface. Ill run "ifconfig eth1 down" (eth1 is the name of my wireless interface) and then run "ifconfig eth0 up" (eth0 is my ethernet interface). Then I do a dhcp refresh on eth0 and Im using my ethernet connection.

For some reason, after a little while, eth1 (wireless) is brought up again automatically. So both interfaces will be going, but my connection seems to default to the wireless. This is a problem, because I need to log into the school network to use wireless. No login, no connection. So when the wireless comes up, anything Im doing network related through ethernet just seems to die.

Is anyone else finding that there wireless interface is coming up automatically? Is there anyway t o prevent this?

- Mike

Hmmm, I got a belkin card that uses the broadcom 94306 chipset but doesnt seem to have issues with coming up on its own. Perhaps these things have finally become self-aware?
I can only assume its a process calling the eth1 interface at given intervals. Possibilities include (I'm just guessing here) time server, mail program, pretty much anything that uses the 'net. I'm surprised it has the ability to call ifconfig up but there we are. Thats where I'd start looking anyway.
Regards
Chris

Ill do some exploring in the startup scripts..

I wonder what would be ifconfig eth1 up??

Thanks for the help!

- Mike

Check your services. I think it might be Samba..... If you have SWAT then use that to check the interface used.