Messages

I'm switching ISP in less than 2 weeks and trying to plan out the best way to update my config to update the connection type, interfaces, gateways, default routes etc etc.

My current ISP (BT) is PPPOE/DHCPv6 and my new ISP (BRSK) is DHCPv4/SLAAC.

Can I achieve this via the GUI or do I need to go to the shell and re-assign interfaces? Which is the best way?

My current ISP uses PPPOE with credentials for IPv4 and DHCPv6 over PPPOE for IPv6 and they give out a /56.

My new ISP has no credentials, I need to clone the MAC address of their supplied router onto my WAN interface and then change to DHCPv4 and SLAAC on WAN to get a /48.

I've seen some posts about residual gateways and routes causing problems so how to go about this please?

I use Kea DHCPv4, Router Advertisements for IPv6 (no DHCPv6 on LAN) and Unbound for DNS if they matter.

Hi @tinkermanuk did you ever get this successfully sorted?

I'm planning on swtiching from BT (pppoe) to BRSK shortly (DHCP IPv4 and SLAAC for IPv6) and was looking at the same settings as you were in OPNSense and got confused.  I had hoped it was a simple setting switch but it looks more complex.  For example did you have to make any changes to  gateways in addition to the pppoe > DHCP switch?

At the very least I would recommend accessing plex via a reverse proxy.  Caddy is a simple reverse proxy to set up and handles certificates etc for you.  Yes you will need a domain and a ddns service (unless you have a static public IP address).

Alternatives are accessing over wireguard/tailscale or some people even use cloudflare tunnels, latter may be against cloudflares ToS but these options do not require any open ports.

If you search the plex and selfhosted subreddits you will find lots of posts on how to do these things and they will all be a step up from forwarding a port directly to plex.

Nobody?

No, 24.7.3_1 is fine for me after the devs reverted back to earlier versions of dhcpv6. I believe there were upstream freebsd ipv6 issues that haven't been fixed.

My system went down at 02:13 last night, I'm assuming my ISP assigned me a new IP address or ipv6 prefix but it looks like dhcpv6 couldn't cope and failed?

My ISP is BT in the UK so I'm stuck with pppoe at the moment, my log file is attached and I've trimmed it to start at the point of failure if you read it bottom up.

Any ideas?  This was on 24.7 and after a restart I've upgraded to 24.7.1.

Think I've cured it, NTP wouldn't start either and was complaining about an fd address issue, so I removed the virtual IPs for my LAN and IoT networks and this has cured both.

Not sure why this is suddenly a problem....?

Unbound won't start after a reboot, message in log is "Unable to open pipe. This is likely because Unbound isn't running."

I've tried turning off as many settings as possible including DNS over TLS and using the system nameservers (configured to 9.9.9.9 and 1.1.1.2) but still won't start.

Unbound is listening on LAN interface, port 53, no overrides, blocklists or any advanced settings enabled other than prefetch.

My WAN connection is pppoe with dual stack ipv4/6

I've always had a handful of errors on my IoT interface but getting a lot more now and just noticed a "collision" on my LAN interface, never seen this before.

Only thing that's changed is upgrading opnsense.

Any one?

Every time I restart my linux server, opnsense unbound and radvd crash and monit has to restart them.

Since upgrading to 24.1.9, whenever certain clients connect to the network, this seems to cause ipv6 to baulk and reset and I get warning messages from monit that radvd and unbound have stopped and had to be restarted.

This morning at 07:57 I started up an Arch Linux PC and it caused a similar issue to what I was seeing yesterday with a chromecast with google TV.  Log from this morning attached.

My setup is an N100 mini PC with i226 NICs and a PPPOE connection (900/100).  Happy to provide any more info.

Has anyone managed to successfully send emails via smtp2go from monit or cron?

I've had opnsense set up to send emails via google for a while but I'm trying to eliminate app passwords from my google account by implementing smtp2go.  I can send emails via smtp2go from linux command line, cron on my linux server and various dockerised services, but cannot get opensense to send emails from monit or cron, possibly because of the lack of a sender field.

I have smtp2go set up against my domain and it needs to verify user@domian.com as the sender to work in addition to smtp username and password, and most services have a sender field where I can enter this.  However in monit settings for example there isn't a sender field.

I sometimes have issues with Unbound, but it seems to be linked to WAN/ISP issues where my ISP either gives me a new IPv6 prefix or sometimes a new IPv4 address as well.

This causes both radvd and Unbound to crash and I have monit setup to report and restart them.

I'm currently having problems with unbound and radvd which I'm still diagnosing.  I think my ISP is having ipv6 issues but can't be sure (pppoe connection).

In the meantime I'd like to use monit to monitor and restart these services so that the family can remain online.

I've achieved this for unbound but find the monit documentation impenetrable so struggling to find the correct syntax to check that the radvd process is running.  As as service test I've tried:

Code Select Expand

check process not exist

And various similar strings but cannot get it to work.

For service settings I've identified the pid file and via ssh found a pluginctl command that successfully stops and starts radvd so I just need to sort the service test with some help please.

Recreated the docker container, nothing at all in there about connecting to the OPNSense LAPI on 192.168.1.1 no errors or even confirmation that it's connected