Firewall Not Saving Adapter Rules/blocking Smb Shares
I'm posting because bitdefender is blocking the SMB shares that are on my home linux server. If I add the IP to the adapter rules its fine, but it refuses to save the rules for long periods of time. Usually they're gone after a reboot and I have to re-enter the IP address. This gets tedious really fast. Very inconvenient. Also, in case any support member responds: Ticket: 201307151029071
Snippet of log file below.
2013/07/15 10:40:09.179 [BDFW] [DEVIO] Firewall enabled.
2013/07/15 10:40:09.193 [BDFWCORE] Updating profiles:
2013/07/15 10:40:09.193 [BDFWCORE] Adapter name: {04960E1B-7A64-46A6-9A1A-2CB032B4D7B7}, flags: 2, stealth: 2, zones: 0
2013/07/15 10:40:09.193 [BDFWCORE] Adapter name: {E97A0D04-F72E-4449-AE89-84F398FB891C}, flags: 2, stealth: 2, zones: 0
2013/07/15 10:40:09.193 [BDFWCORE] Adapter name: {04960E1B-7A64-46A6-9A1A-2CB032B4D7B7}, flags: 2, stealth: 2, zones: 0
2013/07/15 10:40:11.826 [NDISLIB][FILTER] Allowed non-IP packet. First 40 bytes (60 36 DD 51 06 D0 10 6F 3F 87 27 F2 08 06 00 01 08 00 06 04 00 01 10 6F 3F 87 27 F2 C0 A8 01 01 00 00 00 00 00 00 C0 A8)
2013/07/15 10:40:11.826 [NDISLIB][FILTER] Allowed non-IP packet. First 40 bytes (10 6F 3F 87 27 F2 60 36 DD 51 06 D0 08 06 00 01 08 00 06 04 00 02 60 36 DD 51 06 D0 C0 A8 01 7E 10 6F 3F 87 27 F2 C0 A8)
2013/07/15 10:40:20.147 [BDFW] [FILTER] Blocked packet because of rule 25. Direction: Outbound, Local Address: FE80:0000:0000:0000:EC71:10F8:586F:1A52:53927, Remote Address: FF02:0000:0000:0000:0000:0000:0001:0003:5355, Protocol: 17, Local Packet: 0, PID: 1688, Process: c:\windows\system32\svchost.exe, Cmd. Line: -k networkservice.
2013/07/15 10:40:20.247 [BDFW] [FILTER] Blocked packet because of rule 25. Direction: Outbound, Local Address: FE80:0000:0000:0000:EC71:10F8:586F:1A52:53927, Remote Address: FF02:0000:0000:0000:0000:0000:0001:0003:5355, Protocol: 17, Local Packet: 0, PID: 1688, Process: c:\windows\system32\svchost.exe, Cmd. Line: -k networkservice.
2013/07/15 10:40:20.247 [BDFW] [FILTER] Blocked packet because of rule 25. Direction: Outbound, Local Address: FE80:0000:0000:0000:A94B:9781:674F:2915:53927, Remote Address: FF02:0000:0000:0000:0000:0000:0001:0003:5355, Protocol: 17, Local Packet: 0, PID: 1688, Process: c:\windows\system32\svchost.exe, Cmd. Line: -k networkservice.
2013/07/15 10:40:37.119 [BDFW] [FILTER] Blocked packet because of rule 35. Direction: Outbound, Local Address: 192.168.1.126:50462, Remote Address: 98.215.*.*:445, Protocol: 6, Local Packet: 0, PID: 4, Process: system, Cmd. Line: .
2013/07/15 10:40:37.128 [BDFW] [FILTER] Blocked packet because of rule 35. Direction: Outbound, Local Address: 192.168.1.126:50462, Remote Address: 98.215.*.*:445, Protocol: 6, Local Packet: 0, PID: 4, Process: system, Cmd. Line: .
2013/07/15 10:40:37.421 [BDFW] [FILTER] Blocked packet because of rule 35. Direction: Outbound, Local Address: 192.168.1.126:50462, Remote Address: 98.215.*.*:445, Protocol: 6, Local Packet: 0, PID: 4, Process: system, Cmd. Line: .
2013/07/15 10:40:38.021 [BDFW] [FILTER] Blocked packet because of rule 35. Direction: Outbound, Local Address: 192.168.1.126:50462, Remote Address: 98.215.*.*:445, Protocol: 6, Local Packet: 0, PID: 4, Process: system, Cmd. Line: .
2013/07/15 10:40:38.147 [NDISLIB][FILTER] Allowed non-IP packet. First 40 bytes (60 36 DD 51 06 D0 10 6F 3F 87 27 F2 08 06 00 01 08 00 06 04 00 01 10 6F 3F 87 27 F2 C0 A8 01 01 00 00 00 00 00 00 C0 A8)
2013/07/15 10:40:38.147 [NDISLIB][FILTER] Allowed non-IP packet. First 40 bytes (10 6F 3F 87 27 F2 60 36 DD 51 06 D0 08 06 00 01 08 00 06 04 00 02 60 36 DD 51 06 D0 C0 A8 01 7E 10 6F 3F 87 27 F2 C0 A8)
2013/07/15 10:40:39.221 [BDFW] [FILTER] Blocked packet because of rule 35. Direction: Outbound, Local Address: 192.168.1.126:50462, Remote Address: 98.215.*.*:445, Protocol: 6, Local Packet: 0, PID: 4, Process: system, Cmd. Line: .
2013/07/15 10:40:40.421 [BDFW] [FILTER] Blocked packet because of rule 35. Direction: Outbound, Local Address: 192.168.1.126:50462, Remote Address: 98.215.*.*:445, Protocol: 6, Local Packet: 0, PID: 4, Process: system, Cmd. Line: .
2013/07/15 10:40:41.612 [BDFW] [FILTER] Blocked packet because of rule 35. Direction: Outbound, Local Address: 192.168.1.126:50462, Remote Address: 98.215.*.*:445, Protocol: 6, Local Packet: 0, PID: 4, Process: system, Cmd. Line: .
2013/07/15 10:40:44.012 [BDFW] [FILTER] Blocked packet because of rule 35. Direction: Outbound, Local Address: 192.168.1.126:50462, Remote Address: 98.215.*.*:445, Protocol: 6, Local Packet: 0, PID: 4, Process: system, Cmd. Line: .
2013/07/15 10:40:44.125 [NDISLIB][FILTER] Allowed non-IP packet. First 40 bytes (FF FF FF FF FF FF 7A 79 19 20 8D 4B 08 06 00 01 08 00 06 04 00 01 7A 79 19 20 8D 4B 19 20 8D 4B 00 00 00 00 00 00 19 00)
2013/07/15 10:40:44.125 [NDISLIB][FILTER] Allowed non-IP packet. First 40 bytes (7A 79 19 20 8D 4B 7A 79 19 00 00 01 08 06 00 01 08 00 06 04 00 02 7A 79 19 00 00 01 19 00 00 01 7A 79 19 20 8D 4B 19 20)
2013/07/15 10:40:48.813 [BDFW] [FILTER] Blocked packet because of rule 35. Direction: Outbound, Local Address: 192.168.1.126:50462, Remote Address: 98.215.*.*:445, Protocol: 6, Local Packet: 0, PID: 4, Process: system, Cmd. Line: .
2013/07/15 10:40:58.416 [BDFW] [FILTER] Blocked packet for / from closed port because of stealth settings. Direction: Outbound, Local Address: 192.168.1.126:50462, Remote Address: 98.215.*.*:445, Protocol: 6, Local Packet: 0, PID: -1, Process: , Cmd. Line: .
2013/07/15 10:40:58.479 [BDFW] [FILTER] Blocked packet because of rule 35. Direction: Outbound, Local Address: 192.168.1.126:50472, Remote Address: 98.215.*.*:445, Protocol: 6, Local Packet: 0, PID: 4, Process: system, Cmd. Line: .
98.215.*.* is the IP I have to add. Obfuscated for obvious reasons.
Thanks in advance.
0
Comments
-
Hello,
A quick solution for the encountered issue is to upgrade to The New Bitdefender. The upgrade is absolutely free of charge and due to the many improvements brought to this lineup any issues you may have encountered with your current product are now solved.
In order to upgrade to the new version please follow the steps below:
http://forum.bitdefender.com/index.php?act...f=366&id=58
From now on, post in this area of the forum in case you encounter further issues after the upgrade:
http://forum.bitdefender.com/index.php?showforum=360
Thank you.0
This discussion has been closed.
