Topics

Not sure, if this is the right place to do.. to say... and i did not see to much of it.. but..

Yesterday i upgraded my system from 18.7 to 19.1. Prepared everything for a worst case of failure.
It was absolutely seamless and smooth. It can't run better.

I want to send a big thank you for all the effort and motivation to the project team. I cam from ipfire a year ago... and yes it was the right decision to do so... from a technical perspective... and from the feeling of beeing a part of a wider community.

Frank

[/usr/lib/liblzma.so.5 Unsupported version 0 of Elf_Verdef entry]

Hi,

i've updated to 18.7.9.

During boot (first time when filesystems are mounted) message

/usr/lib/liblzma.so.5 Unsupported version 0 of Elf_Verdef entry

appears.

System is skipping this message and discovers USB ports.

After "configuring PHP: OK" same message appears three time during executing php scripts.

Finally system hangs with "Enter full pathname of shell or Teturn for /bin/sh" after Launching the inin system...
Not sure what went wrong.... can you guys support me please ?

regards
Frank

Update to V18.1.4 went great. Thanks for that big job !!
FW run without any issue.

BUT

After Update to V18.1.4 (it run), i updated some hours later one of my firewall alias. After reload, the rules, the IGMPProxy (V1.3) is not longer starting (message in logfile: igmpproxy[62733]: There must be at least 1 Vif as upstream.

Config of IGMPProxy is not changed.

Can't find the issue.

Does anybody knows that issue?

[Since updated from 17 to 18 forwarding of incoming https-traffic (443) from DMZ to LAN is not working.]

First off all, thanks a lot for every effort you made to release V18. that's really great.
Apologize for double-posting.

I am using portforwarding (nat rules) to forward SSL traffic from  DMZ based mail-proxy or ssl-proxy to other servers in the LAN-Area.

Since updated from 17 to 18 forwarding of incoming https-traffic (443) from DMZ to LAN is not working.

1.) before i deactivated listen port in admin for web-gui from all (default) to lan, every ssl request was returned from web-gui certificate (which was the wrong one :))

2.) i changed the web-gui listen port to LAN to ensure access from internal lan. external forwarding to my mail-proxy or ssl-proxy is now not longer answered from (wrong) web-gui certificate of opnsense, BUT the mail-proxy and ssl-proxy is responding with "ERR_SSL_PROTOCOL_ERROR". Means all firewall-rules and NAT-rules working but the "ERR_SSL_PROTOCOL_ERROR" is somehow (i dont know where) in the communication of the firewall to the DMZ based proxys.