Messages

Hi,

changed NIC Setup from vmnet3 to e1000 - at the moment it seems stable

ill keep you informed

Hello,

i got still Problems with a IPSec Site-2-Site Tunnel:

the Setup:

Windows Server A <- LAN Connection -> OPN-Sense <-IPsec Tunnel-> ZyXEL USG Firewall <- LAN Connection -> Windows Server B

The description of the problem:
The Windows Servers can Ping each others.
when i copy Files from Server A to Server B over SMB, the Copy-Jobs aboards
when i copy Files from Server A initiated by Server B, the Copy-Job works

can anyone help me?

Hello,

i have an issue about loging into the Console with an LDAP authenticated User.

I can login, i get a prompt, but when i enter "su" it asks me for a Password. On a Linux-System i need to enter the root password of the system - on my opnsense system i only need to press enter and i am root - without any password. Trying the same with a local user doesnt work.

Any ideas?

Hello,

i got some Problems with opnSense 17.1.5. Firewall Rules stop working after some time. To solve these issue i need to reboot the Firewall. Inbound NATed Connections and Outbound connections are affected.

As an example, there is a NAT Rule for inbound SNMP Traffic to my MailGateway. After a reboot everything is workling for some hours, then it stops - without any Changes in the Config i made.

I tried reinstalling and importing the Config, with no success.

It is an Installation on VMware ESXi 6.0 - the NICs are vmnet3

Can anyone help me?

Cheers,
Stefan

Mit der 17.1.4 wars das gleiche Problem. die 17.1.5 kam per AutoUpdate.

gruss,
Stefan

Hallo zusammen,

bei meiner OPNsense Firewall steigen nach einiger Zeit die Firewall Regeln und Port-Forwarding Regeln aus.

Nach einer gewissen Zeit greifen die Regeln nicht mehr, bis man die Firewall neu startet. Installiert ist OPNsense 17.1.5-amd64 - das Problem hab ich jedoch schon seit (neu)Installation des 17er Releases

Edit: Interessant vielleicht noch, das ganze läuft in einer ESX6 Virtuellen Maschine.

Kennt jemand das Problem?

Viele Grüße,
Stefan

just tried Setting

""Use shared forwarding between packet filter, traffic shaper and captive portal"."

reactivates Workarround 

sysctl net.inet.ipsec.filtertunnel=1

Same here,

Workarround 
sysctl net.inet.ipsec.filtertunnel=1
doesnt work anymore after upgrade from 17.1.1 to 17.1.2

tried

sysctl net.inet.ipsec.filtertunnel=0 + Floting Rule does not work

Connection from LAN to IPSEC possible
Connecitons from IPSEC to LAN (Ping -> Possible, everything else -> Impossible)

Aktuell ist das Buggy (Siehe https://forum.opnsense.org/index.php?topic=4313.0)

Zumindest der dort beschriebene WorkArround funktioniert

Updated to 17.1.1 - still not working

Created a Rule IPSEC <net-a> to <net-b> allow, pingtest, nothing happend

created a Rule IPSEC * * allow -> pingtest, worked

Tried a SSH Session, worked for ~10 Seconds, then the session hangs, Firewall Log shows blocks on these sessions.

Reverted to sysctl net.inet.ipsec.filtertunnel=1 - everything works again...strange

Same problem here

Outbound Connections from the Internal OPNsense Network are working, inbound Connections not.

after setting sysctl net.inet.ipsec.filtertunnel=1 inbound Connections are working - with a strange behavior - External IPSEC-IPs are now Tagged as Interface "WAN" - Corresponding Rules created under Firewall > Rules > WAN with Interface WAN are working, the Same Rule created unter "IPSEC" with Interface IPSEC not....