From 0ec9af431150d8363405469c82f3b8148ed454e9 Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Mon, 10 Feb 2020 19:45:02 +0100 Subject: [PATCH] ++ clarify /22 wording --- content/u/blog/how-to-route-ipv4-via-ipv6/contents.lr | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/u/blog/how-to-route-ipv4-via-ipv6/contents.lr b/content/u/blog/how-to-route-ipv4-via-ipv6/contents.lr index d4d6747..98b5e76 100644 --- a/content/u/blog/how-to-route-ipv4-via-ipv6/contents.lr +++ b/content/u/blog/how-to-route-ipv4-via-ipv6/contents.lr @@ -51,10 +51,11 @@ default via inet6 fe80::21b:21ff:febb:6934 dev wlp0s20f3 Now to be able to actually transmit IPv4 packets, I do need a source IPv4 address. In the current network I can use an address in the -unused 10.0.8.0/22 network: +unused 10.0.8.0/22 network, however I'll add it with a /32 mask to +make it clear that there is no interface local route applied: ``` -ip addr add 10.0.8.42/32 dev wlp0s20f3 +[root@diamond ~]# ip addr add 10.0.8.42/32 dev wlp0s20f3 [root@diamond ~]# ip r default via inet6 fe80::21b:21ff:febb:6934 dev wlp0s20f3 [root@diamond ~]# ip a sh dev wlp0s20f3