Messages

Hi all,

Just upgraded to 25.7.11_1 from 25.7.10. Everything works as normal. Fiddling around with the new feature Interfaces: Neighbors: Automatic Discovery. Noticed that it works, but only with All interfaces selected. Any other subselection of interfaces, including Select All, prevents the service from starting.

See below for examples. When looking at the log (when using All) shows that the adds capture for the various interface devices. I have bridges configured (multiple eth-devices into different LANs (IOT and NET for example) and have pppoe0 as WAN (VLAN6 on physical interface - KPN FttH).

One error always shows up, and does not seem related. Is there when it works, and when the service does not start. No other logs are available in the GUI that show the reason for the service failing. Using promiscuous mode does not make a difference, nor does verbose logging for figuring out what is going wrong. All my interface types can be captured apparently...   

Successful when All:
2026-01-17T13:10:02.890816Z INFO hostwatch: Added capture for device: pppoe0 (WAN_INET (wan))
2026-01-17T14:10:02Noticehostwatch 2026-01-17T13:10:02.890344Z INFO hostwatch: Added capture for device: bridge1 (LAN_IOT (opt12))
2026-01-17T14:10:02Noticehostwatch 2026-01-17T13:10:02.889866Z INFO hostwatch: Added capture for device: bridge0 (LAN_INET (lan))
2026-01-17T14:10:02Noticehostwatch 2026-01-17T13:10:02.889356Z INFO hostwatch: Added capture for device: wg0 (ViperWG (opt13))
2026-01-17T14:10:02Noticehostwatch 2026-01-17T13:10:02.888815Z INFO hostwatch: Added capture for device: vlan03 (LAN_IPTV (opt10))
2026-01-17T14:10:02Noticehostwatch 2026-01-17T13:10:02.888242Z INFO hostwatch: Added capture for device: vlan02 (WAN_IPTV (opt8))
2026-01-17T14:10:02Noticehostwatch 2026-01-17T13:10:02.887692Z INFO hostwatch: Added capture for device: vlan01 (No description)
2026-01-17T14:10:02Noticehostwatch 2026-01-17T13:10:02.887166Z INFO hostwatch: Added capture for device: igb7 (ETH8 (opt9))
2026-01-17T14:10:02Noticehostwatch 2026-01-17T13:10:02.886684Z INFO hostwatch: Added capture for device: igb6 (ETH7 (opt11))
2026-01-17T14:10:02Noticehostwatch 2026-01-17T13:10:02.886156Z INFO hostwatch: Added capture for device: igb5 (ETH6 (opt6))

Error always visible (regardless if the service does or does not start):
2026-01-17T13:10:02.914762Z WARN hostwatch: Failed to initialize capture for device: pfsync0

Edit: Found some logs in the general log in settings.

At failure to start:
2026-01-17T14:15:15Noticekernel <6>[1488] pid 81926 (hostwatch), jid 0, uid 0: exited on signal 6 (no core dump - bad address)
2026-01-17T14:15:15Noticeroot /usr/local/etc/rc.d/hostwatch: WARNING: failed to start hostwatch
2026-01-17T14:14:54Noticekernel <6>[1467] pid 29596 (hostwatch), jid 0, uid 0: exited on signal 6 (no core dump - bad address)
2026-01-17T14:14:54Noticeroot /usr/local/etc/rc.d/hostwatch: WARNING: failed to start hostwatch

At successful start: no logs related to the service in General. Only the change in config XML file (enabled check).

Currently you can bridge VLAN interfaces but not the other way round.

E.g. with FreeBSD 14:

igc0.1 - VLAN 1 on igc0
igc0.2 - VLAN 2 on igc0
igc1.1 - VLAN 1 on igc1
igc1.2 - VLAN 2 on igc1

bridge1 - members igc0.1, igc1.1
bridge2 - members igc0.2, igc2.2

This works well but is complicated and error prone to set up.

With FreeBSD 15:

bridge0 - members igc0, igc1

bridge0.1 - VLAN 1 on all bridge ports
bridge0.2 - VLAN 2 on all bridge ports


HTH,
Patrick

Will this also be implemented in OPNsense? Not sure if all FreeBSD options are also implemented in OPNsense

Happy New Year!

Searching the forum for VLANs on bridges results in a lot of information and configurations (e.g. link, link, link) where the bottomline seems to be "bridge over VLANs" and not use (not possible in OPNsense config) VLANs on bridges.

Now I have been reading up on the matter and see that"

• in FreeBSD 14.x man for IF_BRIDGE(4) there is no VLAN support (link)
• in FreeBSD 15.x man for IF_BRIDGE(4) there is VLAN support (see quote below, link)

Where I am aware that OPNsense is currently based on FreeBSD 14.3 I assume that OPNsense will move to 15.x at some point. this will offer VLAN support on bridges judging by the FreeBSD documentation.

Is this VLAN support on bridges also moving into OPNsense? Couldn't find it on the forum, but when is OPNsense moving to FreeBSD 15.x/16.x?
Arguably, having VLAN support on bridges could make multi-NIC box configurations (such as my trusty Qotom) a little easier with IPTV VLANs, WLAN VLANs, IOT VLANs etc. on top of a multi-NIC LAN_bridge with a single WAN interface. ;-) 

From the FreeBSD 15.x man IF_BRIDGE(4)

VLAN SUPPORT
       The if_bridge driver has   full support for virtual  LANs   (VLANs).   The
       bridge  implements  independent   VLAN  learning,   i.e. MAC addresses are
       learned on a per-VLAN basis, and   the same MAC address may be learned on
       multiple   interfaces on different   VLANs.   Incoming frames   with an   802.1Q
       tag will   be assigned to the appropriate VLAN.

       Traffic sent to or from the host   is not assigned   to a VLAN by  default.
       To  allow the host to communicate on a VLAN, configure a   vlan(4)   inter-
       face on the bridge and (if necessary) assign IP addresses there.

       By default no access control is enabled,   so any interface may  partici-
       pate in any VLAN.

       VLAN  filtering   may  be    enabled  on  a    bridge    using the ifconfig(8)
       vlanfilter option.  When   VLAN filtering is enabled,  an   interface  may
       only send and receive frames based on its configured VLAN access   list.

       The   interface's   untagged  VLAN  ID  may  be   configured  using  the
       ifconfig(8) untagged option.  If   an untagged VLAN ID is configured, in-
       coming frames will be assigned to that VLAN, and   the interface may  re-
       ceive outgoing untagged frames in that VLAN.

       The tagged VLAN access list may be configured using the tagged, +tagged
       and  -tagged options to ifconfig(8).  An   interface may send and receive
       tagged frames for any VLAN in its access   list.

       The bridge will automatically insert or remove 802.1q tags  as  needed,
       based  on  the  interface configuration,   when forwarding   frames between
       interfaces.  This tag processing   is only   done for interfaces with  VLAN
       filtering enabled.

My IGMP Proxy is definitely throwing errors and the behaviour of my network is entirely in keeping with what you would expect from IGMP failure.
I wonder if the error i saw when performing the upgrade is the cause.
Is it possible to rerun the upgrade over the top of the existing upgrade (ie 25.10.7 over 25.10.7) to eliminate this as the possible root cause.

Maybe it is a better idea to uninstall the IGMP Proxy plugin first, reboot the system, reinstall the IGMP Proxy plugin and configure it from scratch. Reinstalling the plugin will trigger the system to register everything (whatever it requires) again from scratch. Maybe there is a corrupt file or something. If that doesn't do the trick, you may need a reinstall. Dunno if you can reinstall the upgrade the way you describe.

Also use IGMP Proxy here. No issues with the upgrade and IGMP is working as it should. I have a standard configuration for KPN (NLD ISP) IPTV.

Upstream is configured for the IPTV platform
213.75.0.0/16, 217.166.0.0/16, 195.121.0.0/1

Downstream has my IPTV LAN VLAN 192.168.40.0/24

Hi, well I use Kea for ipv6 and v4. For ipv4 I have a bunch of reservations with hostnames that get tracked in Unbound. I also have some infrastructure that is in the same subnet but outside the DHCP pool for ipv4. I use unbound overrides for those to get dns resolution.

For ipv6, kea provides the dhcp and the standard router advertisement daemon in services is in assisted mode. This enables the LAN clients to get an ip from the ISP assigned /48 prefix (LAN interface configured as tracking WAN. WAN configured as DHCPv6). I use two subnets  inside the ISP assigned prefix length to provide two VLANs with separate ipv6.

As for local client IPv6 tracking and reservations as well as DNS, do not use that. Internally the clients get a IPv6 from the earlier mentioned infrastructure and that is routeable through the ISP ipv6 gateway. Internal local LAN traffic is all done with IPv4, DNS ipv4 and a Caddy reverse proxy (https with SSL wildcard certs) where applicable.

For all configurations I used guides from either this forum and/or documentation.

Just upgraded through UI. Went flawless. Up and running on KPN NLD (IPv4 &IPv6) without issues. Acme and Caddy working. Kea IPv4/IPv6 and unbound combo OK.

And don't forget the firewall rules allowing ipv6 traffic... :)

https://test-ipv6.com/
https://ipv6-test.com/

These sites when viewing from my iPad show no connectivity IPv6.. iPad gets a 2a02 address as well on lan...  will start puzzling this one later... dhcpv6 starts automatically by the way. Nice.

It works!! I needed to also configure my LAN interface (bridge with link local enabled) and set it to Track interface. After that I got a prefix and dns through KPN (reload WAN interface).

Somewhere, something is ignored by either opnsense or KPN that results in dumping the settings (opnsense) or KPN ignoring the request. Interesting, I did not expect that from the opnsense documentation that says enable and debug wan first.

I can now move on fixing the rest and clients. Clients are issued an address in the 2a02 range now.

Also disabled "prefer ipv4 even if ipv6 is available". I can ping ipv6.google.com from the opnsense machine.

- Interfaces -> I have created separate interfaces for VLAN and Physical to be able to correctly set the MTU's for both. Physical WAN MTU =1512, VLAN MTU=1508, PPPoE WAN=1508
- Interfaces -> I have have "Send Prefix Hint" as "enabled"

First item and second item. Changed MTU to 1508, no difference. Send prefix hint same story.

Looking in Interfaces -> overview i also see a few interfaces working (green plug sign): Physical WAN and LAN. I see that the Physical WAN interface does not receive a IPv6 address, this is assigned to the LAN interface...

Fixing LAN side using SLAAC or track interface is something that I can do if WAN works. This is due to the fact that the KPN provided prefix delegation shows the range to use... right?

So you should take a look at the DHCPv6 logs and the WAN interface information.

Cheers
Maurice

Thanks. KPN ISP uses DHCPv6. No SLAAC. Where can I find the DHCPv6 logs in opnsense?

Hi Rene,

I'm also on KPN FttH and 25.1.5_5 and running well.
I'll take a look at my config and hopefully provide you with some ideas.

Thanks! I am greatly frustrated that I saw DNS once and now nothing. While settings are the same. Stupid me cleared the ppp-logs to filter clutter after it worked. Rookie mistake, will not repeat. That does not help me now though...

Hi all,

I have had a working KPN FttH solution for years now on IPv4. Works perfectly (guides used a.o.): https://wiki.kaldenhoven.org/nl/Computer/Netwerk/opnsense-kpn-glasvezel. No I tried to get IPv6 working. Yesterday I briefly got the KPN DNS IPv6 DNS servers, but now they are gone. I simply do not understand. Hopefully somebody can help.

Now, some settings currently on my Opnsense:

• Still running 25.1.5_5 for now
• MTU physical interface = 1512 byes, the pppoe is 1508 --> provides a KPN connection with 1500 bytes MTU (max as per KPN specification)
• Settings pppoe for IPv6 (WAN) are: DHCPv6, request prefix only, delegation size /48 (as per KPN specification)
• Interface settings: Allow IPv6 is checked.
• no firewall rules blocking IPv6
• rebooted after making the WAN settings complete
• LAN settings are not done yet, as per OPNsense documentation check WAN ipv6 settings first and diagnose from firewall. After that is working, complete LAN setup.
• I am aware that KPN only provides the prefix, so not an IPv6 address to the one (is done for IPv4 of course), but the key give away it is not working is the absence of IPv6 DNS which should be provided by KPN DHCPv6. Only link local addresses fe80... are on the interface

Any help is greatly appreciated.

Now checking out the PPP-logs from a WAN interface reload I get the following (redacted out my IPv4 address and replaced with ZZZ:

Code Select Expand

2025-05-09T13:26:10    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : wireguard_sync())   
2025-05-09T13:26:10    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : webgui_configure_do(,[wan]))   
2025-05-09T13:26:10    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : vxlan_configure_do())   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : unbound_configure_do(,[wan]))   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : openssh_configure_do(,[wan]))   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : opendns_configure_do())   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : ntpd_configure_do())   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanipv6: miniupnpd: Starting service on interface: lan   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : miniupnpd_configure_do())   
2025-05-09T13:26:04    Warning    igmpproxy    select() failure; Errno(4): Interrupted system call   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : igmpproxy_configure_do())   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : dnsmasq_configure_do())   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (execute task : dhcrelay_configure_if(,[wan],inet6))   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure newwanip (,[wan],inet6)   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : wireguard_configure_do())   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : openvpn_configure_do(,[wan]))   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure vpn (execute task : ipsec_configure_do(,[wan]))   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure vpn (,[wan],inet6)   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : wireguard_sync())   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : webgui_configure_do(,[wan]))   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : vxlan_configure_do())   
2025-05-09T13:26:04    Notice    opnsense    /usr/local/etc/rc.configure_interface: plugins_configure newwanip:rfc2136 (1,[wan])   
2025-05-09T13:26:02    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure monitor (execute task : dpinger_configure_do(,[WAN_INET_GW]))   
2025-05-09T13:26:02    Notice    opnsense    /usr/local/etc/rc.newwanipv6: plugins_configure monitor (,[WAN_INET_GW])   
2025-05-09T13:26:02    Notice    opnsense    /usr/local/etc/rc.newwanipv6: ROUTING: keeping inet6 default route to fe80::3e15:fbff:fedb:6958%pppoe0   
2025-05-09T13:26:02    Notice    opnsense    /usr/local/etc/rc.newwanipv6: ROUTING: configuring inet6 default gateway on wan   
2025-05-09T13:26:02    Notice    opnsense    /usr/local/etc/rc.newwanipv6: ROUTING: entering configure using wan   
2025-05-09T13:26:02    Notice    opnsense    /usr/local/etc/rc.newwanipv6: IP renewal starting (address: fe80::2e0:4cff:fe81:c5e8%pppoe0, interface: wan, device: pppoe0)   
2025-05-09T13:26:01    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : unbound_configure_do(,[wan]))   
2025-05-09T13:26:01    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : openssh_configure_do(,[wan]))   
2025-05-09T13:26:01    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : opendns_configure_do())   
2025-05-09T13:26:01    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : ntpd_configure_do())   
2025-05-09T13:26:01    Notice    opnsense    /usr/local/etc/rc.newwanip: miniupnpd: Starting service on interface: lan   
2025-05-09T13:26:01    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : miniupnpd_configure_do())   
2025-05-09T13:26:01    Warning    igmpproxy    select() failure; Errno(4): Interrupted system call   
2025-05-09T13:26:01    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : igmpproxy_configure_do())   
2025-05-09T13:26:01    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dnsmasq_configure_do())   
2025-05-09T13:26:01    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure newwanip (execute task : dhcrelay_configure_if(,[wan],inet))   
2025-05-09T13:26:01    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure newwanip (,[wan],inet)   
2025-05-09T13:26:01    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : wireguard_configure_do())   
2025-05-09T13:26:01    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : openvpn_configure_do(,[wan]))   
2025-05-09T13:26:01    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure vpn (execute task : ipsec_configure_do(,[wan]))   
2025-05-09T13:26:01    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure vpn (,[wan],inet)   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: plugins_configure dns (execute task : unbound_configure_do(1))   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: plugins_configure dns (execute task : dnsmasq_configure_do(1))   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: plugins_configure dns (1)   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: plugins_configure dhcp (execute task : radvd_configure_dhcp(1))   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: plugins_configure dhcp (execute task : dhcpd_dhcp_configure(1))   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: plugins_configure dhcp (1)   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: plugins_configure ipsec (execute task : ipsec_configure_do(1,wan))   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: plugins_configure ipsec (1,wan)   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: Chose to bind WAN_INET_PPPOE on ZZZ.ZZZ.ZZZ.ZZZ since we could not find a proper match.   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: plugins_configure monitor (execute task : dpinger_configure_do(1,[WAN_INET_PPPOE,WAN_INET_GW]))   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: plugins_configure monitor (1,[WAN_INET_PPPOE,WAN_INET_GW])   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: ROUTING: setting inet6 default route to fe80::3e15:fbff:fedb:6958%pppoe0   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: ROUTING: configuring inet6 default gateway on wan   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: ROUTING: keeping inet default route to 195.190.228.6   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: ROUTING: configuring inet default gateway on wan   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: ROUTING: treating '195.190.228.6' as far gateway for 'ZZZ.ZZZ.ZZZ.ZZZ/32'   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.configure_interface: ROUTING: entering configure using wan   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.newwanip: Chose to bind WAN_INET_PPPOE on ZZZ.ZZZ.ZZZ.ZZZ since we could not find a proper match.   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,[WAN_INET_PPPOE]))   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.newwanip: plugins_configure monitor (,[WAN_INET_PPPOE])   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.newwanip: ROUTING: setting inet default route to 195.190.228.6   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.newwanip: ROUTING: configuring inet default gateway on wan   
2025-05-09T13:26:00    Notice    opnsense    /usr/local/etc/rc.newwanip: ROUTING: treating '195.190.228.6' as far gateway for 'ZZZ.ZZZ.ZZZ.ZZZ/32'   
2025-05-09T13:25:59    Notice    opnsense    /usr/local/etc/rc.newwanip: ROUTING: entering configure using wan   
2025-05-09T13:25:59    Notice    opnsense    /usr/local/etc/rc.newwanip: IP renewal starting (new: ZZZ.ZZZ.ZZZ.ZZZ, old: ZZZ.ZZZ.ZZZ.ZZZ, interface: wan, device: pppoe0, force: yes)   
2025-05-09T13:25:59    Notice    ppp    ppp-linkup: executing on pppoe0 for inet   
2025-05-09T13:25:59    Notice    ppp    [wan] ZZZ.ZZZ.ZZZ.ZZZ -> 195.190.228.6   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: LayerUp   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: state change Ack-Sent --> Opened   
2025-05-09T13:25:59    Notice    ppp    [wan] SECDNS 195.121.1.66   
2025-05-09T13:25:59    Notice    ppp    [wan] PRIDNS 195.121.1.34   
2025-05-09T13:25:59    Notice    ppp    [wan] IPADDR ZZZ.ZZZ.ZZZ.ZZZ   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: rec'd Configure Ack #3 (Ack-Sent)   
2025-05-09T13:25:59    Notice    ppp    [wan] SECDNS 195.121.1.66   
2025-05-09T13:25:59    Notice    ppp    [wan] PRIDNS 195.121.1.34   
2025-05-09T13:25:59    Notice    ppp    [wan] IPADDR ZZZ.ZZZ.ZZZ.ZZZ   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: SendConfigReq #3   
2025-05-09T13:25:59    Notice    ppp    [wan] SECDNS 195.121.1.66   
2025-05-09T13:25:59    Notice    ppp    [wan] PRIDNS 195.121.1.34   
2025-05-09T13:25:59    Notice    ppp    [wan] ZZZ.ZZZ.ZZZ.ZZZ is OK   
2025-05-09T13:25:59    Notice    ppp    [wan] IPADDR ZZZ.ZZZ.ZZZ.ZZZ   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: rec'd Configure Nak #2 (Ack-Sent)   
2025-05-09T13:25:59    Notice    ppp    [wan] IFACE: Rename interface ng0 to pppoe0   
2025-05-09T13:25:59    Notice    ppp    [wan] IFACE: Up event   
2025-05-09T13:25:59    Notice    ppp    ppp-linkup: executing on pppoe0 for inet6   
2025-05-09T13:25:59    Notice    ppp    [wan] 02e0:4cff:fe81:c5e8 -> 3e15:fbff:fedb:6958   
2025-05-09T13:25:59    Notice    ppp    [wan] IPV6CP: LayerUp   
2025-05-09T13:25:59    Notice    ppp    [wan] IPV6CP: state change Ack-Sent --> Opened   
2025-05-09T13:25:59    Notice    ppp    [wan] IPV6CP: rec'd Configure Ack #1 (Ack-Sent)
2025-05-09T13:25:59    Notice    ppp    [wan] SECDNS 0.0.0.0   
2025-05-09T13:25:59    Notice    ppp    [wan] PRIDNS 0.0.0.0   
2025-05-09T13:25:59    Notice    ppp    [wan] IPADDR 0.0.0.0   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: SendConfigReq #2   
2025-05-09T13:25:59    Notice    ppp    [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: rec'd Configure Reject #1 (Ack-Sent)   
2025-05-09T13:25:59    Notice    ppp    [wan] IPV6CP: state change Req-Sent --> Ack-Sent   
2025-05-09T13:25:59    Notice    ppp    [wan] IPV6CP: SendConfigAck #1   
2025-05-09T13:25:59    Notice    ppp    [wan] IPV6CP: rec'd Configure Request #1 (Req-Sent)   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: state change Req-Sent --> Ack-Sent   
2025-05-09T13:25:59    Notice    ppp    [wan] IPADDR 195.190.228.6   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: SendConfigAck #1   
2025-05-09T13:25:59    Notice    ppp    [wan] 195.190.228.6 is OK   
2025-05-09T13:25:59    Notice    ppp    [wan] IPADDR 195.190.228.6   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: rec'd Configure Request #1 (Req-Sent)   
2025-05-09T13:25:59    Notice    ppp    [wan] IPV6CP: SendConfigReq #1   
2025-05-09T13:25:59    Notice    ppp    [wan] IPV6CP: state change Starting --> Req-Sent   
2025-05-09T13:25:59    Notice    ppp    [wan] IPV6CP: Up event   
2025-05-09T13:25:59    Notice    ppp    [wan] SECDNS 0.0.0.0   
2025-05-09T13:25:59    Notice    ppp    [wan] PRIDNS 0.0.0.0   
2025-05-09T13:25:59    Notice    ppp    [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid   
2025-05-09T13:25:59    Notice    ppp    [wan] IPADDR 0.0.0.0   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: SendConfigReq #1   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: state change Starting --> Req-Sent   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: Up event   
2025-05-09T13:25:59    Notice    ppp    [wan] IPV6CP: LayerStart   
2025-05-09T13:25:59    Notice    ppp    [wan] IPV6CP: state change Initial --> Starting   
2025-05-09T13:25:59    Notice    ppp    [wan] IPV6CP: Open event   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: LayerStart   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: state change Initial --> Starting   
2025-05-09T13:25:59    Notice    ppp    [wan] IPCP: Open event   
2025-05-09T13:25:59    Notice    ppp    [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] Link: Join bundle "wan"   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] Link: Matched action 'bundle "wan" ""'   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] LCP: authorization successful   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] MESG: Authentication success,Welcome!   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] PAP: rec'd ACK #1 len: 36   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] LCP: LayerUp   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] PAP: sending REQUEST #1 len: 17   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] PAP: using authname "internet"   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] LCP: auth: peer wants PAP, I want nothing   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] LCP: state change Ack-Sent --> Opened   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] MAGICNUM 0x31f33230   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] MRU 1500   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] LCP: rec'd Configure Ack #3 (Ack-Sent)   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] MAGICNUM 0x31f33230   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] MRU 1500   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] LCP: SendConfigReq #3   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] PROTOCOMP   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] LCP: rec'd Configure Reject #2 (Ack-Sent)   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] LCP: state change Req-Sent --> Ack-Sent   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] MAGICNUM 0xd120b8ad   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] AUTHPROTO PAP   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] MRU 1500   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] LCP: SendConfigAck #2   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] MAGICNUM 0xd120b8ad   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] AUTHPROTO PAP   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] MRU 1500   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] LCP: rec'd Configure Request #2 (Req-Sent)   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] MAGICNUM 0x31f33230   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] MRU 1500   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] PROTOCOMP   
2025-05-09T13:25:59    Notice    ppp    [wan_link0] LCP: SendConfigReq #2   
2025-05-09T13:25:57    Notice    kernel    <6>ng0: changing name to 'pppoe0'   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] MAGICNUM 0x31f33230   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] MRU 1500   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] PROTOCOMP   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] LCP: SendConfigReq #1   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] LCP: state change Starting --> Req-Sent   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] LCP: Up event   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] Link: UP event   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] PPPoE: connection successful   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] PPPoE: rec'd PPP-Max-Payload '1500'   
2025-05-09T13:25:57    Notice    ppp    PPPoE: rec'd ACNAME "195.190.228.6"   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] PPPoE: Connecting to ''   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] PPPoE: Set PPP-Max-Payload to '1500'   
2025-05-09T13:25:57    Warning    rtsold    <rtsock_input_ifannounce> interface ng0 removed   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] LCP: LayerStart   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] LCP: state change Initial --> Starting   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] LCP: Open event   
2025-05-09T13:25:57    Notice    ppp    [wan_link0] Link: OPEN event   
2025-05-09T13:25:57    Notice    ppp    [undefined] GetSystemIfaceMTU: SIOCGIFMTU failed: Device not configured   
2025-05-09T13:25:57    Notice    ppp    [wan] Bundle: Interface ng0 created   
2025-05-09T13:25:57    Notice    ppp    web: web is not running   
2025-05-09T13:25:57    Notice    ppp    process 67772 started, version 5.9   
2025-05-09T13:25:57    Notice    ppp        
2025-05-09T13:25:57    Notice    ppp    Multi-link PPP daemon for FreeBSD


Ah, thanks. then this is not my problem not getting an IP from my ISP. Keep looking. Thanks