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'm not familiar enough with IPTables to suggest next steps, I'm more used to diagnosing why a remote device can't connect through some crappy gateway coded by an imbecile (anyone from Zyxel listening ?) who thinks symmetric nat and constantly changing ports is a cute idea ! ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
