diff --git a/LDP/howto/docbook/HOWTO-INDEX/howtoChap.sgml b/LDP/howto/docbook/HOWTO-INDEX/howtoChap.sgml index c40dbc7c..03db1afe 100644 --- a/LDP/howto/docbook/HOWTO-INDEX/howtoChap.sgml +++ b/LDP/howto/docbook/HOWTO-INDEX/howtoChap.sgml @@ -2805,7 +2805,7 @@ Describes how to set up MMBase on a Debian GNU/Linux (Woody) system. Mobile-IPv6-HOWTO, Linux Mobile IPv6 HOWTO -Updated: Dec 2003. +Updated: Feb 2004. Describes the software and procedures to set up and use mobile IPv6 for Linux. diff --git a/LDP/howto/docbook/HOWTO-INDEX/networkingSect.sgml b/LDP/howto/docbook/HOWTO-INDEX/networkingSect.sgml index 84ab6487..55e84016 100644 --- a/LDP/howto/docbook/HOWTO-INDEX/networkingSect.sgml +++ b/LDP/howto/docbook/HOWTO-INDEX/networkingSect.sgml @@ -512,7 +512,7 @@ applications to make them LDAP-aware. Mobile-IPv6-HOWTO, Linux Mobile IPv6 HOWTO -Updated: Dec 2003. +Updated: Feb 2004. Describes the software and procedures to set up and use mobile IPv6 for Linux. diff --git a/LDP/howto/docbook/Mobile-IPv6-HOWTO/Mobile-IP.png b/LDP/howto/docbook/Mobile-IPv6-HOWTO/Mobile-IP.png index 79c65dde..f68e61a9 100644 Binary files a/LDP/howto/docbook/Mobile-IPv6-HOWTO/Mobile-IP.png and b/LDP/howto/docbook/Mobile-IPv6-HOWTO/Mobile-IP.png differ diff --git a/LDP/howto/docbook/Mobile-IPv6-HOWTO/Mobile-IPv6-HOWTO.xml b/LDP/howto/docbook/Mobile-IPv6-HOWTO/Mobile-IPv6-HOWTO.xml index ab02ea52..26b596e0 100644 --- a/LDP/howto/docbook/Mobile-IPv6-HOWTO/Mobile-IPv6-HOWTO.xml +++ b/LDP/howto/docbook/Mobile-IPv6-HOWTO/Mobile-IPv6-HOWTO.xml @@ -1,9 +1,9 @@ - - + "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" []> + +
@@ -22,10 +22,17 @@ LKS - 2003-12-07 + 2004-02-04 + + 1.1 + 2004-02-04 + LKS + Added "Travelling through several foregin LAN's" + and "Returning home". Some cleanup and restructuring. + 1.0 2003-12-02 @@ -33,14 +40,14 @@ Reviewed by LDP - 0.7.2 + 0.5.2 2003-11-26 LKS A lot of cleanup. Thanks to John Levon levon [at] movementarian.org - 0.7.1 + 0.5.1 2003-11-22 LKS Changed the license from - 0.7 + 0.5 2003-11-18 LKS Converted to XML Docbook. Some cleanup. - 0.6 + 0.4 2002-11-07 LKS Fixed some errors + update. Thanks to Henrik Petander petander (at) tcs hut fi. - 0.5.1 + 0.3.1 2003-11-03 LKS Updated to MIPL relase 1.0 (kernel 2.4.22). - 0.5 + 0.3 2003-08-05 LKS Initial release. @@ -154,7 +161,8 @@ - + Mobile IP @@ -260,9 +268,10 @@ updated since 1998, so it is considered obsolete. The other implementation, which is up-to-date, is Helsinki University of Technology's MIPL project. The latest supported kernel is 2.4.22, and they have patches for the upcoming 2.6 -kernel. Visit +kernel (see the FAQ). Visit http://www.mipl.mediapoli.com/ for papers, software or to -browse the mail archive. +browse the mail archive. @@ -362,7 +371,7 @@ browse the mail archive. With debug messages it is easier to figure out what happened when something goes wrong. Also, when reporting a bug, - debug messages are very helpful: + debug messages are very helpful. To be sure you have all the correct options, you can run chkconf_kernel.sh, which is a small shell @@ -373,9 +382,9 @@ browse the mail archive. Next you should compile and install your kernel. Hint: To easily distinguish this kernel from other - kernels, you can change the EXTRAVERSION value in the - /usr/src/linux/Makefile to - for example -MIPv6-1. + kernels, you can change the EXTRAVERSION variable + in the /usr/src/linux/Makefile to for + example -MIPv6-1. @@ -470,6 +479,10 @@ browse the mail archive. # echo '/etc/rc.d/mobile-ip6 start' >> /etc/rc.d/rc.local + + If you don't hack the Makefile, the + mobile-ip6 script is installed at '/' (you + may then move it to /etc/rc.d/). @@ -490,8 +503,9 @@ browse the mail archive. Testcase The addresses we are using in our test-bed are - site-local. Note that linking local addresses won't - work! Our test-bed consist of four nodes; see figure + site-local. You may as well use global addresses, but do + note that link local addresses won't work! + Our test-bed consist of four nodes; see figure "Mobile IPv6 testbed". @@ -518,17 +532,19 @@ browse the mail archive. AR - Access Router: The link - between AR and R is our internet (but is actually only a - cross-cable). The AR has two interfaces; the wired interface - to R has address fec0:106:2300::1, the - wireless has address fec0:106:1100::1. + between AR and R is our internet - but in this + testcase only a cross-cable (can be any network). The AR has + two interfaces; the wired interface to R has address + fec0:106:2300::1, the wireless has + address fec0:106:1100::1. - + Mobile IPv6 testbed @@ -541,15 +557,16 @@ browse the mail archive. - Step-by-step + Step-by-step configuration - Fully functional IPv6 network + Setting up a fully functional IPv6 network Before we can start testing mobile IP, we need a fully functional IPv6 network. All the nodes should be able to ping - each other. This is a crucial part. If, for example, AR is not - able to ping HA, then there will be no binding update. + each other. This is a crucial part. If, for + example, AR is not able to ping HA, then there will be no binding + update. I will give a brief instruction to get our network up and running using IPv6. For more info on setting up an IPv6 network, @@ -577,8 +594,7 @@ browse the mail archive. # echo "1" > /proc/sys/net/ipv6/conf/eth0/autoconf # echo "1" > /proc/sys/net/ipv6/conf/eth0/accept_ra # echo "1" > /proc/sys/net/ipv6/conf/eth0/accept_redirects - # /etc/init.d/mobile-ipv6 start - # ip route add ::/0 via fec0:106:2700::1 + # /etc/init.d/mobile-ip6 start @@ -589,8 +605,9 @@ browse the mail archive. because it uses normal routing to deliver packets captured from a physical interface to the virtual tunnel interface. Note: You must add a default route or else - HA will have problem contacting the MN. One possible solution - is to have HA as the default router of the home network. + HA will have problem contacting the MN on visited LAN's. One + possible solution is to use HA as the default router of the + home network. # iwconfig eth0 mode ad-hoc essid homenet enc off @@ -600,14 +617,14 @@ browse the mail archive. # echo "0" > /proc/sys/net/ipv6/conf/eth0/accept_ra # echo "0" > /proc/sys/net/ipv6/conf/eth0/accept_redirects # ip route add ::/0 via fec0:106:2700::1 - # /etc/init.d/mobile-ipv6 start + # /etc/init.d/mobile-ip6 start R: The (home) Router has two - interfaces, one wireless and one line. The Router must have - forwarding turned on. + interfaces; one wireless and one line. The Router must have + forwarding turned on. # ifconfig eth0 inet6 add fec0:106:2300::2/64 @@ -623,7 +640,7 @@ browse the mail archive. AR: The Access Router (on a foreign - network) also has two interfaces, one wireless and one + network) also has two interfaces; one wireless and one line. Forwarding must be turned on. @@ -646,6 +663,122 @@ browse the mail archive. should now be able to ping all the hosts from every host. + + + Configuring Mobile IPv6 + The last configuration is MIPv6 settings in + network-mip6.conf. In Debian/Slackware the + file is found under /etc/. (RedHat the file + is found under /etc/sysconfig/.) The file + should be pretty self-explanatory. + + + + HA: The HA config file should + contain these settings: + + # cat /etc/network-mip6.conf + + # Home Agent configuration file + FUNCTIONALITY=ha + DEBUGLEVEL=1 + MIN_TUNNEL_NR=1 + MAX_TUNNEL_NR=5 + TUNNEL_SITELOCAL=yes + + + + + MN: The MN config file should + look like this: + + # cat /etc/network-mip6.conf + + # Mobile Node configuration file + FUNCTIONALITY=mn + DEBUGLEVEL=1 + TUNNEL_SITELOCAL=yes + MIN_TUNNEL_NR=1 + MAX_TUNNEL_NR=3 + HOMEDEV=mip6mnha1 + HOMEADDRESS=fec0:106:2700::4/64 # MN's home adress + HOMEAGENT=fec0:106:2700::2/64 # HA's address + + + + + Next, start mobile-IP: + + # /etc/init.d/mobile-ip6 start + Starting Mobile IPv6: OK + + + + + You can verify that it started by doing a + ifconfig on HA. If the tunnel(s) comes up, + ip6tnl1, mobile-ip6 is started: + + + # ifconfig + eth1 Link encap:Ethernet HWaddr 00:02:2D:2D:DE:79 + inet6 addr: fec0:106:2700::2/64 Scope:Site + inet6 addr: fe80::202:2dff:fe2d:de79/64 Scope:Link + UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 + RX packets:618 errors:6 dropped:6 overruns:0 frame:6 + TX packets:1485 errors:22 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:100 + RX bytes:87914 (85.8 KiB) TX bytes:252596 (246.6 KiB) + Interrupt:3 Base address:0x100 + + ip6tnl1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 + UP POINTOPOINT RUNNING NOARP MTU:1460 Metric:1 + RX packets:6 errors:0 dropped:0 overruns:0 frame:0 + TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:0 + RX bytes:576 (576.0 b) TX bytes:624 (624.0 b) + + ip6tnl2 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 + UP RUNNING NOARP MTU:1460 Metric:1 + RX packets:0 errors:0 dropped:0 overruns:0 frame:0 + TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:0 + RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) + + lo Link encap:Local Loopback + inet addr:127.0.0.1 Mask:255.0.0.0 + inet6 addr: ::1/128 Scope:Host + UP LOOPBACK RUNNING MTU:16436 Metric:1 + RX packets:8 errors:0 dropped:0 overruns:0 frame:0 + TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:0 + RX bytes:560 (560.0 b) TX bytes:560 (560.0 b) + + + + + The tunnel is up and ready for connections. + + + Another tunnel ready. + + + + You will also see the mipv6 kernel modules are loaded (MN): + + + # lsmod + Module Size Used by Not tainted + mip6_mn 59888 0 (unused) + ipv6_tunnel 11448 1 [mip6_mn] + mip6_base 40728 0 [mip6_mn] + ipv6 179764 -1 [mip6_mn ipv6_tunnel mip6_base] + ... + + + + + Configuring radvd on AR @@ -671,7 +804,8 @@ browse the mail archive. obtain an advertisement quickly, a host sends one or more Router Solicitations to the all-routers multicast group. --- page 8 - This is where we use RADVD. + This is where we use + RADVD. Read [RFC2462] @@ -683,23 +817,24 @@ browse the mail archive. # cat /etc/radvd.conf - interface eth1 - { + interface eth1 + { AdvSendAdvert on; - AdvIntervalOpt on; + AdvIntervalOpt on; - MinRtrAdvInterval 3; - MaxRtrAdvInterval 10; - AdvHomeAgentFlag off; + MinRtrAdvInterval 3; + MaxRtrAdvInterval 10; + AdvHomeAgentFlag off; - prefix fec0:106:1100::/64 - { - AdvOnLink on; - AdvAutonomous on; - AdvRouterAddr on; - }; - }; + prefix fec0:106:1100::/64 + { + AdvOnLink on; + AdvAutonomous on; + AdvRouterAddr on; + }; + }; + We then start it: @@ -729,8 +864,14 @@ browse the mail archive. AdvSourceLLAddress: 00 02 2D 54 D1 B2 + Note! When using radvd on HA and enabling + autoconf (in proc), you will also get an + autogenerated IPv6 address on MN (which is superfluous) in + addition to your static address: + + Configuring radvd on HA @@ -742,11 +883,11 @@ browse the mail archive. # cat /etc/radvd.conf - interface eth1 + interface eth0 { AdvSendAdvert on; MaxRtrAdvInterval 3; - MinRtrAdvInterval 1; + MinRtrAdvInterval 1; AdvIntervalOpt off; AdvHomeAgentFlag on; HomeAgentLifetime 10000; @@ -763,57 +904,64 @@ browse the mail archive. }; - To be completed. + Also do a radvdump on HA to check + whether radvd messages are beeing sent: + + + # radvdump + Router advertisement from fe80::202:2dff:fe54:d11e (hoplimit 255) + Received by interface eth0 + # Note: {Min,Max}RtrAdvInterval cannot be obtained with radvdump + AdvCurHopLimit: 64 + AdvManagedFlag: off + AdvOtherConfigFlag: off + AdvHomeAgentFlag: on + AdvReachableTime: 0 + AdvRetransTimer: 0 + Prefix fec0:106:2700::2/64 + AdvValidLifetime: 12000 + AdvPreferredLifetime: 10000 + AdvOnLink: on + AdvAutonomous: on + AdvRouterAddr: on + AdvSourceLLAddress: 00 02 2D 54 D1 1E + AdvHomeAgentInfo: + HomeAgentPreference: 20 + HomeAgentLifetime: 1000 + + + + # ifconfig eth0 + eth0 Link encap:Ethernet HWaddr 00:90:7D:F3:03:1A + inet6 addr: fec0:106:2700:0:290:7dff:fef3:31a/64 Scope:Site + inet6 addr: fec0:106:2700::4/64 Scope:Site + inet6 addr: fe80::290:7dff:fef3:31a/64 Scope:Link + UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 + RX packets:513 errors:89 dropped:89 overruns:0 frame:85 + TX packets:140 errors:41 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:100 + RX bytes:56084 (54.7 Kb) TX bytes:19212 (18.7 Kb) + Interrupt:3 Base address:0x100 + + + + + A new (superfluous) autogenerated address. Since we are + setting autoconf in + /proc/sys/net/ipv6/conf/eth0/autoconf + to 1, MN will generate a new adress + combined with HA's prefix and it's own MAC address. I do not + think is it possible to avoid having this address generated. + + + Our original static IPv6 address + + + The link-local address generated at boot. + + - - - - Configuring MIPv6 - The last configuration is MIPv6 settings in - network-mip6.conf. In RedHat the file is - found under - /etc/sysconfig/network-mip6.conf. The file - should be pretty self-explanatory. - - - # cat /etc/sysconfig/network-mip6.conf - - # Home Agent configuration file - FUNCTIONALITY=ha - DEBUGLEVEL=1 - MIN_TUNNEL_NR=1 - MAX_TUNNEL_NR=5 - TUNNEL_SITELOCAL=yes - - # cat /etc/sysconfig/network-mip6.conf - - # Mobile Node configuration file - FUNCTIONALITY=mn - DEBUGLEVEL=1 - TUNNEL_SITELOCAL=yes - MIN_TUNNEL_NR=1 - MAX_TUNNEL_NR=3 - HOMEDEV=mip6mnha1 - HOMEADDRESS=fec0:106:2700::4/64 # MN home adress - HOMEAGENT=fec0:106:2700::2/64 # HA's address - - - Next, start mobile-IP: - - - # /etc/init.d/mobile-ip6 start - - - You can verify that it started by doing: - - - # ifconfig - - - If a tunnel comes up ip6tnl1, mobile-ip6 is started. - - @@ -865,13 +1013,14 @@ browse the mail archive. # tcpdump -i eth0 -vv ip6 or proto ipv6 - To travel to another net, you can issue the command on MN: + To travel to another net, you can issue the + command on MN: # iwconfig eth1 essid visitnet - The MN is the on the other wireless network, and since it is + The MN is then on the other wireless network, and since it is sending out router solicitation (multicast), our AR will respond with it's prefix. MN will then configure itself with at new IPv6 address with the received prefix and it's own MAC address. If @@ -879,30 +1028,36 @@ browse the mail archive. address: - # ifconfig eth0 - eth0 Link encap:Ethernet HWaddr 00:02:A5:6F:A0:8A - inet addr:192.168.100.134 Bcast:255.255.255.255 Mask:255.255.255.255 - inet6 addr: fe80::202:a5ff:fe6f:a08a/10 Scope:Link - inet6 addr: fec0:106:1100:0:202:a5ff:fe6f:a08a/64 Scope:Site - inet6 addr: fec0:106:2700::4/64 Scope:Site - UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 - RX packets:65 errors:44 dropped:0 overruns:0 frame:44 - TX packets:134 errors:5 dropped:0 overruns:0 carrier:0 - collisions:0 txqueuelen:100 - RX bytes:5528 (5.3 Kb) TX bytes:21272 (20.7 Kb) - Interrupt:3 Base address:0x100 + # ifconfig eth0 + eth0 Link encap:Ethernet HWaddr 00:90:7D:F3:03:1A + inet6 addr: fec0:106:1100:0:290:7dff:fef3:31a/64 Scope:Site + inet6 addr: fec0:106:2700:0:290:7dff:fef3:31a/64 Scope:Site + inet6 addr: fec0:106:2700::4/64 Scope:Site + inet6 addr: fe80::290:7dff:fef3:31a/64 Scope:Link + UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 + RX packets:854 errors:154 dropped:154 overruns:0 frame:148 + TX packets:293 errors:58 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:100 + RX bytes:96536 (94.2 Kb) TX bytes:44664 (43.6 Kb) + Interrupt:3 Base address:0x100 + + + The new foreign address, generated by + combining AR's prefix and MAC-address + + + The superfluous home network address (because of HA + radvd messages and MN autoconf set to + true). + + + The original (home) address + The link-local address generated at boot - - The new foriegn address, generated by combining AR's - prefix and MAC-address - - - The old (home) address - Almost at the same time, the MN will perform a binding update @@ -949,19 +1104,19 @@ browse the mail archive. # mipdiag -l Mobile IPv6 Binding update list Recipient CN: fec0:106:2700::2 - BINDING home address: fec0:106:2700::4 care-of address: fec0:106:1100:0:202:a5ff:fe6f:a08a - expires: 115 sequence: 0 state: 1 - delay: 3 max delay 256 callback time: 68 + BINDING home address: fec0:106:2700::4 care-of address: fec0:106:1100:0:290:7dff:fef3:31a + expires: 936 sequence: 0 state: 1 + delay: 3 max delay 32 callback time: 736 You can also verify it on HA with the statistics option - (-s) and with the: + (-s) and with the binding cache (-c) option: # mipdiag -c Mobile IPv6 Binding cache - Home Address Care-of Address Lifetime Type - fec0:106:2700::4 fec0:106:1100:0:202:a5ff:fe6f:a08a 104 2 + Home Address Care-of Address Lifetime Type + fec0:106:2700::4 fec0:106:1100:0:290:7dff:fef3:31a 971 2 @@ -1007,7 +1162,7 @@ browse the mail archive. - You can now see the statistics have been updated: + You can now see the statistics have been updated (on MN): # mipdiag -s @@ -1032,6 +1187,12 @@ browse the mail archive. ::/0 :: UD 64 0 0 ip6tnl1 .... + + If it doesn't add a default route, you may add it manually: + + + # ip route ::/0 via dev ip6tnl + @@ -1039,7 +1200,108 @@ browse the mail archive. Travelling through several foregin LAN's - To be completed. + To travel to several visited networks, is no different than + travel to one network. The only thing you + must have in mind is that you will generate a new address for each + visited network. + + + + + + + + + + + MN travelling through severeal different LANs. + + + + + + MN first visits 'visitnet', as we have been through above. + + + MN is then travelling from 'visitnet' to + 'visitnet2'. + + + When at 'visitnet2', MN generates a new IPv6 address and + do a new binding update to HA. + + + MN then travels back home. (Se next section.) + + + + The AR at visitnet2, is configured exactly + as the other AR (at visitnet), except using address + fec0:106:1000::/64 instead of + fec0:106:1100::/64. + + To make the mobile node travel from 'visitnet' to + 'visitnet2', issue the command (on MN): + + + # iwconfig eth0 essid visitnet2 + + + You will then see the MN configures itself to the new network: + + + # ifconfig eth0 + eth1 Link encap:Ethernet HWaddr 00:90:7D:F3:03:1A + inet6 addr: fec0:106:1000:0:290:7dff:fef3:31a/64 Scope:Site + inet6 addr: fec0:106:1100:0:290:7dff:fef3:31a/64 Scope:Site + inet6 addr: fec0:106:2700:0:290:7dff:fef3:31a/64 Scope:Site + inet6 addr: fec0:106:2700::4/64 Scope:Site + inet6 addr: fe80::290:7dff:fef3:31a/64 Scope:Link + UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 + RX packets:1073 errors:212 dropped:212 overruns:0 frame:204 + TX packets:371 errors:72 dropped:0 overruns:0 carrier:0 + collisions:0 txqueuelen:100 + RX bytes:120340 (117.5 Kb) TX bytes:56912 (55.5 Kb) + Interrupt:3 Base address:0x100 + + + + + The new autoconfigured address at 'visitnet2'. + + + + Note! You may have to restart mobile-ipv6 on MN + when coming to a new network! + + + # /etc/init.d/mobile-ip6 restart + Stopping Mobile IPv6: OK + Starting Mobile IPv6: OK + + + The MN will then perform a new binding update to HA. Notice + the new care-of address: + + # mipdiag -l + Mobile IPv6 Binding update list + Recipient CN: fec0:106:2700::2 + BINDING home address: fec0:106:2700::4 care-of address: fec0:106:1000:0:290:7dff:fef3:31a + expires: 973 sequence: 14 state: 1 + delay: 3 max delay 32 callback time: 773 + + + You can also see the binding cache on HA has + been updated: + + + # mipdiag -c + Mobile IPv6 Binding cache + Home Address Care-of Address Lifetime Type + fec0:106:2700::4 fec0:106:1000:0:290:7dff:fef3:31a 943 2 + + @@ -1047,7 +1309,25 @@ browse the mail archive. Returning home - To be completed. + To make the MN return home, you can just issue the + command: + + + # iwconfig eth0 essid homenet + + + The MN will know it is back home, since HA is sending out + radvd messages with the HA-bit set (AdvHomeAgentFlag), see + + You can see the MN is back home, since the + binding cache information at HA is flushed (empty): + + + Mobile IPv6 Binding cache + Home Address Care-of Address Lifetime Type + + @@ -1061,7 +1341,8 @@ browse the mail archive. - + GnomeMeeting @@ -1092,6 +1373,31 @@ browse the mail archive. module. + + Q: Is there any support for kernel 2.6.x? + + A: Here is the answer + from Henrik Petander on the MIPL mailinglist: + + Here is a short overview of the status of MIPL for + 2.6 kernel series: + + We have finished the kernel infrastructure for + Mobile IPv6 in cooperation with the USAGI project. The + infrastructure does route optimization, tunneling and policy + routing. + + We are now working on the userspace daemon which + handles the MIPv6 signaling and controls the operation of the + kernel part. The userspace part is also progressing + nicely. However, the protocol logic is still missing, so there + isn't really anything for users to test yet. We should have a + well working and tested prototype ready and by the end of + March. + + + Q: Does MIPL support IPSec? @@ -1132,6 +1438,21 @@ browse the mail archive. network. MIPv6 from MIPL can't do this automatically. + + Q: If MN has travelled through several visited + LAN, and then returning home; the interface still has all the + autogenerated IPv6 addresses from all the visited networks! Is + there any way to flush/delete these + addresses? + + A: No, I do not know of any automatic way these adresses + can be removed, but you can delete them manually: + + + # ifconfig eth0 inet6 del <ipv6-address> + + + Q: Host B has two interfaces with two different subnets assigned. When I ping B from host A, it does @@ -1157,12 +1478,16 @@ browse the mail archive. Q: How do I set a default gateway in IPv6? - A: You do that using the traditional route or the newer - IP command: + A: You do that using the traditional route: + + + # route -A inet6 add default gw <ipv6-host> + + + or the newer ip command: - # ip route ::/0 via <ipv6-host> - # route -A inet6 add default gw <ipv6-host> + # ip route ::/0 via <ipv6-host> @@ -1274,7 +1599,7 @@ browse the mail archive. Copyright and License - Copyright © 2003 by Lars Strand. This material may + Copyright © 2003,2004 by Lars Strand. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at An up-to-date version of this document can be found at: - HTML: - http://www.gnist.org/~lars/work/insc/mipv6/ + HTML: + http://www.tldp.org/HOWTO/Mobile-IPv6-HOWTO/ @@ -1330,7 +1655,11 @@ browse the mail archive. Suggestions, corrections, additions wanted. Contributors wanted and acknowledged. Flames not wanted. - I can always be reached at lars at unik no + I can always be reached at lars at unik + no + + Homepage: + http://www.gnist.org/~lars diff --git a/LDP/howto/docbook/Mobile-IPv6-HOWTO/gnomemeeting1.png b/LDP/howto/docbook/Mobile-IPv6-HOWTO/gnomemeeting1.png index baf09367..cb0cfe38 100644 Binary files a/LDP/howto/docbook/Mobile-IPv6-HOWTO/gnomemeeting1.png and b/LDP/howto/docbook/Mobile-IPv6-HOWTO/gnomemeeting1.png differ diff --git a/LDP/howto/docbook/Mobile-IPv6-HOWTO/mipv6-testbed.png b/LDP/howto/docbook/Mobile-IPv6-HOWTO/mipv6-testbed.png index bb09b8e7..60d8a938 100644 Binary files a/LDP/howto/docbook/Mobile-IPv6-HOWTO/mipv6-testbed.png and b/LDP/howto/docbook/Mobile-IPv6-HOWTO/mipv6-testbed.png differ