On Thu, 7 Jul 2011, J. Randall Owens wrote: > Date: Thu, 7 Jul 2011 04:02:37 > From: J. Randall Owens <[email protected]> > To: Shorewall Users <[email protected]> > > I don't think you've shown us the actual tcrules line 4, have you? Does > it start with "TPROXY(10,3128,::1)" (give or take some brackets) shown in > the error message? I don't see anything on the Shorewall Squid page about > putting an address in the parentheses; it looks like address(es) belong in > the third and optionally second columns. > > If that is where you have the [::1], then we'd need to figure out why it's > getting lumped in there when it's sent to process_tc_rule or wherever.
I take that back now. While it's not on that page, I see where Tc.pm has a place for picking out an IP address as a third parameter. In that case, I'd say that process_tc_rule is messing up at line 206/208, where it checks $originalmark to make sure splitting it on colons doesn't produce three or more fields, which was safe with the old MARK values which never had addresses, either IPv4 or IPv6, but might have a colon in there before the [CFPTI] values. And when it finds three (though the second is that empty non-space between the colons), it spits out that error message. (And this time, Tom, I'm looking at a git checkout, not an ancient 4.4.17. ;) -- J. Randall Owens | http://www.ghiapet.net/ ProofReading Markup Language | http://prml.sourceforge.net/ ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
