Hi, Simon Hobson wrote: > Jim Duda wrote: > >> The SIP clients are configured to interface with the private >> 192.168.0.X address on the firewall. The clients are all >> external to the firewall on the local LAN. I would have only >> expected NAT to have been performed if the SIP clients >> where attempting to access something external in the internet. > > I agree, so it looks like the sip nat module is getting involved when > it shouldn't.
I just ran into this bug, which seems at least related: https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=522 Should be fixed in 2.6.20, and it also mentions a work-around by issuing: iptables -t raw -A PREROUTING -j NOTRACK HTH, -- - Pieter ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
