Menu

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.

Show posts Menu

Messages - lucaberta

#1
Thanks @agh1701 and @sot3.

IPv6 has been quite unstable for me too, and this time an upgrade to 23.1.6 broke things for good.

I would normally be able to make IPv6 work again after a reboot by running:

/usr/local/etc/rc.configure_interface wan

from the FreeBSD shell as root, but this time it did not work out.

I reverted back to 23.1.4 as hinted by @AdSchellevis on the GitHub bug thread by using:

opnsense-revert -r  23.1.4 opnsense

and without rebooting, IPv6 came back to life after giving the reconfigure_interface wan command listed above.

I will NOT update my OPNsense box any further, as IPv6 is really unstable at this time, and I'd rather have it than not.

Many thanks,

Luca
#2
23.1 Legacy Series / Re: IPv6 issue?
March 27, 2023, 01:37:53 AM
Quick update, IPv6 seems to be working now that I have performed what is mentioned in this message:

https://forum.opnsense.org/index.php?topic=32263.msg160190#msg160190

Basically running a script from the GUI fixed things for me, at least for the time being.

The simple execution of

/usr/local/etc/rc.configure_interface wan

fixed things. Go figure!

Bye, Luca
#3
23.1 Legacy Series / Re: IPv6 issue?
March 27, 2023, 12:44:51 AM
Quote from: YipieKaie on March 27, 2023, 12:31:06 AM
They change something since 23.1 my friend dont get any prefix from provider.
But no one do anything about it i think, because there ar so many ways to deligate
prefix it depend on what equipment the provider have, so for some it works the rest not
I dont think there is so many that use IPV6 so that could be why it dont have any priority
to be fixed.
I am having the same issue.

I am no longer able to get a prefix and an IPv6 address on the WAN port with 23.1, and browsing the forum did not seem to provide any meaningful solution to the issue, sadly.

It's been a very frustrating experience ever since my ISP turned off 6RD, which used to work perfectly.

With dual stack on OPNsense I have been having only issues since the 6RD switch off.

Bye, Luca
#4
Well, to be fair to Swisscom, they do have minimal documentation on the settings for 3rd party equipment to connect to their network on this page:

https://www.swisscom.ch/en/residential/help/device/internet-router/external-router.html

What they don't clearly say is that navigation to this page in order for the network to "learn" about your router becomes mandatory, otherwise you will not access the Internet:

http://swisscom.ch/start

In general I am quite happy with their service... though I still need to tinker with the IGMP configuration in order to use the Swisscom TV box, which is no big deal as we almost never watch live TV... and for that we use the BlueTV app, if need be.

As far as other ISPs are concerned, I live in a rural area and get VDSL2 from Swisscom via FTTC, and some 15 meters of  copper to my home, giving me some 650M down and 150M up, so I cannot complain!

What other ISPs have you tested here in Switzerland?

Greetings from the "La Côte" area, halfway between Lausanne and Geneva, at the foothills of the Jura mountains!

Bye, Luca
#5
Thanks a lot Mike!

I had no clue that 6rd had been switched off on the Swisscom network, and of course no mention of this was made to the users.

Swisscom makes it very difficult to NOT use their official equipment, and luckily the Swisscom community forum are quite helpful, though not speaking German is sometimes an issue...

It's time to reconfigure IPv6 and make things work again!

Many thanks,

Luca
#6
Hello everyone,

I had been successfully using 6rd on my Swisscom VDSL2 line for more than a year, running OPNsense on an PCengines APU box with a Zyxel router used a plain modem, with OPNsense taking care of all things IP.

Sometimes around the last few months of 2022, I noticed that IPv6 stopped working after an update of OPNsense, but had no time to troubleshoot the issue.

A few more updates have happened, including 23.1_6 which I am now running, but it still looks like 6rd does not seem to work. Now I am taking some time to try and understand where the issue lies.

A couple of packet captures on the WAN interface igb0 port did not show any incoming traffic from the 6rd border relay, whereby the simple ping6 traffic to www.google.com would be normally visible, encapsulated into 6rd with destination the Swisscom 6rd border gateway.

Capturing traffic on wan_stf also shows the IPv6 traffic, of course before the 6rd encapsulation, with only outgoing ping6 traffic.

Please note that this is IPv6 originating from the OPNsense box via the shell CLI.

A quick ifconfig shows this configuration for the wan_stf interface:

wan_stf: flags=4041<UP,RUNNING,LINK2> metric 0 mtu 1452
   description: WAN (wan)
   inet6 2a02:1205:xxxx:xxxx:: prefixlen 28
   groups: stf
   v4net xx.xxx.xxx.xx/0 -> tv4br 193.5.29.1
   nd6 options=101<PERFORMNUD,NO_DAD>

Can anyone comment on what might be the issue?

I have noticed a few mentions of 6rd in the last few releases, could there be any regression bug that I have hit?

Is there any more detailed way to troubleshoot the issue? I am definitely keen to find what caused the issue, as a few months ago things were working fine on my whole LAN with IPv6 thru 6rd on my OPNsense box.

Many thanks,

Luca