SixXS::Sunset 2017-06-06

new tunnel won't work
[de] Shadow Hawkins on Thursday, 27 November 2003 20:20:40
I don't know if this is a setup issue. switching from PsiNET to Easynet didn't work. After editing /etc/network/interfaces and ifconfig sixxs down && ifconfig sixxs up still it looks like this: sixxs Link encap:IPv6-in-IPv4 inet6 addr: fe80::d585:6c55/128 Scope:Link UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1 RX packets:12485067 errors:0 dropped:0 overruns:0 frame:0 TX packets:9520377 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:456529079 (435.3 MiB) TX bytes:3965988478 (3.6 GiB) (I don't know, where RX and TX are from)... Well as you can see there is only a generic inet6 address and not the configured one. I c&p'd the new adresses and looked them over several times. The tunnel is on state enabled since yesterday.
new tunnel won't work
[de] Shadow Hawkins on Thursday, 27 November 2003 21:02:31
A little update: I can't remove the ipv6 module (device busy) lsmod tells me Module Size Used by Not tainted ipv6 151616 -1 not looking very well.. anything to do about it?
new tunnel won't work
[ch] Jeroen Massar SixXS Staff on Friday, 28 November 2003 13:19:35
I suggest you do the reboot trick or at least try some manual configuration.
new tunnel won't work
[fi] Shadow Hawkins on Friday, 28 November 2003 18:03:10
If you use debian as it seems due file /etc/network/interfaces. You should use "ifdown sixxs" and "ifup sixxs" to get new configuration work. Ifconfig won't read /etc/network/interfaces file.
new tunnel won't work
[ch] Jeroen Massar SixXS Staff on Saturday, 29 November 2003 01:48:46
Hmmm... indeed, I thought he wrote the ifup/down command but he used ifconfig :) Reboot would have done the trick too })

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker