Sign up here and you can log into the forum!

IPV6 support?

Have a question about devices internals, memory layout, reverse engineering, etc---This is the place for anything so technical that it would cause a n00b's head to 'splode

IPV6 support?   

Postby signal15 » Mon Mar 28, 2011 9:08 am

Has anyone tried loading an ipv6 kernel module to get IPV6 support?

Or, is this on the roadmap to be enabled in the default kernel?
signal15
Donor
 
Posts: 23
Joined: Thu Sep 02, 2010 11:59 am

Re: IPV6 support?   

Postby KAD » Mon Mar 28, 2011 11:50 am

some of the dev's have been talking about it about this possibility,for now we'll have to see what the future brings

KAD
If you like my work please consider a Donation. Donate
Please read the appropriate documentation before posting questions! READ ME FAQ WIKI
PM's are for private matters. Post support questions to the appropriate forum, or they will be ignored.
User avatar
KAD
Global Moderator
 
Posts: 5103
Joined: Mon Apr 12, 2010 4:59 pm
Location: Seattle, WA USA

Re: IPV6 support?   

Postby signal15 » Tue Mar 29, 2011 12:23 pm

Is the kernel source for this available? If so, I should just be able to go in and compile the ipv6 kernel module, copy it over, and load it. This thing and my security cams are the only devices I have that don't yet support it, so I have them all slapped on their own VLAN instead of putting them where I want them.
signal15
Donor
 
Posts: 23
Joined: Thu Sep 02, 2010 11:59 am

Re: IPV6 support?   

Postby mad_ady » Tue Mar 29, 2011 10:35 pm

Haven't played with the kernel, but as far as I know it is a signed kernel and even if you have the source of the vanilla kernel, you will not be able to compile and load custom modules because of the kernel signature. This is why other wifi dongles don't work, because you are unable to load their module in the kernel. So, only WD can add/compile the modules for this kernel... (but there might be some IPv6 support compiled it already).

@Others - please correct me if I'm giving incorrect information...
User avatar
mad_ady
Developer
 
Posts: 4553
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

Re: IPV6 support?   

Postby recliq » Wed Mar 30, 2011 5:14 am

Not quite right....

Yes the kernel itself is signed and only WD can compile new versions
BUT as long the available kernel supports the dependencies you can compile your own modules and load them.
I have done this with quite some modules by now (lirc_dev, lirc_atiusb, ftdi_sio, etc...)

Problems start when you need a kernel option which is not set in the kernel from WD...
­WDLXTV Project Maintainer
-:] If you like my contributions feel free to donate for a beer or a new flash drive. ...and always remember: RTFM! (README, FAQ, WIKI) [:-
User avatar
recliq
WDLXTV Team
 
Posts: 5513
Joined: Thu Apr 15, 2010 8:09 am
Location: Kiel, Germany

Re: IPV6 support?   

Postby mad_ady » Wed Mar 30, 2011 5:30 am

Thanks for setting the record straight recliq.
User avatar
mad_ady
Developer
 
Posts: 4553
Joined: Fri Nov 05, 2010 9:08 am
Location: Bucharest, Romania

Re: IPV6 support?   

Postby Ixar » Sat Apr 02, 2011 8:21 am

I am just build the modules at the moment, so I'll give you feedback soon.
Ixar
n00b
 
Posts: 8
Joined: Tue Mar 22, 2011 11:07 am

Re: IPV6 support?   

Postby b-rad.cc » Sat Apr 02, 2011 8:27 am

modules have already been built and IPv6 has been confirmed working with one custom kernel.

8mo ago: http://b-rad.cc/binaries/ipv6-modules.tgz
last mo: http://b-rad.cc/binaries/kernel-net-modules.tgz

From digging around in the kernel config I'm pretty sure there was one option that could not be compiled as a module that was required for IPv6.
PM's are for private matters only, please post public matters on the forum to help others who might have the same issue.
:mrgreen:
User avatar
b-rad.cc
WDLXTV Team
 
Posts: 3003
Joined: Sat Apr 03, 2010 9:35 am
Location: New York

Re: IPV6 support?   

Postby Ixar » Sat Apr 02, 2011 11:27 am

Confirming what brad just said, I have the following results when inserting the modules for ipv6:
Code: Select all
ipv6: disagrees about version of symbol skb_free_datagram
ipv6: Unknown symbol skb_free_datagram
ipv6: disagrees about version of symbol __skb_checksum_complete
ipv6: Unknown symbol __skb_checksum_complete
ipv6: Unknown symbol __ipv6_addr_type
ipv6: Unknown symbol xfrm_user_policy
ipv6: Unknown symbol xfrm_lookup
ipv6: Unknown symbol __xfrm_lookup
ipv6: Unknown symbol xfrm_state_get_afinfo
ipv6: Unknown symbol xfrm_state_check_expire
ipv6: Unknown symbol xfrm_state_lookup
ipv6: disagrees about version of symbol sk_run_filter
ipv6: Unknown symbol sk_run_filter
ipv6: Unknown symbol __xfrm_policy_check
ipv6: Unknown symbol __xfrm_state_destroy
ipv6: Unknown symbol xfrm_state_put_afinfo
ipv6: disagrees about version of symbol skb_copy_datagram_iovec
ipv6: Unknown symbol skb_copy_datagram_iovec
ipv6: Unknown symbol inet6_lookup
ipv6: Unknown symbol xfrm_replay_check
ipv6: Unknown symbol xfrm_policy_unregister_afinfo
ipv6: disagrees about version of symbol datagram_poll
ipv6: Unknown symbol datagram_poll
ipv6: Unknown symbol secure_tcpv6_sequence_number
ipv6: Unknown symbol ipv6_skip_exthdr
ipv6: Unknown symbol xfrm_state_check
ipv6: Unknown symbol __secpath_destroy
ipv6: disagrees about version of symbol dev_mc_delete
ipv6: Unknown symbol dev_mc_delete
ipv6: Unknown symbol xfrm_parse_spi
ipv6: Unknown symbol inet6_hash_connect
ipv6: Unknown symbol __xfrm_route_forward
ipv6: disagrees about version of symbol skb_kill_datagram
ipv6: Unknown symbol skb_kill_datagram
ipv6: Unknown symbol ipv6_ext_hdr
ipv6: disagrees about version of symbol skb_copy_and_csum_datagram_iovec
ipv6: Unknown symbol skb_copy_and_csum_datagram_iovec
ipv6: Unknown symbol __inet6_lookup_established
ipv6: disagrees about version of symbol ip4_datagram_connect
ipv6: Unknown symbol ip4_datagram_connect
ipv6: disagrees about version of symbol dev_mc_add
ipv6: Unknown symbol dev_mc_add
ipv6: Unknown symbol xfrm_replay_advance
ipv6: Unknown symbol __inet6_hash
ipv6: Unknown symbol xfrm_policy_count
ipv6: Unknown symbol xfrm_state_unregister_afinfo
ipv6: Unknown symbol xfrm_dst_ifdown
ipv6: disagrees about version of symbol skb_recv_datagram
ipv6: Unknown symbol skb_recv_datagram
ipv6: Unknown symbol xfrm_bundle_ok
ipv6: Unknown symbol xfrm_state_lookup_byaddr
ipv6: disagrees about version of symbol __skb_checksum_complete_head
ipv6: Unknown symbol __skb_checksum_complete_head
ipv6: Unknown symbol inet6_lookup_listener
ipv6: Unknown symbol xfrm_dst_lookup
ipv6: Unknown symbol xfrm_policy_register_afinfo
ipv6: Unknown symbol xfrm_init_pmtu
ipv6: Unknown symbol xfrm_state_register_afinfo
ipv6: Unknown symbol secpath_dup

So it needs a bit more work than just compiling the kernel modules.
Ixar
n00b
 
Posts: 8
Joined: Tue Mar 22, 2011 11:07 am

Re: IPV6 support?   

Postby ReMARKable » Sun Apr 03, 2011 1:01 am

After asking WD for IPv6 more then a year ago (http://community.wdc.com/t5/Live-Live-Plus-Ideas/IPv6-support/idi-p/61018), and the WD reaction somewhere on their forum they accepted as their solution: http://community.wdc.com/t5/Networking/IPv6-support/m-p/33730#M3051

I disagree their solution will be the standard. I see a future of public IPv6 addresses combined with natted IPv4 addresses when IPv4 has run out of space.

I have been busy testing IPv6 on the WDLXTV and got things working more then a month ago.
I now created an IPv6-app.bin which also worked, but this doesn't work with most kernels, so releasing it right now like this will bring up more questions and problems.

So there will be an IPv6 enabled version in the future.
User avatar
ReMARKable
Beta Tester
 
Posts: 34
Joined: Tue Apr 06, 2010 8:56 am
Location: The Netherlands

Next

Return to WDTV Live

Who is online

Users browsing this forum: No registered users and 1 guest