Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - donluca

#1
Quote from: franco on August 11, 2022, 11:45:10 AM
Anyone with the original issue here to try https://github.com/opnsense/core/commit/475cb8ec7f  ?

# opnsense-patch 475cb8ec7f


Thanks,
Franco

I can confirm this is partially working.
The error is gone but the name of the interface in the configuration is still wrong.

In my case, the name of the wireless lan connection is run0_wlan0, but the WAN interface has only run0.

I had to do as hsw suggested here:

Quote from: hsw on August 09, 2022, 12:50:19 PM
I also found that NAT is not working using WIFI as a WAN

in ifconfig the interface appears as iwm0_wlan0 but the NAT does not see this, so no automatic rules are generated.
Adding manual rules looks like
rdr nat on iwm0 inet ...
manually change rules to change to iwmo_wlan0 appears to work

so fix is to edit /conf/config.xml from:
    <wan><if>iwm0</if>
to be
    <wan><if>iwm0_wlan0</if>

Next disable outbound NAT, save, apply.
Finally re enable automatic Nat, save, apply.
Now have working NAT with WIFI WAN.

Although it seems like I didn't need to disable outbound NAT and re-enable it.

EDIT: I just discovered that when I reboot the wireless doesn't autoconnect, I have to go back to the WAN page on the webGUI and click save and then it will connect.

EDIT 2: nevermind! Did an update and everything is now working correctly!