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

#1
Another thing is that when I use a wizard to create an openvpn rule, it creates a rule automatically in WAN, this rule does not work, it is only copied to FLOATING, and this rule is created automatically in the legend is set in direction in , but the option of direction of traffic in / out, it is only possible to configure in FLOATING, I found it strange
#2
okay, but I can not understand the fact of deleting all the WAN and LAN rules, and leave only one rule in the la to go out to the internet and msm so only with that Filter rule association option that I can connect to, and if I do not have any rules in WAN, how can I connect to my machine inside LAN, sorry if I'm being annoying, but I use pfsense for years, I would like to migrate to opnsense, but I do not understand why these basic things that should be the same in the 2 itms, they behave differently, I would like to migrate clients to opnsense, but before I wanted to understand better, it also has the fact that the openvpn soh rules accept connection coming through the WAN if the rule is in FLOATING, the same rule only in WAN no it works, I have already compared the configs between pfssense and opnsense and they are the same and behave so different, I find it strange
#3
I create a rule of port forward, I go in floating, lan and wan, I create rules releasing everything to all senses, and port forward does not work, it gives timeout, and when I select the option "filter rule association = pass", it works First of all, it does not create any firewall rules, so I can understand these things in opnsense, does it create invisible rules and create rules by releasing everything that is possible in the firewall to continue blocking?
#4
nor editing and of i create manual rule in firewall is not work :/
#5
With these firewall rules openvpn does not connect, from the timeout, but when I put the same very restrictive rule on the floating tule I can connect to vpn and access from wan to lan normally, it's not a route problem, I work with pfsense, and I never needed it use floating rule to use openvpn.

in the attached image, when I use these rules in opnevpn, lan and wan, does not connect, when I apply the same rule of wan in floating connect normally, my question would be, because when I put the same rule in floating I connect with it, being exactly the same rule in wan.

obs: 192.168.0.3 = wan address
#6
17.7 Legacy Series / [BUG] openvpn rule pass connect.
October 15, 2017, 07:41:05 PM
openvpn only connects when I create a floating rule releasing everything, the rule created by openvpn wizard does not work, even releasing all traffic on all interfaces opnsense continues giving timeout, only when I apply the rule in floating.

openvpn 2.4.4. en last version opnsense.

I have done several tests to release all traffic for all interfaces, and no matter how I configure, the vpn client of opnevpn only connects when the same rule created automatically by the opnevpn wizard and recreated in floating, is bug?