<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[LAN file sharing]]></title><description><![CDATA[<p dir="auto">Newbie question probably i know, but just to double check, i keep going the following firewall log things</p>
<p dir="auto">Apr 24 14:29:56 VLAN200 192.168.1.202:138 192.168.1.255:138 UDP<br />
Apr 24 14:29:55 VLAN200 192.168.1.197:138 192.168.1.255:138 UDP<br />
Apr 24 14:29:04 VLAN200 192.168.1.200:137 192.168.1.255:137 UDP<br />
Apr 24 14:29:03 VLAN200 192.168.1.200:137 192.168.1.255:137 UDP</p>
<p dir="auto">This is just for file sharing on windows right, between computers on the lan and therefore i should add a rule to pass this safely or? Like port 137 is netbios so i can safely allow this to pass from VLAN200 to VLAN200 so it stays within the lan. I have read that trojans sometimes try to use this port as windows is hardcoded to not filter this port so i should not pass traffic outside the lan or?</p>
<p dir="auto">Cheers<br />
Robin</p>
]]></description><link>https://forum.netgate.com/topic/14873/lan-file-sharing</link><generator>RSS for Node</generator><lastBuildDate>Fri, 17 Apr 2026 09:37:37 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/14873.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 24 Apr 2009 04:36:36 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to LAN file sharing on Fri, 24 Apr 2009 23:44:41 GMT]]></title><description><![CDATA[<p dir="auto">Exactly. The above rule would do nothing apart from keeping it out of your logs.<br />
Every single host connected to your LAN segment is receiving these packet and your firewall can not filter them even theoretically.</p>
]]></description><link>https://forum.netgate.com/post/195835</link><guid isPermaLink="true">https://forum.netgate.com/post/195835</guid><dc:creator><![CDATA[Eugene]]></dc:creator><pubDate>Fri, 24 Apr 2009 23:44:41 GMT</pubDate></item><item><title><![CDATA[Reply to LAN file sharing on Fri, 24 Apr 2009 08:04:12 GMT]]></title><description><![CDATA[<p dir="auto">Hey</p>
<p dir="auto">umm, what do you mean i can't route it?</p>
<p dir="auto">like if i put the following into the firewall rules:<br />
TCP  VLAN200 net  *  VLAN200 net  137 (NetBIOS-NS)  *</p>
<p dir="auto">what would that do? I mean would this just take it out of the list as well with the same result as currently with no rule (like it is a broadcast so if i don't have a specific rule attached it is presumed block from my understanding, but other computers can still hear the broadcast on the network(this is the part i don't get cos if they can then the above rule would do nothing apart from keeping it out of my log))….</p>
<p dir="auto">Cheers<br />
Robin</p>
]]></description><link>https://forum.netgate.com/post/195789</link><guid isPermaLink="true">https://forum.netgate.com/post/195789</guid><dc:creator><![CDATA[riegerrobin]]></dc:creator><pubDate>Fri, 24 Apr 2009 08:04:12 GMT</pubDate></item><item><title><![CDATA[Reply to LAN file sharing on Fri, 24 Apr 2009 07:56:22 GMT]]></title><description><![CDATA[<p dir="auto">This is the regular Windows netbios broadcast (correctly on the subnet's broadcast address .255).<br />
You neither need to route it from VLAN200 to VLAN200 nor could you. It's a broadcast.<br />
Passing it to the outside world would be considered a misconfiguration.</p>
<p dir="auto">It just shows up in the firewall logs. To get rid of the notification put a block rule <em>without</em> logging in your ruleset and those entries are gone.</p>
]]></description><link>https://forum.netgate.com/post/195788</link><guid isPermaLink="true">https://forum.netgate.com/post/195788</guid><dc:creator><![CDATA[jahonix]]></dc:creator><pubDate>Fri, 24 Apr 2009 07:56:22 GMT</pubDate></item></channel></rss>