IPv6 support

[GoogleCodeExporter]

I'd like to know what features for IPv6 are included in most-recent trunk
of this firmware? My provider has native-IPv6 support (but IPv4 is under
NAT) and i would try to test it. 

Original issue reported on code.google.com by Alex.M.V...@gmail.com on 31 Aug 2009 at 9:55

[GoogleCodeExporter]

IPv6 provided "As Is" and unsupported at this moment. At least, FW can be 
compiled
with IPv6 turned on and router boots successfully.

Original comment by lly.dev on 1 Sep 2009 at 6:01

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Does the IPv6 Tunneling work as provided in the web-gui?
I've recompiled with all the IPv6 settings turned on.. still not getting 
connectivity. I'll keep working with it.

Original comment by cybertro...@gmail.com on 7 Sep 2009 at 6:00

[GoogleCodeExporter]

GUI IPv6 support is almost incomplete and can be broken.

Original comment by lly.dev on 7 Sep 2009 at 6:08

[GoogleCodeExporter]

So I got IPv6 working, but I cant get a tunnel working with the HE tunnel 
broker 
service.
I think I need to play with the iptables a bit, because I see packets going out 
on 
the interface, but nothing coming back in.

Original comment by cybertro...@gmail.com on 9 Sep 2009 at 4:15

[GoogleCodeExporter]

Unfortunately, I don't know how to help you - I haven't IPv6 test environment 
at all.

Original comment by lly.dev on 9 Sep 2009 at 9:21

[GoogleCodeExporter]

Would you please post here a short manual (Cybertronic i mean) how you turned 
IPv6
on, with compilation keys, etc

Original comment by Alex.M.V...@gmail.com on 9 Sep 2009 at 6:54

[GoogleCodeExporter]

After pp. 4.2 of CompilingCustomFirmware wiki article you have to:

1) set CONFIG_IPV6=y in .config in /whatever-you-want/broadcom/src/gateway 
manually
or via make menuconfig

2) "make koldconf" from gateway directory

3) proceed with pp. 4.3. of wiki

NB! If resulting FW will be greater than 3800Kb, you will lost your flashfs, 
don't
forget to backup it!

Original comment by lly.dev on 10 Sep 2009 at 9:30

[GoogleCodeExporter]

Suddenly it's not posible to compile firmware with CONFIG_IPV6 enabled, it gives
error after "make install". Can't find modules like tun.o, imq.o, wl.o and one 
more.
If it's necessary i can provide a log laterSuddenly it's not posible to compile
firmware with CONFIG_IPV6 enabled, it gives error after "make install". Can't 
find
modules like tun.o, imq.o, wl.o and one more. If it's necessary i can provide a 
log later

Original comment by Alex.M.V...@gmail.com on 14 Sep 2009 at 9:16

[GoogleCodeExporter]

Something goes wrong in your environment. I successfully build r570 with
CONFIG_IPV6=y moments ago. Try to remove gateway/mipsel-uclibc directory.

Original comment by lly.dev on 14 Sep 2009 at 10:32

[GoogleCodeExporter]

Two comments:

1) IPv6 cannot be included into mainline builds since it don't fit in all 
routers
with 4Mb flash. i.e. wl500gP V1/V2 & wl500W can be flashed only.

2) IPv6 support for our obsolete linux kernel 2.4 is very limited. Volunteers 
for
backports are required.

Original comment by lly.dev on 15 Sep 2009 at 8:55

[GoogleCodeExporter]

So why don't add IPv6 as default for wl500gP and wl500W?
I use ipv6 sucessfully (6to4 tunnel) with oleg 1.9.2.7-10 firmware on my wl500W 
and 
haven't updated because there is no newer firmware supporting it :(

Original comment by josef.schneider on 15 Oct 2009 at 4:33

[GoogleCodeExporter]

Take a look to previous comments:

1) we can't guarantee anything related IPv6 in this FW version due to absence of
qualified testers.

2) we can't maintain separate versions for 4Mb & 8Mb flash currently

Original comment by lly.dev on 15 Oct 2009 at 4:36

[GoogleCodeExporter]

btw, current firmware (r740) with ipv6 enabled fit 4mb flash devices

Original comment by v...@orient-96.ru on 9 Nov 2009 at 5:20

[GoogleCodeExporter]

Original comment by v...@orient-96.ru on 9 Nov 2009 at 5:21

• Changed state: Accepted

[GoogleCodeExporter]

The rest is firewall issues, see http://wl500g.info/showthread.php?t=21119

Original comment by lly.dev on 9 Nov 2009 at 5:44

[GoogleCodeExporter]

In general, core IPv6 functions seems to be working. One major issue is in that
connection tracking support is missing in 2.4 kernels at all. See comment - 

http://www.linux-ipv6.org/ml/usagi-users/msg02587.html

If someone can do ip6_conntrack backport, please help us.

In other words, this means that IPv6 support in FW enters into "pre-beta" phase 
and
we can prepare binaries for semi-closed testing. Unfortunately, we still can't
provide end user support, please ask http://wl500g.info forum community for 
help.

P.S. Of course, there were some bugs in IPv6 kernel 2.4 code, not ported from 
2.6
mainstream.

Original comment by lly.dev on 15 Nov 2009 at 8:52

• Changed state: Started

[GoogleCodeExporter]

I'd like to test a IPv6 firmware on wl500g Premium v1 if posible. My ISP 
provides v4
internet access through VPN and white ipv6 address on physical ethernet 
interface, so
i need only packets forwarding from WAN to br0

Original comment by Alex.M.V...@gmail.com on 15 Nov 2009 at 2:04

[GoogleCodeExporter]

Let's try:
http://code.google.com/p/wl500g/downloads/list?can=4&q=*-r816M

Original comment by lly.dev on 15 Nov 2009 at 3:26

[GoogleCodeExporter]

We don't need ipv6 2.4 conntrack support at all!
There're several ipv6 tunnel services allowed ipv6 routed ip-space, not nat is 
ever 
needed.

Original comment by v...@orient-96.ru on 15 Nov 2009 at 4:28

[GoogleCodeExporter]

All iptables rules with "state" match requires conntrack. We don't need nat, 
yes you
are right, but conntrack != nat 

Original comment by lly.dev on 15 Nov 2009 at 5:10

[GoogleCodeExporter]

yep, but the only profit from "state" match wihout nat is to drop invalid 
connection 
and implement security for new connections from the outside.
we can live without, i'm sure

Original comment by v...@orient-96.ru on 15 Nov 2009 at 5:32

[GoogleCodeExporter]

The firmware you've posted can't apply DNS servers from DHCP properly
(/etc/resolf.conf and /tmp/etc/resolf.conf are empty), so can not connect to 
PPTP
server using URL. Didn't test ipv6 yet

Original comment by Alex.M.V...@gmail.com on 15 Nov 2009 at 5:51

[GoogleCodeExporter]

Very strange, this functionality works well for many customers and in my small 
local
lab. Can you analyze syslog yourself? Which FW you use before?

P.S. Such conversations IMHO will be better at wl500g.info forum.

Original comment by lly.dev on 15 Nov 2009 at 6:00

[GoogleCodeExporter]

Since DNS with DHCP support was broken untill 850,would you please make a new 
firmware with ipv6 
support? Also can you suggest me how to bridge ipv6 packages from WAN to br0, 
while using pptp and 
NAT for ipv4?

Original comment by Alex.M.V...@gmail.com on 24 Nov 2009 at 8:39

[GoogleCodeExporter]

Since DNS with DHCP support was broken untill 850,would you please make a new 
firmware with ipv6 
support? Also can you suggest me how to bridge ipv6 packages from WAN to br0, 
while using pptp and 
NAT for ipv4?

Original comment by Alex.M.V...@gmail.com on 24 Nov 2009 at 9:25

[GoogleCodeExporter]

http://code.google.com/p/wl500g/downloads/list?can=4&q=*-r860M

If you read issues related to IPv6 carefully, I can discover that our major 
problem
in that we can't consult on IPv6 problems! We are at the starting point of IPv6 
too.

Try to read http://wl500g.info/showthread.php?t=21119

Original comment by lly.dev on 24 Nov 2009 at 9:35

[GoogleCodeExporter]

I've tested ipv6 build a bit, so the results:
1) radvd doesn't work with something different then /64 prefix
2) can't ping6 from router to any ipv6 address (local-link or global from /64 
prefix) in inner network
3) can't reach even a default gateway provided by ISP from inner network, 
traceroute 
just stops on router ipv6 address.
If some logs/settings needed, please post here or in topic you provided 1 post 
earlier

Original comment by Alex.M.V...@gmail.com on 25 Nov 2009 at 12:11

[GoogleCodeExporter]

2,3 - works for me & theMIROn (/64 ipv6.he.net tunnel)

As I wrote to you many times, such "end user" tests are useless at this moment! 
You
have to dig problem deeper yourself.

Original comment by lly.dev on 25 Nov 2009 at 7:20

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I had IPv6 working with the "old" oleg firmware 1.9.2.7-10, but ntpd didn't work
(couldn't bind to :: error at startup)
So i Updated to the newest today.
I compiled it myself, because I am not sure if it is enabled in the trx files
available (please note this somewhere).
It works all fine now, even ntpd :D
I use a 6to4 tunnel, like described here:
http://www.wl500g.info/showpost.php?p=97037&postcount=2

If any help with some debugging is needed, I'll be happy to help!

Original comment by josef.schneider on 9 Jan 2010 at 4:17

[GoogleCodeExporter]

One more thing absent in 2.4 kernels - IPv6 multicast routing (IPV6_MROUTE)

Original comment by lly.dev on 13 Feb 2010 at 4:18

[GoogleCodeExporter]

Primary job is done, the known issues is:

* kernel 2.4 related:
  1) ip6_conntrack - need skb fixes backport
  2) IPv6 multicast - need large backports & appropriate real test environment

* common
  1) DHCPv6 PD (Prefix Delegation) - need _qualified_ testers with native IPv6 provider

Original comment by lly.dev on 5 Jul 2010 at 6:35

• Changed state: Fixed
• Added labels: Component-Core

[GoogleCodeExporter]

* kernel 2.6 related:
  1) ipv6_disable - need backport

Original comment by v...@orient-96.ru on 5 Jul 2010 at 7:37

[GoogleCodeExporter]

Thanks, I forget about this. Personally, I don't want to backport IPv6 
multicast to 2.4, so we should implement all pp. 1

Original comment by lly.dev on 5 Jul 2010 at 10:51

[GoogleCodeExporter]

I've partially made it, but accidently rm'ed patched sources...

Original comment by v...@orient-96.ru on 7 Jul 2010 at 5:34