Router - Linux: Difference between revisions

(4 intermediate revisions by one other user not shown)

Line 69:

==IPv6==

Assign your /64 to the inside interface of your router - eth1 in this example.

*Assign your /64 to the inside interface of your router - eth1 in this example.

ifconfig eth1 inet6 add 2001:8b0:blah/64

Enable ipv6 forwarding by adding to /etc/sysctl.conf:

*Enable ipv6 forwarding by adding to /etc/sysctl.conf:

net.ipv6.conf.default.forwarding=1

net.ipv6.conf.all.forwarding=1

If you don't want to reboot, also push these values into /proc/sys/etc.:

*If you don't want to reboot, also push these values into /proc/sys/etc.:

echo 1 > /proc/sys/net/ipv6/conf/all/forwarding

echo 1 > /proc/sys/net/ipv6/conf/default/forwarding

Line 92:

3.2.0-rc5

==PPPoE==

===PPPoE===

Linux is capable of supporting RFC 4638 for an MTU of 1500 (or greater) over PPPoE

*Linux is capable of supporting RFC 4638 for an MTU of 1500 (or greater) over PPPoE

⚫

**This is supported on BT FTTC

⚫

**Kernel 2.6.34 is required to fix bugs with certain network cards and non-linear SKBs (ea8420e9, 19937d04)

⚫

**pppd 2.4.6 is required for RFC 4638 support (this is in git but not yet released)

⚫

==PPP Not coming back after a blip==

⚫

This is supported on BT FTTC

⚫

This was reported in IRC on Feb 6th 2011. If you get people saying their line didn't come back or their linux box crashed (as in kernel oopsed) after a blip, turns out there's a bug in the kernel pppoe code for 2.6.36 which has been hitting me. some kind of double free in the disconnect code causes a kernel panic. there's a patch here: http://kerneltrap.org/mailarchive/linux-kernel/2010/12/3/4654538 which seems to work for me

⚫

Kernel 2.6.34 is required to fix bugs with certain network cards and non-linear SKBs (ea8420e9, 19937d04)

⚫

pppd 2.4.6 is required for RFC 4638 support (this is in git but not yet released)

[[Category:Routers]]

⚫

==PPP Not coming back after a blip:==

⚫

This was reported in IRC on Feb 6th 2011. If you get people saying their line didn't come back or their linux box crashed (as in kernel oopsed) after a blip, turns out there's a bug in the kernel pppoe code for 2.6.36 which has been hitting me. some kind of double free in the disconnect code causes a kernel panic. there's a patch here: http://kerneltrap.org/mailarchive/linux-kernel/2010/12/3/4654538 which seems to work for me