<parazyd>
enyc: The widget is in extras. I didn't bother making it more "secure". Basically it'll run any `rdate` in $PATH, but it seems to work I think.
* parazyd
now upgrades jenkins
<enyc>
horseshoecrab: for static v6 the ideal is that a ipv6 libicd module whatnot, dhcpv6 stateful client, and so-on ...
<enyc>
21:50 < parazyd> Pali: I think we need a module like libicd-network-ipv4 but for ipv6
<enyc>
horseshoecrab: for me the SLAAC happens on leste but unreliable
<enyc>
parazyd: hrrm, new time sync widget seems to jam.... "hildon-status-menu is not respenging. Close application?"
<enyc>
parazyd: what rdate command is called exactly, I want to test manually...
<Entitlement>
parazyd - [ sync-time-now-widget/sync-time-now-menu-widget.c at master · maemo-leste-extras/... ]
<enyc>
parazyd: and the hildon menu runs as *root* ??
<parazyd>
dsme spawns it, as user IIRC
<enyc>
parazyd: in any case... 'sync clock now' not working for me ... in cli I have to as root 'rdate -4 pool.ntp.org' to get far, it seems to be failing with native ipv6 pool entries by dns or NAT64 to ipv4 ntp pool entries
<enyc>
without root/sudo Operation not permitted
<parazyd>
Yeah I guess it doesn't work
<parazyd>
Perhaps a sudoers entry for rdate in this case could be added
<enyc>
just checking on fremantle
<enyc>
maybe there panel runs as root for some reason
<enyc>
uerr hildon-status-menu ar whatever it is
<parazyd>
Yeah /usr/bin/hildon-status-menu
<enyc>
parazyd: hrrm fremantle "user" can use 'rdate' which in that case is provided by busybox
<parazyd>
Then it's suid probably
<enyc>
not that i can see....
<parazyd>
Then I dunno
<enyc>
oh yes sorry it is
<enyc>
confusing
<enyc>
there is an 'sbin' rdate pointing to busybox
<enyc>
but is al/so /usr/bin/rdate which *is* setuid
<enyc>
users' path uses that separate /usr/bin/rdate
<parazyd>
haha
<parazyd>
Yeah then I guess we need a sudoers entry for this
<parazyd>
Mind doing it?
<enyc>
old openrdate package not in debian package database
<parazyd>
It's just rdate
<enyc>
fremantle cas "openrdate" nontheless
<enyc>
parazyd: I could try, but not up on git or sudo atm
<enyc>
also I note pool.ntp.org. is not (supposed) to be directly used, supposed to register a subzone and so on but I guess leste not big yet ;p
<enyc>
in any case reviewing the underpinning command used would be snsebile i think
Guest47005 is now known as t_rex
<parazyd>
ok let me fix it
<enyc>
sudo rdate -n -s 2.debian.pool.ntp.org may be more sensible.... testing with nat64 ...
<enyc>
ok nat64 works with rdate on newer debian not leste. There is some problem with leste and ipv6 routing.
<enyc>
that is not an rdate problem
uvos has quit [Ping timeout: 265 seconds]
<enyc>
in short, sudo rdate -n -s 0.debian.pool.ntp.org points to a zone which does not yet declare AAAA pointers, except where downstream NAT64 fabricates them.
<enyc>
whereas, sudo rdate -n -s 2.debian.pool.ntp.org will allow ipv6 too and I might suggest use of but leste needs newer n900 kernel or whatever to start unbreaking the auto-ipv6 (unreliable at present...)
<parazyd>
Added the sudoers entry, you can upgrade
<parazyd>
As for IPv6, nothing I can do atm
<enyc>
parazyd: sure, my biggest suspicion is kernel ... In any case curious what will be needed to move n9xx-kernel to a debian LTS kernel e.g. 5.10 series =)
<enyc>
iirc there was some problem with some driver not upstreamed or so
<Wizzup>
I think icd2 needs support for it
<Wizzup>
don't think it's driver related
<enyc>
Wizzup: no, this is additional problem
<Pali>
maemo extras has ipv6 icd plugin
<enyc>
routing unreliable etc. even with autoconfi address
<enyc>
as per fremantle, where it was reliable even with automatic address and no usermode support
<Entitlement>
Pali - [ IPv6 support for Nokia N900 (version 0.2) - maemo.org - Talk ]
<Wizzup>
I think that's linked from that issue
<Pali>
I will try to explain state of ipv6 support...
<Pali>
* obviously you need kernel with ipv6 support, stock nokia did not have, kernel-power was needed
<Pali>
* for address assignment there are multiple independent options (and can be combined): static/manual, RA/SLAAC, DHCPv6-statefull (assigns one address, but can also more are possibles), DHCPv6-PD (assigns prefix of addresses)
<Pali>
* for gateway/router assignment there is only one option: RA
<Pali>
* for DNS server assignment there are multiple independent options and can be combined: static/manual, RA, DHCPv6-stateless, DHCPv6-statefull (part of address asignment)
<Pali>
RA/SLAAC part is implemented in kernel, just needs to be enabled via sysctl and kernel automatically assigns SLACC address to interface
<Pali>
for DNS server from RA, kernel exports it via netlink interface, so userspace can read it and overwrite /etc/resolv.conf
<Pali>
all DHCPv6 modes are implemented in userspace and there are more implementations
<Pali>
RA packet also inform about existance of DHCPv6 and also which modes of DHCPv6 are supported... so userspace needs to listen for RA packets, parse them and start DHCPv6 as required
<Pali>
in maemo fremantle as DHCPv6 client was used "wide" and for detecting of DHCPv6 mode was used custom nokia c application (open source)
<Pali>
integration of starting this application and dhcpv6 client into icd was done by that close source plugin
<Pali>
DHCPv6-PD mode was not supported
<Pali>
in maemo there is ipv6-support which depends on all those required software, plus in its scripts it enable (disabled) ipv6 support in random nokia/fremantle applications
<Pali>
I have written software daemon which listen for RA packets and when "state" changes it can start script with info in env what was changed
<Pali>
it can be used e.g. to automaticaly start dhcpv6 client (in required mode), or updating /etc/resolv.conf
<Pali>
daemon puts all required data to env variables prior spawning user script
<Pali>
I can provide you this my daemon (under GPL) if you think it can be useful
<Pali>
but if you are going to strictly mimic libicd-network-ipv6 behavior with nokia open source c application (osso-rtsol) and helper scripts around in libicd-network-ipv6-script then I think you do not need it
<parazyd>
Is it viable to RE libicd-network-ipv6 ?
<Pali>
I do not know details of icd daemon
<Pali>
for sure you need some plugin which integrates it... but if writing it from zero is better and easier then RE this binary I'm not sure