Recent posts

#1
26.1, 26,4 Series / Re: [SOLVED-ish] Degraded Spee...
Last post by juicemain - Today at 10:57:21 PM
Sigh.  So the ISP, after denying that the ONT included logs, sent me this in our conversation:



Full resolution: https://i.postimg.cc/pxVcqhYW/unnamed.png

I'm assuming these are the ONT logs right?  Does anyone know what kind of system this is?  From what I can see, it is showing nonzero Downstream and Upstream Bip error counts.  This isn't normal correct?  Does this confirm errors at the ONT?  Does this point to any particular issue?  Any and all feedback much appreciated.  Fighting an uphill battle here.

I know this isn't the place for this conversation at this point, but I greatly appreciate the help in troubleshooting assistance that you all have offered. 
#2
26.1, 26,4 Series / Re: Upgrade went wrong
Last post by franco - Today at 09:37:32 PM
#3
26.1, 26,4 Series / Re: Update issues when upgradi...
Last post by franco - Today at 09:36:27 PM
>  pkg 2.6.2_1

And we never had that version ;)

# pkg lock -y pkg
# opnsense-revert pkg


Cheers,
Franco
#4
26.1, 26,4 Series / Re: OPNsense 26.4.1 business e...
Last post by franco - Today at 09:35:44 PM
Since it's an upstream issue and the patching is too complicated there is little we can do for a community bound package/plugin.

# opnsense-revert -r 26.4 nut


Cheers,
Franco
#5
26.1, 26,4 Series / Re: Upgrade went wrong
Last post by weilander - Today at 09:11:03 PM
Hello,

I can reproduce a pkg segmentation fault on OPNsense 26.1.10.

System:

* OPNsense 26.1.10
* pkg 2.6.2_1
* os-sensei 2.6
* os-sensei-agent 2.6
* os-sensei-updater 2.0
* os-sunnyvalley 1.5_2

The firewall itself appears completely stable. Routing, services and package integrity checks are working normally.

The segmentation fault occurs consistently after successful completion of pkg operations:

pkg update

Result:

Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
SunnyValley repository is up to date.
All repositories are up to date.
Child process pid=xxxxx terminated abnormally: Segmentation fault

The same happens with:

* pkg version
* pkg upgrade -n

Additional diagnostics:

pkg check -Ba
→ Checking all packages: 100%

pkg audit -F
→ completed successfully

No package conflicts reported.
Repositories update successfully.
The segmentation fault occurs only after the operation has already completed successfully.

Kernel log contains repeated entries like:

(pid xxxx) (pkg) exited on signal 11 (no core dump - bad address)

Can provide additional diagnostics if required.

Regards,
Michael
#6
Hardware and Performance / Re: Inseego MiFi Pro M4 as WAN...
Last post by pfry - Today at 09:04:38 PM
Quote from: Greg_E on Today at 08:02:49 PM[...]Why did I go with that specific device? It was the only in stock 5g device that they offered that also has external antenna connectors (2 of them).[...]

Invisagig? Can't comment on stock, and the Inseego appears to be considerably cheaper.

I'd think the Ethernet would be the way to go from a connectivity standpoint, but only if the device can bridge, like most 802.11 devices. That's always been a question for me, and I'm not curious enough to purchase a service to answer it. Particularly since I need multiple static IPs, and I haven't seen such an offering from any (somewhat reputable) U.S. carrier.
#7
26.1, 26,4 Series / Re: Update issues when upgradi...
Last post by weilander - Today at 08:42:10 PM
Hello,

I can reproduce a pkg segmentation fault on OPNsense 26.1.10.

System:

* OPNsense 26.1.10
* pkg 2.6.2_1
* os-sensei 2.6
* os-sensei-agent 2.6
* os-sensei-updater 2.0
* os-sunnyvalley 1.5_2

The firewall itself appears completely stable. Routing, services and package integrity checks are working normally.

The segmentation fault occurs consistently after successful completion of pkg operations:

pkg update

Result:

Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
SunnyValley repository is up to date.
All repositories are up to date.
Child process pid=xxxxx terminated abnormally: Segmentation fault

The same happens with:

* pkg version
* pkg upgrade -n

Additional diagnostics:

pkg check -Ba
→ Checking all packages: 100%

pkg audit -F
→ completed successfully

No package conflicts reported.
Repositories update successfully.
The segmentation fault occurs only after the operation has already completed successfully.

Kernel log contains repeated entries like:

(pid xxxx) (pkg) exited on signal 11 (no core dump - bad address)

Can provide additional diagnostics if required.

Regards,
Michael
#8
Hardware and Performance / Re: I226 T2 M2 ngff pci-e
Last post by Greg_E - Today at 08:10:19 PM
I've only used single port a+e slot i226v cards and no problems so far. The dual cards are interesting for a few reasons, would like to know how this was fixed in case I ever need to go 6 ports in one of my T740.
#9
Hardware and Performance / Inseego MiFi Pro M4 as WAN?
Last post by Greg_E - Today at 08:02:49 PM
Anyone use or have tips on using a MiFi device as WAN source? I just bought an Inseego MiFi Pro M4 to use with my lab and for use in the car on trips. It says it has USB tethering, but also has rj45. It's T-Mobile so probably behind CGNAT, but that's the world I live in now, Netbird can get me around that for remote work. Everything I do now is behind multiple NAT of one form or another, yes it is less than desirable, just have to work with what you can get.

The hardware does support static IP, so I might look into that later and pay for an IP if T-Mobile can offer that (then run a local Netbird or other server).

Why did I go with that specific device? It was the only in stock 5g device that they offered that also has external antenna connectors (2 of them). External antenna can be a make or break feature depending on your location.

Any tips to get this working with OPNsense would be appreciated, lots of open USB ports if tethering is the best way forward. Link to the product https://inseego.com/products/mobile-hotspot-routers/mifi-pro-m4/
#10
26.1, 26,4 Series / OPNsense 26.4.1 business editi...
Last post by mfld-pub - Today at 07:29:50 PM
3/3 instances just updated to OPNsense 26.4.1 business edition all come up with NUT UPS status blank.

Could it be that

https://github.com/opnsense/ports/issues/270
https://forum.opnsense.org/index.php?topic=51861.0

found its way into the Business Edition ?