freebsd-net Digest, Vol 366, Issue 3
freebsd-n...@freebsd.org
freeb...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-net
or, via email, send a message with subject or body 'help' to
freebsd-n...@freebsd.org
You can reach the person managing the list at
freebsd-...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-net digest..."
Today's Topics:
1. iwi problems on -CURRENT (Apr 6. 2010) (Adam K Kirchhoff)
2. Re: iwi problems on -CURRENT (Apr 6. 2010) (Rui Paulo)
3. Send "connect" control message (serena zanetta)
4. Re: iwi problems on -CURRENT (Apr 6. 2010) (Adam K Kirchhoff)
5. Re: Send "connect" control message (Chuck Swiger)
6. Investment Opportunity of the year. (Ware)
7. Re: net80211 ratectl proof of concept (Weongyo Jeong)
----------------------------------------------------------------------
Message: 1
Date: Tue, 06 Apr 2010 09:35:21 -0400
From: Adam K Kirchhoff <akirchho...@comcast.net>
Subject: iwi problems on -CURRENT (Apr 6. 2010)
To: freeb...@freebsd.org
Message-ID: <4BBB3899...@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
I'm having some problems with iwi on -CURRENT.
FreeBSD scroll.ashke.com 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Sat Apr 3
EDT 2010...@scroll.ashke.com:/usr/obj/usr/src/sys/SCROLL i386
Though this also happens with GENERIC.
In loader.conf I have:
if_iwi_load="YES"
iwi_bss_load="YES"
legal.intel_iwi.license_ack=1
In /etc/rc.conf I have:
wlans_iwi0="wlan0"
ifconfig_wlan0="DHCP wpa"
Upon bootup, iwi fails to work with:
iwi0:<Intel(R) PRO/Wireless 2200BG> at device 3.0 on pci3
iwi0: [ITHREAD]
iwi0: parity error
iwi0: timeout waiting for iwi_bss firmware initialization to complete
iwi0: could not load boot firmware iwi_bss
iwi0: timeout waiting for master
According to the iwi man page, "could not load boot firmware" "should
not happen":-)
Any thoughts on how to get this working? For what it's worth, I
installed FreeBSD on this machine earlier this week, immediately
upgraded to -CURRENT (previous installations from the 8-STABLE series
on this laptop refused to let any wireless driver connect to the APs at
work, so I specifically wanted to see if this had been fixed in
-CURRENT), and iwi worked fine for a few days. Then it stopped, though
I did not change anything on the system. I updated -CURRENT today to
see if doing so would get iwi working again, but it did not.
Adam
------------------------------
Message: 2
Date: Tue, 6 Apr 2010 16:00:12 +0100
From: Rui Paulo <rpa...@freebsd.org>
Subject: Re: iwi problems on -CURRENT (Apr 6. 2010)
To: Adam K Kirchhoff <akirchho...@comcast.net>
Cc: freeb...@freebsd.org
Message-ID: <0AF2E79D-20C9-4815...@freebsd.org>
Content-Type: text/plain; charset=us-ascii
On 6 Apr 2010, at 14:35, Adam K Kirchhoff wrote:
> I'm having some problems with iwi on -CURRENT.
>
> FreeBSD scroll.ashke.com 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Sat Apr 3
> EDT 2010...@scroll.ashke.com:/usr/obj/usr/src/sys/SCROLL i386
>
> Though this also happens with GENERIC.
>
> In loader.conf I have:
>
> if_iwi_load="YES"
> iwi_bss_load="YES"
> legal.intel_iwi.license_ack=1
>
> In /etc/rc.conf I have:
>
> wlans_iwi0="wlan0"
> ifconfig_wlan0="DHCP wpa"
>
> Upon bootup, iwi fails to work with:
>
> iwi0:<Intel(R) PRO/Wireless 2200BG> at device 3.0 on pci3
> iwi0: [ITHREAD]
> iwi0: parity error
> iwi0: timeout waiting for iwi_bss firmware initialization to complete
> iwi0: could not load boot firmware iwi_bss
> iwi0: timeout waiting for master
>
> According to the iwi man page, "could not load boot firmware" "should
> not happen":-)
>
> Any thoughts on how to get this working? For what it's worth, I
> installed FreeBSD on this machine earlier this week, immediately
> upgraded to -CURRENT (previous installations from the 8-STABLE series
> on this laptop refused to let any wireless driver connect to the APs at
> work, so I specifically wanted to see if this had been fixed in
> -CURRENT), and iwi worked fine for a few days. Then it stopped, though
> I did not change anything on the system. I updated -CURRENT today to
> see if doing so would get iwi working again, but it did not.
If it was working fine and you didn't touch anything it can be a hardware fault. Can you boot other OS to check?
Regards,
--
Rui Paulo
------------------------------
Message: 3
Date: Tue, 6 Apr 2010 17:32:40 +0200
From: serena zanetta <sz3...@gmail.com>
Subject: Send "connect" control message
To: freeb...@freebsd.org
Message-ID:
<s2qb2ecfd381004060832oe...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi,
I want to send a connect control message from an ng_hub node to the followin
ng_ksocket node.
I've tired by filling within the ng_hub node the sockaddr_in structure named
connect_addr:
connect_addr->sin_len = 16;
connect_addr->sin_family = AF_INET;
connect_addr->sin_port = htons(55056);
connect_addr->sin_addr.s_addr = htonl(IP_REMOTE);
And send it to the following node as:
*(struct sockaddr_in *)msg->data = connect_addr;
NG_MKMESSAGE(msg,NGM_GINSOCKET_COOKIE,NGM_GINSOCKET_CONNECT,sizeof(struct
sockaddr_in),M_NOWAIT);
NG_SEND_MSG_HOOK(error,node,msg,hook2,0);
But first of all, I don't know how I can convert the IP_REMOTE, which is
currently IP_REMOTE = "10.0.0.90", into a in_addr structure...
Does anyone can suggest me how to fix it?
Thank you,
Serena
------------------------------
Message: 4
Date: Tue, 06 Apr 2010 12:37:23 -0400
From: Adam K Kirchhoff <akirchho...@comcast.net>
Subject: Re: iwi problems on -CURRENT (Apr 6. 2010)
To: Rui Paulo <rpa...@freebsd.org>
Cc: freeb...@freebsd.org
Message-ID: <4BBB6343...@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Shoot, good catch. It doesn't show up in pciconf nor with the Ubuntu
9.10 CD I have here. Thanks. Guess it's time to get my atheros pccard
working.
Adam
On 4/6/2010 11:00 AM, Rui Paulo wrote:
> On 6 Apr 2010, at 14:35, Adam K Kirchhoff wrote:
>
>
>> I'm having some problems with iwi on -CURRENT.
>>
>> FreeBSD scroll.ashke.com 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Sat Apr 3
>> EDT 2010...@scroll.ashke.com:/usr/obj/usr/src/sys/SCROLL i386
>>
>> Though this also happens with GENERIC.
>>
>> In loader.conf I have:
>>
>> if_iwi_load="YES"
>> iwi_bss_load="YES"
>> legal.intel_iwi.license_ack=1
>>
>> In /etc/rc.conf I have:
>>
>> wlans_iwi0="wlan0"
>> ifconfig_wlan0="DHCP wpa"
>>
>> Upon bootup, iwi fails to work with:
>>
>> iwi0:<Intel(R) PRO/Wireless 2200BG> at device 3.0 on pci3
>> iwi0: [ITHREAD]
>> iwi0: parity error
>> iwi0: timeout waiting for iwi_bss firmware initialization to complete
>> iwi0: could not load boot firmware iwi_bss
>> iwi0: timeout waiting for master
>>
>> According to the iwi man page, "could not load boot firmware" "should
>> not happen":-)
>>
>> Any thoughts on how to get this working? For what it's worth, I
>> installed FreeBSD on this machine earlier this week, immediately
>> upgraded to -CURRENT (previous installations from the 8-STABLE series
>> on this laptop refused to let any wireless driver connect to the APs at
>> work, so I specifically wanted to see if this had been fixed in
>> -CURRENT), and iwi worked fine for a few days. Then it stopped, though
>> I did not change anything on the system. I updated -CURRENT today to
>> see if doing so would get iwi working again, but it did not.
>>
> If it was working fine and you didn't touch anything it can be a hardware fault. Can you boot other OS to check?
>
> Regards,
> --
> Rui Paulo
>
>
------------------------------
Message: 5
Date: Tue, 06 Apr 2010 10:41:43 -0700
From: Chuck Swiger <csw...@mac.com>
Subject: Re: Send "connect" control message
To: serena zanetta <sz3...@gmail.com>
Cc: freeb...@freebsd.org
Message-ID: <7FBEC12F-B609-4413...@mac.com>
Content-Type: text/plain; charset=us-ascii
Hi--
On Apr 6, 2010, at 8:32 AM, serena zanetta wrote:
> But first of all, I don't know how I can convert the IP_REMOTE, which is
> currently IP_REMOTE = "10.0.0.90", into a in_addr structure...
To convert a string to an IP address kept as an in_addr, you want inet_aton(), used like so:
const char *ipstr = "127.0.0.1";
struct in_addr ip;
if (!inet_aton(ipstr, &ip))
errx(1, "can't parse IP address %s", ipstr);
[ Example borrowed from "man gethostbyaddr" ]
Regards,
--
-Chuck
------------------------------
Message: 6
Date: Tue, 06 Apr 2010 23:21:14 +0400
From: Ware, Rebekah K. <alonasd...@hotmail.com>
Subject: Investment Opportunity of the year.
To: <freeb...@freebsd.org>
Message-ID: <BLU141-DS139700835...@phx.gbl>
Content-Type: text/plain; charset="utf-8"
Hello freeb...@freebsd.org,
I wanna tell you about a very solid program I participate in
since five month. I made 560% profit at the moment. they are
reliable Hong Kong traders group, active on stock, derivatives, and Forex markets. Their results are
very consistent, they make up to 3% daily and the company pays its
members up to 2.5% daily. HYt fund is really transparent, publishing their trading
results and offering phone, chat, and email support to investors.
I think they are the company to work with in 2010. Check them out: http://texugauto.com/w5wf2xg
------------------------------
Message: 7
Date: Tue, 6 Apr 2010 18:19:25 -0700
From: Weongyo Jeong <weongy...@gmail.com>
Subject: Re: net80211 ratectl proof of concept
To: Rui Paulo <rpa...@freebsd.org>
Cc: freebsd-net <freeb...@freebsd.org>, Andrew Thompson
<tho...@freebsd.org>, Bernhard Schmidt <bsch...@techwires.net>
Message-ID: <20100407011925.GC6799@weongyo>
Content-Type: text/plain; charset=us-ascii
On Mon, Apr 05, 2010 at 05:54:20PM +0100, Rui Paulo wrote:
>
> On 31 Mar 2010, at 14:05, Rui Paulo wrote:
>
> > Hi,
> > I've started developing a ratectl framework for net80211, loosely
> > based on what DragonFly has. Right now only one driver has been
> > ported, but I would like your feedback before continuing.
> >
> > The objective is to, eventually, have all the ratectl stuff (amrr,
> > sample, onoe(?) and rssadapt) in net80211 so all drivers can use it.
> > We can also select which ratectl modules are built in the kernel
> > config file.
> > The framework support changing the current ratectl is out of scope
> > for this patch.
> >
> > You can find the patch here:
> > * http://people.freebsd.org/~rpaulo/ratectl.diff
> >
> > Only the ral driver and the AMRR rate control algorithms were ported.
> >
> > Some comments:
> > o The rate control calls now dereferences several pointers and some
> > inline functions are now real functions. I wonder how much this
> > impacts performance and what we can do to solve it.
> >
> > o I wished there was a better way to do the IEEE80211_AMRR_SUCCESS /
> > IEEE80211_AMRR_FAILURe call.
> >
> > o Some other stuff can also be `const'
> >
> > o I create ieee80211_ratect.[ch] to avoid polluting other files
> >
> > o I moved the AMRR parameters inside amrr_init() on purpose. The
> > drivers we have now only specify a different interval and I plan to
> > add export amrr_set_interval() via the ratectl framework later.
> >
> >
> > I would like very much to see this in, unless there's a strong
> > impending argument.
>
> I've ported all the drivers but I can't test them all. You can read
> the patch at the same URL.
>
> I would like to commit this soon, though.
It looks it's what I really want to see. Please go forward.
regards,
Weongyo Jeong
------------------------------
End of freebsd-net Digest, Vol 366, Issue 3
*******************************************