OpenWRT Samba Scare on WAN: Difference between revisions

Created page with "Using the nmblookup utility to check the WAN IP Address of an OpenWRT router, discovered that it reported Samba ports as "filtered". Filtered means it won't respond, but the..."
 
mNo edit summary
 
Line 9: Line 9:
option target 'DROP'
option target 'DROP'
option family 'ipv4'
option family 'ipv4'
list proto 'all'
list proto 'tcp'
list proto 'udp'


config rule
config rule
Line 18: Line 19:
option target 'DROP'
option target 'DROP'
option family 'ipv4'
option family 'ipv4'
list proto 'all'
list proto 'tcp'
list proto 'udp'


config rule
config rule
Line 27: Line 29:
option target 'DROP'
option target 'DROP'
option family 'ipv4'
option family 'ipv4'
list proto 'all'
list proto 'tcp'
list proto 'udp'


config rule
config rule
Line 36: Line 39:
option target 'DROP'
option target 'DROP'
option family 'ipv4'
option family 'ipv4'
list proto 'all'
list proto 'tcp'
</syntaxhighlight><br />
list proto 'udp'
</syntaxhighlight>'''SPECIAL NOTE:''' When inserting the above rules, it was noticed that attempting to use the following directive it BROKE all rules that followed (as if it were a syntax error): list proto 'all'  (proto 'all' was attempted to and also caused issues).  It's as if ''list proto 'all'<nowiki/>'' and ''proto 'all'<nowiki/>'' is a syntax error, with the emphasis on ''<nowiki/>'all'<nowiki/>''.  Changing it to specific protocols like ''<nowiki/>'tcp'<nowiki/>'' and ''<nowiki/>'udp'<nowiki/>'' (as shown in the above example) worked great.  Lesson?  Do NOT use 'all', instead use specific protocol names.<br />