Stange network issue (probably easy for the gurus)

beakmyn · 02-24-2005

While I don't believe the issue is directly related to the lastest Kismet dev it serves as a way to 'see' the problem.

I boot FC2 and the service startups are going by and I see:

Code:

Brining up interface eth0 pcnet_cs device eth0 
does not seem to be present, delaying initializaion

I've had two cards in this machine one is Netgear Fast Ethernet PCMCIA and the other is my Orinoco. I'm guessing it's thinking eth0 is the Netgear card and it's trying to start it. Except its not there hence the delay.

Then I figure I go and run Kismet and at about 45 seconds in I get the following error

Code:

 eth0 error -5 transmitting packet

The message just fills the screen. I then have to quit kismet wait and then restart it. I assume it's because Linux is trying to re-initialize the card that it incorrectly thinks is the Netgear. After restarting Kismet things seem to be ok.

My question is, are my above assumptions correct? And if they are how to I keep the Network service (I'm assuming it's the Network service) from trying to start eth0?

So, another assumption. If I setup the Network service (using chkconfig) to only start in runlevel 5 will I be ok? I always wardrive in level 3 (console only) and then if I need internet I start up X (which I believe puts me into runlevel 5).

renderman · 02-24-2005

run dmesg and double check that eth0 is the wifi card and that eth1 is the netgear. If not, adjust commands accordingly

Unless, that is, I'm over simplifying the problem

beakmyn · 02-24-2005

I physically have only one card installed at a time. The Netgear tends to run real warm and when I'm wardriving there's no need for the wired card.

Well it seems that the Network service wants to start eth0 in dhcp and it thinks eth0 is going to be the Netgear card. So, I'll make it happy and leave both cards always plugged in. It takes a few seconds longer to boot but at least it's happy now.

02-24-2005	#1 (permalink)
beakmyn root\.workspace\.garbage. Join Date: Aug 2003 Posts: 4,805	Stange network issue (probably easy for the gurus) While I don't believe the issue is directly related to the lastest Kismet dev it serves as a way to 'see' the problem. I boot FC2 and the service startups are going by and I see: Code: Brining up interface eth0 pcnet_cs device eth0 does not seem to be present, delaying initializaion I've had two cards in this machine one is Netgear Fast Ethernet PCMCIA and the other is my Orinoco. I'm guessing it's thinking eth0 is the Netgear card and it's trying to start it. Except its not there hence the delay. Then I figure I go and run Kismet and at about 45 seconds in I get the following error Code: eth0 error -5 transmitting packet The message just fills the screen. I then have to quit kismet wait and then restart it. I assume it's because Linux is trying to re-initialize the card that it incorrectly thinks is the Netgear. After restarting Kismet things seem to be ok. My question is, are my above assumptions correct? And if they are how to I keep the Network service (I'm assuming it's the Network service) from trying to start eth0? So, another assumption. If I setup the Network service (using chkconfig) to only start in runlevel 5 will I be ok? I always wardrive in level 3 (console only) and then if I need internet I start up X (which I believe puts me into runlevel 5). __________________ Daughter with arms inside shirt: "Daddy I'm not Armish" ┌──────────────────────────────┐ ╞ NS Icons Explained\|et hoc genus omne ╡ └──────────────────────────────┘

02-24-2005	#2 (permalink)
renderman Drunken Stumbler Join Date: Jun 2002 Location: Anywhere but Utah Posts: 1,803	run dmesg and double check that eth0 is the wifi card and that eth1 is the netgear. If not, adjust commands accordingly Unless, that is, I'm over simplifying the problem __________________ Never drink anything larger than your head! Scaramental Wine Taster for the Church Of WiFi Buy our books! "I reject your reality, and substitute my own!" – Adam Savage CoWF WPA Hash Tables

02-24-2005	#3 (permalink)
beakmyn root\.workspace\.garbage. Join Date: Aug 2003 Posts: 4,805	I physically have only one card installed at a time. The Netgear tends to run real warm and when I'm wardriving there's no need for the wired card. Well it seems that the Network service wants to start eth0 in dhcp and it thinks eth0 is going to be the Netgear card. So, I'll make it happy and leave both cards always plugged in. It takes a few seconds longer to boot but at least it's happy now. __________________ Daughter with arms inside shirt: "Daddy I'm not Armish" ┌──────────────────────────────┐ ╞ NS Icons Explained\|et hoc genus omne ╡ └──────────────────────────────┘ Last edited by beakmyn : 02-25-2005 at 07:55 AM.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode