|
I need more detailed instructions on setting this up.
![[us]](/s/countries/us.gif) Shadow Hawkins on Monday, 04 May 2015 16:21:55
If there are more detailed instructions for newbies, please direct me. So far, I don't know how do search these forums and RSSOwl only seems to load the last 30 messages.
I am running linux mint and have installed the aiccu software as instructed. I am going through the newer Verizon G1100 router. Verizon appears to block incoming ICMP.
Output from aiccu commands:
gblinux ~ $ sudo aiccu tunnels
T165741 xxxx::2 ayiya usqas01
gbrooks@gblinux ~ $ sudo aiccu brokers
SixXS|tic://tic.sixxs.net|http://www.sixxs.net|eu|
gbrooks@gblinux ~ $ sudo aiccu test
Tunnel Information for Txxxxxxx:
POP Id : usqas01
IPv6 Local : xxxx::2/64
IPv6 Remote : xxxx::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
It appears that the tunnel is up. Partial output from ifconfig:
eth0 Link encap:Ethernet HWaddr b4:b5:2f:b9:d9:97
inet addr:192.168.1.130 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::b6b5:2fff:feb9:d997/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2277293 errors:0 dropped:72 overruns:0 frame:0
TX packets:1323097 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:834194571 (834.1 MB) TX bytes:305152894 (305.1 MB)
The sixxs interface doesn't appear although I have it configured in /etc/modules as:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
#
auto sixxs
iface sixxs inet6 v4tunnel
address xxxx::2
netmask 64
endpoint 66.117.47.228
ttl 64
mtu 1280
gateway xxxx::1
Also, where do I assign the IP address of the subnet that I have been assigned.
I need more detailed instructions on setting this up.
So far, I don't know how do search these forums
Google? use: site:sixxs.net <yoursearchterms>
Tunnel Type : ayiya
That is the important bit, you selected an AYIYA tunnel.
It appears that the tunnel is up.
If there is no interface then you stopped AICCU. Stopping AICCU stops the tunnel, which removes the interface.
I have it configured in /etc/modules as:
There is no kernel module for AYIYA. (AICCU uses tun/tap)
# interfaces(5) file used by ifup(8) and ifdown(8)
There is no way to configure AYIYA tunnels using interfaces(5).
You likely stopped AICCU, and then there is no tunnel.
Check your logs (/var/log/syslog is a good start).
I need more detailed instructions on setting this up.
Shadow Hawkins on Tuesday, 05 May 2015 14:12:13
I really appreciate you taking the time to answer my question. I followed the instructions and links as I best understood.
Google? use: site:sixxs.net <yoursearchterms>
I will do some google searches for help.
That is the important bit, you selected an AYIYA tunnel.
Did not realize that I had a choice.
There is no kernel module for AYIYA. (AICCU uses tun/tap)
I followed one of the links (https://www.sixxs.net/faq/connectivity/?faq=ossetup&os=linuxdebian) which instructed me to use /etc/network/interfaces. I will look to find out how to set up tun/tap for this.
I am not home to verify right now, but I believe that I use tun/tap to access an external VPN on ipv4. Would I need to delete that VPN software to use tun/tap for this? Or would the number increment as maybe tun1?
As I implied before. The instructions presented assume that the user has an intimate knowledge of linux. I am in now way a newbie to IT, however, I am am new to linux. I wish the instructions were a bit more straightforward.
I need more detailed instructions on setting this up.
That is the important bit, you selected an AYIYA tunnel. Did not realize that I had a choice.
What would the world be without choice?
See: FAQ: IPv6 Transition Mechanism / Tunneling Comparison
There is no kernel module for AYIYA. (AICCU uses tun/tap) I followed one of the links (https://www.sixxs.net/faq/connectivity/?faq=ossetup&os=linuxdebian) which instructed me to use /etc/network/interfaces. I will look to find out how to set up tun/tap for this.
At the top there is a little warning icon, note the text behind it.
I am not home to verify right now, but I believe that I use tun/tap to access an external VPN on ipv4. Would I need to delete that VPN software to use tun/tap for this? Or would the number increment as maybe tun1?
AICCU can use a separate tun/tap device. The name of which is configured using the "ipv6_interface" which defaults to 'aiccu' hence, should not cause a clash.
Do note that routing tunnels over tunnels is likely not very nice for performance, thus do avoid that.
As I implied before. The instructions presented assume that the user has an intimate knowledge of linux. I am in now way a newbie to IT, however, I am am new to linux. I wish the instructions were a bit more straightforward.
You need close to zero knowledge for this as on Debian one just uses:
apt-get install aiccu
or click the right buttons in your favourite package manager (eg Synaptic) if one is GUI-inclined.
and then follow the debconf details asking for the questions. Debian is actually the easiest platform to use AICCU on because of Debconf.
Indeed, for proto-41 tunnels one can also do it all manually, that is the FAQ item you looked at. Hence you have a myriad of choices.
I need more detailed instructions on setting this up.
Shadow Hawkins on Tuesday, 05 May 2015 16:23:27
Jeroen Massar wrote:
> So far, I don't know how do search these forums
Google? use: site:sixxs.net <yoursearchterms>
Tunnel Type : ayiya
That is the important bit, you selected an AYIYA tunnel.
It appears that the tunnel is up.
If there is no interface then you stopped AICCU. Stopping AICCU stops the tunnel, which removes the interface.
I have it configured in /etc/modules as:
There is no kernel module for AYIYA. (AICCU uses tun/tap)
# interfaces(5) file used by ifup(8) and ifdown(8)
There is no way to configure AYIYA tunnels using interfaces(5).
You likely stopped AICCU, and then there is no tunnel.
Check your logs (/var/log/syslog is a good start).
I need more detailed instructions on setting this up.
Shadow Hawkins on Tuesday, 05 May 2015 16:32:58
This is the latest. It appears that the tunnel is up. I can finally ping the other endpoint. The only thing that I did was to delete the entries from the interfaces file and then rebooted. My interface is still sixxs.
My next step is to figure out where to assign addresses of the subnet that I have been assigned.
I need more detailed instructions on setting this up.
My next step is to figure out where to assign addresses of the subnet that I have been assigned.
That, you do in interfaces(5). The FAQ has a subject on it.
I need more detailed instructions on setting this up
Shadow Hawkins on Tuesday, 12 May 2015 16:23:16
Jeroen Massar wrote:
> My next step is to figure out where to assign addresses of the subnet that I have been assigned.
That, you do in interfaces(5). The FAQ has a subject on it.
My IPv6: 2001:4830:1600:53f::2/64
My subnet: 2001:4830:1600:853f::/64
I believe that I have set up my interfaces correctly. Here is the output from ifconfig -A
gbrooks@gblinux /usr/share/doc/radvd/examples $ ifconfig -a
eth0 Link encap:Ethernet HWaddr b4:b5:2f:b9:d9:97
inet addr:192.168.1.130 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: 2001:4830:1600:853f::1/64 Scope:Global
inet6 addr: fe80::b6b5:2fff:feb9:d997/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1078336 errors:0 dropped:40 overruns:0 frame:0
TX packets:721550 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:359475403 (359.4 MB) TX bytes:107864161 (107.8 MB)
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:65536 Metric:1
RX packets:596194 errors:0 dropped:0 overruns:0 frame:0
TX packets:596194 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:113185574 (113.1 MB) TX bytes:113185574 (113.1 MB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 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)
sixxs Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::4830:1600:53f:2/64 Scope:Link
inet6 addr: 2001:4830:1600:53f::2/64 Scope:Global
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1280 Metric:1
RX packets:1435 errors:0 dropped:0 overruns:0 frame:0
TX packets:1433 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:1476615 (1.4 MB) TX bytes:1470745 (1.4 MB)
wlan0 Link encap:Ethernet HWaddr 20:16:d8:04:8c:6f
inet addr:192.168.1.129 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: 2001:4830:1600:853f::129/64 Scope:Global
inet6 addr: fe80::2216:d8ff:fe04:8c6f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:322874 errors:0 dropped:1 overruns:0 frame:0
TX packets:4071 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:58132519 (58.1 MB) TX bytes:1035277 (1.0 MB)
I can ping the other side of my tunnel
gbrooks@gblinux ~ $ ping6 2001:4830:1600:53f::1
PING 2001:4830:1600:53f::1(2001:4830:1600:53f::1) 56 data bytes
64 bytes from 2001:4830:1600:53f::1: icmp_seq=1 ttl=64 time=11.0 ms
64 bytes from 2001:4830:1600:53f::1: icmp_seq=2 ttl=64 time=9.90 ms
I can't get any further than that. If I try to ping ipv6.cnn.com, I get this:
gbrooks@gblinux ~ $ ping6 2620:100:e000::8001
PING 2620:100:e000::8001(2620:100:e000::8001) 56 data bytes
From 2001:4830:1600:853f::1 icmp_seq=1 Destination unreachable: Address unreachable
From 2001:4830:1600:853f::1 icmp_seq=2 Destination unreachable: Address unreachable
In addtion, I can't get radvd to start
gblinux ~ # /etc/init.d/radvd start
Starting radvd:
* IPv6 forwarding seems to be disabled.
* See /usr/share/doc/radvd/README.Debian
* radvd will *not* be started.
This is my radvd.conf file:
gbrooks@gblinux /etc $ cat radvd.conf
interface eth0
{
AdvSendAdvert on;
prefix 2001:4830:1600:53f::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
};
The documentation is not clear. Not sure what the value of prefix should be. I have tried both "prefix 2001:4830:1600:53f::/64" and prefix "2001:4830:1600:853f::/64
And my /etc/sysctl.conf file:
gbrooks@gblinux /etc $ cat sysctl.conf
net.ipv4.ip_forward=1
net.ipv6.conf.default.forwarding=1
Any suggestions?
I need more detailed instructions on setting this up
eth0 Link encap:Ethernet HWaddr b4:b5:2f:b9:d9:97 inet addr:192.168.1.130 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: 2001:4830:1600:853f::1/64 Scope:Global ...
wlan0 Link encap:Ethernet HWaddr 20:16:d8:04:8c:6f inet addr:192.168.1.129 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: 2001:4830:1600:853f::129/64 Scope:Global inet6 addr: fe80::2216:d8ff:fe04:8c6f/64 Scope:Link
Unless those wifi and ethernet interfaces are really bridged (by some device), you cannot have the same IPv4 (192.168.1.0/24) or IPv6 (2001:4830:1600:853f::/64) prefixes on the same interfaces.
From 2001:4830:1600:853f::1 icmp_seq=1 Destination unreachable: Address unreachable
That is your host telling not to know what to do with the packet.
Check routing tables and forwarding settings for all interfaces.
Starting radvd: * IPv6 forwarding seems to be disabled.
Pretty clear what is wrong here. See below.
The documentation is not clear. Not sure what the value of prefix should be. I have tried both "prefix 2001:4830:1600:53f::/64" and prefix "2001:4830:1600:853f::/64
FAQ: Using Subnets has a "SixXS Prefixes" section which should explain it.
net.ipv6.conf.default.forwarding=1
That only causes new interfaces to receive that setting, you also need to use the 'all' variant (and depending on kernel version, even set them individually...)
Best to store these in sysctl.d:
/etc/sysctl.d/custom.conf
# Enable forwarding
net.ipv4.conf.default.forwarding=1
net.ipv4.conf.all.forwarding=1
net.ipv6.conf.default.forwarding=1
net.ipv6.conf.all.forwarding=1
Also, instead of using "ifconfig -a" use:
ip -4 addr show
ip -6 addr show
and:
ip -4 ro show
ip -6 ro show
I need more detailed instructions on setting this up
Shadow Hawkins on Tuesday, 12 May 2015 18:38:55
This is the ip routing list.
gbrooks@gblinux /etc $ ip -6 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
inet6 2001:4830:1600:853f::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::b6b5:2fff:feb9:d997/64 scope link
valid_lft forever preferred_lft forever
5: sixxs: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qlen 500
inet6 2001:4830:1600:53f::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::4830:1600:53f:2/64 scope link
valid_lft forever preferred_lft forever
gbrooks@gblinux /etc $ ip -6 ro show
2001:4830:1600:53f::2 dev eth0 proto static metric 1024
2001:4830:1600:53f::/64 dev sixxs proto kernel metric 256
2001:4830:1600:853f::/64 dev eth0 proto kernel metric 256
fe80::/64 dev eth0 proto kernel metric 256
fe80::/64 dev sixxs proto kernel metric 256
default via 2001:4830:1600:53f::2 dev eth0 proto static metric 1
default via 2001:4830:1600:53f::1 dev sixxs metric 1024
To me it is showing that the default route is via eth0 to my side of the tunnel with the metric of 1 and via sixxs to the other side of the tunnel with metric 1024. Should default route with metric of 1 be deleted and changed the metric of the route to sixxs to 1?
I need more detailed instructions on setting this up
2001:4830:1600:53f::2 dev eth0 proto static metric 1024 ... default via 2001:4830:1600:53f::2 dev eth0 proto static metric 1
Both of those should not be there.
First as that address should only exist on the tunnel, second as that would be a loop back to your own host. Hence remove them both, things will work much better then.
I need more detailed instructions on setting this up
Shadow Hawkins on Tuesday, 12 May 2015 18:58:02
Jeroen Massar wrote:
> 2001:4830:1600:53f::2 dev eth0 proto static metric 1024
Thank you so much for your patience. This seems to have done the trick.
... default via 2001:4830:1600:53f::2 dev eth0 proto static metric 1
Both of those should not be there.
First as that address should only exist on the tunnel, second as that would be a loop back to your own host. Hence remove them both, things will work much better then.
I need more detailed instructions on setting this up
Thank you so much for your patience. This seems to have done the trick.
Learning happens with trial and error :)
Enjoy the connectivity!
|
![[ch]](/s/countries/ch.gif)
on Monday, 04 May 2015 20:16:35
Posting is only allowed when you are