16:32 <inky> i am trying to change the lock code. i think it accepted default and then whatever i enter it says that lockcode not changed. on d4.

16:32 <inky> i think i never used it.

16:33 <sicelo> yes the current implementation is N900-only

16:33 <sicelo> i don't recall if it really works there even (but i should think it does)

16:34 <Wizzup> it only works on n900 yes

16:34 <Wizzup> well

16:34 <Wizzup> it definitely doesn't work on the d4 is what I should say perhaps

16:45 <inky> ty!

16:45 <inky> in which /etc/init.d file would you suggest me to put macchanger

16:45 <inky> to initialize it early enough so that icd will work.

16:46 <inky> i tried eudev - didn't boot, tried dbus - booted worked but doesn't connect.

17:10 <sicelo> maybe describe what the end goal is

17:20 <inky> well, mac address randomization.

17:21 <inky> i am adding /usr/bin/macchanger -r wlan0 to /etc/init.d/dbus and every time i boot it changes.

17:49 <Wizzup> does that not change the interface names?

17:57 <sicelo> also does it not affect wireless range? i seem to recall D4 had some issues with incorrect MAC ... or you can change it anyhow once it's calibrated?

18:12 <inky> no no it doesn't impact the interface name.

18:12 <inky> the interface name remains wlan0

18:12 <sicelo> and the range?

18:12 <inky> but i don't know about the wireless range. why would it impact like that? it only changes the mac.

18:12 <sicelo> ok. :-)

18:12 <inky> how can i check the range? i don't think so.

18:14 <inky> i know that our isps are logging mac adresses and heard recently even a story that police came to someone's home and asked about someone they didn't know. and they asked police why did you come here, and police said that they know from the isp that his mac address was connected to their wifi.

18:14 <sicelo> i was just asking. wrong mac was the reason https://github.com/maemo-leste/droid4-wlanconfig was needed. but maybe it's fine after the initial 'calibration'

18:15 <inky> it doesn't work even if i change the mac very early, before dbus starts.

18:16 <inky> so i wonder if it is even possible to connect to wifi if the mac is changed early enough.

18:16 <inky> i learned about macchanger, by the way, long ago from maemo wiki.

18:16 <inky> so probably it was working some time ago.

18:17 <inky> but whenever i tried it didn't work for me.

18:31 <sicelo> inky: i don't really use mac randomization myself, but perhaps you can look at how NetworkManager does it, then look at how our icd could implement it

18:33 <inky> i tried also on pinephone/sxmo/postmarketos and xperia/sailfish.

18:33 <inky> on pmos if i change mac on boot it works well afterwards. otherwise it doesn't work.

18:34 <inky> on sailfish i had to build macchanger and it works without problems at runtime. i just need to disconnect from wifi, run it, and connect again.

18:34 <inky> was surprised by how easy it was.

18:35 <inky> on my notebook it is the most convenient. since i just use wpa_supplicant by hand, at home i do macchanger -p to get the default address which is handled by my openwrt router, and otherwise i do macchanger -r and then wpa_supplicant on one line.

18:35 <sicelo> pmos are using NetworkManager ... i know it has support for that. and iirc there are different types of randomization that it can do, e.g. randomizing only while scanning, or randomizing even for actually connecting (associating)

18:35 <inky> yes i added macchanger at the very beginning of networkmanager startup script.

18:35 <inky> perhaps not the smartest thing.

18:35 <inky> but it works.

18:36 <inky> i didn't know nm can do it.

18:36 <sicelo> i *think* NM can do randomization natively ... i.e. i doubt you need macchanger under pmOS

18:37 <sicelo> anyway, back to Leste ... so yes, our icd/2 doesn't have this feature. but i suppose adding it is doable.

21:54 <humanbeta> inky, you should write something about that spectrum emulator to there: https://talk.maemo.org/showthread.php?t=101449