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 - ddemchuk

#1
Hi,

I have trouble routing traffic over VPN tunnel for Windows client in Road Warrior setup. I've followed these steps enough times, no joy:
https://docs.opnsense.org/manual/how-tos/ipsec-rw-srv-mschapv2.html
https://docs.opnsense.org/manual/how-tos/ipsec-rw-w7.html
My internal network is 10.5.1.0/24, and client network is 192.168.222.0/24. In Phase 2 I tried using both, actual LAN network and "Network" with manually provided network address.
"Use this gateway" is disabled on the client, I only need traffic for my office network to be routed through VPN.

Result:
- Client connects to opnsense - which is good
- Client always gets IP address 192.168.222.1 assigned to it, and routes traffic for 192.168.222.0/24 through it - good
- Static IP assignment on client side has no effect on it, it still gets the same 192.168.222.1 - strange but ok
- Any other traffic is routed via local NIC, including one for my internal network 10.5.1.0/24 - so the client is not reaching out office via VPN

Questions:
1. Client -> Office connectivity: how do I make Win11 client to route traffic for my internal network 10.5.1.0/24 via VPN adapter? Manually adding route does not look right because the next time the client can obtain different address from 192.168.222.0/24 range. Sending all traffic through VPN adapter is not an option.
2. Office -> Client connectivity: How do I make my VPN clients accessible for computers in my internal LAN 10.5.1.0/24?
#2
Never mind. Apparently after adding a NIC one has to reset VnStat DB, there's a button in General tab.
#3
General Discussion / Strange sessions
November 21, 2022, 01:17:09 AM
I observe some strange sessions on my OpnSense box (Firewall -> Diagnostics -> Sessions). I use 1.1.1.1 as DNS provider.
10.5.1.250:2 -> 1.1.1.1:2 - not sure why it is connecting to port 2 at all.
1.1.1.1:2 -> 10.5.1.250:2 somehow matched the "allow DHCP client on WAN" while the rule is about ports 67 and 68, not port 2.
Both sessions remain constantly open, "Expires" value is always 9 or 10 seconds.

Is there some logical explanation to this? Or is there a bug in sessions view?
#4
General Discussion / VnStat not working with my new NIC
November 21, 2022, 12:40:57 AM
Hi,

I've just got a dual NIC from Amazon: https://www.amazon.com/gp/product/B09D3JL14S?ref=ppx_pt2_dt_b_prod_image
It works great with OpnSense as one of the reviews suggested although VnStat fails to display any stats for it while for the other 2 cards it continues to work as expected. See attached screenshots of both cases.
I'd appreciate any ideas.