Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I was trying to troubleshoot a connection problem I was having the other day. I was using wireshark from my wireless laptop, trying to see the packets my hardwired desktop was putting out. However, when I was connected via wifi, I couldn't see the traffic going through the router unless it was from my own laptop. When I connected it through a rj-45 cable, I could. Is it suppose to be like that?
I may be wrong, but I don't believe most wireless drivers allow you to place the wireless NIC into promiscuous mode. That would account for you not being able to see any packets that weren’t meant for your system.
Ethernet switches do NOT replicate all traffic on all ports, otherwise we would all still be using Hubs.
The only thing you should see when sniffing a switched network is brodcast traffic, unless you enable a SPAN port on the switch.
dsniff might work from your wireless connection however to sniff that traffic. It can be used to sniff switched network traffic...
Ethernet switches do NOT replicate all traffic on all ports, otherwise we would all still be using Hubs.
The only thing you should see when sniffing a switched network is brodcast traffic, unless you enable a SPAN port on the switch.
dsniff might work from your wireless connection however to sniff that traffic. It can be used to sniff switched network traffic...
Keep in mind that hubs are still being manufactured and used.
I use a hub on my LAN and I use it specifically to monitor my Windows hosts. I'm not about to go out and buy an expensive piece of equipment that has a SPAN port when I can use a hub.
Also, ethernet taps usually work OK, also. In fact, they work better than hubs, since you don't have to worry about throughput degradation as much (although it theoretically won't matter to someone with a cable connection...but I've FIOS ).
When I compiled my wifi drivers I included the ability to go into 'monitor' mode, however when you are in monitor mode, I don't know if you can limit it to one network and an encrypted one at that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.