Making IPv6 device available on the internet

RE: Making IPv6 device available on the internet

akd — Thu, 07 Nov 2019 07:46:13 GMT

I have a similar setup. But instead of using eth0 i am using wlan0. So in all commands I replaced eth0 to wlan0.

But my ping6 from bt0 to wlan0 is failing.

Any suggestion what can be the issue and where can be the mistake?

Thanks in advance for your help.

Here are the details of the steps:

platform: Raspberry Pi 3 Model B+ and Raspbian Stretch

My Setup is exactly like this:

Bluetooth Node <-- BT --> Raspberry Pi <-- Wifi --> 4G Wireless Router --> Internet

RPI Wifi gets 2405:204:1290:3eb1:ab2c:9c70:7c27:xxxx/64 address from 4G Wireless Router.

My etc/radvd.conf

interface bt0
{
AdvSendAdvert on;
AdvSourceLLAddress on;
prefix 2002::/64
{
AdvOnLink off;
AdvAutonomous on;
AdvRouterAddr on;
}; # End of prefix definition
};

I added a static IPv6 address to bt0
#Ip address add 2002::1/64 dev bt0

My “ip -6 addr show” gives:
# ip -6 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
inet6 2405:204:1290:3eb1:ab2c:9c70:7c27:xxxx/64 scope global mngtmpaddr noprefixroute
valid_lft forever preferred_lft forever
inet6 fe80::9ed1:3e80:de2a:e601/64 scope link
valid_lft forever preferred_lft forever
4: bt0: <MULTICAST,UP,LOWER_UP> mtu 1280 state UNKNOWN qlen 1000
inet6 2002::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::b827:ebff:fe3d:4f70/64 scope link
valid_lft forever preferred_lft forever

Other commands I have run:
#echo 1 > /proc/sys/net/ipv6/conf/all/forwarding
#ip route add 2002::/64 dev bt0
#ip6tables -A FORWARD -i bt0 -o wlan0 -j ACCEPT
#ip6tables -A FORWARD -i wlan0 -o bt0 -j ACCEPT
#ip6tables -t nat -A POSTROUTING -o wlan0 -j MASQUERADE
#service radvd restart

#My “ip -6 route show” gives:
2002::/64 dev bt0 proto kernel metric 256 pref medium
2002::/64 dev bt0 metric 1024 pref medium
2405:204:1290:3eb1::/64 dev wlan0 proto kernel metric 303 mtu 1500 pref medium
fe80::/64 dev wlan0 proto kernel metric 256 pref medium
fe80::/64 dev bt0 proto kernel metric 256 pref medium
default via fe80::8bf:4ace:e70a:xxxx dev wlan0 metric 303 mtu 1500 pref medium

My ping6 from bt0 to wlan0 global address returns:
#ping6 -I bt0 2405:204:1290:3eb1:ab2c:9c70:7c27:xxxx
connect: Network is unreachable
My ping6 from bt0 to wlan0 Link Local address returns:
#ping6 -I bt0 fe80::9ed1:3e80:de2a:e601
PING fe80::9ed1:3e80:de2a:e601(fe80::9ed1:3e80:de2a:e601) from fe80::b827:ebff:fe3d:4f70%bt0 bt0: 56 data bytes
^C
--- fe80::9ed1:3e80:de2a:e601 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1071ms

RE: Making IPv6 device available on the internet

gsalazar — Thu, 22 Mar 2018 14:49:49 GMT

Hi,

I'm trying to follow these steps however when running:

ip addr add 2002:xAB:xCD::1/16 dev 6to4 (I followed the SDK documentation)

I keep getting the error: Error: ??? prefix is expected rather than "2002:192168:106145::1/16".

What should be the format of xAB and xBC? Could you provide an example?

Thanks in advance

RE: Making IPv6 device available on the internet

mueller — Tue, 11 Apr 2017 17:33:58 GMT

To safe others time, here is the answer if your provides does NOT support ipv6 on your local box (which seems to be the unstated assumption for all answers and the IOT SDK documentation).

First, run

http://test-ipv6.com/

To determine if you have full ipv6 support. If not, keep reading. If you're in a NAT'ed environment (192.X, 10.X etc.) give up. But if your bridge (pi3 in my case) has a DNS-resolvable IP, then follow the description above except for the ip6table commands and then:

Create a 6to4 connection from the pi3 (w/ eth0 IP A.B.C.D, make sure to use the corresponding hex values in the 3rd cmd below):

ip tunnel add 6to4 mode sit remote any local A.B.C.D

ip link set 6to4 up

ip addr add 2001:xAB:xCD::1/16 dev 6to4

ip -6 route add default via ::192.88.99.1 dev 6to4

(This assumes the commands above. If you followed the SDK documentation, which uses 2001:db8::1 for bt0, you'd have to use 2002:... in the ip addr cmd above instead. They need to be 2 different prefixes.)

Then create an ipv6 NAT:

/sbin/ip6tables -t nat -A POSTROUTING -o 6to4 -j MASQUERADE

/sbin/ip6tables -A FORWARD -i 6to4 -o bt0 -m state --state RELATED,ESTABLISHED -j ACCEPT

/sbin/ip6tables -A FORWARD -i bt0 -o 6to4 -j ACCEPT

and viola! I strongly suggest to add this to the SDK documentation to save others days of tinkering w/ broken kernels (6lowpan is briddle), misleading answers on posts etc.

On a related note, why even go ipv6 at all? Most IOT devices will be behind a NAT, using ipv4 would have been much easier (since ipv6 may never see full support by ISPs)? But that's more of a philosophical RFC question.

RE: Making IPv6 device available on the internet

MarcelS — Tue, 28 Jun 2016 11:58:13 GMT

Okay for everyone that is encountering the same problem: The solution is quite simple

As hirotaka mentioned, you have to setup a Route from the raspberry pi to your nRF-Device. Outgoing packets from the nRF are using the standard gateway to reach the internet - but packets from the internet to the nRF cannot reach your device.

To build up a route you just have to put up this command:

sudo route -A inet6 add 2002::/64 dev bt0

While 2002::/64 is the prefix from radvd and bt0 is the bluetooth interface.

RE: Making IPv6 device available on the internet

MarcelS — Mon, 27 Jun 2016 14:00:18 GMT

Hello guys,

I am also encounterin that problem. I was also not able to setup a bridge via brctl-command because I am also receiving Invalid argument-Error.

The nRF51 has received a IPv6 Address from the Raspberry Pi via radvd. The device can send DNS-Queries to the Internet and I was also able to receive DNS-Responses on the Raspberry Pi. For some reason the Pi refuses to forward the answers to the nRF. Its also interesting, that NAT doesn't work properly - I can see that IP-Frames are sent and also received with the IPv6 Address from the nRF, not the IPv6 Address from the Pi as intended.

Could you guys please help me with tracking down the error? Maybe some command I forgot, some switch I have to trigger? The project I am trying to get to work is the Cloud -> CoAP Example. I also tried it with the nRF52 but it still didn't work.

Init-Script:

#!/bin/sh
# Moutn debugfs file system
mount -t debugfs none /sys/kernel/debug

# Load 6LoWPAN module
sudo modprobe bluetooth_6lowpan
# Enable 6LoWPAN
sudo echo 1 > /sys/kernel/debug/bluetooth/6lowpan_enable
# Set IPv6 forwarding
sudo echo 1 > /proc/sys/net/ipv6/conf/all/forwarding

# Run Router-Advertisement Daemon (radvd)
sudo service radvd restart

# Look for available HCI devices
# hciconfig

# Reset HCI device
hciconfig hci0 reset

# Read BLE-Address from nRF51
# hcitool lescan

# Connect to the device
sudo echo "connect 00:XX:XX:XX:C1:A9 1" > /sys/kernel/debug/bluetooth/6lowpan_control

# Add the IP prefix to the Bluetooth Interface bt0
sudo ifconfig bt0 add 2002::1/64
# Restart radvd service
service radvd restart
#####################
# Firewalll rules
#####################
# Delete all former rules (flush)
ip6tables -F INPUT
ip6tables -F OUTPUT
ip6tables -F FORWARD
ip6tables -F
ip6tables -X

# Set the default policy to accept
ip6tables -P INPUT ACCEPT
ip6tables -P OUTPUT ACCEPT
ip6tables -P FORWARD ACCEPT

# Enabling IPv6 forwarding disables route-advertisement reception
# A static gateway will need to be assigned.
echo 1 > /proc/sys/net/ipv6/conf/all/forwarding

# Forward all traffic from Bluetooth-Interface to Ethernet-Interface
sudo ip6tables -A FORWARD -i bt0 -o eth0 -j ACCEPT
# Forward all traffic from Ethernet-interface to Bluetooth-Interface
sudo ip6tables -A FORWARD -i eth0 -o bt0 -m state --state RELATED,ESTABLISHED -j ACCEPT
# Use Network Address Translation (NAT) for all traffic to the internet
ip6tables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

etc/radvd.conf

interface bt0
{
    AdvSendAdvert on;
    prefix 2002::/64
    {
        AdvOnLink     off;
        AdvAutonomous on;
        AdvRouterAddr on;
    };
};

ifconfig

    pi@raspberrypi:~ $ ifconfig
bt0       Link encap:UNSPEC  HWaddr 00-XX-XX-XX-XX-XX-XX-XX-00-00-00-00-00-00-00-00
          inet6 addr: fe80::21a:7dff:xxxx:xxxx/64 Scope:Link
          UP POINTOPOINT RUNNING MULTICAST  MTU:1280  Metric:1
          RX packets:63 errors:0 dropped:0 overruns:0 frame:0
          TX packets:191 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:4725 (4.6 KiB)  TX bytes:10502 (10.2 KiB)

eth0      Link encap:Ethernet  HWaddr XX:XX:XX:XX:XX:XX
          inet addr:192.168.0.16  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fd00:bc14:1b9:6082:2f6:xxxx:xxxx:xxxx/64 Scope:Global
          inet6 addr: 2a02:8108:1a40:23f4:7330:xxxx:xxxx:xxxx/64 Scope:Global
          inet6 addr: fe80::2964:4ac:xxxx:xxxx/64 Scope:Link
          inet6 addr: 2a02:8108:xxxx:xxxx::2/128 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:38800 errors:0 dropped:2 overruns:0 frame:0
          TX packets:44508 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4279815 (4.0 MiB)  TX bytes:39169823 (37.3 MiB)

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:167005 errors:0 dropped:0 overruns:0 frame:0
          TX packets:167005 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:423921129 (404.2 MiB)  TX bytes:423921129 (404.2 MiB)

wlan0     Link encap:Ethernet  HWaddr XX:XX:XX:XX:XX:XX
          inet6 addr: xxxx::xxxx:xxxx:xxxx:xxxx/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:1553 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

RE: Making IPv6 device available on the internet

samchang — Sun, 15 May 2016 13:46:31 GMT

Hello Christoph S, and everyone. Does this(brctl addbr br0 ,brctl addif br0 eth0 bt0) means that the Nrf51-DK can be routable from other WAN networks ? Thanks

RE: Making IPv6 device available on the internet

hirotakaster — Thu, 19 Feb 2015 07:27:33 GMT

see "route" command on Linux.

RE: Making IPv6 device available on the internet

Trygve Laugstøl — Thu, 19 Feb 2015 07:03:02 GMT

What would the routing command look like?

RE: Making IPv6 device available on the internet

hirotakaster — Thu, 19 Feb 2015 05:55:28 GMT

Of course, you must add your IPv6 routing table to Linux hosts using route command(or others) on your own. Radvd don't add routing table.

RE: Making IPv6 device available on the internet

Trygve Laugstøl — Wed, 18 Feb 2015 18:34:30 GMT

Hm, how is the routing table entries supposed to be added? That is not something that radvd can will do, is it?

RE: Making IPv6 device available on the internet

hirotakaster — Wed, 18 Feb 2015 15:54:59 GMT

Can you check the IPv6 Global IP address(RA from your Linux host radvd) packet between the Linux and nrf51 using ping6? If you can check that Global IPv6 ping6 packet, next you have to check your Linux host IPv6 routing table and next check the IPv6 packet using tcpdump or Wireshark. Bay be you will find the point where the IPv6 packet is stopping.

RE: Making IPv6 device available on the internet

Trygve Laugstøl — Wed, 18 Feb 2015 14:33:32 GMT

That sound like what I've been doing. I'm running radvd on my desktop and the device is getting an IP as expected. But packets won't flow from the LAN (or the WAN) to the device so some sort of routing/switching/bridging is missing.

RE: Making IPv6 device available on the internet

hirotakaster — Wed, 18 Feb 2015 13:30:57 GMT

I think you don't have to use bridge device. If your DSL router can RA /62 prefix, you can try like this. I think you should use Linux Host as a IPv6/6lowpan edge router. DSL router(/60) <-> Linux Host(eth0:/62 RA from router, bt0:/64 prefix on randvd to bluetooth) <-> (nrf51)

RE: Making IPv6 device available on the internet

Trygve Laugstøl — Tue, 10 Feb 2015 20:50:12 GMT

If you have gotten this to work I wonder what your kernel version is and the version of your bridge-utils package is.

RE: Making IPv6 device available on the internet

Trygve Laugstøl — Tue, 10 Feb 2015 20:49:03 GMT

I should have said so in my question, but I have tried this already. When I try to add the bt0interface I always get Invalid argument. I haven't looked at the sources, but I assume that this is because the bt interface is classified as a POINTTOPOINT interface and not a BROADCAST interface as normal Ethernet interfaces are.

RE: Making IPv6 device available on the internet

Christoph S. — Sun, 08 Feb 2015 16:26:58 GMT

What you need is a bridge on the Linux host between the ethernet device and the bt0 device:

brctl addbr br0

Then add the ethernet device (eth0 below) and the bt0 to the new bridge br0:

brctl addif br0 eth0 bt0

For more details see wiki.debian.org/BridgeNetworkConnections