Messages

1

21.7 Legacy Series / Re: trouble using port alias

« on: February 20, 2022, 11:02:30 am »

Hi,

I think you are right.
Is it possible that scheduled rules change the rules reordering also ?

Best regards,
B LORAND

2

21.7 Legacy Series / Re: trouble using port alias

« on: February 10, 2022, 11:55:05 pm »

Another thing, currently i just remove the destination port alias by setting protocols to "any" and it's working (not like i want because all port but it's better than having some traffic allow instead of deny).

3

21.7 Legacy Series / Re: trouble using port alias

« on: February 10, 2022, 10:07:43 pm »

Hi Fright,
Thanks about your interest for my case.

First of all, here my OPNSense version. Notice that i already had this mistake in previous version.



Here the rule that match.



Here aliases that are used by that rule.


Admins_Hosts is a network group that contain other hosts aliases. So here is the result :



And here what i see in session under Diagnostics. Notice that Source IP and destination port match nothing.


If you think to another information that could help for diagnose this problem. You can ask me for.
Thanks

Benoit LORAND

4

21.7 Legacy Series / Re: trouble using port alias

« on: February 09, 2022, 10:35:07 pm »

For information, i'm using port's alias to specify multiple port for one or more firewall rules.
Rules thats are faulty applied also have source filter on only some ip. But they match also other.
I have just trying to disable rule optimisation but they are faulty apply again.

5

21.7 Legacy Series / trouble using port alias

« on: January 25, 2022, 11:18:08 pm »

Hi,

I'm using opnsense community edition 21.7.7

I have discovered recently that some connexion are allowed by one rule who should not be use.
After some research, i found that when i link an alias for destination ports, this rule seem to be used in diagnostics/session.

Is there anyone who already see this ?

Best regards,
B LORAND

6

Virtual private networks / Re: I need to bridge 2 vlan interfaces

« on: December 18, 2020, 08:30:35 pm »

It's not what i want to do. I just want to bridge em3.100 and em2.100. But it's not possible.

If i bridge em3 and em2 and after that apply vlan on bridge. i couldn't separate my lan from my wan anymore...

7

Virtual private networks / I need to bridge 2 vlan interfaces

« on: November 29, 2020, 03:00:57 pm »

Hi everybody,

I need to bridge 2 vlan interfaces for my TV work.

My ISP have two devices. One is firewall and other is the TV player. My opnSense is between them. Where my computers have internet without tagging any packets, my tv player need to communicate with the firewall throught the vlan id 100. So i have setup the vlan id 100 on my WAN and LAN interfaces but i need to bridge them without bridge other VLAN.

Is opnsense able to do this ? in GUI or in CLI ?

Best regards,
Benoit

8

Virtual private networks / route openvpn client throught one gateway first

« on: November 19, 2020, 10:33:58 pm »

Hi all,

I'm using opnsense since many month now and i really appreciate it. At home i use it for routing my wan throught 1 ADSL connexion and an 4G connexion. I use openvpn client to stay connected to my cloud server but this connexion is more stable through ADSL than 4G.

I think this representation attached could help us to understand.

In openvpn settings, if i set output interface to ADSL, i expect it it to use my ADSL gateway, but nothing to do. If my prefer interface is 4G, my vpn connexion will established throught 4G.

In fact i found that in FloatingRules, no indication force traffic originating from 192.168.22.1 to use my adsl gateway.

The other attachments display what i say.

Have i missed something ? is there something else to do ?

regards,
Benoit LORAND