Messages

https://sourceforge.net/projects/win32diskimager/ Win32 Disk Imager.

Works for me.

pfSense, OPNSense, OpenSUSE, Kubuntu and so forth.. if it's using img file or "hybrid" iso it's the go-to program.

Anything GPT formatted on memstick makes this board go for UEFI only.Then it does not allow for legacy boot at all. Tried with Linuxes as well. No way to go into legacy boot mode as long as media is in GPT format. No issue with MBR formatted media.

Been months since original post but had router running and had no wish to experiment before next major reinstall.

okay, thanks. I did not try i386 memstick option because of more than 4GB RAM onboard.

I am pretty sure its pure "board issue". It seemed to assume that if the detected boot media was in GPT format, it also just had to be UEFI and "legacy boot" just can't be done.

Same problem btw trying 16.1 memstick on same board. Board either does give UEFI error or skips right over to the next boot device in list. Depending on how I set the bios.

[dd=OPNsense-16.7.r2-OpenSSL-vga-amd64.img of=/dev/sda2 bs=16k]

I have Asus AM1M-A motherboard. It's one of those AMD AM1 SOC boards. It has UEFI bios on it and had I had any hair in the first place, I would have tore all off today.

I downloaded memstick image for AMD64, VGA. I did "burn" it to the memstick using dd=OPNsense-16.7.r2-OpenSSL-vga-amd64.img of=/dev/sda2 bs=16k (I used Linux machine for this)

upon POST, banged F8, got boot menu, selected memstick, hit Enter and got after 3 seconds thrown into UEFI bios. Over and over. Changed hard drives, USB sticks, USB slots etc. Finally tore the case open, grabbed DVD device and attached it to the router. Then burned another file to blank DVD (OPNsense-16.7.r2-OpenSSL-cdrom-amd64.iso) and tried it.

Okay, cdrom boot worked. I installed using "Guided" setup and choose GPT. After reboot got black screen and message on it stating "the system found unauthorized changes on the firmware operating system or uefi drivers"

Tried memstick quickly again but now intentionally selected UEFI (memstick name) from F8 menu. Got black screen and identical message. Previously with memstick, I had tried booting it by "legacy method" since it was manually enabled in BIOS already and should have taken priority over UEFI crap.

I have installed OPNSense on another Asus board which also has UEFI Bios (Asus M5A99X Evo R2 which is AM3+ board in ATX size, leftover from my old gaming system) and had no such opera with it. I could force "Legacy Oprom" option and board would listen booting GPT formatted media without issues or complaining about firmwares. I used it briefly in a router and also used OPNSense installed on it.

Not so with this AM1 board. Seems like only option to use OPNSense installed on it is by using DVD and only doing MBR install.

Conclusion. I hate UEFI.

Any of you, who can't seem to get OPNSense on memstick to boot, try it by using cdrom based install and go with MBR option under "Guided setup". Might get over the issue.

I'd recommend AR9280 and/or AR9462. Former has usually re-flashable firmware (can modify/rewrite firmware using software utilities. Sometimes you want to change regdom, output power slightly upwards or smth), latter is fine for abgn (can do AP for either 2,4Ghz/5-5,8Ghz band). But it's firmware can no longer be tinkered with.

Yes, it was on AHCI because I used SSD. Eventually got past the issue and installed.

EDIT: Sorry, I did not grasp the changed logic. Found now how to do it. Thank you for development.

Different question : Is 802.11gn WLAN stable or should I stick to pure "g"?

HostAP based on Atheros AR9462 abng card.

OPNsense-15.7.11-OpenSSL-AMD64, tried both, iso written to cdrom and image written to USB.

9 out of 10 times installation would be stuck at one specific point (64% at default options for keymaps etc), I gave it half an hour and then manually rebooted the machine. One time I managed to complete install, system instantly shut itself down after I pressed F1 for boot (bootloader). And it also kept shutting itself down while attempting automatic boot.

Suggestions?

EDIT:
Machine in question is AMD AM1 platform, cpu AMD Athlon 5350 and motherboard is Asus Am1M-a, equipped with Sandisk SSD and Intel dual-nic, nothing else.

Could you import Atheros WLAN driver from 11-CURRENT?

It would help with 802.11na (5Ghz "n").

At the moment getting

May 2 00:51:49    kernel: ar9300_Stub_GetAntennaSwitch: called
May 2 00:51:49    kernel: ar9300_Stub_GetAntennaSwitch: called
May 2 00:51:49    kernel: ar9300_Stub_GetCTSTimeout: called
May 2 00:51:49    kernel: ar9300_Stub_GetCTSTimeout: called
May 2 00:51:38    kernel: ar9300_Stub_GetAntennaSwitch: called
May 2 00:51:38    kernel: ar9300_Stub_GetAntennaSwitch: called
May 2 00:51:38    kernel: ar9300_Stub_GetCTSTimeout: called
May 2 00:51:38    kernel: ar9300_Stub_GetCTSTimeout: called
May 2 00:51:27    kernel: ar9300_Stub_GetAntennaSwitch: called
May 2 00:51:27    kernel: ar9300_Stub_GetAntennaSwitch: called
May 2 00:51:27    kernel: ar9300_Stub_GetCTSTimeout: called
May 2 00:51:27    kernel: ar9300_Stub_GetCTSTimeout: called
May 2 00:51:16    kernel: ar9300_Stub_GetAntennaSwitch: called

into syslog.. WLAN card I'm trying to use is Atheros AR9580

these are pro's and con's that come from applying different development philosophies.

Open the linux kernel's config/menuconfig/xconfig and you can often see remarks behind options like (EXPERIMENTAL), (DANGEROUS) etc..

You get more bleeding-edge functionalities but at a price..

Wifi-side seems to lag behind yes. I think "ac" has, for example, no support at all in FreeBSD yet.

Yeah, it's more problematic with FreeBSD than with Linux. FreeBSD, until very recently, lacked decent support for 5Ghz band.

It should be fixed in FreeBSD 11.

One way for devs would be to "loan" the newer drivers from FreeBSD 11 and modify them to work in OPNsense

Downloaded and installed (AMD Athlon 5350 on Asus AM1M-A, 4Gb ECC unb DDR3).

System logs (Gateway section) complains:

Feb 22 17:04:15    OPNsense apinger: SIGHUP received, reloading configuration.
Feb 22 17:03:43    OPNsense apinger: SIGHUP received, reloading configuration.
Feb 22 16:56:58    OPNsense apinger: SIGHUP received, reloading configuration.
Feb 22 16:56:31    OPNsense apinger: Starting Alarm Pinger, apinger(18779)
Feb 22 16:55:01    OPNsense apinger: No usable targets found, exiting
Feb 22 16:55:01    OPNsense apinger: Starting Alarm Pinger, apinger(14594

other than that in logs, everything I am using (basic fw, DHCP4, upnp) seems to work.

I predict there is going to be an issue with PowerD but it's issue of a FreeBSD itself (AM1 platforms crash after turning on cpu power management)

OpenBSD has one big disadvantage, it's pf is not SMP capable like FreeBSD's pf fork. By now, even their syntax is different. That's my guess but if the change of base OS were attempted, it would as good as starting from scratch. And getting less performing end product as a result

[15.1.4_1-4b16c7531 (amd64) FreeBSD 10.0-RELEASE-p17]

OPNsense looks nice from every angle so far. Build from source took under a hour, less than setting up builder machine itself (it ran FreeBSD 10.1-RELEASE).

Pretty stark contrast compared to hours and hours wasted when I tried compiling pfSense from source (I've done it with 2.1.5 and 2.2-ALPHA - took sometimes days off and on figuring out and around the dependency/script/whatever random issues with the latter, before finishing a build)

Web GUI looks refreshingly different as well, though I sort of like more pfSense's compactness.

Dashboard shows for now 15.1.4_1-4b16c7531 (amd64) FreeBSD 10.0-RELEASE-p17. Would building against 10.1 sources work or OPNsense is for now using strictly 10.0's code? I am trying to get around issues with Atheros AR9580 and AMD AM1 platform, might need to use newer sources, not sure yet.

just out of curiosity? Whats wrong with the UFS? Why you would want ZFS? Any inherent advantages for a firewall?