fryfrog
02-23-2002, 06:44 AM
i cvs'd and compiled the most recent version of showeq this morning. well, i then ran it when i got home and low and behold it wasn't sniffing a single packet. after troubleshooting a bit, i found that for some reason it was sniffing 10.0.0.1. i THEN found that is what i had in my showeq.conf file. i have a script that was starting it like this: but after this cvs, it seems to have started ignoring the ip specified on command line.
./showeq -i eth0 10.0.0.10
i then rand ./showeq --help and found that i could also use the following to force a certain ip at startup.
./showeq -i eth0 --ip-address=10.0.0.10
this works fine, so if you have the same problem i did... you can fix it if you have read this post!
./showeq -i eth0 10.0.0.10
i then rand ./showeq --help and found that i could also use the following to force a certain ip at startup.
./showeq -i eth0 --ip-address=10.0.0.10
this works fine, so if you have the same problem i did... you can fix it if you have read this post!