headers
Darren Reed | 1 Jul 2008 12:56
Picon

Re: [patch] modular ifconfig

Jason Thorpe wrote:
>
> On Jun 26, 2008, at 2:51 PM, David Young wrote:
>
>> I don't think I understand the use-case you have in mind.  Where does
>> the list come from?  If the list is static, why not link all of the
>> modules, always?
>
> The modules live in directory, and you enumerate the directory 
> looking, loading each one that's there.

I'd like to see this too...

I wonder if it makes sense to adapt netstat to this model?
Or one slightly more complex, that deals with both families
(-f inet) and protocols (-p tcp)?

I'd almost suggest that the family blob that is delivered contains
interfaces for both ifconfig and netstat, but that might be going
just a bit too far.

I don't think there are any other networking commands that
come to mind as benefitting from this style of backend?

Darren

Darren

Darren
(Continue reading)

Permalink | Reply | 3 comments |
headers
Hubert Feyrer | 1 Jul 2008 12:58
Picon
Favicon

Re: [patch] modular ifconfig

On Tue, 1 Jul 2008, Darren Reed wrote:
> I don't think there are any other networking commands that
> come to mind as benefitting from this style of backend?

route(8)?

  - Hubert
Permalink | Reply | 2 comments |
headers
George Michaelson | 2 Jul 2008 05:22
Picon
Favicon

Re: [patch] modular ifconfig

On Tue, 01 Jul 2008 12:58:17 +0200, Hubert Feyrer wrote:

> On Tue, 1 Jul 2008, Darren Reed wrote:
>> I don't think there are any other networking commands that come to mind
>> as benefitting from this style of backend?
> 
> route(8)?
> 
> 
>   - Hubert

wlanctl?

-G
Permalink | Reply | 1 comment |
headers
Daniel Carosone | 2 Jul 2008 05:53
Picon

Re: [patch] modular ifconfig

On Wed, Jul 02, 2008 at 03:22:28AM +0000, George Michaelson wrote:
> On Tue, 01 Jul 2008 12:58:17 +0200, Hubert Feyrer wrote:
> 
> > On Tue, 1 Jul 2008, Darren Reed wrote:
> >> I don't think there are any other networking commands that come to mind
> >> as benefitting from this style of backend?
> > 
> > route(8)?
> 
> wlanctl?

Nice suggestions, but if a whole-sale refactoring of these tools is in
order, heading towards proplib rather than loads-of-ioctl's and
special-code-to-call-them would probably be better.  That still leaves
the question of "syntax modules", but that more restricted space could
be handled with some grammar specifier rule files, or maybe/mostly by
direct inspection of the proplib interface offered by the kernel.

just since we're passing around idle design mandates.. :-)

--
Dan.
Permalink | Reply | 0 comments |
headers
Kaspar Brand | 2 Jul 2008 09:16
Picon

Rules for adding new network drivers?

Are there any particular rules when deciding if a new network driver
should be added to NetBSD? Specifically, I'm wondering about the
et driver (Agere ET1310/ET1301) originally written by Sepherosa Ziehau
for DragonFly [1] and ported to OpenBSD by Jonathan Gray [2].

Would this driver be considered for inclusion even when its current
vendor (LSI) now dubs it as a "legacy product"? [3]

I'm asking because I've actually ported it to NetBSD, since I recently
bought a board with this chip. Does it make sense to submit a patch
(needs some finishing touches), or is that just a waste of effort?
[Don't get me wrong: I'm willing to do the work, but I'd like to know
what the chances are that it gets accepted/included.]

Thanks for any guidance.

Kaspar

[1] http://leaf.dragonflybsd.org/cgi/web-man?command=et&section=4
[2] http://www.openbsd.org/cgi-bin/man.cgi?query=et&sektion=4
[3] http://www.lsi.com/networking_home/networking_products/legacy/index.html
    http://www.lsi.com/networking_home/networking_products/legacy/ethernet/gigabit_ethernet_controllers/et1310/index.html
Permalink | Reply | 2 comments |
headers
Stephen Borrill | 2 Jul 2008 09:56
Picon
Favicon

Re: Rules for adding new network drivers?

On Wed, 2 Jul 2008, Kaspar Brand wrote:
> Are there any particular rules when deciding if a new network driver
> should be added to NetBSD? Specifically, I'm wondering about the
> et driver (Agere ET1310/ET1301) originally written by Sepherosa Ziehau
> for DragonFly [1] and ported to OpenBSD by Jonathan Gray [2].
>
> Would this driver be considered for inclusion even when its current
> vendor (LSI) now dubs it as a "legacy product"? [3]

Being obsolete never stopped NetBSD supporting it. Some would say it was 
quite the opposite!

--

-- 
Stephen
Permalink | Reply | 1 comment |
headers
Jason Thorpe | 3 Jul 2008 05:54

Re: interesting paper at usenix...


On Jun 29, 2008, at 2:45 AM, Matt Fleming wrote:

> I don't think packet aggregation is feasible for NetBSD in general
> because of this statement,

Uh, it's really easy to determine that at run-time.

>
>
> "Packet aggregation is done only for valid TCP packets, i.e., those  
> with
> a valid TCP and IP checksum. We verify only the IP checksum field of  
> the
> network TCP packet before it is used for aggregation. For the TCP
> checksum, we assume the common case that the NIC supports checksum
> offloading, and has validated the TCP checksum. This is because
> verifying the TCP checksum in software would make the aggregation
> expensive."
>
> Matt

-- thorpej
Permalink | Reply | 0 comments |
headers
Kaspar Brand | 3 Jul 2008 19:31
Picon

Re: Rules for adding new network drivers?

Thanks for the replies (also those off-list)! Based on these
"recommendations", I've submitted PR 39094, actually. If it's considered
useful, I can send the patch files to the list as well, of course.

Let me know if there's anything else I should do - or if something is
missing.

Kaspar
Permalink | Reply | 0 comments |
headers
Patrick Welche | 4 Jul 2008 17:47
Picon
Picon
Favicon

hostapd fun

I'm having my first attempt at hostapd, but get

  ioctl[SIOCS80211]: No such file or directory  == ENENT

It seems to come from 

set80211var(..., op=IEEE80211_IOC_DELKEY
bsd_del_key()

trying to delete a key with

      memcpy(wk.idk_macaddr, addr, IEEE80211_ADDR_LEN);
      wk.idk_keyix = (u_int8_t) IEEE80211_KEYIX_NONE; /* XXX */

The idk_macaddr really is the correct macaddress of the client.

So I must be hitting

                        ni = ieee80211_find_node(&ic->ic_sta, dk.idk_macaddr);
                        if (ni == NULL)
                                return ENOENT;

in ieee80211_ioctl.c:ieee80211_ioctl_delkey().

Any idea why?

Cheers,

Patrick
(NetBSD-4.99.68/amd64, ath0)
(Continue reading)

Permalink | Reply | 3 comments |
headers
David Young | 4 Jul 2008 20:02
Picon
Favicon

Re: hostapd fun

On Fri, Jul 04, 2008 at 04:47:31PM +0100, Patrick Welche wrote:
> I'm having my first attempt at hostapd, but get
> 
>   ioctl[SIOCS80211]: No such file or directory  == ENENT

Does this stop it from working?

Dave

--

-- 
David Young             OJC Technologies
dyoung <at> ojctech.com      Urbana, IL * (217) 278-3933 ext 24
Permalink | Reply | 2 comments |

Gmane