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

Topics - juantxorena

#1
I opened a post a couple of days ago about ddclient not starting nor logging. Apparently, my configs weren't correct and it failed silently, so I lost a couple of days on that instead of it saying there were some problem.

Anyway, it starts now, and I've found the following problems, just checking if anybody has a solution and this "new and improved" version of a working plugin that caused no problems to anybody can get to a working state, or even feature parity:

- With the opnsense backend, there's no way of using an API token. The global token has to be used, otherwise it complains about:

error receiving ZoneID [[{"code": 6003, "message": "Invalid request headers", "error_chain": [{"code": 6103, "message": "Invalid format for X-Auth-Key header"}]}]]


Using global token instead of an API one is a serious security issue.

- When using more than one hostname in a config, it gives the error:
failed to set new ip XXXX [{"result":null,"success":false,"errors":[{"code":9000,"message":"DNS name is invalid."}],"messages":[]}]

- More importantly: I have some proxied domains and some unproxied. Updating them via opnsense backend set all of them as unproxied. There is an optional parameter in the body of the query (see here), but there's no way of setting it. I guess a frontend change should be made, and have a checkbox to control this.
#2
Hello everybody,

I'm trying to migrate from the working-but-soon-to-be-deprecated dyndns service to the new-but-barely-working ddclient for the 4th or 5th time. I'm using cloudflare with a DNS token and dual stack.

If I use the ddclient backend, it works, but it doesn't work dual stack, so it's useless for me. If I try the opnsense backend, which apparently supports dual stack, it refuses to start. I have applied the patch f920b48a94, as suggested in this link, but it doesn't fix anything.

I would like to post some logs or something, but there's nothing, nor in the ddclient logs, nor in the backend logs, nor in the console. If I try to start it from the console with /usr/local/sbin/pluginctl -s ddclient start it says Service `ddclient' has been started. but it doesn't really do it. /usr/local/sbin/pluginctl -s ddclient status says ddclient is not running.
#3
23.1 Legacy Series / os-ddclient does not update IPv4
February 12, 2023, 07:43:35 PM
Hello,

I have a domain with cloudflare, and I'm trying to update the dynamic IPs (both 4 and 6), but only IPv6 gets updated. I have tried all the IP check methods, with wildcard, without wildcard, a single entry, one entry for IPv4 and another for IPv6. It simply doesn't work. I attach a screenshot of my latest config attempt.

The old deprecated dyndns plugin works perfectly (and it has more options, a widget, actually works, and it's in general better).

Another thing is that the new ddclient occasionally stops working, and it's only fixed by restarting.
#4
22.1 Legacy Series / IPv6: static ULAs help
July 10, 2022, 01:22:11 PM
Hello everybody,

I'm having trouble configuring DHCPv6 for ULA.

I have a working ipv6 situation using SLAAC. I get a dynamic prefix from my ISP, and I have a bunch of VLANs tracking it, so the clients receive a couple of ipv6 addresses via SLAAC. Since the prefix is dynamic, I also have ULAs for internal network use. I have some virtual IPs with them, and the router advertisments configured so they give out the prefixes, and every client is also getting a couple of ULAs via SLAAC. I can put them in the override list of unbound and they are being used, I can ping, everything.

Because I want to have a server with some services, I thought I could try to configure DHCPv6 so it can give out static addresses to these services. Since I only want to use them from the internal network, I thought I would only distribute the ULAs with DHCPv6, and the global addresses with SLAAC (I wouldn't mind if SLAAC also gives ULAs and DHCPv6 GUAs).

When I activated the DHCPv6, I found no way for it to give out ULAs, no matter how I configured, it only gives GUAs. Then I saw this pull request https://github.com/opnsense/core/pull/5313, which looked that it could help. I used the following file for a VLAN (not the real prefix):

subnet6 fd01:2345:6789:abcd::/64 {
  # Range for clients
  range6 fd01:2345:6789:abcd:ffff:: fd01:2345:6789:abcd:ffff:ffff:ffff:ffff;

   # Range for clients requesting a temporary address
  range6 fd01:2345:6789:abcd::/64 temporary;

   # Additional options
  option dhcp6.name-servers fd01:2345:6789:abcd::;

  # Prefix range for delegation to sub-routers
  prefix6 fd01:2345:6789:abef:: fd01:2345:6789:abff::/60;
}



DHCPv6 fails to start with the following error:

Quote/status_services.php: The command '/usr/local/sbin/dhcpd -6 -user dhcpd -group dhcpd -chroot /var/dhcpd -cf /etc/dhcpdv6.conf -pf /var/run/dhcpdv6.pid igb2_vlan20 igb2_vlan50 igb2_vlan30 igb2_vlan128' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.4.2-P1 Copyright 2004-2021 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Config file: /etc/dhcpdv6.conf Database file: /var/db/dhcpd6.leases PID file: /var/run/dhcpdv6.pid Wrote 3 NA, 0 TA, 0 PD leases to lease file. Interface igb2_vlan20 matches multiple shared networks If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging. exiting.'

Commenting the different config lines doesn't help (I'm not sure if it was properly configured). Removing the ULA prefix from the router advertisments doesn't help neiter. Only removing the virtual IP for this VLAN allows it to start, but then DHCPv6 doesn't give out any ULA address, and ipv6 with ULAs stops working.

Could somebody help me to configure it, or maybe tell me another way of achieving what I want, static ULAs?

Thanks in advance
#5
Hello everybody,

IPv6 from the local network to the internet suddenly stopped working. I'm not sure exactly when, but probably when I updated to 22.1 some days ago. In the local network, it works as expected.

What works:

- WAN gets an IPv6 address and a prefix
- All the clients of the VLANs get a proper IPv6 address within the subprefix (actually more than one)
- All the clients get an ULA, which I configured using virtual IPs and router advertisements (and that worked before)
- Clients can communicate between each other using IPv6, both with ULAs and GUAs, respecting the firewall rules

What doesn't work:

- Clients cannot communicate with the internet with IPv6, e.g. pinging google.com fails, no message, just 100% packet loss
- However, I can IPv6 ping from the firewall to the outside and it works: Interfaces -> Diagnostics -> Ping, pinging to google.com with MAIN as the source address (that's the main VLAN, where computer, phones, etc are) works
- Running e.g. https://ipv6-test.com/ from any client says there is no IPv6 connectivity

What I've tried:

- Deactivating firewall rules
- Deactivating virtual IPs and ULAs
- Deactivating manual router advertisements
- Changing types of RA (assisted, managed, stateless, etc)
- Restarting multiple times

I suspect opnsense is failing to route properly. I captured the packages in both MAIN and WAN interfaces while trying to ping from my computer to google.com. The pings packets appear in both captures, and it says: [Expert Info (Warning/Sequence): No response seen to ICMPv6 request in frame 3]

Gateways and routes are with the default values.

Thanks for the help.
#6
I have a local network with a bunch of hosts composed of linux, windows and android clients. I'm trying to have ipv6 working locally with DNS resolution. i.e., I want to be able to e.g. go to local-computer.local-domain.com, and have the DNS server resolve its IPv6 address, and access using it. Because of android, I am forced to use, or at least support, SLAAC.

My current setup:


  • OPNsense
  • Unbound - I am open to use any other DNS server if that solves the problem
  • I have a /56 IPv6 DYNAMIC prefix from my ISP, no possibility to make it static (also, I don't want to change everything if I change ISP)
  • Multiple VLANs, with ipv6 configured via tracking interface
  • I have static ipv4 addresses for most hosts of my network via DHCPv4, which also assigns a hostname, correctly and automatically registered in unbound

What works:

  • DNS IPv4 resolution in the local network
  • Every host have (at least one) an ipv6 address
  • Hosts can use ipv6 locally: they can ping, ssh, whatever
  • Hosts can access the internet with ipv6: when going to google.com it resolves to the ipv6 address and it works

What doesn't work:

  • Hosts accessing the local network with hostnames and ipv6
What I have tried:

  • After reading a lot , I think that one solution is to set ULA for the VLANS.
  • I have set virtual IPs with an ULA for each VLAN, in fd::. It works, meaning that the hosts get at least one ULA address. However, I don't know what to do with it. Honestly I haven't tried to set up firewall rules with them, but if I set them using them, would it work, considering they also have more addresses? I mean, if I put a rule that says "hosts with address fdULA:address:of:IOT:VLAN" cannot comunicate with "hosts with address fdULA:address:of:IOT:MANAGEMENT", wouldn't they be able to send things to MANAGEMENT since they have other addresses not related to ULA?
  • In any case, despite having ULA addresses, I don't know what to do with it, or how it solves my problem. I cannot set static ULA addresses in DHCPv6 because they are "virtual" addresses, and it complains about "A valid range must be specified."
  • I think I would have the same DNS problem as before, the addresses won't be registered in the DNS server.

What I'm trying:

  • Apparently mdns is an important thing with IPv6. However, I would like to keep using a normal DNS server, because I might have things (usually IoT things) that don't understand mdns. What I thought was to let the mdns devices send their multicast, and have the DNS server get them and register them, so it will answer to normal DNS requests. However it seems that that's quite a weird thing to do and it's not supported anywhere, so if I go with that route, I would have to do a script or something.
  • I have found this thing that looks it could help: http://www.dns-sd.org/ , but I have no idea what to do with it, or how to implement it.

Other possibilities:

  • Use only ULA for the internal network, and use NPT for translating it to the external prefix. However, AFAIK OPNsense doesn't support dynamic prefixes in NPT, making it useless.
  • Use IPv4 internally, but allow hosts to have IPv6 addresses for communicating with the exterior. The more I try things, and the more I learn about IPv6, the more I like this solution. I don't see how can I implement it, though, it looks that is either IPv6 for everything, or for nothing. I would have to force the DNS server to give only IPv4 addresses internally, or something.

I'm a bit surprised that I haven't found anything on the internet about this, it seems like a quite basic thing to do. Here are some links I've read and haven't helped. I have read way more things, but I cannot find them right now:
https://www.reddit.com/r/OPNsenseFirewall/comments/gnsa1t/multiple_ipv6_prefixes_per_interface/
https://forum.opnsense.org/index.php?topic=15529.0
#7
Hi all,

Since some time (I cannot exactly pinpoint when, but at least a couple of months), I have this problem where the local nets loss IPv6 connectivity after exactly 4 hours. It is restored after reconfiguring the WAN interface (or reconnecting in Interfaces -> Overview). Restarting radvd doesn't do anything. The WAN interface still has a working IPv6 address, however.

When this happens, the service dhcpd6 is down and cannot be (re)started. If I try to start it from the console, I get the following:
Quote
/usr/local/etc/rc.d/dhcp6c: WARNING: /usr/local/etc/dhcp6c.conf is not readable.

that file doesn't exist, btw.

My setup:

ISP: Telekom in Germany, known for not providing static IPv6 addreses or prefixes.

WAN Interface, connecting using PPPoE and a Draytek Vigor 165 modem in bridge mode:
Request only an IPv6 prefix: true
Prefix delegation size: 56
Send IPv6 prefix hint: true
Use IPv4 connectivity: true
Prevent release: true

Local interfaces: A bunch of VLANs, all of them tracking the WAN interface with different prefixes.

DHCPv6, router advertisments, etc. are all running with the default values.

I'm currently running radvd 2.19 because I thought it may be related to the famous bug https://github.com/opnsense/core/issues/4338, but no luck. I also ran the rtadvd patch of the same bug, with same result. I can attach the full system, routing and dhcp logs for a period of ~4 hours between a restart of the interface and the loss of IPv6 if needed, for now I'll post the things I think are relevant (max debug settings), when IPv6 is lost

system:

2021-01-17T21:29:38 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=9, retrans=115332
2021-01-17T21:29:38 dhcp6c[83558] transmit failed: No route to host
2021-01-17T21:29:38 dhcp6c[83558] set IA_PD
2021-01-17T21:29:38 dhcp6c[83558] set IA_PD prefix
2021-01-17T21:29:38 dhcp6c[83558] set option request (len 4)
2021-01-17T21:29:38 dhcp6c[83558] set elapsed time (len 2)
2021-01-17T21:29:38 dhcp6c[83558] set identity association
2021-01-17T21:29:38 dhcp6c[83558] set client ID (len 14)
2021-01-17T21:29:12 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=129, retrans=127656
2021-01-17T21:29:12 dhcp6c[83558] transmit failed: No route to host
2021-01-17T21:29:12 dhcp6c[83558] set option request (len 4)
2021-01-17T21:29:12 dhcp6c[83558] set elapsed time (len 2)
2021-01-17T21:29:12 dhcp6c[83558] set identity association
2021-01-17T21:29:12 dhcp6c[83558] set client ID (len 14)
2021-01-17T21:27:26 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=8, retrans=131892
2021-01-17T21:27:26 dhcp6c[83558] transmit failed: No route to host
2021-01-17T21:27:26 dhcp6c[83558] set IA_PD
2021-01-17T21:27:26 dhcp6c[83558] set IA_PD prefix
2021-01-17T21:27:26 dhcp6c[83558] set option request (len 4)
2021-01-17T21:27:26 dhcp6c[83558] set elapsed time (len 2)
2021-01-17T21:27:26 dhcp6c[83558] set identity association
2021-01-17T21:27:26 dhcp6c[83558] set client ID (len 14)
2021-01-17T21:27:18 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=128, retrans=113724
2021-01-17T21:27:18 dhcp6c[83558] transmit failed: No route to host
2021-01-17T21:27:18 dhcp6c[83558] set option request (len 4)
2021-01-17T21:27:18 dhcp6c[83558] set elapsed time (len 2)
2021-01-17T21:27:18 dhcp6c[83558] set identity association
2021-01-17T21:27:18 dhcp6c[83558] set client ID (len 14)
2021-01-17T21:25:28 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=7, retrans=118056
2021-01-17T21:25:28 dhcp6c[83558] transmit failed: No route to host
2021-01-17T21:25:28 dhcp6c[83558] set IA_PD
2021-01-17T21:25:28 dhcp6c[83558] set IA_PD prefix
2021-01-17T21:25:28 dhcp6c[83558] set option request (len 4)
2021-01-17T21:25:28 dhcp6c[83558] set elapsed time (len 2)
2021-01-17T21:25:28 dhcp6c[83558] set identity association
2021-01-17T21:25:28 dhcp6c[83558] set client ID (len 14)
2021-01-17T21:25:14 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=127, retrans=124500
2021-01-17T21:25:14 dhcp6c[83558] transmit failed: No route to host
2021-01-17T21:25:14 dhcp6c[83558] set option request (len 4)
2021-01-17T21:25:14 dhcp6c[83558] set elapsed time (len 2)
2021-01-17T21:25:14 dhcp6c[83558] set identity association
2021-01-17T21:25:14 dhcp6c[83558] set client ID (len 14)
2021-01-17T21:24:38 dhcp6c[83558] removing an event on pppoe0, state=REBIND
2021-01-17T21:24:28 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=6, retrans=60193
2021-01-17T21:24:28 dhcp6c[83558] transmit failed: No route to host
2021-01-17T21:24:28 dhcp6c[83558] set IA_PD
2021-01-17T21:24:28 dhcp6c[83558] set IA_PD prefix
2021-01-17T21:24:28 dhcp6c[83558] set option request (len 4)
2021-01-17T21:24:28 dhcp6c[83558] set elapsed time (len 2)
2021-01-17T21:24:28 dhcp6c[83558] set identity association
2021-01-17T21:24:28 dhcp6c[83558] set client ID (len 14)
2021-01-17T21:23:57 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=5, retrans=30329
2021-01-17T21:23:57 dhcp6c[83558] transmit failed: No route to host
2021-01-17T21:23:57 dhcp6c[83558] set IA_PD
2021-01-17T21:23:57 dhcp6c[83558] set IA_PD prefix
2021-01-17T21:23:57 dhcp6c[83558] set option request (len 4)
2021-01-17T21:23:57 dhcp6c[83558] set elapsed time (len 2)
2021-01-17T21:23:57 dhcp6c[83558] set identity association
2021-01-17T21:23:57 dhcp6c[83558] set client ID (len 14)
2021-01-17T21:23:42 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=4, retrans=15552
2021-01-17T21:23:42 dhcp6c[83558] transmit failed: No route to host
2021-01-17T21:23:42 dhcp6c[83558] set IA_PD
2021-01-17T21:23:42 dhcp6c[83558] set IA_PD prefix
2021-01-17T21:23:42 dhcp6c[83558] set option request (len 4)
2021-01-17T21:23:42 dhcp6c[83558] set elapsed time (len 2)
2021-01-17T21:23:42 dhcp6c[83558] set identity association
2021-01-17T21:23:42 dhcp6c[83558] set client ID (len 14)
2021-01-17T21:23:34 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=3, retrans=7950
2021-01-17T21:23:34 dhcp6c[83558] transmit failed: No route to host
2021-01-17T21:23:34 dhcp6c[83558] set IA_PD
2021-01-17T21:23:34 dhcp6c[83558] set IA_PD prefix
2021-01-17T21:23:34 dhcp6c[83558] set option request (len 4)
2021-01-17T21:23:34 dhcp6c[83558] set elapsed time (len 2)
2021-01-17T21:23:34 dhcp6c[83558] set identity association
2021-01-17T21:23:34 dhcp6c[83558] set client ID (len 14)
2021-01-17T21:23:30 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=2, retrans=4145
2021-01-17T21:23:30 dhcp6c[83558] transmit failed: No route to host
2021-01-17T21:23:30 dhcp6c[83558] set IA_PD
2021-01-17T21:23:30 dhcp6c[83558] set IA_PD prefix
2021-01-17T21:23:30 dhcp6c[83558] set option request (len 4)
2021-01-17T21:23:30 dhcp6c[83558] set elapsed time (len 2)
2021-01-17T21:23:30 dhcp6c[83558] set identity association
2021-01-17T21:23:30 dhcp6c[83558] set client ID (len 14)
2021-01-17T21:23:27 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=1, retrans=2116
2021-01-17T21:23:27 dhcp6c[83558] transmit failed: No route to host
2021-01-17T21:23:27 dhcp6c[83558] set IA_PD
2021-01-17T21:23:27 dhcp6c[83558] set IA_PD prefix
2021-01-17T21:23:27 dhcp6c[83558] set option request (len 4)
2021-01-17T21:23:27 dhcp6c[83558] set elapsed time (len 2)
2021-01-17T21:23:27 dhcp6c[83558] set identity association
2021-01-17T21:23:27 dhcp6c[83558] set client ID (len 14)
2021-01-17T21:23:26 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=0, retrans=1046
2021-01-17T21:23:26 dhcp6c[83558] transmit failed: No route to host
2021-01-17T21:23:26 dhcp6c[83558] set IA_PD
2021-01-17T21:23:26 dhcp6c[83558] set IA_PD prefix
2021-01-17T21:23:26 dhcp6c[83558] set option request (len 4)
2021-01-17T21:23:26 dhcp6c[83558] set elapsed time (len 2)
2021-01-17T21:23:26 dhcp6c[83558] set identity association
2021-01-17T21:23:26 dhcp6c[83558] set client ID (len 14)
2021-01-17T21:23:26 dhcp6c[83558] a new XID (c66c0e) is generated
2021-01-17T21:23:26 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=126, retrans=108036
2021-01-17T21:23:26 dhcp6c[83558] transmit failed: No route to host
2021-01-17T21:23:26 dhcp6c[83558] set option request (len 4)
2021-01-17T21:23:26 dhcp6c[83558] set elapsed time (len 2)
2021-01-17T21:23:26 dhcp6c[83558] set identity association
2021-01-17T21:23:26 dhcp6c[83558] set client ID (len 14)
2021-01-17T21:23:26 dhcp6c[83558] remove a site prefix 2003:f6:1720:b300::/56
2021-01-17T21:23:26 dhcp6c[83558] prefix timeout for 2003:f6:1720:b300::/56
2021-01-17T21:21:27 dhcp6c[83558] reset a timer on pppoe0, state=SOLICIT, timeo=125, retrans=118908

routing:

2021-01-17T21:27:04 radvd[81185] processed RA on igb1_vlan20
2021-01-17T21:27:04 radvd[81185] igb1_vlan20 received RA from: fe80::2e0:67ff:fe21:15e0 (myself)
2021-01-17T21:27:04 radvd[81185] igb1_vlan20 received a packet
2021-01-17T21:27:04 radvd[81185] igb1_vlan20 recvmsg len=104
2021-01-17T21:27:04 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:27:04 rtsold[10889] <rtsol_input> received RA from fe80::2e0:67ff:fe21:15e0 on an unexpected IF(igb1_vlan20)
2021-01-17T21:27:04 radvd[81185] polling for 43.857 second(s), next iface is igb1_vlan128
2021-01-17T21:27:04 radvd[81185] igb1_vlan20 processed an RS
2021-01-17T21:27:04 radvd[81185] igb1_vlan20 next scheduled RA in 447.997 second(s)
2021-01-17T21:27:04 radvd[81185] sending RA to ff02::1 on igb1_vlan20 (fe80::2e0:67ff:fe21:15e0), 5 options (using 104/1224 bytes)
2021-01-17T21:27:04 radvd[81185] checking ipv6 forwarding not supported
2021-01-17T21:27:04 radvd[81185] igb1_vlan20 is ready
2021-01-17T21:27:04 radvd[81185] igb1_vlan20 address: fe80::2e0:67ff:fe21:15e0
2021-01-17T21:27:04 radvd[81185] igb1_vlan20 linklocal address: fe80::2e0:67ff:fe21:15e0
2021-01-17T21:27:04 radvd[81185] checking ipv6 forwarding of interface not supported
2021-01-17T21:27:04 radvd[81185] prefix length for igb1_vlan20 is -1
2021-01-17T21:27:04 radvd[81185] link layer token length for igb1_vlan20 is 48
2021-01-17T21:27:04 radvd[81185] mtu for igb1_vlan20 is 1500
2021-01-17T21:27:04 radvd[81185] igb1_vlan20 supports multicast or is point-to-point
2021-01-17T21:27:04 radvd[81185] igb1_vlan20 is running
2021-01-17T21:27:04 radvd[81185] igb1_vlan20 is up
2021-01-17T21:27:04 radvd[81185] ioctl(SIOCGIFFLAGS) succeeded on igb1_vlan20
2021-01-17T21:27:04 radvd[81185] igb1_vlan20 received RS from: ::
2021-01-17T21:27:04 radvd[81185] igb1_vlan20 received a packet
2021-01-17T21:27:04 radvd[81185] igb1_vlan20 recvmsg len=8
2021-01-17T21:27:02 radvd[81185] polling for 19.184 second(s), next iface is igb1_vlan20
2021-01-17T21:27:02 radvd[81185] igb0 received icmpv6 RS/RA packet on an unknown interface with index 1
2021-01-17T21:27:02 radvd[81185] igb0 received a packet
2021-01-17T21:27:02 radvd[81185] igb0 recvmsg len=104
2021-01-17T21:27:02 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:27:02 rtsold[10889] <rtsol_input> received RA from fe80::2e0:67ff:fe21:15e0 on an unexpected IF(igb0)
2021-01-17T21:27:02 radvd[81185] polling for 19.184 second(s), next iface is igb1_vlan20
2021-01-17T21:27:02 radvd[81185] processed RA on igb1
2021-01-17T21:27:02 radvd[81185] igb1 received RA from: fe80::2e0:67ff:fe21:15e0 (myself)
2021-01-17T21:27:02 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:27:02 radvd[81185] igb1 received a packet
2021-01-17T21:27:02 rtsold[10889] <rtsol_input> received RA from fe80::2e0:67ff:fe21:15e0 on an unexpected IF(igb1)
2021-01-17T21:27:02 radvd[81185] igb1 recvmsg len=104
2021-01-17T21:27:02 radvd[81185] polling for 19.184 second(s), next iface is igb1_vlan20
2021-01-17T21:27:02 radvd[81185] igb1 next scheduled RA in 545.178 second(s)
2021-01-17T21:27:02 radvd[81185] sending RA to ff02::1 on igb1 (fe80::2e0:67ff:fe21:15e0), 5 options (using 104/1210 bytes)
2021-01-17T21:27:02 radvd[81185] checking ipv6 forwarding not supported
2021-01-17T21:27:02 radvd[81185] igb1 is ready
2021-01-17T21:27:02 radvd[81185] igb1 address: fe80::2e0:67ff:fe21:15e0
2021-01-17T21:27:02 radvd[81185] igb1 linklocal address: fe80::2e0:67ff:fe21:15e0
2021-01-17T21:27:02 radvd[81185] checking ipv6 forwarding of interface not supported
2021-01-17T21:27:02 radvd[81185] prefix length for igb1 is 64
2021-01-17T21:27:02 radvd[81185] link layer token length for igb1 is 48
2021-01-17T21:27:02 radvd[81185] mtu for igb1 is 1500
2021-01-17T21:27:02 radvd[81185] igb1 supports multicast or is point-to-point
2021-01-17T21:27:02 radvd[81185] igb1 is running
2021-01-17T21:27:02 radvd[81185] igb1 is up
2021-01-17T21:27:02 radvd[81185] ioctl(SIOCGIFFLAGS) succeeded on igb1
2021-01-17T21:27:02 radvd[81185] timer_handler called for igb1
2021-01-17T21:24:55 radvd[81185] polling for 127.233 second(s), next iface is igb1
2021-01-17T21:24:55 radvd[81185] pppoe0 received icmpv6 RS/RA packet on an unknown interface with index 15
2021-01-17T21:24:55 radvd[81185] pppoe0 received a packet
2021-01-17T21:24:55 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:24:55 rtsold[10889] <rtsol_input> received RA from fe80::9ecc:83ff:fe81:ea6e on an unexpected IF(pppoe0)
2021-01-17T21:24:55 radvd[81185] pppoe0 recvmsg len=96
2021-01-17T21:23:26 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 13, len=164
2021-01-17T21:23:26 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 2, len=272
2021-01-17T21:23:26 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 2, len=344
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 13, len=164
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 2, len=272
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 2, len=344
2021-01-17T21:23:26 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:23:26 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 2, len=344
2021-01-17T21:23:26 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 13, len=164
2021-01-17T21:23:26 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 2, len=272
2021-01-17T21:23:26 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 2, len=344
2021-01-17T21:23:26 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 13, len=164
2021-01-17T21:23:26 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 2, len=272
2021-01-17T21:23:26 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 2, len=344
2021-01-17T21:23:26 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 13, len=164
2021-01-17T21:23:26 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:23:26 rtsold[10889] <rtsock_input> rtmsg type 2, len=272
2021-01-17T21:23:25 radvd[81185] polling for 217.167 second(s), next iface is igb1
2021-01-17T21:23:25 radvd[81185] processed RA on igb1_vlan20
2021-01-17T21:23:25 radvd[81185] igb1_vlan20 received RA from: fe80::2e0:67ff:fe21:15e0 (myself)
2021-01-17T21:23:25 radvd[81185] igb1_vlan20 received a packet
2021-01-17T21:23:25 radvd[81185] igb1_vlan20 recvmsg len=104
2021-01-17T21:23:25 rtsold[10889] <rtsol_check_timer> there is no timer
2021-01-17T21:23:25 rtsold[10889] <rtsol_input> received RA from fe80::2e0:67ff:fe21:15e0 on an unexpected IF(igb1_vlan20)
2021-01-17T21:23:25 radvd[81185] polling for 217.167 second(s), next iface is igb1
2021-01-17T21:23:25 radvd[81185] igb1_vlan20 processed an RS
2021-01-17T21:23:25 radvd[81185] igb1_vlan20 next scheduled RA in 236.363 second(s)
2021-01-17T21:23:25 radvd[81185] sending RA to ff02::1 on igb1_vlan20 (fe80::2e0:67ff:fe21:15e0), 5 options (using 104/1224 bytes)
2021-01-17T21:23:25 radvd[81185] checking ipv6 forwarding not supported
2021-01-17T21:23:25 radvd[81185] igb1_vlan20 is ready
2021-01-17T21:23:25 radvd[81185] igb1_vlan20 address: fe80::2e0:67ff:fe21:15e0
2021-01-17T21:23:25 radvd[81185] igb1_vlan20 address: 2003:f6:1720:b314:2e0:67ff:fe21:15e0
2021-01-17T21:23:25 radvd[81185] igb1_vlan20 linklocal address: fe80::2e0:67ff:fe21:15e0


I don't have a radvdump file, but after the error happens, it losses the lines for the prefix and RDNSS.

I also have tcpdump files for this 4 hour period of all the interfaces, I can attach them by request. Surprisingly, the capture for the pppoe interface is empty.

One thing that bothers me, that may or may not be related, are all the "dhcp6c[83558]   transmit failed: No route to host" messages that appear in the system log. They are also there when the WAN interface is reconnected and the IPv6 are running.

When I have time, I may start with a fresh opnsense installation from scratch, maybe is some wrongly configured thing somewhere, but I would like to avoid it if possible, since I'm working from home and need internet.

Thanks for the help.