Messages

1. ich gehe mit franco einig: iOS und OS X am besten via L2TP over IPsec anbinden.
2. es funktioniert tadellos mit der von franco verlinkten anleitung (gerade eben ausprobiert).
3. UNBEDINGT die floating rule welche unter dem abschnitt "Troubleshooting" erwaehnt wird einrichten!


grz!
m.

EDIT:
IPsec phase2 habe ich AES 256
IPsec phase1 habe ich DH key group 2 (1024bit) und Lifetime 3600

why not just use the nano image? I installed OPNsense-15.1.11.1_OpenSSL-nano-i386.img to an mSATA SSD and my soekris net6501-50 now boots fine.

yup, I can confirm this behavior with my net6501. installation onto an mSATA SSD went fine but then it'll never boot properly. I had zero trouble to get OPNsense up and running on my PC Engines APU though...

regards,
michael

I have to agree to some extent. the GUI looks very pretty but a bit like OS X Yosemite: IMHO it's too much design over functionality. the good news is though that under /System/General Setup/ one will be able to switch themes in the future...

regards,
michael

thank you for your reply, franco.

hm, but if it would work as expected I should get IP addresses from the DHCP service configured on the LAN in the first place, correct?  and this didn't happen AFAIR...

regards,
michael

hello everybody. this is my first (actually 2nd) post here. I'm evaluating OPNsense because of m0n0wall being declared as EOL. so far I think that OPNsense looks great! I'm having a small issue with WiFi/DHCP. I did setup OPNsense on a PC Engines APU. to get the WiFi up and running, I bridged it to the LAN interface. I didn't get any IP addresses on the WiFi. ah, ok, there's a seprate config for DHCP on the WiFi interface. I then activated the DHCP service on the WiFi interface with its own range (same subnet though). now I'm getting IP addresses from the DHCP range of the WiFi on both interfaces (LAN and WiFi). I don't think that it should behave that way...?

Google still thinks that the confirmation e-mail sent from the forum is spam...