Messages

I notice the management interface becomes unresponsive if the following conditions are met:

1. NUT is configured for APCSmartUPS (I am using an APC Back UPS Pro)
2. Click on diagnostics to view UPS status. At this point the management interface becomes unresponsive and requires a reboot of the machine to get back the interface.

NB: The APC Back UPS Pro works fine if set to default USB HID.

I am writing up disaster recovery procedures ready to put OpnSense into production. The disaster recovery procedures includes a full h/w meltdown and the requirement to install on top of new h/w.

I notice that depending on the order of attaching the VLANs to the new interfaces affects how the firewall rules and DHCP settings are also attached. For example: If I attach VLAN3 to the new interface first but which it was created after VLAN2 then VLAN3 will inherit VLAN2 firewall rules and DHCP settings.

Is reattaching VLANs to new interfaces in their order of creation correct for documenting disaster recovery or am I going about it the wrong way?

OK...my bad again...

there was a virtual IP on the firewall for 192.168.1.2 and so I deleted it.

I downloaded the backup XML file and did a search for all IPs and found it was configured for some reason by mistake. Next time will use this method instead of clicking through all the menu options looking for a mistake and not finding it.

Maybe a menu option would be great to get a flat file overview of every configuration would be handy.

Can anyone help me explain why the ARP tables are being polluted?

configuration:
192.168.1.1 -> opnSense (re0)
192.168.1.2 -> openWRT AP

ARP Table:
192.168.1.1 -> opnSense (re0)
192.168.1.2.-> opnSense (re0)

ifconfig re0 delete 192.168.1.2

reboot

ARP Table after reboot:
192.168.1.1 -> opnSense (re0)
192.168.1.2 -> opnSense (re0)

Help????

Ignore this. sorry. my bad.

I looked at the ARP tables and saw 192.168.1.2 was assigned to the LAN interface. However it doesn't show on the configuration page for some reason. Will remove the offending ip address manually.

Can anyone advise of the FW rules so I can http access to my openWRT APs?

1. I have the default LAN Net created on install of opnSense.
2. I created 3 SSIDs and put them on 3 VLANs. At this point no problem with accessing the APs.
3. I added access rules for DNS and TCP 8000-10000 and then isolated each VLAN with block rules. No problem with CP and gaining access to internet.
4. I try to connect to my first AP on LAN Net 192.168.1.2 and it simply reroutes me to opnSense on 192.168.1.1 webgui. I also tried pinging 192.168.1.2 but the packets go to opnSense instead of the AP. Other than this the AP seems to be functioning correctly.

So up to step 2 everything is kosher but after creating the rules my packets get redirected to opnSense.

I am stumped. Any ideas?

Hi everyone,

I have just migrated from Pfsense. Am I blind or does Opnsense not have this option to limit per user bandwidth? I did like the option in Pfsense to limit user bandwidth in the captive portal section. Not a deal breaker though as I plan to stick with Opnsense.