24 replies to this topic

[stefan1983]

Hey guys,

I just wanted to ask if there are any plans to support IPv6 within OpenPLI in the near future?

Thanks
Stefan

[littlesat]

As far I know... it is already in????

root@et9x00:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:16:B4:02:FE:9B
inet addr:192.168.1.10 Bcast:0.0.0.0 Mask:255.255.255.0
inet6 addr: fe80::216:b4ff:fe02:fe9b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3030 errors:0 dropped:0 overruns:0 frame:0
TX packets:3131 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:431045 (420.9 KiB) TX bytes:909833 (888.5 KiB)
Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 TX bytes:0 (0.0

Edited by littlesat, 14 January 2013 - 21:11.

[WanWizard]

I think Erik's entire house is IPv6, so yeah, don't think that's a problem.

[Zuppelan]

Well... you can't really configure an ipv6 address in Enigma. It's just the kernel that has support. You either have to hack it into the boot-scripts or use a Routing Advertisement Daemon.

[WanWizard]

Ah, you want to be able to configure IPv6 in the GUI?

[Zuppelan]

Configuration from GUI would be the most elegant, but I wouldn't care editing some file in /etc to add the IP-address. But the actual issue is it cannot be configured at all in a proper way: For example, hacking the boot-scripts has the disadvantage they will get overwritten at the next update.

[WanWizard]

Let's wait until Erik wakes up. As he uses it, he should be able to explain how...

[MiLo]

ipv6 should not need any configuration, that was one of the design primitives of the protocol.

Creating a configuration plugin for it for the handful of people that actually know and need to configure it isn't a very grateful task.

[WanWizard]

If you only need it locally that is indeed the case. If you want your box to have a valid public IP, you must give it a fixed IP manually.

[MiLo]

Only if your router is broken.

In a normal IPv6 setup, the router advertises the public settings, so the box would automatically get a routable address (in addition to its link-local address).

In a regular "home" situation, the only reason I can think of to deviate from that is privacy: Your MAC address is used as public IP address, which makes every device trackable across the world. But now that the IPv6 guys have come to their senses and there's NAT for IPv6, you can once more hide your identity behind the router.

[Erik Slagter]

I think Erik's entire house is IPv6, so yeah, don't think that's a problem.

Absolutely!

BTW telnet on OpenPLi doesn't work on ipv6, but ssh (dropbear) does!

[Erik Slagter]

OOW for "normal" users, no adjustments have to be made. Just make sure radv runs somewhere.

Personally I don't want a mac address in my ip address (not for privacy purposes, btw), so indeed I need to set the addresses manually.

[WanWizard]

Thought so.

So back to the OP: how to do that?

[Zuppelan]

A router advertisement daemon has to run in the network. I don't use router advertisements in my network at home, but static IP adresses. Obviously if I were to give the satreceivers an IPV6 address, I want to give them a static address too.

[MiLo]

A router advertisement daemon has to run in the network.

Yeah, on the router. If the router does not do that, take it back to the shop because it is either broken or it doesn't really support the IPv6 protocol.

[Zuppelan]

That's nonsense, in ipv6 you can use static, routing advertisement or DHCP, completely at your choice.

Your statement is similar that no static ip assignment is needed in ipv4 because a router that cannot do DHCP is broken or doesn't support IPV4.

[Zuppelan]

From a practical point of view, you would need to be able to do this in /etc/network/interfaces:

# automatically generated by enigma2
# do NOT change manually!

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address 192.168.1.98
        netmask 255.255.255.0

iface eth0 inet6 static
        address fc00::98
        netmask 64

Now, if adding a GUI to Enigma is too much effort for the use case, how about making Enigma not overwrite the entire file, but a section? Like this:

# This section of this file was automatically generated by Enigma2. Do not edit manually!
# BEGIN AUTOGENERATED SECTION -- DO NOT REMOVE
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address 192.168.1.98
        netmask 255.255.255.0
# END AUTOGENERATED SECTION   -- DO NOT REMOVE

iface eth0 inet6 static
        address fc00::98
        netmask 64

This would allow people to use most or all functionality that Busybox is able to offer, rather than to limit users by the possibilities of the Enigma2 user interface.

Edited by Zuppelan, 16 January 2013 - 15:38.

[littlesat]

Under which circumstances a static IP for IPv6 is really required?

Edited by littlesat, 16 January 2013 - 15:52.

[MiLo]

That's nonsense, in ipv6 you can use static, routing advertisement or DHCP, completely at your choice.
Your statement is similar that no static ip assignment is needed in ipv4 because a router that cannot do DHCP is broken or doesn't support IPV4.

The difference is that router anouncement for IPv6 is mandatory, while DHCP is optional. An IPv4 router that doesn't support DHCP is still a perfectly valid router, it just lacks some feature.

An router that does not support RA is not an IPv6 router, it does not conform to the specification. It should not be sold as "IPv6" router.

Edited by MiLo, 16 January 2013 - 16:04.

[MiLo]

Under which circumstances a static IP for IPv6 is really required?

From a technical point of view: Never.

In addition to that, there are all kinds of perfectly valid reasons to assign or add static addresses to the box, such as unicast and multicast targets, or simply a simple address as to not have to type so many hex characters when you use the box's raw address.