Messages

My statement apply solely to IPv4 addressing. IPv6 support is currently disabled in my environment.

I have the same effect since update to 25.7. Using dnsmasq for DHCP and unbound DNS for DNS on port accessable for AdGuardHome. Since update to 25.7 only hostnames for fixed adresses are visible in AdGuardHome. All others are IP-Adresses only.

I am using DNSmasp for DHCP and Unbound DNS for DNS. Several VLAN active. Since update to 25.7 no internal hostnames are provided. But defined in override.

Ja ist an.

[nicht]

Ich kann auf IP-Adressen (8.8.8.8) pingen. Auf namen (google.de) nicht.  Die Namensauflösung geht nicht.

Der Proxy ist es nicht.
Die Namensauflösung funktioniert leider auf der LAN Schnittstelle seit dem Update auf 20.1.3 nicht mehr.
Interessanterweise funktionier die Namensauflösung auf den VLAN's einwandfrei.
Ich erkenne keinen Unterschied in der Konfiguration...

Hast Du es gelöst?

Has anyone figured out, why clients (based on linux) has issues to resolve names since last update of opnsense, and windows machines not?

My NAS and Ubiquity Controler are not able to resolve adresses anymore, using opnsense as DNS and Gateway.

Same issue here... since update.. Some Clients (e.g. NAS) is not longer able to resolve via unbound dns running on OPNSense...

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

Hi,

i expected same behaviour since i have VLAN's configured.
When i push the login-button after, lets say 5 secs again, the initial page appears immediately.

I am using chrome.

THANK YOU marjohn56, THANK YOU franco,

i installed from new media and adviced to use an old configuration via installation.
That works brilliant.

- two remarks
1.) During installation the normal warning messages that all data on the selected disk will be erased. even when i have upfront to this message the old installation from disk selected and imported. That was confusing :)

2.) It took me a while to figure out, why i do not have access to the GUI and no Internet access. Reason was, i have seperated my LAN into VLAN's, and also descripted in the alias section. AND... the reason for the issue was, that alias are not included into the backup, or at leased they were not installed from the former installation.
I saw a post here, that you guys have it at your plate, because of inconsistency of old backup to new fw-version.

having this said... again... thanks a lot...

best
Frank

A complete new installation... puuh... 
is there no other possible solution.....?

[/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

I found an different solution, outside the opnsense box. Means... i am out... sorry.