Ethereal does not detect my modem!

knightofnee1112 · Post by **knightofnee1112** » Sat Apr 26, 2003 10:43 pm

I downloaded ethereal packet sniffer application and it only sees my VIA Tahoe nic. it doesn't detect my modem at all. I am still looking through all the documents on this application. how can i get it to use my modem?

thanks!

BillyGoat · Post by **BillyGoat** » Sat Apr 26, 2003 10:59 pm

why would you be packet sniffing your modem, trying to record your own passwords going out? :-)
i use to have alot of fun with packet sniffers in college- i was a network lab aid :-)

knightofnee1112 · Post by **knightofnee1112** » Mon Apr 28, 2003 12:15 am

All i want is for the thing to disply packets that are going into my modem. not my nic. it for some reson, wont allow me to do that.

DocSilly · Post by **DocSilly** » Mon Apr 28, 2003 12:59 am

Is it under Windoze or Lunix ? Isn't there an option to point Ethereal to ppp0 for capturing your modem traffic ? (for da penguin)

knightofnee1112 · Post by **knightofnee1112** » Mon Apr 28, 2003 10:36 am

Sorry, I should have said what OS, for linux i'll just use tcpdump, I am tired of netstat for 2k, i downloaded ethereal for winblows.

DocSilly · Post by **DocSilly** » Mon Apr 28, 2003 11:31 am

> Is it possible to set Ethereal to capture packets from a modem card?

Only if you're running SLIP or PPP over the modem line, i.e. if you're using it for networking - and then it'll work only if the packet capture mechanism on your machine supports capturing on SLIP or PPP links. (For example, WinPcap on Windows NT/2000 doesn't support it.)

Q-6: Can I use WinPcap on a PPP connection?

A: We have tested WinPcap on PPP connections under Windows 95, Windows 98 and Windows ME. In Windows 95, due to a bug in NDIS, WinPcap sometimes resets the PPP connection. In Windows 98/ME this bug appears to be corrected, and WinPcap seems to receive correctly, however it is not able to send packets. Under Windows NT/2000/XP there are problems with the binding process, that prevent a protocol driver from working properly on the WAN adapter. The problem is caused by the PPP driver of WinNTx, ndiswan, that doesn't provide a standard interface to capture.

Snort also relies on the WinPcap for windows ... so that's also no go.