Skip to content
Laurent Deru edited this page Jun 24, 2015 · 7 revisions

Connecting to 6LBR depends on the mode of operation and the configuration parameters as well as the operting system of your host.

See the bottom of the page for accessing 6LBR and the WSN from the Native Host

Connecting to 6LBR in Router mode

In Router mode, the WSN subnet has a different prefix than the Ethernet subnet. By default the WSN subnet has prefix aaaa::/64 and Ethernet subnet has bbbb::/64.

Automatic connection

Unless deactivated, 6LBR will send periodially a Router Advertisement (RA) messages on the Ethernet subnet containing the configured prefix and the route to access the WSN subnet.

You have to activate the reception of this message on your host :

On Linux, if your network interface is eth0 :

sysctl -w net.ipv6.conf.eth0.accept_ra=1
sysctl -w net.ipv6.conf.eth0.accept_ra_rt_info_max_plen=64

These commands have to be run each time the interface is restarted; this can be automated depending on your Linux distribution by enabling IPv6 autoconfiguration in your Network Manager.

On Windows 7 and forwards, RA are accepted by default.

On MacOS-X :

sysctl -w net.inet6.ip6.accept_rtadv=1
route add -inet6 -prefixlen 64 aaaa:: bbbb::100

Note that route must be manually added.

Manual connection

If periodic RA is deactivated or not accepted by the host, the host address and route must be configured manually :

On Linux, if your network interface is eth0 :

sudo ip -6 addr add bbbb::101/64 dev eth0
route -A inet6 add aaaa::/64 gw bbbb::100

On Windows :

todo

On MacOS-X, if your network interface is en0 :

ifconfig en0 inet6 bbbb::101/64 add
route add -inet6 -prefixlen 64 aaaa:: bbbb::100

Connecting to 6LBR in SmartBridge mode

In SmartBridge mode, the WSN subnet has the same prefix as the Ethernet subnet. By default the prefix is acquired from the Ethernet subnet but it can be manually set.

Automatic connection

If 6LBR is set to autoconf, it will learn its address and prefix to be used from the RA sent by the Router advertisement daemon running on the subnet.

For RADVD, the smallest configuration needed if you are running RADVD on a dedicated host :

interface eth0
{
        AdvSendAdvert on;

        prefix aaaa::0/64
	{
                AdvOnLink on;
                AdvAutonomous on;
        };

        #This machine can not be used as default router
        AdvDefaultLifetime 0;
};

Your host must be configured as a Router otherwise RADVD will not start.

sysctl -w net.ipv6.conf.eth0.forwarding=1

Also /etc/radvd.conf must not be readable by others.

If you are running RADVD on the same host as 6LBR, you must use the following configuration :

TODO !

For RTADVD, the smallest configuration is :

en0:\
	:addrs#1:addr="aaaa::":prefixlen#64:

Manual connection

If you don’t want to have a running router advertisement daemon, you can manually configure the prefix in 6LBR in line with the used prefix on the Ethernet segment.

Local connection from Native Host

First of all, if you are using Raw Ethernet, you can not access 6LBR and the WSN from the Native Host.

All the above description applies in tap bridge mode, but you have to replace

eth0
with your bridge interface
br0
Clone this wiki locally