Messages

1

18.1 Legacy Series / Re: Unable to let connect a mobile device to the LAN

« on: January 07, 2019, 10:16:20 am »

Technically that was not solved. Practically it's up to you, I don't really care anymore since I'm not using it any longer. 

2

18.1 Legacy Series / Re: Unable to let connect a mobile device to the LAN

« on: January 04, 2019, 09:52:07 am »

Never mind, this thread can be closed as I uninstalled OPNSense and installed another product.

Thanks

3

18.1 Legacy Series / Re: Unable to let connect a mobile device to the LAN

« on: December 29, 2018, 06:59:00 pm »

Hello

nobody willing to help ? 

4

18.1 Legacy Series / Unable to let connect a mobile device to the LAN

« on: December 12, 2018, 08:17:08 pm »

Hello guys

I started to have this issue about a month ago and since then, I was not able to figure out what's wrong. In short, I have a mobile device of mine which was used to connect perfectly fine to internal LAN systems from the WAN network, now seems there's no way to get it back.
I pretty much tried everything I could think ok, which includes:
- Changing existing rules (which were working perfectly fine before the issue)
- Changing the alias (I'm using aliases within the rules, and I associated 1 alias to my device)
- Restart all the devices involved (routers, switches, virtual hosts and so on)
- Upgrade the firewall to the latest version and re-importing settings
- Spinning up a new machine (I use OPNSense on a VM) and install it from scratch without re-importing anything
- Trying from another mobile device
- Plus tons of other things I forgot
None of the above worked. What I noticed during the troubleshooting though (hope this can help somehow), is that as soon as I change the IP of the device and try to connect, it seems some packets go through (for example I'm able to initiate an RDP session), but then it stops and hang there. If I try it again without changing the IP, it doesn't work at all. If I change the IP (and consequently the rule), it works for a little while then it stops.

If I disable packet filtering completely it works perfectly every time.

I'm not an expert at all, but to me it looks like the firewall starts to block the device at the first connection attempt and it needs some packets to identify it so that it can block it, but I can't understand where this setting would be. Within the firewall logs, it says "pass" for all the connections attempted by that device.

This thing is driving me crazy, I really hope somebody will help me to sort it out, otherwise I'll just disable the packet filtering and use it for routing only.

Thank you guys !!