Messages

1

23.1 Legacy Series / Wireguard ipv6 over ipv4-tunnel

« on: March 30, 2023, 11:10:43 pm »

I have a wireguard vpn running over ipv4 between a site with ipv6-connectivity and a /64 to a site without ipv6

Can I assign some of the ipv6-adresses to the ipv4-only site and route over the vpn?
 
Is this possible?
Any recipies on how out there?

2

23.1 Legacy Series / Re: Hourly Internet outage.

« on: March 30, 2023, 11:04:19 pm »

That's not fair...
At least hint what the problem was ;-)

3

23.1 Legacy Series / HE IPv6 tunnel behind CGNAT

« on: March 30, 2023, 11:01:52 pm »

Is this possible?

4

23.1 Legacy Series / old static ipv6 will not disappear

« on: March 30, 2023, 10:38:57 pm »

My opnsense had a static ipv6 on fibre, but now it's connected to a 5G modem instead.

I've changed the wan to dhcpv6

But still, if I go in shell, I see the old static ip

I've examined the backup xml, but the old ipv6 is not there.

I can remove it with ifconfig re0 inet6 2a02:xxx::2 delete but it reappears a little later

Where could it be hiding?

5

22.1 Legacy Series / wg0 renamed to wg1 to wg2

« on: May 28, 2022, 01:21:54 am »

I have 3 opn tunnels running. Well, I had it when I ran 21.7.8


After upgrading to 22.1.8_1 I get

wg0: link state changed to UP
wg0: link state changed to DOWN
wg0: changed name tp 'wg1'
wg1: link state changed to UP
wg1: link state changed to DOWN
wg0 changing name to 'wg2'
wg2: link state changed to UP


This means I only have one wireguard connection: wg2

I have another opnsense box at 22.1.8_1 with 3 working wg-interfaces.

6

General Discussion / BIBD gui lacks allow-update

« on: January 03, 2022, 04:44:52 pm »

It should be possible to add "allow-update" in the same way as "allow-transfer" and "allow-query"

I can add it manually, but naturally it disappears at configuration updates

7

21.7 Legacy Series / Re: "remove redundant NPTv6 binat rule (Maurice Walker)" breaks my setup

« on: January 03, 2022, 01:10:34 am »

The old thread is for 21.1, this is 21.7

Strangely it broke on both 21.1.5-6 og 21.7.5-6

I have ipv6 working on 21.7.5, install 21.7.6 and reboots, ipv6 not working. (i.e. not reachable from outside)

I rollback to the 21.7.5 vmware snapshot, and it works again.

As this is a production site, I'm only testing in the middle of the night.

8

General Discussion / Re: nut as server (ups monitor)

« on: December 31, 2021, 05:28:47 pm »

Just too bad my ups weren't nut-compatible, so the question is mooo ;-) :-(

9

21.7 Legacy Series / "remove redundant NPTv6 binat rule (Maurice Walker)" breaks my setup

« on: December 31, 2021, 05:20:17 pm »

I have a vmware server at OVH.
On this I have an opnSense firewall.
Due to the somewhat strange handling of IPv6 at OVH, I have assigned the public addresses
2001:0DB8::201/128
2001:0DB8::202/128
2001:0DB8::203/128
2001:0DB8::204/128 to the public interface.
Then NPTv6 Nats
2001:0DB8::/65 to fd30::/65.
The internal hosts have the adresses
fd30::201
fd30::202
fd30::203
fd30::204
This works in Opnsense 21.7.5, is broken in 21.7.6.

I believe the "remove redundant NPTv6 binat rule (Maurice Walker)" breaks my setup.

10

21.1 Legacy Series / Re: NPTv6 only working one way

« on: December 31, 2021, 05:04:38 pm »

This is spooky.
Can't remember when it started working again, but 21.7.5 works, 21.7.6 doesn't ?!?

11

General Discussion / nut as server (ups monitor)

« on: August 25, 2021, 12:18:31 am »

It appears nut can only operate in standalone and netclient mode, not netserver.

Is there a workaround?
Could I write the config-files directly?

12

21.1 Legacy Series / Re: NPTv6 only working one way

« on: April 27, 2021, 08:40:53 am »

This started in 20.7.6

https://www.facebook.com/groups/1827180887561143/permalink/2927844414161446

I have a vmware server at OVH.
On this I have an opnSense firewall.
Due to the somewhat strange handling of IPv6 at OVH, I have assigned the public addresses
2001:0DB8::201/128
2001:0DB8::202/128
2001:0DB8::203/128
2001:0DB8::204/128 to the public interface.
Then NPTv6 Nats
2001:0DB8::/65 to fd30::/65.
The internal hosts have the adresses
fd30::201
fd30::202
fd30::203
fd30::204
This works in Opnsense 20.7.5, is broken in current version, but already in 20.7.6.