wuslor
(Wuslor)
23 April 2023 12:30
1
Hi Community, i have to come back with a Problem what i had some time ago.
See post below (no Internet because of broken Domain Name System):
Dear Community,
i have Vodafone Internet.
Yesterday i recevied the new Modem because i changed my contract from 500Mbit to 1000Mbit.
The old modem was running in Bridge Mode.
I changed the Modem and then i changed again in the Interface of Vodafone the Mode to Bridge.
Now my IP-Fire gets the Public IP (its working)
[2_1]
But i dont have any DNS resolve or DNS, therefore internet is not working.
In the Domain Name System i get the Status broken.
[https://s20.directupload.net/images/2106…
Iam facing the same issue again.
But i can not solve it. (vodafone Kabel Modem in Bridge Mode)
This is how it looks:
I tried follow:
turn off Vodafone Kabel Modem (2 minutes - 60 minutes)
switch from Bridge, to non Bridge and Back with enough time to boot and sync
reinstall IPFire to newest version
turned off / restarted several times with different sequences IPFire and Vodafone Modem
changed the DNS to TCP / TLS
changed back to Provider DNS as UDP
After spending a complete day i have no idea anymore how to fix.
Does someone have an idea?
Thanks!
BR
Wuslor
bbitsch
(Bernhard Bitsch)
23 April 2023 12:57
2
Can you ping the name servers 1.1.1.1 or 8.8.8.8?
angrytux
(Me Here)
23 April 2023 13:03
3
Keep TLS, no need for UDP.
Seems like it’s the same problem I had with my VF cable connection → DHCP client on red0 won't reassign IP upon reconnection - #25 by angrytux
I named it check_red.sh and a cronjob checks if red is down. If that’s the case ipfire handles a reconnect. Cronjob: */15 * * * * /root/check_red.sh
It takes a few minutes and all works again, including dns.
1 Like
angrytux
(Me Here)
23 April 2023 13:08
5
Your dns servers aren’t correct for dns over tls too. You need an ip and the tls host name.
Example:
1 Like
wuslor
(Wuslor)
23 April 2023 13:10
6
Hi, thanks for the feedback.
Looks like is a VF problem… had this in the past but not so extreme like.
Somehow it always worked after view times
I made it in the console manual:
dhcpcd -k red0
waited 60 sec
dhcpcd -n red0
still not working
And i changed back to TLS.
wuslor
(Wuslor)
23 April 2023 13:12
7
No, thats correct:
example for one of my DNS Servers
bbitsch
(Bernhard Bitsch)
23 April 2023 13:15
8
If you do the red restart sequence you should get messages on the console and/or in /var/log/messages.
If the ping to the servers isn’t possible, I think there is problem on the IPFire-modem connection or in the modem itself.
Does the modem ( VF router in bridge mode ) signal successful connection to the provider network?
wuslor
(Wuslor)
23 April 2023 13:24
9
When i connect my laptop and restart the modem i get a DHCP and able to have internet access (bridge mode).
Therefore i beleive the modem is ok.
In the morning i turned the bridge off, everything works fine, too.
But i turned it of course back.
Still same issue
Last step says DNS not functioning, before the OK overrides
wuslor
(Wuslor)
25 April 2023 16:19
10
Is there any idea from someone?
I think i go back to 173.
How can i find the old versions of ipfire?
Thanks
jon
(Jon)
26 April 2023 21:00
11
Here is CU 173:
https://mirror1.ipfire.org/releases/ipfire-2.x/2.27-core173/
Installing this will wipe your drive so make sure you have a backup on a separate hard drive.
1 Like