Going to have to apologize here, I just tried it again and it is now working, I can only think that I must have made some other typo that triggered it to fail, miss-placed - perhaps because it had previously had issues with the exact same rule I just added so given the only change here is that I only just typed it in again the cause would seem most likely user typed it in wrong first time.
Never saw anything when I checked it over though, guess easy enough to miss a single character though especially with the danger of reading what you expect not what's actually there. *Wanders off feeling rather stupid for that one* On 08/03/13 17:05, Tom Eastep wrote: > On 03/08/2013 08:57 AM, Matt Joyce wrote: >> Just reminded me I planned to write a message yesturday and mention, I >> got the idea to use the new notation to consolidate the prioritizing >> rules for both NTP and DNS which currently is a seperate rule for >> outgoing queries and for outgoing replies from the local servers >> figuring less rules being easier to read and for iptables to process. >> Didn't consider it would be an issue until running shorewall check and >> it complained the = was unexpected. I'm guessing that it was simply not >> intended to be used in the tcrules file as there was no other error >> messages to indicate that I broke anything, just wanted to mention it as >> without checking the finalized documentation I can't be certain whether >> you meant that to work or not and I figured waiting on that could well >> be leaving it too late. >> > What rule failed to work? I just testing this entry in /etc/shorewall/rules: > > ACCEPT net fw tcp 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15 = > > Note that there is another patch (which I just posted on the development > list) that is required for port lists longer than 15. > > -Tom > > > ------------------------------------------------------------------------------ > Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester > Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the > endpoint security space. For insight on selecting the right partner to > tackle endpoint security challenges, access the full report. > http://p.sf.net/sfu/symantec-dev2dev > > > _______________________________________________ > Shorewall-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/shorewall-users
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
