Packet Capture Suggestion
-
Any chance we could see a count of the packets captured on the Packet Capture page, while a capture is taking place.
I'm trying to figure out where SSDP / IGMP are coming from, I've bridged LAN (Ethernet) & OPT1 (WiFi) to OPT99 and I'm occasionally seeing packets from 169.254.179.31 (local link) to 239.255.255.250 being blocked on OPT1 & OPT99.
-
Device found, my Apple Timecapsule
-
It might be possible to do that, but tricky. The way tcpdump outputs the packet count I could see that being hard to capture in a way that the GUI could display while also running in the background. Possible, but non-trivial.
-
On a side note, you have 3 interfaces bridged because you like slow traffic and think switches are the devil?
-
I don't have extra space for an additional switch in the current router location and I'd rather not route between wifi & ethernet.
I've got a power line 1200 connected to the LAN port, feeding my NAS & AV equipment the other side of the room & elsewhere in the house.
The OPT1 is connected to the timecapsule, if I reboot the timecapsule I don't hose my AV connectivity just the WiFi.
I'm aware of the issues bridging, I don't think switches are the devil, been dealing with Cisco routers & switches for over 20 years with a company who's HQ was in your home town, I'm over the pond. :)
Plus we don't have gig broadband here >:(
-
"I don't have extra space for an additional switch"
You do understand switches are tiny these days right ;) Not talking a cisco nexus 7k ;)
A 5 port smart switch for under $40 takes up nothing 94x100x27mm pretty freaking tiny.. That's like 4x4x1 you don't have space for something like that?
As to putting wifi and lan same layer 2 - lets agree to disagree here.. They really should not be on the same network - for what reason should they be? So your guests and your devices that use wifi all same network. IoT as well?
-
As to putting wifi and lan same layer 2 - lets agree to disagree here.. They really should not be on the same network - for what reason should they be? So your guests and your devices that use wifi all same network. IoT as well?
It's terribly convenient in many cases. It makes things like chromecast, printing, and other AV/file sharing much simpler. Sure, most of that can be isolated and done in a separate subnet, but there is a good case for bridging wireless in some cases. Particularly in homes. In businesses, not so much.
I'm spoiled having a UAP at home, I have an SSID in my LAN, and a couple other isolated SSIDs for testing and guests that land in other VLANs.
-
And when ever has convenience been in line with secure ;) heheh Just saying..
If you want your wifi on the same layer 2 as some other devices then ok - plug your AP into that layer 2 network. Or you have an I would agree with get a real AP that allows you to put your different wifi networks on whatever network you want via a vlan.
My normal wifi network that "my" devices auth to with eap-tls are on the same layer 2 as my printer sure for ease of airprint.. It could be done with something like avhai. But all of my devices that are on my normal wired network have no issues with pointing to a printer via its IP. Its only stupid devices like ipads and phones and their users that might have issues with setting up the printer. So better to put those specific device together on the same layer 2 then to just use 1 big flat layer 2 with all wifi and wired and guest wifi, etc. all on the same layer 2.
Maybe my tinfoil hat is a bit too tight, but I sure don't want my guests having access to my devices be it a printer or chromecast, etc. etc. Shoot I don't even let "guests" use pfsense for dns ;) They are "guests" they can use the internet, and I will let them ping their gateway but other than that I don't want any of their traffic on any of my other networks.
-
As to putting wifi and lan same layer 2 - lets agree to disagree here.. They really should not be on the same network - for what reason should they be? So your guests and your devices that use wifi all same network. IoT as well?
It's terribly convenient in many cases. It makes things like chromecast, printing, and other AV/file sharing much simpler. Sure, most of that can be isolated and done in a separate subnet, but there is a good case for bridging wireless in some cases. Particularly in homes. In businesses, not so much.
I'm spoiled having a UAP at home, I have an SSID in my LAN, and a couple other isolated SSIDs for testing and guests that land in other VLANs.
Yup the problem I had when I put the WiFi on it's own subnet I broke UPnP/DNLA for the WiFi devices.
Managed to remove the bridge by a moving some of the other device to other rooms and connected the LAN port to a LAN port on the Timecapsule.
