|
Hint: local <ipv4> in ifup/-down scripts
![[de]](/s/countries/de.gif) Shadow Hawkins on Wednesday, 28 April 2004 15:26:23
It seems so, that the documentation of the ifup/-down scripts act not as written in the manual. I only use Debian, so it might be only a issue of debian stable.
Problem:
If you want to run your IPv6-in-IPv4-tunnel on a machine with more than one ip, you have to specify the ipv4-address of your end of the tunnel. Normally you do this in the cmdline with:
# ip tunnel add sixxs mode sit local <your-ipv4-address> remote <endpoint-ipv4>
To make this permanent after reboot, there are the ifup/-down-scripts. When you make it the way written in the manual, the line "local <ipv4>" gets ignored.
Solution:
iface sixxs inet6 v4tunnel
address <your-ipv6-address>
netmask <your-ipv6-netmask>
[bold]endpoint <pop-ipv4> local <your-tunnel-ending-ipv4>[/bold]
gateway <pop-ipv6>
ttl 64
up ip link set mtu 1280 dev sixxs
Hope this helps.
Greets,
Kai Baumgart
Hint: local <ipv4> in ifup/-down scripts
There is a very easy solution to this: Upgrade to the latest Debian unstable tree as that supports IPv6 much better than the Debian 'stable' tree. FYI... unstable is *very* stable, one only has to pay attention for broken packages.
I would rather call unstable 'steaminghot' though ;)
Also you might want to change your config to:
(thus the local on a seperate line)
iface sixxs inet6 v4tunnel
address <your-ipv6-address>
netmask <your-ipv6-netmask>
endpoint <pop-ipv4>
local <your-tunnel-ending-ipv4>
gateway <pop-ipv6>
ttl 64
up ip link set mtu 1280 dev sixxs
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 28 April 2004 15:32:02
Posting is only allowed when you are