1
23.1 Legacy Series / Re: IPV6 not routing after update to 23.1.5_4
« on: April 24, 2023, 03:04:42 am »
i have found this to be hit or miss. have you rebooted? I am staying on .4 for now.
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.
2
23.1 Legacy Series / Re: IPV6 not routing after update to 23.1.5_4
« on: April 05, 2023, 03:45:02 am »3
23.1 Legacy Series / Re: IPv6 routing problem after update to 23.1.5_4
« on: April 05, 2023, 01:52:06 am »4
23.1 Legacy Series / Re: IPV6 not routing after update to 23.1.5_4
« on: April 02, 2023, 03:09:37 pm »
Summery of problem
Ping for client:
to router LAN RE(0) 2603:: address No
to router LAN RE(0) fe80:: address Yes
to any other client Lan 2603:: Address Yes
to any internet ipv6 address no
Ping from router:
to router LAN RE(0) 2603:: address No
to router LAN RE(0) fe80:: address Yes
to any client LAN 2603:: No ping: UDP connect: Network is unreachable
to any internet ipv6 address Yes with DNS name resolution
The router WAN RE(1) is fully functional.
The router LAN RE(0) ISP assigned address is not honored.
Attached log with errors
Ping for client:
to router LAN RE(0) 2603:: address No
to router LAN RE(0) fe80:: address Yes
to any other client Lan 2603:: Address Yes
to any internet ipv6 address no
Ping from router:
to router LAN RE(0) 2603:: address No
to router LAN RE(0) fe80:: address Yes
to any client LAN 2603:: No ping: UDP connect: Network is unreachable
to any internet ipv6 address Yes with DNS name resolution
The router WAN RE(1) is fully functional.
The router LAN RE(0) ISP assigned address is not honored.
Attached log with errors
5
23.1 Legacy Series / Re: IPV6 not routing after update to 23.1.5_4
« on: April 01, 2023, 07:00:03 pm »
Update:
I can ping from opnsense to the internet with name resolution.
I cannot ping a lan address from opnsense. there is something going on with the lan(re0) interface
I can ping from opnsense to the internet with name resolution.
Code: [Select]
root@rtr:~ # ping -6 www.opnsense.org
PING6(56=40+8+8 bytes) 2607:fcc8:bfc0:30:bd23:9401:4a3e:5d78 --> 2001:1af8:4700:a1fa:3::2
16 bytes from 2001:1af8:4700:a1fa:3::2, icmp_seq=0 hlim=46 time=110.054 ms
16 bytes from 2001:1af8:4700:a1fa:3::2, icmp_seq=1 hlim=46 time=110.434 ms
^C
--- www.opnsense.org ping6 statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 110.054/110.244/110.434/0.190 msI cannot ping a lan address from opnsense. there is something going on with the lan(re0) interface
Code: [Select]
root@rtr:~ # ping xxxx:xxxx:xxxx:xxxx::148
ping: UDP connect: Network is unreachable
6
23.1 Legacy Series / IPV6 not routing after update to 23.1.5_4
« on: April 01, 2023, 03:17:16 pm »
The simplest description is that i cannot pint the router using ipv6. needless to say I cannot contact the internet via ipv6. 23.1.4 worked, other prior versions also had the same problem.
Code: [Select]
Pinging rtr.bs.net [xxxx:xxxx:xxxx:xxxx:201:2eff:fea3:a866] with 32 bytes of data:
Destination host unreachable.
Request timed out.
Destination host unreachable.
Destination host unreachable.
Ping statistics for xxxx:xxxx:xxxx:xxxx:201:2eff:fea3:a866:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
7
23.1 Legacy Series / Re: ipv6 trouble here as well, dhcpd6 dies
« on: February 28, 2023, 11:11:47 pm »
Yes, same problem if the modem reboots either by itself or if I manually reboot it DHCPD6 goes down and must be started. RADVD must also be restarted and then connectivity is restored.
The mods might be missing this and other posts as they might think its related to the PPPOE DHCPD6 problem that I believe they have fixed.
The mods might be missing this and other posts as they might think its related to the PPPOE DHCPD6 problem that I believe they have fixed.
8
23.1 Legacy Series / Re: DHCPv6 prefix not updated after nightly forced disconnect
« on: February 20, 2023, 05:47:10 pm »
did you have to start dhcpd6?
Never mind I see you are not using dhcpd6. Duh!
Never mind I see you are not using dhcpd6. Duh!
9
23.1 Legacy Series / Re: DHCPv6 prefix not updated after nightly forced disconnect
« on: February 20, 2023, 04:27:43 pm »
@franco, can you help? What logs should I collect to file a bug report?
Thanks,
Al
Thanks,
Al
10
23.1 Legacy Series / Re: DHCPv6 prefix not updated after nightly forced disconnect
« on: February 18, 2023, 12:17:34 am »
Me to, after a cable modem reboot on v23.1_6. dhcpd6 goes down. Must restart radvd and dhcpd6
11
23.1 Legacy Series / Re: Wireguard kernel not working like it should
« on: January 27, 2023, 02:49:10 pm »
Thank you Franco, The patch worked.
Al
Al
12
23.1 Legacy Series / Re: Wireguard
« on: January 26, 2023, 07:37:23 pm »
The services monitor. I could be wrong but i thought the service monitor was widget. not to be confused with the wireguard widget.
Al
Al
13
23.1 Legacy Series / Re: Wireguard
« on: January 26, 2023, 07:23:09 pm »
Yes, the dashboard widget is still monitoring the wireguard-go service and not the kernel module. It would be nice if the dashboard widget monitored the kernel module and allowed us to start stop and restart the kernel module, if possible.
Thanks,
Al
Thanks,
Al
14
23.1 Legacy Series / Re: No wireguard-go after upgrade to 23.1
« on: January 26, 2023, 05:25:44 pm »15
23.1 Legacy Series / Re: Wireguard
« on: January 15, 2023, 03:13:03 pm »
Thanks, that worked. I am hoping that we will be able to see the kmod status at some point.