Help with Firewall Log
-
Same. This issue looks odd. Please capture the packets
-
4944 is not a registered port. I can find no info on what application/service would send such traffic.
Is it udp or tcp? I would really sniff that traffic and open it up in wireshark to see.. 0.0.0.0 is listed in bogon.. But that doesn't mean it is, a client asking for dhcp would send from 0.0.0.0 etc.. But not to port 4944.
If all your wanting to do is clear up your log you could set a rule to not log the traffic. But I would be curious what it is so I wold setup packet capture under diag, and then download that file and either post it here or load it up your self in say wireshark..
How much of it are you seeing? Is your log just full of it, hundreds of packets a second, a minute, a day? What?
Thanks for you help ;)
Status/System/LogsFirewall/Normal View
Aug 6 18:40:32 em0 0.0.0.0:15217 255.255.255.255:4944 UDP
Aug 6 18:40:22 em0 0.0.0.0:15154 255.255.255.255:4944 UDP
Aug 6 18:40:12 em0 0.0.0.0:15100 255.255.255.255:4944 UDP
Aug 6 18:40:02 em0 0.0.0.0:15055 255.255.255.255:4944 UDP
Aug 6 18:39:52 em0 0.0.0.0:15019 255.255.255.255:4944 UDP
Aug 6 18:39:42 em0 0.0.0.0:14992 255.255.255.255:4944 UDPThere seems to be repetition every 00:00:10
-
4944 is not a registered port. I can find no info on what application/service would send such traffic.
Is it udp or tcp? I would really sniff that traffic and open it up in wireshark to see.. 0.0.0.0 is listed in bogon.. But that doesn't mean it is, a client asking for dhcp would send from 0.0.0.0 etc.. But not to port 4944.
If all your wanting to do is clear up your log you could set a rule to not log the traffic. But I would be curious what it is so I wold setup packet capture under diag, and then download that file and either post it here or load it up your self in say wireshark..
How much of it are you seeing? Is your log just full of it, hundreds of packets a second, a minute, a day? What?
Thanks for you help ;)
StatusSystem/LogsFirewall/Normal View
Aug 6 18:40:35 WLAN 0.0.0.0 224.0.0.1 IGMP
Aug 6 18:40:34 WLAN 0.0.0.0 224.0.0.1 IGMP
Aug 6 18:40:32 em0 0.0.0.0:15217 255.255.255.255:4944 UDP
Aug 6 18:40:22 em0 0.0.0.0:15154 255.255.255.255:4944 UDP
Aug 6 18:40:12 em0 0.0.0.0:15100 255.255.255.255:4944 UDP
Aug 6 18:40:02 em0 0.0.0.0:15055 255.255.255.255:4944 UDP
Aug 6 18:39:52 em0 0.0.0.0:15019 255.255.255.255:4944 UDP
Aug 6 18:39:42 em0 0.0.0.0:14992 255.255.255.255:4944 UDPDo you have DSL? Search on Google and the forums for. "igmp 4944"
https://forum.pfsense.org/index.php?topic=92054.0
-
4944 is not a registered port. I can find no info on what application/service would send such traffic.
Is it udp or tcp? I would really sniff that traffic and open it up in wireshark to see.. 0.0.0.0 is listed in bogon.. But that doesn't mean it is, a client asking for dhcp would send from 0.0.0.0 etc.. But not to port 4944.
If all your wanting to do is clear up your log you could set a rule to not log the traffic. But I would be curious what it is so I wold setup packet capture under diag, and then download that file and either post it here or load it up your self in say wireshark..
How much of it are you seeing? Is your log just full of it, hundreds of packets a second, a minute, a day? What?
Thanks for you help ;)
StatusSystem/LogsFirewall/Normal View
Aug 6 18:40:35 WLAN 0.0.0.0 224.0.0.1 IGMP
Aug 6 18:40:34 WLAN 0.0.0.0 224.0.0.1 IGMP
Aug 6 18:40:32 em0 0.0.0.0:15217 255.255.255.255:4944 UDP
Aug 6 18:40:22 em0 0.0.0.0:15154 255.255.255.255:4944 UDP
Aug 6 18:40:12 em0 0.0.0.0:15100 255.255.255.255:4944 UDP
Aug 6 18:40:02 em0 0.0.0.0:15055 255.255.255.255:4944 UDP
Aug 6 18:39:52 em0 0.0.0.0:15019 255.255.255.255:4944 UDP
Aug 6 18:39:42 em0 0.0.0.0:14992 255.255.255.255:4944 UDPDo you have DSL? Search on Google and the forums for. "igmp 4944"
https://forum.pfsense.org/index.php?topic=92054.0
Yes I have aDSL Thanks for you help ;)
I did a capture (Diagnostics/Packet Capture) but it stays empty, I choose WAN as interface any-any and 0.0.0.0 for host => nothing even with and without Enable promiscuous mode still nothing, am I doing something wrong or should I move over to wireshark. Why is the log mentioning em0 and not WAN btw?
Thanks to all that replied for your help !
-
https://forum.pfsense.org/index.php?topic=92054.0
Strange thing is I have Draytek Vigir 130 to. Mine is in PPPoA to PPPoE bridge mode so it's transperant.
-
Just capture on WAN with the port set to 4944. Leave the hosts as any.
-
Just capture on WAN with the port set to 4944. Leave the hosts as any.
Only filled in the port and set the count to 1 waiting for over 10min still the capture is running, stopped it and the log file is empty? On the status/dashboard/firewall logs there are numerous counts of "em0 0.0.0.0 to 255.255.255.255:4944" (still don't understand why the log is mentioning em0 in stead of WAN).
I still wanna analyze this strange log in the firewall, but just out of curiosity I unchecked the logging of block bogon networks (status/system logs/settings), but it doesn't help they are still in the logs?
I tested a simple (so with default setting any-any) capture on the WAN and it's working fine, strangely but consistent, there are no captures on 0.0.0.0. in this file?
-
wan is going to be assigned to an interface.. What are you interface assignments? Can you post them. Is your wan actually a vlan on top of em0?
Use tcpdump directly with -i em0 and port udp 4944.. If you see the traffic then you can write it to a file and we can open it in wireshark.
-
wan is going to be assigned to an interface.. What are you interface assignments? Can you post them. Is your wan actually a vlan on top of em0?
Use tcpdump directly with -i em0 and port udp 4944.. If you see the traffic then you can write it to a file and we can open it in wireshark.
NIC1 = em0 = WAN
NIC2 = em1 = LAN
on em1 I have assigned 2 VLAN'stcpdump -> wireshark thanks for pointing that one out to me!
So I did a
tcpdump -c 10 -w /tmp/port.4944.debug.txt -i em0 'port 4944'
than I looked at it with wireshark. To my limited knowledge it seems it originates from the the PPPoA to PPPoE bridge (Draytek Vigor 130) which is between WAN(em0) and ISP as this ISP uses PPPoA and as far as I know this cannot be done by pfSense. I though this bridge should be transparent? I would like to know our opinion insights, thanks for having a look in advance.
-
So did you go into your daytek and
UNmarking "Broadcast DSL status to LAN" under ->System Maintenance->Management
-
So did you go into your daytek and
UNmarking "Broadcast DSL status to LAN" under ->System Maintenance->Management
I will take a look at it and report back soon, at this time it is not possible to power it down. Not to be on hasty side, but I thought a Draytek Vigor 130 set into PPPoA to PPPoE and as so bridging between ISP and WAN was totally transparent.
btw if you have taken a look I remove the file as there's a mac address in there you can't be to carefull ;)
-
why would you have to power it down?
-
As I said settings it to bridge mode between PPPoA and PPPoe, to the best of my knowledge it has no IP (that's why I said it was transparent) so I don't know how to login on it, is there a way? The moment I disconnect it from the Internet it get's an IP (static).
-
well my cable modem is "transparent" ie pfsense gets a public IP.. And I can still access the cable modem via 192.168.100.1 - I would assume daytek would have the same sort of default IP for management even when in "bridge" mode.
-
http://just.draytek.com/index.php?option=com_k2&view=item&id=5617&Itemid=293&lang=en From what the specs say it seems that it could send DSl info (you are wright, still not checked it in the hardware though ;) ), although I never checked this option and as I know not how to access it, I am still mandatory to power it down and connect it to my LAN as I don't know how to set an IP as It is on on the WAN side?
-
well the IP by default is 192.168.1.1 I think - this might be the IP even when in bridge mode.
What IP you using on pfsense lan side?
-
192.168.1.1 so they are the same I can change it, but I still don't understand that there can be a IP thats in the LAN range set on the WAN side ???
-
you can not.. if your pfsense lan is 192.168.1.0/24 then no you wouldn't be able to access your isp devices IP of 192.168.1.1 from devices on your lan.
Doesn't mean that device can not have that IP..
For example my cable modem is 192.168.100.1 my lan is 192.168.9.0/24 I can access it just fine without doing anything because pfsense send that traffic out its wan interface and the cable modem picks it up and answers. Some devices might not do that - and you might have to setup a vip on your wan interface to be on the same network as your device, etc..
See the pfsense doc about accessing modem on wan, etc.
-
Thanks I wll look into it it seems according to these http://www.geekzone.co.nz/forums.asp?forumid=66&topicid=196693 that it might be done I will report back also on the 0.0.0.0 port 4944 thanks (so far) for all your time, I am wiser now !!
-
<off topic="">I see my Disk usage ( /mnt ) is 102% of 595MiB - ufs never saw that?</off>
