ieee80211: Extra spaces in nwid

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

ieee80211: Extra spaces in nwid

Alex Holst
When defining a nwid in hostname.ath0 that contains a space, an extra
space is inserted in the nwid assigned to the nic. "Toften 5" becomes
"Toften  5" .. which is not where I live. When setting the nwid manually
with ifconfig, the nwid is set correctly. Can anyone confirm this
behaviour? Full dmesg here:
        http://mongers.org/openbsd/dmesg.tori

tori$ uname -a
OpenBSD tori.inside.mongers.org 3.9 GENERIC#865 i386
tori$ cat /etc/hostname.ath0
nwid "Toften 5" nwkey <network key> chan 3 up
tori$ ifconfig ath0
ath0: flags=8963<UP,BROADCAST,NOTRAILERS,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:0a:e4:2f:1e:ea
        trunk: trunkdev trunk0
        media: IEEE802.11 autoselect (DS1)
        status: no network
        ieee80211: nwid "Toften  5" chan 3 nwkey <not displayed>
        inet6 fe80::20e:9bff:fe98:f655%ath0 prefixlen 64 scopeid 0x2
tori$ sudo ifconfig ath0 nwid "Toften 5"
tori$ ifconfig ath0
ath0: flags=8963<UP,BROADCAST,NOTRAILERS,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:0a:e4:2f:1e:ea
        trunk: trunkdev trunk0
        media: IEEE802.11 autoselect (DS1)
        status: no network
        ieee80211: nwid "Toften 5" chan 3 nwkey <not displayed>
        inet6 fe80::20e:9bff:fe98:f655%ath0 prefixlen 64 scopeid 0x2
tori$


--
I prefer the dark of the night, after midnight and before four-thirty,
when it's more bare, more hollow.                http://a.mongers.org 

Reply | Threaded
Open this post in threaded view
|

Re: ieee80211: Extra spaces in nwid

Jason McIntyre-2
On Sat, Jun 10, 2006 at 12:00:35AM +0200, Alex Holst wrote:
> When defining a nwid in hostname.ath0 that contains a space, an extra
> space is inserted in the nwid assigned to the nic. "Toften 5" becomes
> "Toften  5" .. which is not where I live. When setting the nwid manually
> with ifconfig, the nwid is set correctly. Can anyone confirm this
> behaviour? Full dmesg here:
>         http://mongers.org/openbsd/dmesg.tori
>

todd@ just fixed this.
jmc