|
tunnel dosen't migrate when my public IP address changes, what have I done wrong?
![[gb]](/s/countries/gb.gif) Shadow Hawkins on Friday, 06 April 2012 12:49:18
I currently have a tunnel configured to use AYIYA.
my ISP changes my public v4 every 48 hours, when this happens my tunnel goes down.
The tunnel runs from a Ubuntu server which is behind a NAT.
I have configured my router so that the server is set as a DMZ.
I have left a packet sniffer running on my servers interface at the point of the IP change. I see the AYIYA heartbeat packets continue to leave however I don't get any return traffic from the tunnel endpoint.
can anyone suggest anything that I might have set-up wrong?
tunnel dosen't migrate when my public IP address changes, what have I done wrong?
I have configured my router so that the server is set as a DMZ.
For AYIYA one does not need to configure the host to become the DMZ target, that is the whole point of using UDP as NATs can properly track and pass that along unlike protocol-41 for which it is needed.
I see the AYIYA heartbeat packets continue to leave however I don't get any return traffic from the tunnel endpoint.
Maybe the state in your NAT is messing things up because of the DMZ setting?
|
![[ch]](/s/countries/ch.gif)
on Tuesday, 10 April 2012 11:21:04
Posting is only allowed when you are