Re: NAT state not deleted after IP change (DHCP)

2005-02-10 Thread Michiel van Baak
On 22:55, Tue 08 Feb 05, Cyrill R?ttimann wrote: > Hi Daniel, > > Thanks for the answer and insights to the lower levels of the networked > world. I have now hopefully solved my problem. I can see in the state > table, that the state expires and after a few seconds, the state is > recreated aga

Re: NAT state not deleted after IP change (DHCP)

2005-02-10 Thread Cyrill Rüttimann
Hello, I couldn't resist to comment on some lines here. First of all, if you enable keepalive from the sip proxy to the phones (both SER and asterisk can do that) the state from server to phone won't be expiring. That way it is also not true that SIP is not well suited for firewalled connections. I

Re: NAT state not deleted after IP change (DHCP)

2005-02-10 Thread Michiel van Baak
On 21:00, Thu 10 Feb 05, Cyrill R?ttimann wrote: > Hello, > Keep alive on the server is nat=yes in the sip.conf? > yes. > > Not well suited means, that you have to define the internal ip on the > asterisk server (sip.conf) and the external ip on the sip.conf. If you > are running several server

transparent squid and load balancing outgoing traffic REVISITED

2005-02-10 Thread Emilio Lucena
Hi there, On Thu, 27 Jan 2005, Daniel Hartmeier wrote: > Instead of using route-to on $int_if, you can let connections go out > through the one interface to the default gateway, and use route-to on a > 'pass out on $ext_if1' rule to re-route the outgoing connection to > another interface. Packets

link failover

2005-02-10 Thread guilgamesh70
Hi group, I have this situation + + +--- IPSec link Internal network + Obsd Box+ + +--- Private