| 1 |
* Ian Zimmerman: |
| 2 |
|
| 3 |
> So, how to configure IPv6 on an end user gentoo box (not a router)? |
| 4 |
|
| 5 |
This depends on how clever your existing router is. If it provides |
| 6 |
Router Advertisement, like the FRITZ!Box 7xxx line does, IPv6 clients |
| 7 |
should be configured automatically. As an alternative, you can run |
| 8 |
net-misc/radvd in your network. It is also possible to use fixed |
| 9 |
addresses like so (2001:1111:2222:3333 is an imaginary /64 subnet and |
| 10 |
the rest is based on what you posted): |
| 11 |
|
| 12 |
config_enp2s0="192.168.1.10/24 |
| 13 |
2001:1111:2222:3333::10/64" |
| 14 |
routes_enp2s0="default via 192.168.1.1 |
| 15 |
default via fe80::1" |
| 16 |
|
| 17 |
In case you're wondering, the variables config_x and routes_x can indeed |
| 18 |
contain line breaks. Personally, I don't think static IPv6 addresses are |
| 19 |
very useful, because machines in a local IPv6 network can easily locate |
| 20 |
each other using link-local addressing, without the need to configure |
| 21 |
this in any way. In the example above, the link-local address fe80::1 |
| 22 |
means "the default IPv6 gateway out of here". |
| 23 |
|
| 24 |
IPv6 has more convenient mechanisms, like unique local addresses (ULA), |
| 25 |
that can be configured but don't need to be. If your router is smart |
| 26 |
enough, no configuration is required on the end nodes; be it Linux, |
| 27 |
macOS, Windows, or various smartphones. |
| 28 |
|
| 29 |
One of the many available sources of information is hosted by The Linux |
| 30 |
Documentation Project[1]. |
| 31 |
|
| 32 |
-Ralph |
| 33 |
|
| 34 |
[1] https://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/index.html |
Archives