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).