Keeps blocking
-
Are you using ipv6.
The default allow ipv6 rule would prevent the logging if changed to any as source. I think NogBad is correct in that the fe80 link local is what is flagging it to be dropped because it does not = the ipv6 net on your wlan interface?
Comes down to are you using ipv6 or not to the best way to remove this sort of noise from the logs.
-
Are you using ipv6.
The default allow ipv6 rule would prevent the logging if changed to any as source. I think NogBad is correct in that the fe80 link local is what is flagging it to be dropped because it does not = the ipv6 net on your wlan interface?
Comes down to are you using ipv6 or not to the best way to remove this sort of noise from the logs.
Apr 15 15:28:13 WLAN Default deny rule IPv6 (1000000105) [fe80::1885:465b:bf10:40b6]:5353 [ff02::fb]:5353 UDPI tried adding it to the allow but it still keeps hammering the logs (pulling my hairs out :( ).
I don't quit understand what you and @NogBad mean to say. Could you give and example or point out what I am not doing or doing wrong in my firewall rules to get rid of it.
-
your rule to dest ff02:fb should work other than your source is set o wlan net.. which is not what the source is fe80 is not wlan net. Set the source to any ipv6 on that rule and it should stop your log spam..
If you don't want to set any for the source, set it to the link local prefix FE80::/10
-
your rule to dest ff02:fb should work other than your source is set o wlan net.. which is not what the source is fe80 is not wlan net. Set the source to any ipv6 on that rule and it should stop your log spam..
If you don't want to set any for the source, set it to the link local prefix FE80::/10
That worked, your a lifesaver jhonpoz 2 thumbs up ;)
Apr 15 16:57:33 WLAN Default deny rule IPv6 (1000000105) [fe80::5c94:2cc1:5329:99c4]:546 [ff02::1:2]:547 UDPI looked at Wireshark and saw the mac address, looked at the DHCP server (as it serves IP on mac address) and found it to be a Labtop. Is there any other way I could have looked it up an easier way, preferably using pfSense and not Wireshark?
I still don't understand why WLAN as source did not work, could you point that out to me?
-
Because your wlan net is say 192.168.1/24 or whatever your IPv6 global network is you got from your ISP or HE tunnel you setup, etc.. say 2001:470:xxxx::/64
fe80::XXXX is not your IPv4 or your IPv6 network, its a link local address that does not fall under your "net" listings for your different interfaces.
You could of just done your sniff on pfsense for that dest port if you wanted to find the mac of what was sending it.. Just set the level to FULL and it would show you the mac in the output.
-
Because your wlan net is say 192.168.1/24 or whatever your IPv6 global network is you got from your ISP or HE tunnel you setup, etc.. say 2001:470:xxxx::/64
fe80::XXXX is not your IPv4 or your IPv6 network, its a link local address that does not fall under your "net" listings for your different interfaces.
You could of just done your sniff on pfsense for that dest port if you wanted to find the mac of what was sending it.. Just set the level to FULL and it would show you the mac in the output.
I'd missed that setting, were can I set it to Full?
-
In the packet capture settings when you do the capture… Its right there next to the start but - kind of have to be blind to miss it.
-
In the packet capture settings when you do the capture… Its right there next to the start but - kind of have to be blind to miss it.
LOL ;) Maybe Yesterday, I was not the sharpest knife in the drawer, but getting sharper by every post!
Could you advise on my rule-set, as I already have 3 rules now for multicast, I would like to catch all multicast ipv6 and ip4 addresses or is that not wise?
btw under advanced options should not be enabling Allow IP options not be a thing?
-
pfsense is not going to do anything with multicast unless your running the igmp proxy?
If you do not want to see the log of such noise its almost easier to just turn off default logging and create the rules to log the traffic you want to see. Say tcp syn only packets.
You could combine those 3 rules into one by just using ff02::/16
-
pfsense is not going to do anything with multicast unless your running the igmp proxy?
If you do not want to see the log of such noise its almost easier to just turn off default logging and create the rules to log the traffic you want to see. Say tcp syn only packets.
You could combine those 3 rules into one by just using ff02::/16
I'm quit lost when it comes to CIDR (but there are calculators enough around) and Multicast is not really my thing, but as I need to give phones and tablets control over Sonos devices that are in different VLAN's, I have a IGMP proxy setup (don't want IGMP snooping using a switch). I also have the Avahi service running as Bonjour printers are also in a different VLAN. So suddenly, I am confronted with IPv6 and Multicast…
If I would like to follow your advise are there examples "better a good copy, than a bad original"
