"Recent posts
#1
26.7, 26.10 Series / Re: [CALL FOR TESTING] Defer P...
Last post by RedVortex - Today at 05:43:14 AMWorks on an HA pair (two nodes, CARP, PPPoE on a VLAN) on 26.7.9_1 with 39cca4ca785 plus the CARP check from PR #9896 on top:
For HA the deferral needs that check on top. On its own, the deferred start, a reconfigure or a Save/Apply would still dial on the BACKUP. With both, the BACKUP skips the start ("no parent device is CARP MASTER") and only the MASTER dials. Reboots, maintenance mode, failover and failback all behave. The deferral also took over the boot-race handling the PR used to carry, so the PR is now just the CARP check. Thanks Franco.
Details and the 8 test cases: https://github.com/opnsense/core/pull/9896#issuecomment-6871223343
Thanks a lot for this ! :-)
Code Select
opnsense-patch 39cca4ca785 f2c74235ed Both nodes log "PPP start deferred during boot", and every test ended with exactly one PPPoE session across the pair.For HA the deferral needs that check on top. On its own, the deferred start, a reconfigure or a Save/Apply would still dial on the BACKUP. With both, the BACKUP skips the start ("no parent device is CARP MASTER") and only the MASTER dials. Reboots, maintenance mode, failover and failback all behave. The deferral also took over the boot-race handling the PR used to carry, so the PR is now just the CARP check. Thanks Franco.
Details and the 8 test cases: https://github.com/opnsense/core/pull/9896#issuecomment-6871223343
Thanks a lot for this ! :-)
#2
26.7, 26.10 Series / Re: FreeRADIUS MAC-Based Auth ...
Last post by firemywall - Today at 04:35:53 AMWhen trying to revert I get this message:
Code Select
opnsense-revert -r 26.7.8 os-freeradius
Fetching os-freeradius.pkg: ..[fetch: https://pkg.opnsense.org/FreeBSD:15:amd64/26.7/MINT/26.7.8/latest/Latest/os-freeradius.pkg.sig: Not Found] failed
#3
General Discussion / Issue with update from 26.7.8_...
Last post by acpower1975 - Today at 02:04:17 AMHi,
Keep encountering this issue when I try to do an update (since 13 Nov till 14 Nov). Any similar issue faced by other users? How to go about this?
Thanks.
Regards
Andy
Keep encountering this issue when I try to do an update (since 13 Nov till 14 Nov). Any similar issue faced by other users? How to go about this?
Thanks.
Regards
Andy
#4
26.7, 26.10 Series / Re: [CALL FOR TESTING] Defer P...
Last post by hharry - Today at 01:58:16 AMI've done some testing, OPNsense 26.7.9_1-amd64 + the patch, running in ESXi 6.7 VM, and all looks good
1. confirmed the defered start of mpd5
I also did some extra testing and confirm that;
1. PPPoE adaptive LCP echo request is still successfully working as before the patch
2. PPPoE recovers successfully after WAN link failure
3. frr running eBGP automatically re-established BGP session
1. confirmed the defered start of mpd5
Code Select
<13>1 2026-11-14T11:29:39+11:00 OPNsense_LAB.localdomain opnsense 596 - [meta sequenceId="303"] /usr/local/etc/rc.bootup: PPP start deferred during boot on 'pppoe1'
<13>1 2026-11-14T11:29:39+11:00 OPNsense_LAB.localdomain kernel - - [meta sequenceId="309"] <6>[48] vmx2: link state changed to UP
<13>1 2026-11-14T11:29:39+11:00 OPNsense_LAB.localdomain kernel - - [meta sequenceId="312"] <6>[48] vmx3: link state changed to UP
<13>1 2026-11-14T11:29:39+11:00 OPNsense_LAB.localdomain kernel - - [meta sequenceId="315"] <6>[48] vmx0: link state changed to UP
<13>1 2026-11-14T11:29:39+11:00 OPNsense_LAB.localdomain kernel - - [meta sequenceId="318"] <6>[48] vmx1: link state changed to UP
<13>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain kernel - - [meta sequenceId="372"] <118>[53] Reconfiguring IPv4 on vmx2
<13>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain kernel - - [meta sequenceId="373"] <118>[53] Dialing PPP on wan
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="374"] Multi-link PPP daemon for FreeBSD
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="375"]
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="376"] process 34295 started, version 5.9
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="377"] web: web is not running
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="378"] [wan] Bundle: Interface ng0 created
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="379"] [wan_link0] Link: OPEN event
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="380"] [wan_link0] LCP: Open event
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="381"] [wan_link0] LCP: state change Initial --> Starting
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="382"] [wan_link0] LCP: LayerStart
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="385"] [wan_link0] PPPoE: Connecting to ''
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="386"] PPPoE: rec'd ACNAME "VYOS03"
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="387"] [wan_link0] rec'd proto LCP while dead
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="388"] [wan_link0] PPPoE: connection successful
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="389"] [wan_link0] Link: UP event
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="390"] [wan_link0] LCP: Up event
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="391"] [wan_link0] LCP: state change Starting --> Req-Sent
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="392"] [wan_link0] LCP: SendConfigReq #1
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="393"] [wan_link0] MRU 1492
<29>1 2026-11-14T11:29:45+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="394"] [wan_link0] MAGICNUM 0x8fc2e45a
<13>1 2026-11-14T11:29:46+11:00 OPNsense_LAB.localdomain kernel - - [meta sequenceId="395"] <6>[54] ng0: changing name to 'pppoe1'
<29>1 2026-11-14T11:29:46+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="396"] [wan_link0] LCP: rec'd Configure Ack #1 (Req-Sent)
<29>1 2026-11-14T11:29:46+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="397"] [wan_link0] MRU 1492
<29>1 2026-11-14T11:29:46+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="398"] [wan_link0] MAGICNUM 0x8fc2e45a
<29>1 2026-11-14T11:29:46+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="399"] [wan_link0] LCP: state change Req-Sent --> Ack-Rcvd
<13>1 2026-11-14T11:29:46+11:00 OPNsense_LAB.localdomain opnsense 29837 - [meta sequenceId="400"] /usr/local/etc/rc.newwanip: ROUTING: ignoring down gateways: AU761NORDVPNCOM_VPNV4, WAN_PPPOE
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="416"] [wan_link0] LCP: state change Ack-Rcvd --> Req-Sent
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="417"] [wan_link0] LCP: SendConfigReq #2
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="418"] [wan_link0] MRU 1492
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="419"] [wan_link0] MAGICNUM 0x8fc2e45a
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="420"] [wan_link0] LCP: rec'd Configure Ack #2 (Req-Sent)
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="421"] [wan_link0] MRU 1492
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="422"] [wan_link0] MAGICNUM 0x8fc2e45a
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="423"] [wan_link0] LCP: state change Req-Sent --> Ack-Rcvd
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="424"] [wan_link0] LCP: rec'd Configure Request #89 (Ack-Rcvd)
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="425"] [wan_link0] AUTHPROTO CHAP MD5
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="426"] [wan_link0] MRU 1492
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="427"] [wan_link0] MAGICNUM 0x17ea5805
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="428"] [wan_link0] LCP: SendConfigAck #89
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="429"] [wan_link0] AUTHPROTO CHAP MD5
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="430"] [wan_link0] MRU 1492
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="431"] [wan_link0] MAGICNUM 0x17ea5805
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="432"] [wan_link0] LCP: state change Ack-Rcvd --> Opened
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="433"] [wan_link0] LCP: auth: peer wants CHAP, I want nothing
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="434"] [wan_link0] LCP: LayerUp
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="435"] [wan_link0] CHAP: rec'd CHALLENGE #1 len: 30
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="436"] [wan_link0] Name: "accel-ppp"
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="437"] [wan_link0] CHAP: Using authname "username@example.com"
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="438"] [wan_link0] CHAP: sending RESPONSE #1 len: 50
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="439"] [wan_link0] CHAP: rec'd SUCCESS #1 len: 28
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="440"] [wan_link0] MESG: Authentication succeeded
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="441"] [wan_link0] LCP: authorization successful
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="442"] [wan_link0] Link: Matched action 'bundle "wan" ""'
<29>1 2026-11-14T11:29:48+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="443"] [wan_link0] Link: Join bundle "wan"
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="444"] [wan] Bundle: Status update: up 1 link, total bandwidth 64000 bps
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="445"] [wan] IPCP: Open event
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="446"] [wan] IPCP: state change Initial --> Starting
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="447"] [wan] IPCP: LayerStart
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="448"] [wan] IPCP: Up event
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="449"] [wan] IPCP: state change Starting --> Req-Sent
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="450"] [wan] IPCP: SendConfigReq #1
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="451"] [wan] IPADDR 0.0.0.0
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="452"] [wan] IPCP: rec'd Configure Request #6 (Req-Sent)
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="453"] [wan] IPADDR 192.168.40.254
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="454"] [wan] 192.168.40.254 is OK
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="455"] [wan] IPCP: SendConfigAck #6
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="456"] [wan] IPADDR 192.168.40.254
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="457"] [wan] IPCP: state change Req-Sent --> Ack-Sent
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="458"] [wan] IPCP: rec'd Configure Nak #1 (Ack-Sent)
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="459"] [wan] IPADDR 192.168.40.1
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="460"] [wan] 192.168.40.1 is OK
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="461"] [wan] IPCP: SendConfigReq #2
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="462"] [wan] IPADDR 192.168.40.1
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="463"] [wan] IPCP: rec'd Configure Ack #2 (Ack-Sent)
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="464"] [wan] IPADDR 192.168.40.1
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="465"] [wan] IPCP: state change Ack-Sent --> Opened
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="466"] [wan] IPCP: LayerUp
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="467"] [wan] 192.168.40.1 -> 192.168.40.254
<13>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 83722 - [meta sequenceId="469"] ppp-linkup: executing on pppoe1 for inet
<13>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain opnsense 85347 - [meta sequenceId="470"] /usr/local/opnsense/scripts/interfaces/ppp-ipv6.php: ROUTING: entering configure using wan
<13>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain opnsense 85347 - [meta sequenceId="472"] /usr/local/opnsense/scripts/interfaces/ppp-ipv6.php: ROUTING: ignoring down gateways: WAN_PPPOE, AU761NORDVPNCOM_VPNV4
<13>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain opnsense 85347 - [meta sequenceId="473"] /usr/local/opnsense/scripts/interfaces/ppp-ipv6.php: plugins_configure monitor (,[])
<13>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain opnsense 85347 - [meta sequenceId="474"] /usr/local/opnsense/scripts/interfaces/ppp-ipv6.php: plugins_configure monitor (execute task : dpinger_configure_do(,[]))
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="475"] [wan] IFACE: Up event
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="476"] [wan] IFACE: Rename interface ng0 to pppoe1
<29>1 2026-11-14T11:29:49+11:00 OPNsense_LAB.localdomain ppp 34295 - [meta sequenceId="477"] [wan_link0] rec'd unexpected protocol IPv6, rejecting
<29>1 2026-11-14T11:29:50+11:00 OPNsense_LAB.localdomain ppp 14387 - [meta sequenceId="478"] Last message '[wan_link0] rec'd un' repeated 1 times, suppressed by syslog-ng on OPNsense_LAB.localdomain
<13>1 2026-11-14T11:29:50+11:00 OPNsense_LAB.localdomain opnsense 87249 - [meta sequenceId="479"] /usr/local/etc/rc.newwanip: IP renewal starting (new: 192.168.40.1, old: , interface: wan, device: pppoe1, force: yes)
<13>1 2026-11-14T11:29:50+11:00 OPNsense_LAB.localdomain opnsense 87249 - [meta sequenceId="482"] /usr/local/etc/rc.newwanip: ROUTING: ignoring down gateways: WAN_PPPOE, AU761NORDVPNCOM_VPNV4
<13>1 2026-11-14T11:29:50+11:00 OPNsense_LAB.localdomain opnsense 87249 - [meta sequenceId="483"] /usr/local/etc/rc.newwanip: plugins_configure monitor (,[WAN_PPPOE])
<13>1 2026-11-14T11:29:50+11:00 OPNsense_LAB.localdomain opnsense 87249 - [meta sequenceId="484"] /usr/local/etc/rc.newwanip: plugins_configure monitor (execute task : dpinger_configure_do(,[WAN_PPPOE]))
<13>1 2026-11-14T11:29:50+11:00 OPNsense_LAB.localdomain opnsense 87249 - [meta sequenceId="485"] /usr/local/etc/rc.newwanip: Chose to bind WAN_PPPOE on 192.168.40.1 since we could not find a proper match.
I also did some extra testing and confirm that;
1. PPPoE adaptive LCP echo request is still successfully working as before the patch
2. PPPoE recovers successfully after WAN link failure
3. frr running eBGP automatically re-established BGP session
#5
26.7, 26.10 Series / Re: [SOLVED] A bug in 26.7.9_1...
Last post by Greelan - November 13, 2026, 11:40:53 PMYes, it is normal since those files are the ones changed in the patch.
You can expect the patch to be cherry-picked into 26.7.10.
You can expect the patch to be cherry-picked into 26.7.10.
#6
26.7, 26.10 Series / Re: [SOLVED] A bug in 26.7.9_1...
Last post by lmoore - November 13, 2026, 11:10:39 PMDeleted.
#7
Tutorials and FAQs / Re: [HOWTO] Configure WAN MTU ...
Last post by meyergru - November 13, 2026, 10:33:42 PMDid you reboot? As mentioned, the order of interface initialisation matters and the results upon initial configuration may be different.
I am with the exact same ISP and do not see your results with http://pmtud.enslaves.us/. My setup is shown above, and I get the same effective MTUs as you with the pings but then:
You could also look into "grep -n 'max-mss' /tmp/rules.debug" and see if there is any rule that limits your TCP MSS to 1452.
Contrary to the instructions one difference might be that I set MSS 1500 on pppoe0 explicitely - although it should not be the culprit, you may want to try it.
I am with the exact same ISP and do not see your results with http://pmtud.enslaves.us/. My setup is shown above, and I get the same effective MTUs as you with the pings but then:
QuotePath MTU Discovery Test
Results
Direction Tested Maximum Size Segment Client Sent MSS Notes
Server to Client IPv4 1460 (MTU 1500) 1460 (MTU 1500) OK
Client to Server IPv4 unlimited (n/a) OK
Server to Client IPv6 1440 (MTU 1500) 1440 (MTU 1500) OK
Client to Server IPv6 unlimited (n/a) OKCode Selectgot server to client probe for mss 536 (max seg 1460)
got server to client probe for mss 1460 (max seg 1460)
got server to client probe for mss 1460 (max seg 1460)
finished s2c4 probing, maximum mss 1460 peer mss 1460 initial peer mss 1460
got client to server probe for mss 520
got client to server probe for mss 1461
got client to server probe for mss 9000
finished c2s4 probing, maximum mss 9000
got server to client probe for mss 536 (max seg 1440)
got server to client probe for mss 1440 (max seg 1440)
got server to client probe for mss 1440 (max seg 1440)
finished s2c6 probing, maximum mss 1440 peer mss 1440 initial peer mss 1440
got client to server probe for mss 520
got client to server probe for mss 1441
got client to server probe for mss 9000
finished c2s6 probing, maximum mss 9000
You could also look into "grep -n 'max-mss' /tmp/rules.debug" and see if there is any rule that limits your TCP MSS to 1452.
Contrary to the instructions one difference might be that I set MSS 1500 on pppoe0 explicitely - although it should not be the culprit, you may want to try it.
#8
General Discussion / Any plan to support 4G umb (MB...
Last post by Oulra - November 13, 2026, 10:32:32 PMHello everyone,
I've been using a 4G PPP connection with an EM7565 modem for several years now, and FreeBSD 15 now supports the use of the umb driver for MBIM interfacing.
I just tried it manually by playing around with umbctl, and it's pretty simple to set up. I lose the ability to have automatic outbound NAT rules, but other than that, the connection is night and day! I've more than doubled my download and upload speeds, and the latency has improved dramatically.
So I'm pretty excited about the idea of being able to use it properly, and I'm wondering if there are plans to support this natively within the OPNsense core in the future?
Here's some info for anyone interested in switching my EM7565 to MBIM mode:
Load the umb driver by adding umb_load="YES" to /boot/loader.conf.local and reboot.
After rebooting, verify that the umb0 interface appears, then configure the APN number, PIN, and enable roaming by creating a file umb.conf:
Initiate the connection:
All that's left is to assign your interface to umb0 (IPv4 None), add the gateway manually, add NAT rules and you're good to go!
I've been using a 4G PPP connection with an EM7565 modem for several years now, and FreeBSD 15 now supports the use of the umb driver for MBIM interfacing.
I just tried it manually by playing around with umbctl, and it's pretty simple to set up. I lose the ability to have automatic outbound NAT rules, but other than that, the connection is night and day! I've more than doubled my download and upload speeds, and the latency has improved dramatically.
So I'm pretty excited about the idea of being able to use it properly, and I'm wondering if there are plans to support this natively within the OPNsense core in the future?
Here's some info for anyone interested in switching my EM7565 to MBIM mode:
Code Select
cu -l /dev/cuaU0.0
AT!ENTERCND="A710"
AT!USBCOMP=1,1,100DLoad the umb driver by adding umb_load="YES" to /boot/loader.conf.local and reboot.
After rebooting, verify that the umb0 interface appears, then configure the APN number, PIN, and enable roaming by creating a file umb.conf:
Code Select
apn=Free
pin=0000
roamingInitiate the connection:
Code Select
umbctl -f umb.conf umb0All that's left is to assign your interface to umb0 (IPv4 None), add the gateway manually, add NAT rules and you're good to go!
#9
26.7, 26.10 Series / Re: [Solved] UPNP fatal error ...
Last post by Component0002 - November 13, 2026, 10:23:17 PMI'm getting the exact same issue as axsdenied after updating:
ErrorminiupnpdSTUN server not supported, not returning OTHER-ADDRESS / support CHANGE-REQUEST's required for endpoint-independent (1:1) CGNAT filtering tests per RFC 5780.
This seems to be unique to stun.l.google.com as if I change it to stun.3cx.com it starts correctly.
Should we open a bug report for this somewhere?
ErrorminiupnpdSTUN server not supported, not returning OTHER-ADDRESS / support CHANGE-REQUEST's required for endpoint-independent (1:1) CGNAT filtering tests per RFC 5780.
This seems to be unique to stun.l.google.com as if I change it to stun.3cx.com it starts correctly.
Should we open a bug report for this somewhere?
#10
Portuguese - Português / Re: Sem acesso ao site de cons...
Last post by mamebill2 - November 13, 2026, 09:39:38 PMA sugestão de utilizar Sticky Connections faz bastante sentido em ambientes com Multi-WAN, pois manter a mesma conexão pela mesma interface pode evitar problemas de autenticação e interrupções durante o acesso a determinados portais. Também vale testar uma regra de Policy Routing específica para o domínio da Receita, acompanhando os logs para identificar o resultado.
Para quem gosta de jogos clássicos no computador, gta san andreas notebook é uma busca interessante para encontrar informações sobre instalação e compatibilidade. Antes de instalar, vale conferir os requisitos de hardware, memória e sistema operacional para garantir que o jogo funcione adequadamente no notebook.
Para quem gosta de jogos clássicos no computador, gta san andreas notebook é uma busca interessante para encontrar informações sobre instalação e compatibilidade. Antes de instalar, vale conferir os requisitos de hardware, memória e sistema operacional para garantir que o jogo funcione adequadamente no notebook.
