Messages

What I found strange is that the broadcast address is used to forward a UDP packet with port 1900 (which is SSDP). I expected this to be forwarded to 239.255.255.250?

Coming at this from a different direction, I have my sonos speakers working *without* udpbroadcastrelay for the mobile app, but the desktop app won't work.

Perhaps there's a "fallback" the mobile client can do when multicast isn't working, so maybe you aren't relaying like you think? (guessing?)

[Confirmed : Disabling vm.pmap.pti is the winner]

EDIT: On 2nd thought, would it be possible to just install OPNsense on a different system and swap the drive over to the older Athlon x2 system? That should get around the install bug, yes?

tried it, no, once the "real" OPNsense boots, it dies at the same place, mounting drives.

However, I've been scouring the internets, and I found something to try, and MAGIC SAUCE, it works?
(By works I mean, I booted a hard-drive with a 21.1 install on a NON-AMD machine, set the tunables, then moved the drive back over to the AMD machine, and it now works)

Set in the UI as:
System: Settings: Tunables
vm.pmap.pti 0
Page Table Isolation (Meltdown mitigation, requires reboot.)

Adding those to the boot options would allow us to work around it at install time, I think like this:
* boot installer
* (3) escape to loader prompt
* "set vm.pmap.pti=0"
* "boot"

(going out to the garage to try this now)

Confirmed : Disabling vm.pmap.pti is the winner

I have an embarrassing amount of older AMD hardware, so I was able to test with x2, x4, x6, semperons, opterons, phenoms, and some newer FX-4000, FX-6000, and FX-8300 series (which work fine btw, gave me a control group)

to successfully install, you need to :
1. Disable it at the (3) loader prompt, install as normal
2. disable it at the (3) loader prompt on first boot
3. set it either in the UI via "System: Settings: Tunables", or add it to /boot/loader.conf.local (create the file if it doesn't exist)
4. Reboot - make sure it works.
5. Profit


Now we just need this added next to "Safe Mode" as a boot option, and future generations would be set.

I would start with the earliest available version on the official mirrors, which is OPNsense 19.7.

https://mirror.wdc1.us.leaseweb.net/opnsense/releases/19.7/

Start there and see if the install completes, then upgrade to the latest. I would recommend against using the i386 install. Download and attempt to use the AMD64 version first, it will have a much longer lifespan. i386 is no longer supported after OPNsense 20.1.

It's a circle.

The amd64 installers won't get past the "mounting" point on the Athlon x2/x4/x6 CPU's.  We're bumping up against a bug in FreeBSD12.1.  FreeBSD12.2 works fine, but.. isn't supported for OPNSense yet.

Same issue? Common thread is the x2/x4/x6 CPU's - all same behavior

* https://forum.opnsense.org/index.php?topic=19180.0
* https://forum.opnsense.org/index.php?topic=16728.0
* https://github.com/opnsense/core/issues/3438

It's ironic because I can't spot a patch reference in there so I can't go digging for "something" that was fixed in 12.2 that in turn has no relation to this bug report in the (extensive) commit history. ;(


Cheers,
Franco

Sorry Franco, I'll try to find more data.

Did a bit more testing today, dug out an old FX-8300, works perfectly, swap the CPU back to the x2, x4, x6, etc, and it fails. Same everything except CPU.

EDIT: Found it - see : https://forum.opnsense.org/index.php?topic=23348.msg111140#msg111140

take a peek at this : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235017

Try to run the OPNSense 21.1 installer on AMD Phenom series CPU's (have tried x2, x4, and x6, others mention Opterons from same generation) hangs at mounting filesystems. I've installed on a intel Core.i5 machine, then moved the HD over to the AMD CPU, and the install hangs at the same spots.

all (4) machines boot FreeBSD 12.2 installer just fine - so I suspect that bug is the thread to pull.

presently running 20.1.9.i386 just fine on a AMD Athlon(tm) II X4 620, but can't upgrade because the installer hangs.

Turns out I'm running 20.1.9.i386 - hence the binary not running.

Any chance there's a version for those of us still on the i386 version?

had the same problem this weekend, similar age of machine (x4 620). Had to install 17, then upgrade repeatedly to get to 20.1.9 (i386).

after much screwing around, I've determined there's an issue with that generation of CPU's and the present installer. Seems to be related to : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235017

What's the current status of this package? I'm running 20.7, and I've installed the 0.5_0.6 beta, but it fails to run.

/usr/local/sbin/udpbroadcastrelay: Exec format error. Binary file not executable.

I see hints of it being installed in 21, but is there a version of those of us on 20.x stable?

I dug through the docs, and I don't see this explicitly mentioned, so I figured I'd ask here.


Are 2G/3G/4G modems on the roadmap for OPNSense support? I see the couple that are presently supported, but I have several, from a variety of carriers, and none of them are supported.

T-Mobile: 4G Rocket
OPNsense root: Unknown USB device: vendor 0x19d2 product 0x0157 bus uhub1

AT&T Beam (Netgear 340U)
OPNsense root: Unknown USB device: vendor 0x1199 product 0x9051 bus uhub1

Verizon 4G/LTE 551L
OPNsense root: Unknown USB device: vendor 0x1410 product 0xb001 bus uhub1

They're all well supported under linux in recent kernels, using qmi, mbim, ncm, or rndis.