Forum - Activating tunnel on Linux without AICCU :: SixXS

Activating tunnel on Linux without AICCU

Shadow Hawkins on Tuesday, 26 May 2015 16:18:00

Considered that I have problems in using AICCU on linux (opensuse), I was wondering if it's possible to use the Sixxs tunnel trough terminal commands, like below: modprobe ipv6 ip tunnel add SixXS mode sit remote <IPv4 Sixxs server> local <Client IPv4> ttl 200 ip link set SixXS up ip addr add <Client IPv6> dev SixXS ip route add ::/0 dev SixXS ip -f inet6 addr If yes, what's the value of "ttl" (in first command) that I need to use?

Activating tunnel on Linux without AICCU

Jeroen Massar SixXS Staff

on Tuesday, 26 May 2015 16:21:52

Considered that I have problems in using AICCU on linux (opensuse),

What kind of problems? Do you have any details?

I was wondering if it's possible to use the Sixxs tunnel trough terminal commands

Did you check the FAQ? It has all the examples needed. Note that manual configuration only works for static proto-41 tunnels. Heartbeat and AYIYA tunnels require AICCU.

modprobe ipv6

If you still have a kernel that does not have the IPv6 module per default you should really upgrade.

If yes, what's the value of "ttl" (in first command) that I need to use?

ttl is an optional value, though as it is taken over from the lower interface, which is typically 255, it is better to set it at the more reasonable 64.

Activating tunnel on Linux without AICCU

Shadow Hawkins on Tuesday, 26 May 2015 21:06:21

thanks for reply. ok so I need to use AICCU. I don't know what is wrong. I've edited aiccu.conf with my account data. I used "autotest" and "start" commands from linux terminal. So when I check for my IPv6 connectivity the result is negative. This is my aiccu.conf: http://paste.opensuse.org/56941680 And this is my autotest log: http://paste.opensuse.org/10421172

Activating tunnel on Linux without AICCU

Jeroen Massar SixXS Staff

on Tuesday, 26 May 2015 21:19:09

This is my aiccu.conf: http://paste.opensuse.org/56941680

Try setting 'verbose' to true. That might give some extra details.

And this is my autotest log: http://paste.opensuse.org/10421172

Note that AICCU's "test" merely confirms that stuff works or not, it does not pinpoint problems. It looks a lot though that nothing is configured. Checking output of commands like 'ip link show', 'ip -6 addr show' 'ip -6 ro show' etc can be very useful as a start. Could be anything though, without verbose log and/or checking syslog, little one can say about it.

Activating tunnel on Linux without AICCU

Shadow Hawkins on Tuesday, 26 May 2015 22:31:18

thank you for reply. I set verbose to true and now when I use "start" command I get this: http://paste.opensuse.org/21824633 But the tunnel doesn't work same. These are the outputs requested: ip link show: http://paste.opensuse.org/60945514 ip -6 addr show: http://paste.opensuse.org/69912446 ip -6 ro show: http://paste.opensuse.org/4590996

Activating tunnel on Linux without AICCU

Jeroen Massar SixXS Staff

on Wednesday, 27 May 2015 07:07:06

thank you for reply. I set verbose to true and now when I use "start" command I get this:

http://paste.opensuse.org/21824633

One can do inline code blocks here ( [ code] ..... [/code ], don't have to use the paste feature.

But the tunnel doesn't work same.

Did you check syslog and other logs for more output?

ip -6 addr show: http://paste.opensuse.org/69912446

ip -6 ro show: http://paste.opensuse.org/4590996

default via fe80::e0d8:abff:fee9:9679 dev wlp2s0 proto ra metric 1024 expires 25sec

You are getting a default route from a different source already. AICCU won't override that. Likely that is part of your problem.

Activating tunnel on Linux without AICCU

Shadow Hawkins on Wednesday, 27 May 2015 13:21:06

Jeroen Massar wrote:

Did you check syslog and other logs for more output?

No, I don't. How can I do that?

> default via fe80::e0d8:abff:fee9:9679 dev wlp2s0 proto ra metric 1024 expires 25sec You are getting a default route from a different source already. AICCU won't override that. Likely that is part of your problem.

But I'm not using other tunnel service. So why that? Can I fix it?

Activating tunnel on Linux without AICCU

Jeroen Massar SixXS Staff

on Wednesday, 27 May 2015 13:44:46

No, I don't. How can I do that?

Check the files in /var/log/ But if you did not know that, then I sincerely hope you visit somebody who can explain computer security to you and who helps you secure your host properly. IPv6 is per default globally reachable, hence unless you properly secure your host you are open to a lot of attacks.

default via fe80::e0d8:abff:fee9:9679 dev wlp2s0 proto ra metric 1024 expires 25sec

You are getting a default route from a different source already. AICCU won't override that.

Likely that is part of your problem.

But I'm not using other tunnel service. So why that? Can I fix it?

That default route comes from another computer on your network, which thus is not a tunnel but "native" (depending on where it actually leads). The address ( fe80::e0d8:abff:fee9:9679) contains the mac address:

$ ipv6calc -i  fe80::e0d8:abff:fee9:9679
No input type specified, try autodetection...found type: ipv6addr
No output type specified, try autodetection...found type: ipv6addr
Address type: unicast, link-local, iid, iid-local, iid-eui48
Registry for address: reserved(RFC4291#2.5.6)
Interface identifier: e0d8:abff:fee9:9679
EUI-48/MAC address: e2:d8:ab:e9:96:79
MAC is a local one
MAC is an unicast one

Seems to be a locally defined address, thus little one can state about the actual machine. Maybe it is a Virtual Machine of sorts?

ip nei show

should contain the MAC and any IPv4 address if it has one to help you narrow down what computer might be announcing that to you. Tcpdump can also become a good friend to see which host it is and what RA it is actually sending.

Activating tunnel on Linux without AICCU

Shadow Hawkins on Wednesday, 27 May 2015 17:08:53

I really don't know what is that. The MAC address resulting is not one of my wifi devices (connected to my router wifi). I used again "ip -6 ro show" command:

demonoid@linux-xtbn:~> ip -6 ro show
fe80::/64 dev wlp2s0  proto kernel  metric 256 
default via fe80::24bb:9ff:fef3:df72 dev wlp2s0  proto ra  metric 1024  expires 28sec

And:

demonoid@linux-xtbn:~> ipv6calc -i fe80::24bb:9ff:fef3:df72
If 'ipv6calc' is not a typo you can use command-not-found to lookup the package that contains it, like this:
    cnf ipv6calc
demonoid@linux-xtbn:~> ipv6calc -i fe80::24bb:9ff:fef3:df72
No input type specified, try autodetection...found type: ipv6addr
No output type specified, try autodetection...found type: ipv6addr
Address type: unicast, link-local
Registry for address: reserved
Interface identifier: 24bb:09ff:fef3:df72
EUI-48/MAC address: 26:bb:09:f3:df:72
MAC is a local one
MAC is an unicast one

So I used "ip nei show":

fe80::24bb:9ff:fef3:df72 dev wlp2s0 lladdr e8:94:f6:9a:7d:d6 router STALE
192.168.1.1 dev wlp2s0 lladdr e8:94:f6:9a:7d:d6 REACHABLE

IP and MAC address are now different, but I don't know what is it! It's not in my network. At least according to my knowledge... I just know that "wlp2s0" is my wifi device (on my laptop).

Activating tunnel on Linux without AICCU

Jeroen Massar SixXS Staff

on Wednesday, 27 May 2015 17:24:15

fe80::24bb:9ff:fef3:df72 dev wlp2s0 lladdr e8:94:f6:9a:7d:d6 router STALE

192.168.1.1 dev wlp2s0 lladdr e8:94:f6:9a:7d:d6 REACHABLE

The MAC address is "e8:94:f6:9a:7d:d6" in both cases. As 192.168.1.1 is likely your default gateway, that thing is IPv6 enabled and telllng devices in your network about IPv6. What kind of device is 192.168.1.1?

Activating tunnel on Linux without AICCU

Shadow Hawkins on Wednesday, 27 May 2015 18:19:38

Jeroen Massar wrote:

> fe80::24bb:9ff:fef3:df72 dev wlp2s0 lladdr e8:94:f6:9a:7d:d6 router STALE

192.168.1.1 dev wlp2s0 lladdr e8:94:f6:9a:7d:d6 REACHABLE

Yes, 192.168.1.1 is the gateway of my Wifi Router (Tp-Link: TD-W8970). This router naturally supports IPv6.

Activating tunnel on Linux without AICCU

Shadow Hawkins on Thursday, 28 May 2015 12:01:24

How can I fix it?

Activating tunnel on Linux without AICCU

Jeroen Massar SixXS Staff

on Thursday, 28 May 2015 12:45:38

How can I fix it?

Option 1) Use the IPv6 provided by that device already in your network, likely it is native IPv6. Option 2) Disable IPv6 in the device that is telling there is IPv6.

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