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

Topics - benoit.lorand

#1
21.7 Legacy Series / trouble using port alias
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

#2
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
#3
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