Correct. But the reverse must also be true. The destination host must have a route back if it normally follows a different route, however a traceroute will show you the path it takes.
This is just plain routing on linux and does not really have anything to do with sipx. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: [email protected] <[email protected]> To: sipx-users <[email protected]> Sent: Mon Nov 08 12:04:21 2010 Subject: Re: [sipx-users] Adding second route > When you use this command: > route add -net 172.16.30.0 netmask 255.255.255.0 gw 192.168.1.1 > > All Traffic sent by your sipx that is destined to the network 172.16.30.0 > is sent over the gateway 192.168.1.1 all other traffic is not affected at > all. To confirm then, traffic originated from 172.16.30.0 such as port 8443 is the only traffic that would flow back to 172.16.30.0 correct? Everything else would remain as it is, flowing back to it's origin firewall. I want to make sure I don't go introducing any weirdness into the system by adding this. Thanks. Mike _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
