Messages

The connection does not fail ,  on the lan interface , i can see incoming VPN traffic source ip as 10.10.0.6.
what i wanted is to change the source ip from 10.10.0.6 to any ip address that belong to lan network (192.168.2.x)

i tried your suggestion by putting an outbound NAT on the OpenVPN interface.
Firewall, NAT, Outbound: interface=OpenVPN, source=any, port=*, destination=LAN net, destination port=*, NAT address=LAN address NAT Port=*

but this rule is not changing the source ip, as you can see in below trace
lan      2022-04-13T21:44:49   10.10.0.6:51945   192.168.2.100:80   tcp   

Another thing,  OpenVPN interface need to be created in the interface section  for the outband NAT works correctly?

Any more idea guys?

I dont know if this is possible , Is there a way to make vpn traffic  appears in the LAN network as local traffic (same subnet IP's)?.

Yes, put an outbound NAT on the OpenVPN interface. Firewall, NAT, Outbound: interface=OpenVPN, source=any, port=*, destination=LAN net, destination port=*, NAT address=LAN address NAT Port=*

Hello,

I set the outband NAT entry as advised,
OpenVPN   any   *   LAN net   *   LAN address   *   NO

however it didn't work. i can still see the  source ip as 10.10.0.6  on the lan network

lan      2022-04-14T18:41:03   10.10.0.6:49681   192.168.2.100:80   tcp   let out anything from firewall host itself

I dont know if this is possible , Is there a way to make vpn traffic  appears in the LAN network as local traffic (same subnet IP's)?. Basically i want to change the source IP  for VPN traffic once on LAN network.
192.168.2.X instead of 10.10.X.X

Hello,

I configured VPN server on opnsense , LAN network :192.168.2.0/24  , VPN network: 10.10.0.0/24 .
VPN clients connect successfully to the server and i can surf the internet via the tunnel with gateway redirection.
However , i have an issue with routing in regards to reaching the LAN network .  firewall rules are attached .

i can see in the firewall live view the following when i try to reach the following box:192.168.2.100
   lan      2022-04-13T21:44:49   10.10.0.6:51945   192.168.2.100:80   tcp   let out anything from firewall host itself    (direction out)

if i add a static route on my box that to reach 10.10.x.x is via 192.168.2.1  , the problem will be fixed.  however, obviously i have some misconfiguration somewhere.
Appreciate your help ,

Thanks! problem fixed

Thanks! ,

-How can i know the chipset number ?
-Did you try the tunable option? in case yes, what did you put there exactly?

In this specific case, what to add exactly in tunable ?

Hello schnipp,

Please let me know the outcome of this new usb lan adapter.

Br
Elie

You probably encountered the same problems like me since updating to Opnsense 22.x (see here). It's either a general or a specific problem related to my realtek USB NIC. Which USB NIC do you use?i

My temporary solution is to shutdown and restart the interface using the CLI.

Yes , i think we have similar problems,

ure0 on uhub1
ure0: <Realtek USB 10/100/1000 LAN, class 0/0, rev 2.10/30.00, addr 2> on usbus7
miibus0: <MII bus> on ure0
ue0: <USB Ethernet> on ure0

Hello, basically this is what i can find in logs:

at 11:17 , i remove the power from the switch , the firewall detect that UE0 state has change to down and then i receive some errors regarding to memory allocation, and yes i have enabled and configured arp static entries.

2022-03-13T11:17:35   Error   opnsense   /usr/local/etc/rc.linkup: The command '/usr/sbin/arp -s '192.168.2.5' '80:ea:96:06:4e:65'' returned exit code '1', the output was 'arp: writing to routing socket: Cannot allocate memory'   
2022-03-13T11:17:35   Error   opnsense   /usr/local/etc/rc.linkup: The command '/usr/sbin/arp -s '192.168.2.4' '90:e7:c4:d7:35:62'' returned exit code '1', the output was 'arp: writing to routing socket: Cannot allocate memory'   
2022-03-13T11:17:35   Error   opnsense   /usr/local/etc/rc.linkup: The command '/usr/sbin/arp -s '192.168.2.3' '60:36:dd:61:ab:93'' returned exit code '1', the output was 'arp: writing to routing socket: Cannot allocate memory'   
2022-03-13T11:17:35   Error   opnsense   /usr/local/etc/rc.linkup: The command '/usr/sbin/arp -s '192.168.2.2' '84:8e:0c:07:45:d1'' returned exit code '1', the output was 'arp: writing to routing socket: Cannot allocate memory'   
2022-03-13T11:17:35   Error   opnsense   /usr/local/etc/rc.linkup: DEVD: Ethernet detached event for static lan(ue0)

No it is not.  What you suggest?

Hello,
I am facing a strange issue and i need some help.
I have a laptop where opnsense is installed on it.  This laptop has 2 adapters  , default ethernet port of laptop connected to WAN  and  an eth usb adapter connected to LAN . a cable goes from the usb adapter to a L2 switch connected to my other devices.  The issue im facing , is when i lose electricity power on the switch (then after power up) , i lose internet and connectivity,  and the problem cannot be resolved till i restart opnsense . Any idea why this is happening and how to solve it?
Elie 

After disabling ad blockers, problem is solved!

Thanks

Hello,
I updated recently from 18.1 to 18.7.1 , however i noticed that i am not able to configure netflow parameters anymore with chrome browser.
There is no options displayed to choose the LAN and WAN interface,version and destinations from,while using chrome browser. However , these options are available when using internet explorer.
Can you please help?

Elie