1
Documentation and Translation / Re: Step 1 for "Configure IPv6 Tunnel Broker" fails
« on: August 02, 2018, 11:44:44 pm »
And I am running 18.7
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Documentation and Translation / Re: Step 1 for "Configure IPv6 Tunnel Broker" fails
« on: August 02, 2018, 11:43:34 pm »
I am having the same issue.
There appears to be a bug in the UI code.
That is, I can manually put a /64 after the tunnel-local-addr, like this:
<tunnel-local-addr>2001:XX:XX:XX::2/64</tunnel-local-addr>
in /conf/config.xml
And if I immediately restart, and go to Interfaces->other-GIF0 and click edit,
2001:XX:XX:XX::2/64 appears in the "GIF Tunnel Local Address" web field.
If I click "Save", I get the red banner of input error:
The following input errors were detected:
The tunnel local and tunnel remote fields must have valid IP addresses.
So, I leave it as I manually input into config.xml (i.e. don't save)
And I still get a prefixlen of 128:
AND That's OK, when I look back at the tunnelbroker documentation for FreeBSD.
So It's just the UI issue. And a manual edit of config.xml is a workaround.
#ifconfig gif0
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1280
options=80000<LINKSTATE>
tunnel inet 207.XXX.XXX.21 --> 216.66.22.2
inet6 2001:XXX:XXX:XXX::2 --> 2001:XXX:XXX:XXX1e::1 prefixlen 128
inet6 fe80::20c:xxxx:xxxx:xxxx%gif0 prefixlen 64 scopeid 0xa
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
groups: gif
Cheers!
-sam
There appears to be a bug in the UI code.
That is, I can manually put a /64 after the tunnel-local-addr, like this:
<tunnel-local-addr>2001:XX:XX:XX::2/64</tunnel-local-addr>
in /conf/config.xml
And if I immediately restart, and go to Interfaces->other-GIF0 and click edit,
2001:XX:XX:XX::2/64 appears in the "GIF Tunnel Local Address" web field.
If I click "Save", I get the red banner of input error:
The following input errors were detected:
The tunnel local and tunnel remote fields must have valid IP addresses.
So, I leave it as I manually input into config.xml (i.e. don't save)
And I still get a prefixlen of 128:
AND That's OK, when I look back at the tunnelbroker documentation for FreeBSD.
So It's just the UI issue. And a manual edit of config.xml is a workaround.
#ifconfig gif0
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> metric 0 mtu 1280
options=80000<LINKSTATE>
tunnel inet 207.XXX.XXX.21 --> 216.66.22.2
inet6 2001:XXX:XXX:XXX::2 --> 2001:XXX:XXX:XXX1e::1 prefixlen 128
inet6 fe80::20c:xxxx:xxxx:xxxx%gif0 prefixlen 64 scopeid 0xa
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
groups: gif
Cheers!
-sam
Pages: [1]