forum.ipfire.org

As I upgraded to core 128 I tested again with the IPFIRE-DNS broadcasted via DHCP. Again the errors are there as long I broadcast the IPFIRE-DNS. As soon my FritzBox-DNS is broadcasted the errors are gone. Very annoying as this way DNSSEC is bypassed. What modification is generating this problem ? I...

Arne.F wrote: ↑

March 6th, 2019, 8:34 am

IPFire validate DNSSec since core80 but something has changed in the last weeks. (Independed from the installed IPFire version).

Any idea what's going on and how it can be solved ?
Any solution (almost) available ?

something has changed in the last weeks Seems to fit the time-frame of the problems. Really back luck, I started with 3 local changes which could be the source of the errors, additionally there is a 4th external one. A nightmare for pinpointing the culprit. Problem is I don't know how DNSSec works....

So if understand it correctly it's DNSSec related. In which core was this implemented in IPFIRE ? Because till Core125 I didn't have any comparable problems. You wrote announcing FRITZBOX-DNS disables the DNSSec validation (in IPFIRE), that explains why then there are no problems. So somewhere there...

Be carefull. With this you disable the DNSSec validation. I know, but it's the only way to have a workable situation together with IPFIRE I have never seen such problems with core127 but now with core128 (i run the testing release for a while) so i think it is not IPFire itself. We search for the P...

So the problem is for sure in IPFIRE's DNS ! I modified DHCP-settings in IPFIRE. Now IPFIRE announces the FRITZBOX-DNS as "Primary DNS:" instead of the IPFIRE-DNS. With that all problems seem to be gone (as a workaround) even when a client is connected via IPFIRE. But it not the way it should be ......

Investigated further. When the problem occurs, a tracert of the url gives "Unable to resolve target system name" >tracert forum.ipfire.org Unable to resolve target system name forum.ipfire.org. A couple of minutes later : >tracert forum.ipfire.org Tracing route to fw01.ipfire.org [81.3.27.38] over a...

Let me first explain my local setup : VDSL-->FritzBox-->IPFIRE-->LAN and Wifi-AP (both connected to the same LAN-port) After upgrading to Core127 many devices had intermittent problems to access sites (even if the site was available a couple of minutes before and reachable again after a couple of mi...

I upgraded today from 124->127 Why oh why did someone change the backup naming ? Backup from 2019-02-11-13:26 .ipf Size 11.10 MB Backup from 20190211-0109 .ipf Size 15.33 MB resulting in a out of order sorting ? ??? and also Backup from ipfire-2.21.i586-full-core127- 2019-02-11-13:26 .iso Size 260.0...

ISO's sind noch immer ein problem (siehe beilage)

Am anfang war auch Backup from ipfire-2.21.i586-full-core124.iso 0 Mb

Deepcuts wrote: ↑

October 16th, 2018, 10:37 am

https://ipfire:444/cgi-bin/hosts.cgi

I know that hosts.cgi, I'm using it for local hostnames.

But the are not specified there

That's the reason I normally modify /etc/hosts.
In the past (before 2.21) that never gave any problems

In the past I had custom entries in the /etc/hosts file
But that doesn't seem to be possible anymore, the /etc/hosts seems to be overwritten at reboot with the default entries I need the additional entries, where can I add them ?

Keine Ahnung was da passiert ist, aber nach einem neuen Restart (including poweroff/on) geht es jetzt.
Und einem Restart hatte ich vorher auch getan !

Frage: was ist die ISO ohne Date-Time die immer dabei kommt ?

The Location in FireInfo is not the correct Country.
Where can I correct that ? How is it determined ?

In Core122 gab es : falsche ISO-name und 0 Mb
In Core123 : ISO-name OK aber noch immer 0 Mb