Provided all clients are inside your perimeter and not having another NAT in front of them, you can safely use SER without NAT. Just make sure you specify:
listen=xxx where xxx is the private of your FreeBSD box.
Note that it will not communicate well with outside world in this configuration. If you need that, than yes, your clients will be detected as NATed and you have to use the public IP interface for SER.
Zeus
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Michael C. Cambria Sent: Tuesday, 31 August 2004 12:42 PM To: serusers@lists.iptel.org Subject: [Serusers] NAT + Clients directly connected to SER
Using ser 0.8.14 from cvs, I have a question regarding the example nathelper.cfg file. The file is in sip_router/etc/nathelper.cfg
# !! Nathelper # Special handling for NATed clients; ....
I'd like to understand if clients are considered NATed in my configuration. I have ser running on the NAT box itself (FreeBSD 4.10-Stable). There is one public address, and several private subnets. SER running on this box is the sip proxy for all clients on the private subnets.
In this topology, would the UA's on the private subnets be considered "NATed clients" and thus pass the nat_uac_test("3") test in this nathelper.cfg file? Or does this test only apply when NAT exists between SER and the clients?
Thanks, MikeC
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers