IPv6 implementation on edge OS

Okay, There must be some auto generated config somewhere. there are fe80 addresses I never entered and whatever change I make to my config, nothing will impact the network itself (I already had some problems before with that ubiquiti edge-router wich did applyed half of my config and had to reboot it 3 times for it to work correctly)

Update :
I did rebuild the entire config from scratch with the learning I got from the previous errors, config seems to work. Still in need to test if it’s stable or not. Until now it seems to be.

Apologies i took a nap
I believe the fe80 is like the 192 ip and 10/12. Ip are for(private home lans)
Try doing ip6(fe80 linklocal)toip4 and its reverse
I figured your isp not have ip6 being a dsl type connection

Point is since your isp not have ip6 you need build your own network ip6 system
This needs to talk to your isp ip4 system (ip6toip4, 6to4(yup there different)) and translate the returned ip6data from ip4 packets
Subnet level to top levels(purpose of different ip6 to ip4 tools is different levels of networking layers)
Dont forget your ip6subnet to ip4subnet or all automatic tools will fail
dns ip6 to ip4 as well too but not as much an issue

Overall goal is to tell your local device that its ip6 needs to use its ip4 as wan port (ip4 sees ip4 gateway as wanport and gateway sees your isp supplied ip as true wan port)

It failed back after 30 minutes.
I still get IPv6 in my network…

Now, My Ip route gives me :
::1 dev lo proto kernel metric 256 pref medium
2a02:a03f:3e76:aa01::/64 dev wlp3s0 proto ra metric 600 pref medium
2a02:a03f:3e81:d701::/64 dev wlp3s0 proto ra metric 600 pref medium
fe80::/64 dev wlp3s0 proto kernel metric 600 pref medium
default via fe80::f29f:c2ff:fe0c:4be0 dev wlp3s0 proto ra metric 600 pref medium

my router ip’s are :
arnold@Cipher:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address S/L Description


eth0 192.168.1.2/24 u/u Proxibouse : shithouse
eth1 - u/u To NOC
eth2 - A/D CONFIG !
eth3 - u/D Workstation papa
eth4 - u/u To-AP
lo 127.0.0.1/8 u/u
::1/128
pppoe0 91.178.59.123 u/u
2a02:a03f:3e00:2759:955c:a9b:c90d:371e/64
switch0 - u/u Switch
switch0.2 172.20.33.33/28 u/u NOC
2a02:a03f:3e81:d701:f29f:c2ff:fe0c:4be0/64
2a02:a03f:3e81:d701::1/64
2a02:a03f:3e76:aa01:f29f:c2ff:fe0c:4be0/64
switch0.3 172.16.0.1/24 u/u Dechamps
switch0.4 172.18.0.1/24 u/u guest
switch0.5 192.168.2.200/24 u/u Datacenter
switch0.8 172.19.0.200/24 u/u Management
switch0.9 192.168.10.1/24 u/u Internet of Shit
switch0.10 192.168.178.1/24 u/u Fritzbox

and a traceroute to outside IPv6 is :
arnold@altea:~$ traceroute -6 mirror.adct.be
traceroute to mirror.adct.be (2001:41d0:700:1b09::2), 30 hops max, 80 byte packets
1 2a02:a03f:3e76:aa01:f29f:c2ff:fe0c:4be0 (2a02:a03f:3e76:aa01:f29f:c2ff:fe0c:4be0) 2.313 ms 2.240 ms 2.177 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

So on the info I have here, I suppose that it’s at the router.

Your idea is to put IPv6 to IPv4… But why? if the ISP provides me a /64, I suppose that means that everything should be working… No?
If I have to go back to IPv4 to go to the internet, that means that even tough my local network could be full IPv6, the uplink is still not IPv6 wich is the objective (correct me if I’m wrong)

pppoe0 91.178.59.123 u/u (wan)
2a02:a03f:3e00:2759:955c:a9b:c90d:371e/64 (wan)
switch0 - u/u Switch
switch0.2 172.20.33.33/28 u/u NOC (gateway)
2a02:a03f:3e81:d701:f29f:c2ff:fe0c:4be0/64. (gateway)
2a02:a03f:3e81:d701::1/64. (linklocal)
2a02:a03f:3e76:aa01:f29f:c2ff:fe0c:4be0/64. (“subnet”)
switch0.3 172.16.0.1/24 u/u Dechamps
switch0.4 172.18.0.1/24 u/u guest
switch0.5 192.168.2.200/24 u/u Datacenter
switch0.8 172.19.0.200/24 u/u Management
switch0.9 192.168.10.1/24 u/u Internet of Shit
switch0.10 192.168.178.1/24 u/u Fritzbox

eth0 192.168.1.2/24 u/u Proxibouse : shithouse

Try porting shithouse to datacenter(im assuming pulled ip6 Address or as stated ip6toip4 needed from shithouse to shithouse ip4 to get passed to main ip4 gateway with ip6 main gateway)
Shithouse ip6 to shithouse link local ip6(fe80)
Link ip6 to ip4 shithouse
Shit ip4 to ip4 gateway it sees and continue ip4toip4 along switch route till at ip6 device wan ip host then
Ip4toip6 linklocal
ip6toip6 of linklocal to wan
Linklocal to me is programable subnet,

eth1 - u/u To NOC
eth2 - A/D CONFIG !
eth3 - u/D Workstation papa
eth4 - u/u To-AP
lo 127.0.0.1/8 u/u
::1/128

With it working then failing i would check heating issues even moisture as well(room humidity checker)