getting SSID that are ifconfig list scan unfriently (spaces and unprintable characters)

2008-03-28 Thread Zane C.B.
Just sitting down beginning to write a perl module for getting wireless info under FreeBSD. With out knowing C, is there any way to get SSID info for networks that contain something that makes ifconfig list scan unfriendly to parse? Like spaces and unprintable characters. _

Re: oddness with wpa_cli save_config (FIXED)

2008-03-28 Thread Zane C.B.
On Fri, 28 Mar 2008 13:27:07 -0500 "Zane C.B." <[EMAIL PROTECTED]> wrote: > Just sat down and begin playing around with wpa_cli. > > I have one network network setup already in > '/etc/wpa_supplicant.conf'. This is working with out issue. Now I > try th

oddness with wpa_cli save_config

2008-03-28 Thread Zane C.B.
Just sat down and begin playing around with wpa_cli. I have one network network setup already in '/etc/wpa_supplicant.conf'. This is working with out issue. Now I try the following from wpa_cli and just the the message back "FAIL". > add_network test 1 > set_network 1 ssid "test" OK > save_config

Re: inter pro wireless problems

2006-04-11 Thread Zane C.B.
On Tue, 11 Apr 2006 11:38:24 +0200 (CEST) <[EMAIL PROTECTED]> wrote: > I have a problem setting up Intel PRO / Wireless 2200BG on Asus > A3500N machine running FreeBSD 6.0. I tried to follow instructions > at http://damien.bergamini.free.fr/ipw/ipw-freebsd.html but they are > ok up till some point

Re: is NFS production-ready ?

2006-04-11 Thread Zane C.B.
On Tue, 11 Apr 2006 17:59:50 +0400 dima <[EMAIL PROTECTED]> wrote: > > On Mon, Apr 10, 2006 at 11:26:40PM +0400, dima wrote: > > > 3. Is at least implementation of NFS client (either kernel-side or > > > user-space) stable enough for production use? Client OS > > > replacement is impossible (hardl

Re: is NFS production-ready ?

2006-04-10 Thread Zane C.B.
On Mon, 10 Apr 2006 23:26:40 +0400 dima <[EMAIL PROTECTED]> wrote: > First, searching through the archives I'm about to say "No". > > My goal is to provide NFS service to many FreeBSD clients sharing the > exports. The usage pattern appears to be "many reads and not as much > writes". The deploym