Auteur Sujet: Every 7 days my internet stops working.... (Lu 2308 fois)

Baz · « **le:** 11 octobre 2021 à 11:56:24 »

Hi all,
Sorry this post is in English, my written French is not at a high enough level to write such a complex question.

I have 2 problems after swapping out the freebox revolution for a linux router. I suspect both problems are linked.

1) Every 7 days my internet stops working. I can see traffic (arp requests) with tcpdump when the issue occurs. I can send traffic to the default gateway but I get no response. To resolve the problem I have to unplug the sfp and fibre from the linux box and put it into the freebox router. Let the freebox boot and then swap everything back into the linux router. I suspect this is a DHCP request timeout as it happens exactly 7 days later.

2) I am unable to find a configuration that works for IPv6.

My setup:
I currently have freebox revolution with FTTH. I have replaced my freebox with a linux router. I am using the below settings. No IPv6 tunneling. I assume I have the old P2P architecture.

From /etc/network/interfaces

Citer

#LAN
allow-hotplug eth0
auto eth0
iface eth0 inet static
address 192.168.1.254
netmask 255.255.255.0
broadcast 192.168.1.255
dns-nameservers 192.168.1.254

#DMZ
allow-hotplug eth1
auto eth1
iface eth1 inet static
address 172.16.0.254
netmask 255.255.255.0
broadcast 172.16.0.255

allow-hotplug eth3
auto eth3
iface eth3inet manual
hwaddress ether XX:XX:XX:XX:XX:XX

#Internet IPv4
allow-hotplug eth3.836
auto eth3.836
iface eth3.836 inet static
address <My IPv4 address>
netmask 255.255.254.0
broadcast <My Boardcast subnet>
gateway <My IPv4 gateway address>
hwaddress ether XX:XX:XX:XX:XX:XX

#Internet IPv6
iface eth3.836 inet6 static
#I have tried /60 also. Doesn't work.
address <Public IPv6 address>/64
hwaddress ether XX:XX:XX:XX:XX:XX
post-up sysctl -q net.ipv6.conf.enp5s0/836.accept_ra=2
accept_ra 2

#This works and gets and IP address from DHCP 10.x.x.x/24
allow-hotplug eth3.835
auto eth3.835
iface eth3.835 inet dhcp
hwaddress ether XX:XX:XX:XX:XX:XX

Thanks in advance for your help.

Ping6 · « **Réponse #1 le:** 11 octobre 2021 à 18:57:49 »

Hi,

Be sure to backup your original configuration just in case.

For you 1st issue, I see you use static IPv4 address. I would try to use DHCP to get your WAN address:

Code: [Sélectionner]

iface eth3.836 inet dhcpAnd remove other parameters on the block such as address, netmask, broadcast and gateway. Keep hwaddress.

From my experience (also on with a GNU/Linux home made router), I had also this kind of disconnection, I switch to dhcp6 and problem disapear.

For your second issue, if your IPv4 internet is working via DHCP, it seems you are on "old" Free infrastructure. So to have IPv6 you need to setup a 6rd tunnel. I may be wrong but being on P2P infrastructure does not change anything for IPv6.

Please note that on "recent" Free infrastructure deployment, IPv6 is native and IPv4 goes by a IPv4-over-IPv6 tunnel. You may be migrated one day though so remember that

. FYI on the forum you will find my notes to setup a Debian GNU/Linux box for this kind of infrastructure.

Regards,

cali · « **Réponse #2 le:** 11 octobre 2021 à 20:42:43 »

Citation de: Baz le 11 octobre 2021 à 11:56:24

I suspect this is a DHCP request timeout as it happens exactly 7 days later.

Correct. You are required to send DHCP packets even if you're using a static config.

I would recommend you to keep your static configuration and just have a dhcp daemon sends the annoying renew/solicitation.

Baz · « **Réponse #3 le:** 13 octobre 2021 à 20:22:39 »

Hi,
Changing the interfrace eth3.836 to DHCP works. So I am definitely on the old infrastructure. Now I just have to wait 7 days to see if that solves my first problem.

As for IPv6 I will look at putting dhcp6 in place.

I have already read your guide and I planned a complete setup using it, before realizing I was on the older infrastructure. When/If I get changed over to ipv6, I will be using your guide to do the switch over. Thank you for writing that.

Also cheers for the responses.

Hugues · « **Réponse #4 le:** 13 octobre 2021 à 21:15:53 »

there is no native ipv6 on the legacy infrastructure, you will never have connectivity unless you use 6rd tunnel

eahlys · « **Réponse #5 le:** 13 octobre 2021 à 21:45:38 »

I second the idea that lack of DHCP request are causing trouble to your connection.
In fact, your ISP needs to know that you are online so that traffic directed to you can be routed to your freebox (or custom router) by its own routers. This is done via DHCP. If you do not send DHCP requests for long enough, it will assume that you’re online and therefore stop routing your IP.
Keep it simple : send DHCP requests while keeping your WAN interface static. But without those DHCP requests you will keep loosing your connection every 7 days.