Avahi causes a ton of ping chatter
-
Who's who ?
192.168.4.24 - 192.168.4.23 - 192.168.1.30 - 192.168.4.91
edit :
I'm using Avahi on my LANs.
I've 'packet captured' ICMP for a minute or two.
Found nothing. -
@gertjan: You are right. I should have clarified.
192.168.1.130: IKEA Trådfri Gateway trying to establish an internet connection
192.168.4.23, 192.168.4.24, 192.168.4.91: Linksys Velop APsI guess, you don’t have Linksys Velops.
-
I'm guessing its down to the inbuilt Homekit support.
AVAHI traffic would be multicast.
https://www.linksys.com/gb/support-article?articleNum=316767#H01
FWIW I gave up trying to get AVAHI to work and plonked all my IOT type stuff on the same IOT vlan.
-
@dominikhoffmann said in Avahi causes a ton of ping chatter:
I guess, you don’t have Linksys Velops.
Dono what 'velop' is.
I do have a boatload of WRT54GS and other E1200 'Linksys' (or Cisco now ?) devices.
The 'WRT54GS ' are ancient, I know, but as I have just 20 Mbit/sec to share they do the job just fine.Actually, @home and @work : I guess I've no 'IOT' devices.
I use AVAHI just so from one LAN, 192.168.2.0/24 users (visitors) can find and use printers on another LAN 192.168.1.0/24. This works.
I don't share doorbells and other web cams - type devices.edit : wait : I ditched the Linksys firmware for a DDWRT version.
-
@gertjan: The Linksys Velop system is a home mesh network router package:
https://www.linksys.com/us/c/whole-home-mesh-wifi/
Linksys is now a Belkin company.
-
@dominikhoffmann said in Avahi causes a ton of ping chatter:
https://www.linksys.com/us/c/whole-home-mesh-wifi/
Yep, I saw them as I threw 'velop' in Google ;)
Noop, never dealt with these kind of 'mesh toys'. I'm a cable man, me, with just one AP's on every end of the wire.@dominikhoffmann said in Avahi causes a ton of ping chatter:
Belkin .....
Hummmm, .....
-
Your the one bridging two different L3 networks are you not? That sort of config is broken from the get go.. So yeah prob all kinds of weird stuff going on.
If you want everything on the same L2, then they should be on the same L3.. If you want them on 2 different L3, then they should be on 2 different L2 networks.
If you then want some multicast discovery to work across this segmentation then avahi could be leveraged.
-
-
No you shouldn't do that.. Especially if your going to use different L3 networks.
Not unless your using the same L3 ie like a /16? as your mask..
What is the masks on these nettworks?
192.168.1.x is my wired LAN, and 192.168.4.x is my wireless LAN. Both are bridged together.
Generally speaking - bridge is always the WRONG answer.. your bridging a tun and a tap interface??
-
@johnpoz: That configuration is obviously based on my incomplete understanding of subnets and bridging. I’d be most grateful, if you could recommend specific changes I should make.
-
What are you trying to accomplish exactly.. Why do you think you should bridge all your networks together?
Why are you trying to use a tap vpn connection? The only point to such a setup would before allowing for L2 discovery.. Ie broadcast and multicast? Why would you want/need that?
Do you want to control traffic between your wireless network and your lan?
