A message for Linux.com registered users: We are in the process of making changes to the Linux forums. Starting Monday, 8/13/18 at 6:00 PM PT, you will be unable to access the forums. They will re-launch as soon as possible on Wednesday, 8/15/18 with new features and improved functionality. Thank you for your patience and stay tuned for the new improved forums.

November 30, 2016

IPv6 routing across Debian interfaces

Forums: 

Hello,

I am a newbie when it comes to Linux so I am hoping the answer is simple here. I am testing VOIP traffic across a wireless mesh network using different routing protocols. For some reason one of the protocols will not route between interfaces on the edge devices. I tried static routing without the protocol and it suffers the same problem. I am assuming there is some security feature that the first two protocols disable that the third does not.

Topology

ClientA-----wired------AP01-------wireless-------AP02-----wired------ClientB

ClientA eth0 - 2002::2/64
AP01 eth0 - 2002::1/64
AP01 wlan0 - 2001::1/64
AP02 wlan0 - 2001::2/64
AP02 eth0 - 2003::1/64
ClientB eth0 - 2003::2/64

Client A default gateway is 2002::1/64
Client B default gateway is 2003::1/64
AP01 has a static route to the network 2003::/64 with next hop 2001::2/64
AP02 has a static route to the network 2002::/64 with next hop 2001::1/64
Note: This is when I configure it statically. The routing protocol add the routes when I configure it

ClientA can ping both interfaces of AP01 but no further
ClientB can ping both interfaces of AP02 but no further
AP01 can ping Client A and both interfaces of AP02
AP02 can ping Client B and both interfaces of AP01

ClientA and ClientB are IBM desktops running Debian Jessie
AP01 and AP02 are Raspberry Pi3 devices running Rasbian Wheezy

When the mesh is configured using BMX6 or OLSR I can ping end to end.
When the mesh is configured using Babel or using static routes I hit the problem.

All devices are configured as dual stack with IPv4 addresses on eth0 used for management traffic. The IPv4 network is a flat network 172.20.20.0/24 which I do not believe should be relevant but I have included it here for completeness.

I have confirmed that the correct interfaces are being used to reach each network.

Thank you in advance for reading my post and hopefully somebody can help.

Click Here!