|
Raspberry Pi & sixxs
![[ca]](/s/countries/ca.gif) Shadow Hawkins on Friday, 06 February 2015 17:26:14
I am using my Raspberry Pi (RPi) as my IPv6 gateway, connecting to Sixxs.net and creating my IPv6 subnet. In general this all works, though every time the RPi restarts up radvd fails, since it complain that 'IPv6 forwarding is not enabled'. In /etc/sysctl.conf I have enabled forwarding, but the value appears to be ignored. Currently I need to enable it via the command line.
Relevant link in /etc/sysctl.conf;
net.ipv6.conf.default.forwarding=1
net.ipv6.conf.all.forwarding=1
Command I type to get things enabled:
sudo sysctl net.ipv6.conf.all.forwarding=1
I am using Raspbian. Is there another file I should be modifying or something else to be checking?
Raspberry Pi & sixxs
Relevant link in /etc/sysctl.conf;
Link or file?
I tend to put my configs in:
/etc/sysctl.d
By just creating a 644 permed file named custom.conf which contains the relevant lines.
Setting both default + all should do the trick.
I am using Raspbian.
Which is a Debian derivative.
There are two other approaches you can try:
- putting the 'sudo sysctl ...' lines in /etc/rc.local
- putting the sysctl lines in /etc/network/interfaces in the post-up
iface eth0 inet6 static
address 2001:db8:20b0::2
netmask 64
gateway 2001:db8:20b0::1
post-up sysctl -w net.ipv6.conf.all.forwarding=1
post-up sysctl -w net.ipv6.conf.eth0.forwarding=1
That should then also have effect every time the interface comes up again.
(your 'static' might vary of course, the 'post-up' is what matters)
Raspberry Pi & sixxs
![[nz]](/s/countries/nz.gif) Shadow Hawkins on Wednesday, 17 June 2015 09:51:07
Andre-John Mas wrote:
I am using my Raspberry Pi (RPi) as my IPv6 gateway, connecting to Sixxs.net and creating my IPv6 subnet. In general this all works, though every time the RPi restarts up radvd fails, since it complain that 'IPv6 forwarding is not enabled'. In /etc/sysctl.conf I have enabled forwarding, but the value appears to be ignored. Currently I need to enable it via the command line.
Relevant link in /etc/sysctl.conf;
net.ipv6.conf.default.forwarding=1
net.ipv6.conf.all.forwarding=1
Command I type to get things enabled:
sudo sysctl net.ipv6.conf.all.forwarding=1
I am using Raspbian. Is there another file I should be modifying or something else to be checking?
Raspberry Pi & sixxs
Shadow Hawkins on Wednesday, 17 June 2015 09:53:06
Oooops,
Sorry
Pushed the wrong button.
Will have another go.
Raspberry Pi & sixxs
Shadow Hawkins on Wednesday, 17 June 2015 10:14:45
This time...
I have a Raspberry Pi 2 running the Raspbian OS.
It is NOT my SIXXS gateway and is just one of a number of PCs on my local LAN.
My SIXXS Gateway is on a Linux Desktop PC and has been running for over a year now.
Now all other LAN pcs have ipv6 running smoothly with no problems. (Including the Windows 7 PC) So radvd is performing as it should be.
I can run up the Ubuntu OS for the Raspberry Pi 2 and this also performs nicely with ipv6 on the LAN.
However the Raspbian OS on the Raspberry Pi 2 has a "Lease expiry" problem that I cannot trace down.
1. On startup all is ok and the lease runs for some 1800 seconds and I can use ipv6 for this period
2. After the Lease expires I can no longer use ipv6 on the Raspberry Pi2 ??
Ipv4 is not affected.
3. Within the first 1800 seconds I get:
"ip -6 route show
2001:4428:200:8059::/64 dev wlan0 proto kernel metric 256 expires 86074sec
fe80::/64 dev wlan0 proto kernel metric 256
fe80::/64 dev eth0 proto kernel metric 256
default via fe80::227:eff:fe01:9f81 dev wlan0 proto ra metric 1024 expires 1474sec hoplimit 64"
and:-
"ip -6 nei show
fe80::227:eff:fe01:9f81 dev wlan0 lladdr 00:27:0e:01:9f:81 router REACHABLE"
4. After the lease expires I get:
"ip -6 route show
2001:4428:200:8059::/64 dev wlan0 proto kernel metric 256 expires 85204sec
fe80::/64 dev wlan0 proto kernel metric 256
fe80::/64 dev eth0 proto kernel metric 256 "
and:-
"ip -6 nei show
fe80::227:eff:fe01:9f81 dev wlan0 lladdr 00:27:0e:01:9f:81 router STALE"
5. I notice other Linux PCs on the LAN "refresh" their leases and so never expire ??
So I am stuck as to just why this Raspbian OS wants to do this??
I am using a WLAN as you can see above. I have not tried the eth0 path, as I suspect it would behave the same.
I guess it will be a config problem somewhere.
Any ideas please.
Thankyou
Raspberry Pi & sixxs
Sounds that multicast is giving you problems.
Wireless behaves differently there, thus wired might actually solve the problem.
Try putting the interface in promisc mode and/or wireshark the interface to see what is happening with it and if you see the regular RA from the server coming by.
|
![[ch]](/s/countries/ch.gif)
on Friday, 06 February 2015 18:16:25
Posting is only allowed when you are