Hello, kind people. There is a system with this connection: router - IPFire - computers. So, when the Internet was first connected, not all sites were opened. I registered the DNS manually and now I periodically lose the Internet. The Internet does not appear until I restart IPFire. Who knows what the problem is?
Last time we discussed your network setup, did you change your connections?
because it should be
WAN -RED-> IPFire -GREEN-> router.
and not
WAN → router -LAN->-RED->IPFire
The ipf router connection failed with my operator. Therefore, the Internet cable is connected to the wan port of the router 192.168.30.2, then from the LAN port of the router to the wan Ipf 192.168.30.3 and the lan output IPF 192.168.50.2.
1 Like
Well first we need to get it working correctly with the operator instead of trying to link through a Chinese compromised router such as the tplink.
But first, list what you have for hardware as the ipfire computer, and what version of ipfire is installed.
Unfortunately, it didn’t work out with the operator, although everything was fine on our side. IPF equipment 2 GB ddr3 RAM, 250 GB disk, intel pentium g2020, old memory cards, one 1000 mbit/s, the other 100 mbit/s.
maybe things are getting lost in translation
When you refer to operator, do you mean internet service provider?
I want to know what network card brand and model # or if this is on the motherboard, its brand and model # that is used for the red.
And ipfire version is loaded (190, 191…etc)
There is no reason why its not working in place of the tp-link router, other than hardware drivers and kernel version that has been the only real source of it not working.
The operator, yes, the Internet provider. The latest version of ipfire is 191. Unfortunately, the model is not reflected anywhere. But I can say that the problem is with the Internet provider, since everything works with it. Since we need to connect it to an Internet provider with which ipf does not work instead of a router, I made an ipf router. And basically everything works fine, but after a while the Internet disappears. That’s my task. After reading a lot of articles, it seems to me that DNS may be to blame for the Internet outage, although it is written correctly.
It could be driver related that is patched in the later version. Go into pakfire and change the repository to testing and save, the page will refresh and update the system to 192 testing.
Also make sure all the power savings features are disabled in bios.
Do you have a working DNS configuration?
1 Like
If this is a dhcp red0, next time it goes down, type
ip link show red0
and see if the link is down or up, either way, then reset it:
ip link set red0 down
ip link set red0 up
dhclient red0 -v
Tell us if the link was down or up before resetting. This will tell me if the driver is timing out and/or the dchp is not renewing.
Of course we can auto reset red by creating a watchdog script.
navigate to the auto trigger directory of the condition of red being down:
cd /etc/init.d/networking/red.down
then open an editor and write the file, 00-watchdog :
nano 00-watchdog
and enter this code:
#!/bin/bash
ip link set red0 down
ip link set red0 up
dhclient red0 -v
Then ctrl+o to write the file, then ctrl+x to exit the editor
Now we make sure root owns it, and mark it as executable :
chown root 00-watchdog
chmod +x 00-watchdog
Thanks a lot for the advice, I’ll try everything and write it here.
My DNS configuration is as follows: 77.88.8.8, common.dot.dns.yandex.net
From: [www.ipfire.org - List of Public DNS Servers]Preformatted text(www.ipfire.org - List of Public DNS Servers)
DNS providers not recommended for IPFire
These providers are not recommended for use with IPFire because they do not support DNSSEC or tamper with DNS traffic in another way, such as filtering advertisement, malware or porn. While there is a legitimate use-case for the latter, such filtering breaks DNSSEC, being indistinguishable from an adversary from a technical point of view.
| Operator | IP Addresses | Reason |
|---|---|---|
| Adfree.world | 139.99.176.64 | Domain Blacklist1 |
| Cleanbrowsing | 2a0d:2a00:1::2 / 185.228.168.9, 2a0d:2a00:2::2 / 185.228.169.9 | Domain Blacklist2 |
| DNS for Family | 94.130.180.225 / 2a01:4f8:1c0c:40db::1, 78.47.64.161 / 2a01:4f8:1c17:4df8::1, dns-dot.dnsforfamily.com, https://dns-doh.dnsforfamily.com/dns-query | Domain Blacklist3 |
| Comodo Secure DNS | 8.26.56.26, 8.20.247.20 | Domain Blacklist 4 |
| dnsforge.de | 176.9.93.198, 176.9.1.117, 2a01:4f8:151:34aa::198, 2a01:4f8:141:316d::117 | Domain Blacklist5 |
| Nuernberg Internet Exchange (N-IX) | 194.8.57.12 | Not resolving6 |
| OpenDNS (Hosted Blacklists) | 208.67.222.222, 208.67.220.220, 208.67.220.222, 208.67.222.220 | Domain Blacklist7 |
| Quad 9 | 9.9.9.9, 149.112.112.112, 9.9.9.10, 149.112.112.10 | Domain Blacklist8 |
| SWITCH | 130.59.31.248 / 2001:620:0:ff::2, 130.59.31.251 / 2001:620:0:ff::3 | Domain Blacklist9 |
| *Yandex.DNS | 77.88.8.88, 77.88.8.2* | Domain Blacklist10 |
| SafeDNS | 195.46.39.39, 195.46.39.40 | Questionable regulations11 |
*note 10 : Yandex DNS states “…block adult-only and dangerous websites” (aka self-explanatory) : https://dns.yandex.com/. The mentioned IPs are from the “Safe” section.
Try selecting a recommanded dns provider
2 Likes
kinky yandex Russians!! 
lol adding Look into the “Safe” section