What do you mean by have you used a profile? I use a profile in netcfg which works and I enabled it in /etc/conf.d/netcfg.
I mean /etc/network.d profiles that show the network you want to connect to automatically.
It is working fine for me.
]]>wconfig
eth0 no wireless extensions.
lo no wireless extensions.
wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=off
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
If I restarted the service after starting X, it worked.
What do you mean by have you used a profile? I use a profile in netcfg which works and I enabled it in /etc/conf.d/netcfg.
]]>are you sure the interface is called wlan0 try iwconfig to see what is shown. have you used a profile.
]]>/usr/lib/systemd/system/net-auto-wireless.timer
[Timer]
OnStartupSec=5
[Install]
WantedBy=multi-user.target
Then, I disabled the net-auto-wireless.service and enabled the timer.
]]>Yes, although the bug report is from 2 months ago, and the solution is to not use netcfg with systemd. It isn't even a 'bug'. It's a design flaw that can't be fixed.
So I was thinking in use a solution as using .config/openbox/autostart (I'm using Openbox). I like netcfg.
I'll try your solutions, nm and swifer.
Thank you by your ideas.
]]>interesting tool, Trilby. After i get around to switching my laptop to openrc, i'll consider looking into it.
Alber : looks like trilby's new tool might be just what you're looking for.
]]>This does properly put the interface up, and will connect at boot if the service file is activated. It also has minimal dependencies (you almost certainly have them all installed already).
EDIT: lone_wolf, if you only use wired, why do you need any management tool? Just enable dhcpcd@eth0.service.
]]>example : NM has wpa_supplicant as a hard dependency , for netcfg it's an optional dependency.
My desktop only uses wired connections, i have no need for wpa_supplicant there.
Alber : since the problems are between netcfg and systemd, you could also switch to another init system.
]]>cfr: Yes, although the bug report is from 2 months ago, and the solution is to not use netcfg with systemd. It isn't even a 'bug'. It's a design flaw that can't be fixed.
]]>