Messages

I recently reactivated my account with Hurricane Electric's tunnelbroker.net. I've created a tunnel, and set it up in opnsense. But I'm seeing terrible performance: pings report around 700 ms latency, and I can only download files over IPv6 at around 10-20 KB/s. Over IPv4 that increases to around 300 KB/s, but when I disable the tunnel v4 downloads jump to over 2 MB/s - and the IPv4 gateway monitoring stops warning about the latency.

I don't expect the same level of performance over a tunnel than I'd get with native IPv6, but I'm guessing there's something wrong locally?

Bex

Oh, thanks! It worked with Chromium.

On https://docs.opnsense.org/_images/opnsense_add_gif.png (which is included on https://docs.opnsense.org/manual/how-tos/ipv6_tunnelbroker.html) it shows '64' on the "GIF tunnel remote address" field.

I have an IPv6 tunnel from Hurricane Electric, and went to configure it in "Interfaces: Other Types: GIF". However, the documentation says the "GIF tunnel remote address" should be configured as /64, but the drop-down only goes from 1 to 32.

Also, when I enter the information per the documentation, the UI complains about the IP addresses not being valid.

Is it the same bug as reported in https://forum.opnsense.org/index.php?topic=8733.0 ?

There, they say:

"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."

I've just had a DSL connection installed and have a /29 static IP allocation, with the WAN being a PPPoE connection.

With my previous connection I configured the WAN as a /29 interface and bridged it with my two public ports on my router. But now, with PPPoE being /32 opnsense wants to route traffic for my web server out to the WAN, and nothing I've tried in terms of creating additional gateways and routes seems to help.

For now I've disabled transparent bridging mode on the DSL modem, but I'm wondering if anyone else has run into this issue and has any solutions?

Thanks.
Bex

I got this working after I realized the Comcast modem is configured just for a /64.

I've been trying to set up IPv6 on my LAN for a while, with no success. I've tried with both interface tracking with DHCPv6 on the WAN, and with static addresses - ideally I want to just set it up with static IPv6 addresses, handing out allocations via router advertisements and/or DHCPv6.

I'm on Comcast, and have been given what they claim is a /56 allocation, but I've read elsewhere that I should treat is as a /60 or /64. I have four ports in use - WAN, PUB1, PUB2 and LAN. The WAN, PUB1 and PUB2 are bridged, giving public IP addresses to the PUB1 and PUB2 machines behind the firewall and allowing them to be reached from the internet. The LAN is currently using NAT for IPv4, and my problem is that while the machines on PUB1 and PUB2 have no problems with IPv6 connectivity, I can't reach the internet over IPv6 from the LAN.

Unfortunately I only have 5 IPv4 addresses, so I can't entirely turn off NAT v4 on the LAN. When I set up OPNsense to use interface tracking on the LAN with DHCPv6 on the WAN, the LAN interface didn't get an IPv6 address.

Does anyone have any tips or help how I might get it working?