Recent posts

#1

25.7, 25.10 Series / Re: Reporting logs: comma in t...

Last post by SenseX - Today at 11:09:39 AM

Are you referring to the comma after the date number, "December 11, 2025"? Are there other commas I am not seeing in the images?

That is one of the standard (i.e. common) date formats.

Hi,
It's not the date. The other numbers: First image:

user: 2,304   <------ 2,3 or 2304?
nice: 0
system: 1,59       <------ 1,59 or 159 ?
interrupt: 0
processes: 370,081       <------ What is this, 370 or 370,081 (three hundred seventy thousand and eighty-one)


Second image: System Information - Quality | WAN_DHCP   (ping)

Delay: 0,002      < ------ Belive this should be the ping in ms, so my ping to the gateway on the widget is 2.3ms and I was thing this number should also be 2.3 and not 0,002. The Quality should show you the real RTT to what every you are pinging from your gateway.

#2

25.7, 25.10 Series / Re: PPPoE link only comes up a...

Last post by chemlud - Today at 10:44:36 AM

https://www.startpage.com/do/dsearch?q=problem+pppoe+opnsense&cat=web&language=english

and so...

https://www.youtube.com/watch?v=pAyKJAtDNCw

I know, it's not really giving comfort, but...

#3

General Discussion / Re: Gateway Monitoring and Pac...

Last post by OPNenthu - Today at 08:16:13 AM

The chart is showing delay in seconds, so 0.002 means 2ms.

#4

25.7, 25.10 Series / Re: PPPoE link only comes up a...

Last post by ToasterPC - Today at 07:02:53 AM

Bump

#5

25.7, 25.10 Series / Re: WAN load balancing behavio...

Last post by OPNenthu - Today at 06:12:40 AM

I might be asking my question the wrong way or presenting too much detail.

tldr; I have two active VPN gateways that each work on their own, but when put into a load balancing group only one seems to be in use the majority of the time.  When I first set this up (sometime before 25.7.6, I think) the load balancing was working, so I don't know if something changed in recent versions or if the "problem exists between keyboard and chair" as they say.

Appreciate any tips on what to look into.

#6

Hardware and Performance / Re: [solved] Intel i226 Firmwa...

Last post by OPNenthu - Today at 06:02:29 AM

It Just Works™ in Linux.  Nothing needed besides the NIC driver (built in) and userspace tools like NetworkManager.

I have an i225-v on my client PC and I'm not having any issue with vlan and bridge interfaces for sharing a tagged trunk between my host and some guest VMs.

Code Select Expand

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp6s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq state DOWN group default qlen 1000
    link/ether 78:xx:xx:xx:xx:55 brd ff:ff:ff:ff:ff:ff
3: enp10s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP group default qlen 1000
    link/ether 24:xx:xx:xx:xx:cd brd ff:ff:ff:ff:ff:ff
4: enp10s0.20@enp10s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br20 state UP group default qlen 1000
    link/ether 24:xx:xx:xx:xx:cd brd ff:ff:ff:ff:ff:ff
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 24:xx:xx:xx:xx:cd brd ff:ff:ff:ff:ff:ff
    inet 172.21.30.100/24 brd 172.21.30.255 scope global dynamic noprefixroute br0
       valid_lft 62774sec preferred_lft 62774sec
    inet6 2601:xx:xxxx:xxxx:944a:5d1:1c72:95a2/64 scope global temporary dynamic
       valid_lft 86390sec preferred_lft 19546sec
    inet6 2601:xx:xxxx:xxxx:xxxx:xxxx:xxxx:c3d/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 86390sec preferred_lft 86390sec
    inet6 fe80::xxx:xxxx:xxxx:fb89/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
6: br20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a2:xx:xx:xx:xx:5a brd ff:ff:ff:ff:ff:ff
7: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:xx:xx:xx:xx:76 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever


#7

General Discussion / Re: PSA: recent Comcast firmwa...

Last post by OPNenthu - Today at 05:51:21 AM

IPv6-PD is not commonly used and it is not actively monitored-at least by Tier 1 support since they told me their diagnostics all show green.

If that's the case for business accounts... then the fact that IPv6-PD works at all for my home connection is something of a miracle and I'm on my own.

Great.

#8

25.7, 25.10 Series / Re: How to prevent outside use...

Last post by Redmond - Today at 05:23:24 AM

Fair.

Thats all I see if i filter for the translated prefix.

I setup Tayga with https://docs.opnsense.org/manual/how-tos/tayga.html . I'm trying to go IPv6-Mostly, so I do use Tayga as a CLAT on my desktop for 464XLAT.

It isn't just ICMPv6 messages getting in. But Live View doesn't show it.

#9

25.7, 25.10 Series / Re: How to prevent outside use...

Last post by Maurice - Today at 04:07:13 AM

The screenshot shows a packet passing the nat64 interface. That's an internal virtual interface connecting Tayga to the kernel. In this context, "let out anything" means "allow the kernel to send packets to Tayga".

Do you only see such matches for ICMPv6? The default rules allow certain inbound ICMPv6 types on all interfaces, like Destination Unreachable or Time Exceeded.

Do you maybe use Tayga as a CLAT?

Cheers
Maurice

#10

German - Deutsch / Re: Von ISC- zu KEA DHCP wechs...

Last post by meyergru - Today at 01:51:57 AM

Und damit stehe ich nicht allein ;-)

Rischtisch. Ich denke, ungeachtet von Kea vs. DNSmasq ist das Hauptproblem bei DHCPv6 mit dynamischen Adressen in jedem Fall, dass DHCP eben ein Pull-Ansatz ist: Bevor der Client nicht selbst fragt, bekommt er keine neue IPv6-Adresse, auch, wenn er sie aufgrund des geänderten Präfixes bräuchte. Bis zum Ablauf des Lease ist er dann offline.

Deswegen setze ich im IPv6-HOWTO auf SLAAC, wo der neue Präfix gepusht wird, sowie er sich ändert.