[arch-projects] [netcfg] 2.7.1 break my laptop wlan
I have a static wpa2 profile setup that breaks with the new release in testing. :: home.wlan [BUSY] RTNETLINK answers: No such process
Adding gateway 192.168.1.1 failed [FAIL]
my wlan0 device is still present though. everything.log seems clean. Any idea how to debug this? -Andy
Can we see the profile? Thanks, - Jouke On Tue, Mar 20, 2012 at 20:00, Andreas Radke <andyrtr@archlinux.org> wrote:
I have a static wpa2 profile setup that breaks with the new release in testing.
:: home.wlan [BUSY] RTNETLINK answers: No such process > Adding gateway 192.168.1.1 failed [FAIL]
my wlan0 device is still present though. everything.log seems clean.
Any idea how to debug this?
-Andy
CONNECTION="wireless" HOSTNAME=laptop64 #INTERFACE=ath0 INTERFACE=wlan0 #INTERFACE=wlan1 # Interface Settings (use IP="dhcp" for DHCP) IP="static" IFOPTS="192.168.1.110 netmask 255.255.255.0 broadcast 192.168.1.255" GATEWAY=192.168.1.1 # DHCP Example #IP=dhcp #DHCP_TIMEOUT=20 # Default is 10. #DHCP_OPTIONS="" # Extra arguments for dhcpcd # DNS Settings (optional) #DOMAIN=localdomain #DNS1=192.168.0.1 #DNS2=145.253.2.11 #SEARCH= # Standard Wireless Settings ESSID="WLAN69" SECURITY="wpa" # One of wep, wpa, wpa-config, none KEY="XXXXXXXX" # Scans to see if network is available before connecting (reccomended) SCAN="YES" #SCAN="no" # Time to wait to connect to a network. Default 15. TIMEOUT=20 # Pass *custom* options to iwconfig. Usually not needed (optional) IWOPTS="mode managed essid $ESSID" # channel 6" # key restricted $KEY" # Any extra arguments for wpa_supplicant #WPA_OPTS= # For SECURITY='wpa-config' only - filename of a wpa-supplicant config #WPA_CONF= # Commands to run at various stages of configuration #PRE_UP= #POST_UP= #PRE_DOWN= #POST_DOWN="some command"
Wow, that looks old! IFOPTS and IWOPTS are deprecated (the latter is long gone). Please look at the wpa-static example or read the netcfg-profiles man page. It might be that you just need to add ADDR='192.168.1.110'. I would like to hear whether that solves your problem. Regards, - Jouke On Tue, Mar 20, 2012 at 20:04, Andreas Radke <andyrtr@archlinux.org> wrote:
CONNECTION="wireless"
HOSTNAME=laptop64
#INTERFACE=ath0 INTERFACE=wlan0 #INTERFACE=wlan1
# Interface Settings (use IP="dhcp" for DHCP) IP="static" IFOPTS="192.168.1.110 netmask 255.255.255.0 broadcast 192.168.1.255" GATEWAY=192.168.1.1
# DHCP Example #IP=dhcp #DHCP_TIMEOUT=20 # Default is 10. #DHCP_OPTIONS="" # Extra arguments for dhcpcd
# DNS Settings (optional) #DOMAIN=localdomain #DNS1=192.168.0.1 #DNS2=145.253.2.11 #SEARCH=
# Standard Wireless Settings ESSID="WLAN69" SECURITY="wpa" # One of wep, wpa, wpa-config, none KEY="XXXXXXXX"
# Scans to see if network is available before connecting (reccomended) SCAN="YES" #SCAN="no"
# Time to wait to connect to a network. Default 15. TIMEOUT=20
# Pass *custom* options to iwconfig. Usually not needed (optional) IWOPTS="mode managed essid $ESSID" # channel 6" # key restricted $KEY"
# Any extra arguments for wpa_supplicant #WPA_OPTS=
# For SECURITY='wpa-config' only - filename of a wpa-supplicant config #WPA_CONF=
# Commands to run at various stages of configuration #PRE_UP= #POST_UP= #PRE_DOWN= #POST_DOWN="some command"
Am 20.03.2012 20:15, schrieb Jouke Witteveen:
Wow, that looks old! IFOPTS and IWOPTS are deprecated (the latter is long gone). Please look at the wpa-static example or read the netcfg-profiles man page.
Both IFOPTS and IWOPTS are gone (not only deprecated). IWOPTS was often used to connect to hidden networks, which can now be done with the HIDDEN=yes option. IFOPTS seems weird, I didn't think netcfg ever supported that - it is ifconfig syntax, which we got rid of.
Am 20.03.2012 20:19, schrieb Thomas Bächler:
Am 20.03.2012 20:15, schrieb Jouke Witteveen:
Wow, that looks old! IFOPTS and IWOPTS are deprecated (the latter is long gone). Please look at the wpa-static example or read the netcfg-profiles man page.
Both IFOPTS and IWOPTS are gone (not only deprecated).
IWOPTS was often used to connect to hidden networks, which can now be done with the HIDDEN=yes option.
IFOPTS seems weird, I didn't think netcfg ever supported that - it is ifconfig syntax, which we got rid of.
Here we go: https://projects.archlinux.org/netcfg.git/commit/?id=4ed88705b8ea1dae9adc109...
With a clean example profile file it is back working now. Thank you guys. -Andy
Am 20.03.2012 20:00, schrieb Andreas Radke:
I have a static wpa2 profile setup that breaks with the new release in testing.
:: home.wlan [BUSY] RTNETLINK answers: No such process
Adding gateway 192.168.1.1 failed [FAIL]
my wlan0 device is still present though. everything.log seems clean.
Any idea how to debug this?
Your actual profile might be useful. This looks like you use static IP and routes. I am redirecting you to arch-projects, as the soon-to-become new maintainer of netcfg has no access here.
Am 20.03.2012 20:04, schrieb Thomas Bächler:
Am 20.03.2012 20:00, schrieb Andreas Radke:
I have a static wpa2 profile setup that breaks with the new release in testing.
:: home.wlan [BUSY] RTNETLINK answers: No such process
Adding gateway 192.168.1.1 failed [FAIL]
my wlan0 device is still present though. everything.log seems clean.
Any idea how to debug this?
Your actual profile might be useful. This looks like you use static IP and routes.
I am redirecting you to arch-projects, as the soon-to-become new maintainer of netcfg has no access here.
Spoke too soon, you already posted on arch-projects. Stupid me.
participants (3)
-
Andreas Radke
-
Jouke Witteveen
-
Thomas Bächler