1
24.7 Production Series / Re: Traceroute / ICMP issue after 24.7.1 update
« on: August 09, 2024, 12:59:36 pm »
Thx Franco for the clarification and your relentless commitment
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
24.7 Production Series / Re: Traceroute / ICMP issue after 24.7.1 update
« on: August 09, 2024, 12:53:17 pm »
So it is not a special kernel which should be generally used with opnsense in a Xen hypervisor scenario?
3
24.7 Production Series / Re: Traceroute / ICMP issue after 24.7.1 update
« on: August 09, 2024, 11:55:16 am »
# opnsense-update -zkr 24.7-xen3
I'll leave it there for a while longer then.
What are the differences and benefits of that "xen Kernel"?
4
24.7 Production Series / Re: OPNsense and KVM's Virtio Network Driver
« on: August 05, 2024, 12:43:08 am »
Your proxmox version is not the newest one:
https://www.proxmox.com/de/downloads/proxmox-virtual-environment
U have to upgrade as described on proxmox.
If that doesn't help, I'm sure there is a missconfiguration of your bridge(s) in proxmox. Have a look here:
https://homenetworkguy.com/how-to/virtualize-opnsense-on-proxmox-as-your-primary-router/
https://www.proxmox.com/de/downloads/proxmox-virtual-environment
U have to upgrade as described on proxmox.
If that doesn't help, I'm sure there is a missconfiguration of your bridge(s) in proxmox. Have a look here:
https://homenetworkguy.com/how-to/virtualize-opnsense-on-proxmox-as-your-primary-router/
5
24.7 Production Series / Re: Deutsche Telekom VDSL IPv6 having issues after upgrade to 24.7
« on: July 29, 2024, 12:57:11 pm »
Perhaps there are scripts that also restart other components depending on the radvd restart?
6
24.7 Production Series / Re: New Dashboard
« on: July 29, 2024, 10:51:10 am »
@OzziGoblin
Have you noticed that you can add more widgets to the dashboard, e.g. interface statistic? The view also depends how large you make the widgets.
Have you noticed that you can add more widgets to the dashboard, e.g. interface statistic? The view also depends how large you make the widgets.
7
24.7 Production Series / Re: New Dashboard
« on: July 29, 2024, 10:03:04 am »
Will there be widgets for speedtest and NTP be added?
They have been there in the old version of the dashboard.
They have been there in the old version of the dashboard.
8
24.7 Production Series / Re: [SOLVED] DHCP6 Gateway is shown as disconnected in 24.7
« on: July 29, 2024, 09:11:18 am »
Good morning,
I did a reboot meanwhile, the gateway settings are retained. gateway is shown online and the monitoring works. I'm still not sure, if this workaround with the VIP Ipv6 address in the gateway config is ok or not.
Also no idea why the automatic assigned IPv6 is detached, which maybe the reason that the gateway is offline / monitoring doesn't work.
If I can provide any logs let me know.
I did a reboot meanwhile, the gateway settings are retained. gateway is shown online and the monitoring works. I'm still not sure, if this workaround with the VIP Ipv6 address in the gateway config is ok or not.
Also no idea why the automatic assigned IPv6 is detached, which maybe the reason that the gateway is offline / monitoring doesn't work.
If I can provide any logs let me know.
9
24.7 Production Series / Re: Deutsche Telekom VDSL IPv6 having issues after upgrade to 24.7
« on: July 28, 2024, 02:31:54 pm »
I use unmanaged RA on all my VLANs for different devices (Linux, Android, MS Windows) and advertise the default gateway too. Works for me before and after the upgrade without problems.
10
24.7 Production Series / Re: [SOLVED] DHCP6 Gateway is shown as disconnected in 24.7
« on: July 28, 2024, 11:32:14 am »
Hi Franco, hi Patrick,
sorry for the confusing statement. ifconfig shows the automatically assigned and the VIP address in the CLI as described. The automatically assigned one is shown as detached.
What was meant was that after logging on to the CLI, only the IPv4 is displayed in the overview of interfaces for the WAN interface and no IPv6.
Incidentally, the gatway and the monitoring have been running stably since yesterday evening. However, I have not yet rebooted to see if this changes the configuration of the WAN_DHCP6 gateway.
sorry for the confusing statement. ifconfig shows the automatically assigned and the VIP address in the CLI as described. The automatically assigned one is shown as detached.
What was meant was that after logging on to the CLI, only the IPv4 is displayed in the overview of interfaces for the WAN interface and no IPv6.
Incidentally, the gatway and the monitoring have been running stably since yesterday evening. However, I have not yet rebooted to see if this changes the configuration of the WAN_DHCP6 gateway.
11
24.7 Production Series / Re: [SOLVED] DHCP6 Gateway is shown as disconnected in 24.7
« on: July 27, 2024, 08:26:49 pm »
Hi Franco,
I did further tests after applying the patch and a reboot. There is nothing better and nothing worth in my installation (Deutsche Telelkom business static IP). Everything with IPv6 is working only the gateway monitoring still didn't work.
Using DHCPv6 without selecting "Request Prefix only" results in
- WAN getting assigned an IPv6 address from my WAN net (/64) automatically, but still showed as detached in CLI
- WAN getting assigned the configured VIP IPv6 from my WAN net (/64) and shown in the GUI
- WAN_DHCP6 gateway is generated automatically with the automatically assigned gateway (fe80...) and it shows in the GUI offline (monitoring activated). Restarting dpinger, saving the gateway with changed selections etc. doesn't change anything
- LAN and other interfaces get there static IPv6
- IPv6 traffic works (pings to outside, my website is reachable via IPv6,...)
In CLI I can ping the IPv6 address used for gateway monitoring only via the VIP. Using the automatically assigned but detached IPv6 as source results in an error message
This brought me to the idea to change the automatically assigned IP address for the gateway in the configuration to the VIP I configured for the WAN interface. And after saving the monitoring works as expected and the gateway is shown as online.
One more hint, in CLI the WAN interface doesn't show any IPv6 address at all.
I dont't know if this kind of gateway configuration is completely bullshit, but maybe this information will help you to find out what is missing or maybe need some configuration changes.
If it is better to open a new post, let me know
Torsten
I did further tests after applying the patch and a reboot. There is nothing better and nothing worth in my installation (Deutsche Telelkom business static IP). Everything with IPv6 is working only the gateway monitoring still didn't work.
Using DHCPv6 without selecting "Request Prefix only" results in
- WAN getting assigned an IPv6 address from my WAN net (/64) automatically, but still showed as detached in CLI
- WAN getting assigned the configured VIP IPv6 from my WAN net (/64) and shown in the GUI
- WAN_DHCP6 gateway is generated automatically with the automatically assigned gateway (fe80...) and it shows in the GUI offline (monitoring activated). Restarting dpinger, saving the gateway with changed selections etc. doesn't change anything
- LAN and other interfaces get there static IPv6
- IPv6 traffic works (pings to outside, my website is reachable via IPv6,...)
In CLI I can ping the IPv6 address used for gateway monitoring only via the VIP. Using the automatically assigned but detached IPv6 as source results in an error message
Code: [Select]
ping: bind: Can't assign requested addressThis brought me to the idea to change the automatically assigned IP address for the gateway in the configuration to the VIP I configured for the WAN interface. And after saving the monitoring works as expected and the gateway is shown as online.
One more hint, in CLI the WAN interface doesn't show any IPv6 address at all.
I dont't know if this kind of gateway configuration is completely bullshit, but maybe this information will help you to find out what is missing or maybe need some configuration changes.
If it is better to open a new post, let me know
Torsten
12
24.7 Production Series / Re: [SOLVED] DHCP6 Gateway is shown as disconnected in 24.7
« on: July 27, 2024, 11:50:11 am »
@Franco
With which IPv6 configuration for the WAN interface should this patch be tested?
- DHCPv6 with or without selected "Request Prefix only"
- PPPOeV6
- SLAAC
With which IPv6 configuration for the WAN interface should this patch be tested?
- DHCPv6 with or without selected "Request Prefix only"
- PPPOeV6
- SLAAC
13
24.7 Production Series / Re: [SOLVED] DHCP6 Gateway is shown as disconnected in 24.7
« on: July 26, 2024, 11:28:34 pm »
Even after almost 5 hours the IPv6 address on my WAN interface is still detached and dpinger doesn't work.
Might this bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263986
still exists?
Might this bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263986
still exists?
14
24.7 Production Series / Re: No public ipv6 address after upgraded to 24.7
« on: July 26, 2024, 06:58:52 pm »
Which internet provider do you use?
15
24.7 Production Series / Re: [SOLVED] DHCP6 Gateway is shown as disconnected in 24.7
« on: July 26, 2024, 06:53:33 pm »After selecting the option dpinger starts instantly while the interface has just its fe80::/10 address. After some time the interface also holds a GUA, which again is outside the delegated IPv6 prefix.
I will try that configuration, maybe I was too impatient waiting for a GUA.
For Telekom you find in the "Business Kundencenter" following:
IPv6 (Öffentlich/WAN):2003:000a:XXXX:ff1f:0000:0000:0000:0000/64
IPv6 (Kundennetz/LAN):2003:000a:XXXX:1f00:0000:0000:0000:0000/56
So the delegated IPv6 should be an address out of the WAN/64, which is true for my installation.