<div dir="ltr"><div><div><div><div><br></div>Thanks Mark,<br><br></div>interesting one, the change of WAN IP happened during "commit" command.<br><br></div>Trace files I collected are overly verbose. I can only see that something provoked re-negotiation of it.<br><br></div>Interestingly enough, a trivial configuration change (added description to ip-0/0/0 interface) and commit after that triggered another WAN IP change...<br><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On 2 February 2016 at 13:25, Diogo Montagner <span dir="ltr"><<a href="mailto:diogo.montagner@gmail.com" target="_blank">diogo.montagner@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Try to find out why the address is changing when the tunnel comes up.<div><br></div><div>Try enabling few traceoptions. </div><div><br></div><div>Below are few suggestions:</div><div><br></div><div><div>[edit]</div><div>dmontagner@vmx# show | compare</div><div>[edit]</div><div>+ routing-options {</div><div>+ traceoptions {</div><div>+ file routing-optinos-trace;</div><div>+ flag all;</div><div>+ }</div><div>+ resolution {</div><div>+ traceoptions {</div><div>+ file resolution;</div><div>+ flag all;</div><div>+ }</div><div>+ }</div><div>+ }</div><div>+ protocols {</div><div>+ pppoe {</div><div>+ traceoptions {</div><div>+ file pppoe-trace;</div><div>+ level all;</div><div>+ flag all;</div><div>+ }</div><div>+ }</div><div>+ }</div><div><br></div><div>[edit]</div><div>dmontagner@vmx#</div></div><div><br></div><div>Another thing you can do is:</div><div><br></div><div>- via another session, do a monitor traffic interface at-x/0/0 size 1500 no-resolve extensive</div><div><br></div><div>This will show you the PPPoE packets (PADI, PADS, PADT and PADO) exchanged for the change in the IP address.</div></div><div class="gmail_extra"><span class="HOEnZb"><font color="#888888"><br clear="all"><div><div>./diogo -montagner<br>JNCIE-SP 0x41A</div></div></font></span><div><div class="h5">
<br><div class="gmail_quote">On Tue, Feb 2, 2016 at 10:56 AM, Goran Aleksic <span dir="ltr"><<a href="mailto:goran.aleksic@gmail.com" target="_blank">goran.aleksic@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi Diogo,<br><br></div>many thanks. I was suspecting this should work, but seemed to deplete my options reading forums...<br><br><br></div>Cheers,<br><br></div>Goran<br><br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On 2 February 2016 at 02:47, Diogo Montagner <span dir="ltr"><<a href="mailto:diogo.montagner@gmail.com" target="_blank">diogo.montagner@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Goran,<div><br></div><div>This works fine. I have the same setup at home.</div><div><br></div><div>I will send you my conf tomorrow with some additional troubleshooting stuff.</div><div><br></div><div>Thanks<div><div><span></span><br><br>On Monday, 1 February 2016, Goran Aleksic <<a href="mailto:goran.aleksic@gmail.com" target="_blank">goran.aleksic@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>HI all,</div><div><br></div><div>I've got Optus ADSL and dynamic public IP.</div><div>Needed 6-in-4 tunnel (IPv6 encapsulated into IPv4 tunnel), tried using Hurricane Electric IPv6 provider, as I saw positive reviews.</div><div>I got Juniper SRX 110 modem and have implemented configuration as stated on <a href="http://forums.juniper.net/t5/SRX-Services-Gateway/HE-IPv6-tunnel-with-flow-based-IPv6-in-10-4/td-p/69338/highlight/true/page/3" target="_blank">http://forums.juniper.net/t5/SRX-Services-Gateway/HE-IPv6-tunnel-with-flow-based-IPv6-in-10-4/td-p/69338/highlight/true/page/3</a></div><div><br></div><div>Issue is – my public IP (on at-1/0/0.0 interface) keeps changing every time I attempt the tunnel.</div><div>This is a twofold problem:</div><div>1. on Hurricane Electric page, you need to specify one endpoint of the tunnel, i.e. your public IP</div><div>2. In configuration of ip-0/0/0.0 interface (tunnel interface) on Juniper SRX, you need to specify your tunnel source IP (a public IP). There doesn't seem to be a trick like with Cisco, to use ip unnumbered and imply IP address from your WAN interface...</div><div><br></div><div>Why would an attempt to establish a IPv4 tunnel to another host trigger my public IP to be changed?</div><div><br></div><div>I'm wondering if anyone has experienced the same or similar issue?</div><div><br></div><div>Thanks,</div><div><br></div><div>Alex</div></div>
</blockquote></div></div></div><span><font color="#888888"><br><br>-- <br>./diogo -montagner<br>JNCIE-SP 0x41A<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div>
</blockquote></div><br></div>