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. RE: PF + BRIDGE + PFSYNC causes system freezing (kevin)
2. RE: PF + BRIDGE + PFSYNC causes system freezing (kevin)
3. Re: PF + BRIDGE + PFSYNC causes system freezing (Giulio Ferro)
4. RE: PF + BRIDGE + PFSYNC causes system freezing (Greg Hennessy)
5. Re: PF + BRIDGE + PFSYNC causes system freezing (Giulio Ferro)
6. zero copy HTTP server (Vasily Kirin)
7. Re: PF + BRIDGE + PFSYNC causes system freezing (Max Laier)
8. Re: PF + BRIDGE + PFSYNC causes system freezing (Giulio Ferro)
9. Re: PF + BRIDGE + PFSYNC causes system freezing (Max Laier)
10. Kernel panic with lagg configuration. (Leslie Jensen)
11. Re: PF + BRIDGE + PFSYNC causes system freezing (Greg Hennessy)
12. Re: sscanf in kernel (igeek)
13. Re: sscanf in kernel (Juli Mallett)
14. Re: sscanf in kernel (Brad)
15. Re: sscanf in kernel (Saleh Batati)
16. Re: kern/144826: [patch] Add support for bcm5761, bcm5784,
bcm5785 gigabyte lan (bru...@FreeBSD.org)
17. Re: Choosing CPU for router (Ivan Voras)
18. Re: Choosing CPU for router (Brandon Penglase)
19. Re: kern/144826: [patch] Add support for bcm5761, bcm5784,
bcm5785 gigabyte lan (yon...@FreeBSD.org)
20. Re: Choosing CPU for router (Andrew Snow)
21. Re: kern/140682: [netgraph] [panic] random panic in netgraph
(lin...@FreeBSD.org)
22. Re: kern/144844: [netgraph] souce in svn in 8/stable branch
different from shipped source - causing PPP errors with mpd
(lin...@FreeBSD.org)
23. Re: kern/66225: [netgraph] [patch] extend ng_eiface(4)
control messages (lin...@FreeBSD.org)
24. Re: kern/82881: [netgraph] [panic] ng_fec(4) causes kernel
panic after interface detach (lin...@FreeBSD.org)
25. Re: kern/87421: [netgraph] [panic]: ng_ether + ng_eiface +
if_bridge (lin...@FreeBSD.org)
26. Re: kern/102540: [netgraph] [patch] supporting vlan(4) by
ng_fec(4) (lin...@FreeBSD.org)
27. Re: kern/106444: [netgraph] [panic] Kernel Panic on Binding
to an ip to a virtual atm interface(ng_atmpif) (lin...@FreeBSD.org)
28. Re: kern/144808: xbox 360 unable to connect to ath in hostap
mode (re...@FreeBSD.org)
----------------------------------------------------------------------
Message: 1
Date: Wed, 17 Mar 2010 09:55:05 -0400
From: "kevin" <k...@kevinkevin.com>
Subject: RE: PF + BRIDGE + PFSYNC causes system freezing
To: "'Daniel Hartmeier'" <dan...@benzedrine.cx>
Cc: freeb...@freebsd.org, freeb...@freebsd.org
Message-ID: <012301cac5d9$73d933f0$5b8b9bd0$@com>
Content-Type: text/plain; charset="us-ascii"
>What are your settings for
>
> $ sysctl -a | grep bridge.pfil
#bridge options
net.link.bridge.pfil_onlyip=1
net.link.bridge.pfil_member=1
net.link.bridge.pfil_bridge=0
> Have you tried filtering only on one of the physical bridge interfaces,
> with net.link.bridge.pfil_bridge=0 and set skip on { lo0, bridge0, em1 }?
I've only been filtering on one of the bridge interfaces , however I have
not 'set skip on' the other interfaces. I will try that.
------------------------------
Message: 2
Date: Wed, 17 Mar 2010 10:41:38 -0400
From: "kevin" <k...@kevinkevin.com>
Subject: RE: PF + BRIDGE + PFSYNC causes system freezing
To: "'kevin'" <k...@kevinkevin.com>, "'Daniel Hartmeier'"
<dan...@benzedrine.cx>
Cc: freeb...@freebsd.org, freeb...@freebsd.org
Message-ID: <013701cac5df$f4c3ec20$de4bc460$@com>
Content-Type: text/plain; charset="us-ascii"
>>What are your settings for
>>
>> $ sysctl -a | grep bridge.pfil
>#bridge options
>net.link.bridge.pfil_onlyip=1
>net.link.bridge.pfil_member=1
>net.link.bridge.pfil_bridge=0
>> Have you tried filtering only on one of the physical bridge interfaces,
>> with net.link.bridge.pfil_bridge=0 and set skip on { lo0, bridge0, em1}?
>I've only been filtering on one of the bridge interfaces , however I have
>not 'set skip on' the other interfaces. I will try that.
I have 'set skip' all interfaces except one of the bridged ones (em0) , in
pf.conf.
Interesting symptom currently is that the load on both servers is quite high
considering they are just virtual machines that aren't actually doing
anything :
[server1]
last pid: 1176; load averages: 2.66, 3.01, 2.87 up 0+00:36:26
10:34:24
22 processes: 1 running, 21 sleeping
CPU: % user, % nice, % system, % interrupt, % idle
Mem: 8140K Active, 9400K Inact, 27M Wired, 34M Buf, 195M Free
Swap: 120M Total, 120M Free
[server2]
last pid: 1116; load averages: 8.50, 10.11, 8.66 up 0+00:39:35
10:37:46
22 processes: 2 running, 20 sleeping
CPU: 0.0% user, 0.0% nice, 95.2% system, 4.8% interrupt, 0.0% idle
Mem: 8116K Active, 9560K Inact, 16M Wired, 8K Cache, 34M Buf, 205M Free
Swap: 120M Total, 120M Free
I decided to ping the pfsync0 interface from server 1 > server 2 :
# ping 10.0.0.11
PING 10.0.0.11 (10.0.0.11): 56 data bytes
64 bytes from 10.0.0.11: icmp_seq=3 ttl=64 time=91.159 ms
64 bytes from 10.0.0.11: icmp_seq=3 ttl=64 time=114.017 ms (DUP!)
64 bytes from 10.0.0.11: icmp_seq=4 ttl=64 time=206.446 ms
64 bytes from 10.0.0.11: icmp_seq=5 ttl=64 time=92.209 ms
64 bytes from 10.0.0.11: icmp_seq=5 ttl=64 time=181.774 ms (DUP!)
64 bytes from 10.0.0.11: icmp_seq=5 ttl=64 time=363.855 ms (DUP!)
^C
--- 10.0.0.11 ping statistics ---
9 packets transmitted, 3 packets received, +3 duplicates, 66.7% packet loss
round-trip min/avg/max/stddev = 91.159/174.910/363.855/95.135 ms
If theres anything else I could check , suggestions are welcome.
Thanks,
Kevin K.
------------------------------
Message: 3
Date: Wed, 17 Mar 2010 16:46:15 +0100
From: Giulio Ferro <au...@zirakzigil.org>
Subject: Re: PF + BRIDGE + PFSYNC causes system freezing
To: Daniel Hartmeier <dan...@benzedrine.cx>
Cc: freeb...@freebsd.org, kevin <k...@kevinkevin.com>,
freeb...@freebsd.org
Message-ID: <4BA0F947...@zirakzigil.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 17.03.2010 11:47, Giulio Ferro wrote:
> On 17.03.2010 09:12, Daniel Hartmeier wrote:
>> On Tue, Mar 16, 2010 at 03:19:51PM -0400, kevin wrote:
>>
>>> I would like to assist in diagnosing this issue so if anyone wants
>>> me to
>>> check anything or test, please let me know. I would really like to
>>> understand this problem.
>> What are your settings for
>>
>> $ sysctl -a | grep bridge.pfil
>
> net.link.bridge.pfil_local_phys: 0
> net.link.bridge.pfil_member: 1
> net.link.bridge.pfil_bridge: 1
> net.link.bridge.pfil_onlyip: 1
>
>
>> Have you tried filtering only on one of the physical bridge interfaces,
>> with net.link.bridge.pfil_bridge=0 and set skip on { lo0, bridge0,
>> em1 }?
>>
>> Daniel
>
> Ok, I'm trying "set skip on {lo0, bridge0}".
> I'll let you know if there is any improvement.
No, no improvement.
The system froze anyway after about 3-4 hours this time.
Please advise!
------------------------------
Message: 4
Date: Wed, 17 Mar 2010 15:50:32 +0000
From: Greg Hennessy <Greg.H...@nviz.net>
Subject: RE: PF + BRIDGE + PFSYNC causes system freezing
To: Giulio Ferro <au...@zirakzigil.org>, Daniel Hartmeier
<dan...@benzedrine.cx>
Cc: "freeb...@freebsd.org" <freeb...@freebsd.org>,
"freeb...@freebsd.org" <freeb...@freebsd.org>
Message-ID:
<9E8D76EC267C9444AC737...@PEMEXMBXVS02.jellyfishnet.co.uk.local>
Content-Type: text/plain; charset="us-ascii"
A possible corner case with the virtual hosting platform ?
Try changing the NICS from EM to something else supported RL on vmware IIRC.
Greg
________________________________________
From: owner-fr...@freebsd.org [owner-fr...@freebsd.org] On Behalf Of Giulio Ferro [au...@zirakzigil.org]
Sent: 17 March 2010 15:46
To: Daniel Hartmeier
Cc: freeb...@freebsd.org; freeb...@freebsd.org
Subject: Re: PF + BRIDGE + PFSYNC causes system freezing
On 17.03.2010 11:47, Giulio Ferro wrote:
> On 17.03.2010 09:12, Daniel Hartmeier wrote:
>> On Tue, Mar 16, 2010 at 03:19:51PM -0400, kevin wrote:
>>
>>> I would like to assist in diagnosing this issue so if anyone wants
>>> me to
>>> check anything or test, please let me know. I would really like to
>>> understand this problem.
>> What are your settings for
>>
>> $ sysctl -a | grep bridge.pfil
>
> net.link.bridge.pfil_local_phys: 0
> net.link.bridge.pfil_member: 1
> net.link.bridge.pfil_bridge: 1
> net.link.bridge.pfil_onlyip: 1
>
>
>> Have you tried filtering only on one of the physical bridge interfaces,
>> with net.link.bridge.pfil_bridge=0 and set skip on { lo0, bridge0,
>> em1 }?
>>
>> Daniel
>
> Ok, I'm trying "set skip on {lo0, bridge0}".
> I'll let you know if there is any improvement.
No, no improvement.
The system froze anyway after about 3-4 hours this time.
Please advise!
------------------------------
Message: 5
Date: Wed, 17 Mar 2010 17:37:31 +0100
From: Giulio Ferro <au...@zirakzigil.org>
Subject: Re: PF + BRIDGE + PFSYNC causes system freezing
To: Greg Hennessy <Greg.H...@nviz.net>
Cc: "freeb...@freebsd.org" <freeb...@freebsd.org>, Daniel
Hartmeier <dan...@benzedrine.cx>, "freeb...@freebsd.org"
<freeb...@freebsd.org>
Message-ID: <4BA105...@zirakzigil.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 17.03.2010 16:50, Greg Hennessy wrote:
> A possible corner case with the virtual hosting platform ?
>
> Try changing the NICS from EM to something else supported RL on vmware IIRC.
>
>
>
Nope, I'm not using virtualization, that's the other guy.
I'm using a physical machine...
> Greg
>
> ________________________________________
> From: owner-fr...@freebsd.org [owner-fr...@freebsd.org] On Behalf Of Giulio Ferro [au...@zirakzigil.org]
> Sent: 17 March 2010 15:46
> To: Daniel Hartmeier
> Cc: freeb...@freebsd.org; freeb...@freebsd.org
> Subject: Re: PF + BRIDGE + PFSYNC causes system freezing
>
> On 17.03.2010 11:47, Giulio Ferro wrote:
>
>> On 17.03.2010 09:12, Daniel Hartmeier wrote:
>>
>>> On Tue, Mar 16, 2010 at 03:19:51PM -0400, kevin wrote:
>>>
>>>
>>>> I would like to assist in diagnosing this issue so if anyone wants
>>>> me to
>>>> check anything or test, please let me know. I would really like to
>>>> understand this problem.
>>>>
>>> What are your settings for
>>>
>>> $ sysctl -a | grep bridge.pfil
>>>
>> net.link.bridge.pfil_local_phys: 0
>> net.link.bridge.pfil_member: 1
>> net.link.bridge.pfil_bridge: 1
>> net.link.bridge.pfil_onlyip: 1
>>
>>
>>
>>> Have you tried filtering only on one of the physical bridge interfaces,
>>> with net.link.bridge.pfil_bridge=0 and set skip on { lo0, bridge0,
>>> em1 }?
>>>
>>> Daniel
>>>
>> Ok, I'm trying "set skip on {lo0, bridge0}".
>> I'll let you know if there is any improvement.
>>
>
> No, no improvement.
>
> The system froze anyway after about 3-4 hours this time.
>
> Please advise!
> _______________________________________________
> freeb...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-pf
> To unsubscribe, send any mail to "freebsd-pf-...@freebsd.org"
------------------------------
Message: 6
Date: Wed, 17 Mar 2010 19:20:11 +0300
From: Vasily Kirin <vasily...@gmail.com>
Subject: zero copy HTTP server
To: freeb...@freebsd.org
Message-ID:
<a97f34a1003170920y112...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi.
As I can read here:
http://www.freebsd.org/cgi/man.cgi?query=zero_copy&apropos=0&sektion=0&manpath=FreeBSD+8.0-RELEASE&format=html(man
9 zero_copy)
FreeBSD can deliver received TCP data from the kernel to userspace without
any copy ("DMAed from the NIC to a buffer that will then be given to the
user" - from `man 9 zero_copy`)
Further, TCP content cannot be copied to continuous buffer without NIC with
"header splitting" feature. (Achieving page aligned payloads requires a NIC
that can split an incoming packet into multiple buffers. It also generally
requires some sort of intelligence on the NIC to make sure that the payload
starts in its own buffer. This is called ``header splitting``''. - from `man
9 zero_copy`)
I've found several Intel cards with this feature, but still can't find any
example or using this technique.
Is there any example or comprehensive manual of receiving TCP stream
in continuous buffer and passing this buffer to userspace without copy?
Best Regards,
Vasily
------------------------------
Message: 7
Date: Wed, 17 Mar 2010 17:47:28 +0100
From: Max Laier <m...@love2party.net>
Subject: Re: PF + BRIDGE + PFSYNC causes system freezing
To: freeb...@freebsd.org
Cc: "freeb...@freebsd.org" <freeb...@freebsd.org>, Giulio Ferro
<au...@zirakzigil.org>, Greg Hennessy <Greg.H...@nviz.net>
Message-ID: <20100317174...@love2party.net>
Content-Type: Text/Plain; charset="iso-8859-1"
On Wednesday 17 March 2010 17:37:31 Giulio Ferro wrote:
> On 17.03.2010 16:50, Greg Hennessy wrote:
> > A possible corner case with the virtual hosting platform ?
> >
> > Try changing the NICS from EM to something else supported RL on vmware
> > IIRC.
>
> Nope, I'm not using virtualization, that's the other guy.
>
> I'm using a physical machine...
Can you enable WITNESS and compile in DDB. Make sure to report any LORs and
once the system freezes try to enter the debugger and get ps and locks
information.
show allchains
show alllocks
ps
After that you can try to "call doadump" so you get the information in the
coredump and don't have to transcribe it manually.
Thanks,
Max
------------------------------
Message: 8
Date: Wed, 17 Mar 2010 17:57:54 +0100
From: Giulio Ferro <au...@zirakzigil.org>
Subject: Re: PF + BRIDGE + PFSYNC causes system freezing
To: Max Laier <m...@love2party.net>
Cc: "freeb...@freebsd.org" <freeb...@freebsd.org>, Greg Hennessy
<Greg.H...@nviz.net>, freeb...@freebsd.org
Message-ID: <4BA10A12...@zirakzigil.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 17.03.2010 17:47, Max Laier wrote:
> On Wednesday 17 March 2010 17:37:31 Giulio Ferro wrote:
>
>> On 17.03.2010 16:50, Greg Hennessy wrote:
>>
>>> A possible corner case with the virtual hosting platform ?
>>>
>>> Try changing the NICS from EM to something else supported RL on vmware
>>> IIRC.
>>>
>> Nope, I'm not using virtualization, that's the other guy.
>>
>> I'm using a physical machine...
>>
> Can you enable WITNESS and compile in DDB. Make sure to report any LORs and
> once the system freezes try to enter the debugger and get ps and locks
> information.
>
> show allchains
> show alllocks
> ps
>
> After that you can try to "call doadump" so you get the information in the
> coredump and don't have to transcribe it manually.
>
> Thanks,
> Max
>
Sorry, I'm not really an expert of this, but how can I enter the debugger
if the system has frozen?
------------------------------
Message: 9
Date: Wed, 17 Mar 2010 18:00:51 +0100
From: Max Laier <m...@love2party.net>
Subject: Re: PF + BRIDGE + PFSYNC causes system freezing
To: Giulio Ferro <au...@zirakzigil.org>
Cc: "freeb...@freebsd.org" <freeb...@freebsd.org>, Greg Hennessy
<Greg.H...@nviz.net>, freeb...@freebsd.org
Message-ID: <20100317180...@love2party.net>
Content-Type: Text/Plain; charset="iso-8859-1"
On Wednesday 17 March 2010 17:57:54 Giulio Ferro wrote:
> On 17.03.2010 17:47, Max Laier wrote:
> > On Wednesday 17 March 2010 17:37:31 Giulio Ferro wrote:
> >> On 17.03.2010 16:50, Greg Hennessy wrote:
> >>> A possible corner case with the virtual hosting platform ?
> >>>
> >>> Try changing the NICS from EM to something else supported RL on vmware
> >>> IIRC.
> >>
> >> Nope, I'm not using virtualization, that's the other guy.
> >>
> >> I'm using a physical machine...
> >
> > Can you enable WITNESS and compile in DDB. Make sure to report any LORs
> > and once the system freezes try to enter the debugger and get ps and
> > locks information.
> >
> > show allchains
> > show alllocks
> > ps
> >
> > After that you can try to "call doadump" so you get the information in
> > the coredump and don't have to transcribe it manually.
> >
> > Thanks,
> > Max
>
> Sorry, I'm not really an expert of this, but how can I enter the debugger
> if the system has frozen?
Ctrl+Alt+ESC (in default configuration).
------------------------------
Message: 10
Date: Wed, 17 Mar 2010 18:13:02 +0100
From: Leslie Jensen <les...@eskk.nu>
Subject: Kernel panic with lagg configuration.
To: freeb...@freebsd.org
Cc: nvas...@gmx.com
Message-ID: <4BA10D9E...@eskk.nu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hello list.
As you can see below I get a kernel panic if I have a certain line in my
rc.conf.
I would like to provide a backtrace of the problem. Please advise me on
how to proceed.
Thanks
/Leslie
PS: Maybe it's the iwn driver, which is still under development?
-------- Original Message --------
Subject: Re: kernel panic when if_lagg is not loaded.
Date: Wed, 17 Mar 2010 11:59:36 +0200
From: Nikos Vassiliadis <nvas...@gmx.com>
To: Leslie Jensen <les...@eskk.nu>
CC: freebsd-...@freebsd.org <freebsd-...@freebsd.org>
Leslie Jensen wrote:
>
> I'm on a 8.0-RELEASE-p2 system.
>
> Actually after more testing I found out that the line
>
> ifconfig_iwn0="ether 00:16:ea:61:01:e8"
>
> in my rc.conf is the culprit. If I comment it out the system will start
> but only with the wired interface working.
If you don't comment the line it causes a kernel panic?
If that's the case, you should report it to net@. If you
could include a backtrace of the panic, it would be most helpful.
> I have if_lagg_load="YES" in /boot/loader.conf
>
> and the following in /etc/rc.conf
>
> wpa_supplicant_enable="YES"
> ifconfig_em0="up"
> # ifconfig_iwn0="ether 00:16:ea:61:01:e8"
> wlans_iwn0="wlan0"
> ifconfig_wlan0="WPA"
> cloned_interfaces="lagg0"
> ifconfig_lagg0="laggproto failover laggport em0 laggport wlan0 DHCP"
>
> /Leslie
hm, what you do really matches the process described in the handbook.
It should work, please report it.
Nikos
------------------------------
Message: 11
Date: Wed, 17 Mar 2010 17:38:50 +0000
From: Greg Hennessy <Greg.H...@nviz.net>
Subject: Re: PF + BRIDGE + PFSYNC causes system freezing
To: Giulio Ferro <au...@zirakzigil.org>
Cc: "freeb...@freebsd.org" <freeb...@freebsd.org>, Daniel
Hartmeier <dan...@benzedrine.cx>, "freeb...@freebsd.org"
<freeb...@freebsd.org>
Message-ID:
<1893309981.58859.1268...@bda094.bisx.produk.on.blackberry>
Content-Type: text/plain; charset="Windows-1252"
My bad, that'll teach me to reply in haste :-)
Sent using BlackBerry® from Orange
-----Original Message-----
From: Giulio Ferro <au...@zirakzigil.org>
Date: Wed, 17 Mar 2010 16:37:31
To: Greg Hennessy<Greg.H...@nviz.net>
Cc: Daniel Hartmeier<dan...@benzedrine.cx>; freeb...@freebsd.org<freeb...@freebsd.org>; freeb...@freebsd.org<freeb...@freebsd.org>
Subject: Re: PF + BRIDGE + PFSYNC causes system freezing
On 17.03.2010 16:50, Greg Hennessy wrote:
> A possible corner case with the virtual hosting platform ?
>
> Try changing the NICS from EM to something else supported RL on vmware IIRC.
>
>
>
Nope, I'm not using virtualization, that's the other guy.
I'm using a physical machine...
> Greg
>
>________________________________________
> From: owner-fr...@freebsd.org [owner-fr...@freebsd.org] On Behalf Of Giulio Ferro [au...@zirakzigil.org]
> Sent: 17 March 2010 15:46
> To: Daniel Hartmeier
> Cc: freeb...@freebsd.org; freeb...@freebsd.org
> Subject: Re: PF + BRIDGE + PFSYNC causes system freezing
>
> On 17.03.2010 11:47, Giulio Ferro wrote:
>
>> On 17.03.2010 09:12, Daniel Hartmeier wrote:
>>
>>> On Tue, Mar 16, 2010 at 03:19:51PM -0400, kevin wrote:
>>>
>>>
>>>> I would like to assist in diagnosing this issue so if anyone wants
>>>> me to
>>>> check anything or test, please let me know. I would really like to
>>>> understand this problem.
>>>>
>>> What are your settings for
>>>
>>> $ sysctl -a | grep bridge.pfil
>>>
>> net.link.bridge.pfil_local_phys: 0
>> net.link.bridge.pfil_member: 1
>> net.link.bridge.pfil_bridge: 1
>> net.link.bridge.pfil_onlyip: 1
>>
>>
>>
>>> Have you tried filtering only on one of the physical bridge interfaces,
>>> with net.link.bridge.pfil_bridge=0 and set skip on { lo0, bridge0,
>>> em1 }?
>>>
>>> Daniel
>>>
>> Ok, I'm trying "set skip on {lo0, bridge0}".
>> I'll let you know if there is any improvement.
>>
>
> No, no improvement.
>
> The system froze anyway after about 3-4 hours this time.
>
> Please advise!
>_______________________________________________
> freeb...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-pf
> To unsubscribe, send any mail to "freebsd-pf-...@freebsd.org"
------------------------------
Message: 12
Date: Wed, 17 Mar 2010 23:39:12 +0300
From: igeek <gds...@gmail.com>
Subject: Re: sscanf in kernel
To: serena zanetta <sz3...@gmail.com>
Cc: freeb...@freebsd.org
Message-ID: <D9ECA4E6-9FC7-4DA4...@msn.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
sscanf() has a kernel version declared in kernel.h.
http://www.gelato.unsw.edu.au/lxr/source/include/linux/kernel.h#L196
-- Saleh
On Mar 17, 2010, at 2:12 PM, serena zanetta wrote:
> Hi,
> I need to convert an ascii string in its corresponding hex version
> (the same
> as sscanf(str,"%02x%02x...",...) does) in the kernel.
>
> Could someone help me?
>
> Thank you in advice,
>
> Serena
> _______________________________________________
> freeb...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net...@freebsd.org"
>
------------------------------
Message: 13
Date: Wed, 17 Mar 2010 14:13:32 -0700
From: Juli Mallett <jmal...@FreeBSD.org>
Subject: Re: sscanf in kernel
To: igeek <gds...@gmail.com>
Cc: freeb...@freebsd.org, serena zanetta <sz3...@gmail.com>
Message-ID:
<eaa228be1003171413x7b8...@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
On Wed, Mar 17, 2010 at 13:39, igeek <gds...@gmail.com> wrote:
> On Mar 17, 2010, at 2:12 PM, serena zanetta wrote:
>> Hi,
>> I need to convert an ascii string in its corresponding hex version (the
>> same
>> as sscanf(str,"%02x%02x...",...) does) in the kernel.
FreeBSD has sscanf in the kernel. See <sys/systm.h>. That said,
sscanf is pretty evil — are you sure it's what you want? Are you sure
you need to parse it in the kernel instead of in userland?
> sscanf() has a kernel version declared in kernel.h.
> http://www.gelato.unsw.edu.au/lxr/source/include/linux/kernel.h#L196
I believe you are confused. FreeBSD is not Linux.
------------------------------
Message: 14
Date: Wed, 17 Mar 2010 17:22:46 -0400
From: Brad <br...@comstyle.com>
Subject: Re: sscanf in kernel
To: igeek <gds...@gmail.com>, freeb...@freebsd.org
Message-ID: <1268860966.7985.5.camel@Nokia-N900-42-11>
Content-Type: text/plain; charset=utf-8
----- Original message -----
> sscanf() has a kernel version declared in kernel.h.
> http://www.gelato.unsw.edu.au/lxr/source/include/linux/kernel.h#L196
>
> -- Saleh
You must have missed the name of this mailing list, it is freebsd-net not linux-net.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
------------------------------
Message: 15
Date: Thu, 18 Mar 2010 00:25:26 +0300
From: Saleh Batati <gds...@gmail.com>
Subject: Re: sscanf in kernel
To: Juli Mallett <jmal...@freebsd.org>
Cc: freeb...@freebsd.org, serena zanetta <sz3...@gmail.com>
Message-ID:
<9997386c1003171425t449...@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
My bad, I thought that I am working on a different mailing list (linux-net).
-- Saleh
On Thu, Mar 18, 2010 at 12:13 AM, Juli Mallett <jmal...@freebsd.org> wrote:
> On Wed, Mar 17, 2010 at 13:39, igeek <gds...@gmail.com> wrote:
> > On Mar 17, 2010, at 2:12 PM, serena zanetta wrote:
> >> Hi,
> >> I need to convert an ascii string in its corresponding hex version (the
> >> same
> >> as sscanf(str,"%02x%02x...",...) does) in the kernel.
>
> FreeBSD has sscanf in the kernel. See <sys/systm.h>. That said,
> sscanf is pretty evil — are you sure it's what you want? Are you sure
> you need to parse it in the kernel instead of in userland?
>
> > sscanf() has a kernel version declared in kernel.h.
> > http://www.gelato.unsw.edu.au/lxr/source/include/linux/kernel.h#L196
>
> I believe you are confused. FreeBSD is not Linux.
>
------------------------------
Message: 16
Date: Wed, 17 Mar 2010 21:47:05 GMT
From: bru...@FreeBSD.org
Subject: Re: kern/144826: [patch] Add support for bcm5761, bcm5784,
bcm5785 gigabyte lan
To: bru...@FreeBSD.org, freebs...@FreeBSD.org,
freeb...@FreeBSD.org
Message-ID: <201003172147....@freefall.freebsd.org>
Old Synopsis: Add support for bcm5761,bcm5784,bcm5785 gigabyte lan
New Synopsis: [patch] Add support for bcm5761,bcm5784,bcm5785 gigabyte lan
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: brucec
Responsible-Changed-When: Wed Mar 17 21:46:41 UTC 2010
Responsible-Changed-Why:
Over to maintainer(s).
http://www.freebsd.org/cgi/query-pr.cgi?pr=144826
------------------------------
Message: 17
Date: Wed, 17 Mar 2010 23:07:07 +0100
From: Ivan Voras <ivo...@freebsd.org>
Subject: Re: Choosing CPU for router
To: freeb...@freebsd.org
Message-ID: <hnrjqc$87a$1...@dough.gmane.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Jon Otterholm wrote:
> Den 2010-03-17 10.12, skrev "Gilles WAGNER" <gil...@gmail.com>:
>> 2010/3/17 Andrew Snow <and...@modulus.org>
>>> The Supermicro Atom miniserver is more than enough CPU grunt for this sort
>>> of routing/ipfw task. The main reason to go Xeon is if you need ECC RAM,
>>> and even then you can get away with just using the cheapest CPU available.
> This machine is going to act as access-router serving ~500 FTTH-customers.
> About 500Mbit/s and 200kpps. The big issue is Dummynet, around 1000 pipes (2
> pipes/customer).
>
> I don't think an Atom-based machine can handle this, am I wrong?
Yes, don't use an Atom for this. At the very least it will by default
come with a Realtek NIC which won't make you particularly happy.
200kpps is not small or trivial load - think about it: 200 kpps per
direction on a 2 GHz CPU (to simplify calculations) this means only
10,000 CPU cycles per packet - this must include servicing an interrupt
in the incoming path, receiving and parsing the packet, routing it,
firewalling it and then processing it by dummynet and scheduling it on
output. To put this into perspective, a single context switch can take
from ~~1000 CPU cycles to more than 5000 CPU cycles. In short, don't.
------------------------------
Message: 18
Date: Wed, 17 Mar 2010 18:39:20 -0400
From: Brandon Penglase <sysup...@spaceservices.net>
Subject: Re: Choosing CPU for router
To: freeb...@freebsd.org
Message-ID: <20100317183...@Nereus.wlmsprt.pa.neltia.net>
Content-Type: text/plain; charset=US-ASCII
Now that we know the purpose for the router, yes, you will need a beefy
box. Especially if you're going to be running something like Quagga to
handle IGP (which you may or may not be doing...), you will need the
RAM and CPU. If you build a box, get server hardware. I know of one
place that uses Dell 1u servers with either Broadcom or Intel network
cards. I believe the preferred is an Intel NIC.
For a NIC Vendor, check out Silicom: http://www.silicom-usa.com/
They offer a lot of different NICs, both Broadcom and Intel solutions,
but the best is probably the SFP NIC, so you can pick between Fiber or
Copper if you need to.
http://www.silicom-usa.com/default.asp?contentID=1303
Offered in PCI-X, PCI-E, 1Gigabit, and 10Gigabit.
On Wed, 17 Mar 2010 11:22:34 +0100
Jon Otterholm <jon.ot...@ide.resurscentrum.se> wrote:
>
> This machine is going to act as access-router serving ~500
> FTTH-customers. About 500Mbit/s and 200kpps. The big issue is
> Dummynet, around 1000 pipes (2 pipes/customer).
>
> I don't think an Atom-based machine can handle this, am I wrong?
>
> //Jon
>
------------------------------
Message: 19
Date: Thu, 18 Mar 2010 00:07:58 GMT
From: yon...@FreeBSD.org
Subject: Re: kern/144826: [patch] Add support for bcm5761, bcm5784,
bcm5785 gigabyte lan
To: king...@gmail.com, yon...@FreeBSD.org, freeb...@FreeBSD.org,
yon...@FreeBSD.org
Message-ID: <201003180007....@freefall.freebsd.org>
Synopsis: [patch] Add support for bcm5761,bcm5784,bcm5785 gigabyte lan
State-Changed-From-To: open->feedback
State-Changed-By: yongari
State-Changed-When: Thu Mar 18 00:07:04 UTC 2010
State-Changed-Why:
This is very odd. bge(4) already supported these controllers since
r196370. Are you sure latest stable/7, stable/8 and CURRENT still
does not work on these controllers?
Responsible-Changed-From-To: freebsd-net->yongari
Responsible-Changed-By: yongari
Responsible-Changed-When: Thu Mar 18 00:07:04 UTC 2010
Responsible-Changed-Why:
Track.
http://www.freebsd.org/cgi/query-pr.cgi?pr=144826
------------------------------
Message: 20
Date: Thu, 18 Mar 2010 11:32:52 +1100
From: Andrew Snow <a...@octopus.com.au>
Subject: Re: Choosing CPU for router
To: freeb...@freebsd.org
Message-ID: <4BA174B4...@octopus.com.au>
Content-Type: text/plain; charset=UTF-8; format=flowed
Jon Otterholm wrote:
> This machine is going to act as access-router serving ~500
> FTTH-customers.
> About 500Mbit/s and 200kpps. The big issue is Dummynet, around 1000
> pipes (2
> pipes/customer).
That doesn't sound right, 200kpps @ 500Mbps works out to an average
packet size of 250 bytes? Am I missing something
- Andrew
------------------------------
Message: 21
Date: Thu, 18 Mar 2010 04:23:36 GMT
From: lin...@FreeBSD.org
Subject: Re: kern/140682: [netgraph] [panic] random panic in netgraph
To: lin...@FreeBSD.org, freeb...@FreeBSD.org,
freeb...@FreeBSD.org
Message-ID: <201003180423....@freefall.freebsd.org>
Synopsis: [netgraph] [panic] random panic in netgraph
Responsible-Changed-From-To: freebsd-fs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Mar 18 04:23:21 UTC 2010
Responsible-Changed-Why:
Fix assignment brain-o.
http://www.freebsd.org/cgi/query-pr.cgi?pr=140682
------------------------------
Message: 22
Date: Thu, 18 Mar 2010 04:24:05 GMT
From: lin...@FreeBSD.org
Subject: Re: kern/144844: [netgraph] souce in svn in 8/stable branch
different from shipped source - causing PPP errors with mpd
To: lin...@FreeBSD.org, freebs...@FreeBSD.org,
freeb...@FreeBSD.org
Message-ID: <201003180424....@freefall.freebsd.org>
Old Synopsis: souce in svn in 8/stable branch different from shipped source - causing PPP errors with mpd
New Synopsis: [netgraph] souce in svn in 8/stable branch different from shipped source - causing PPP errors with mpd
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Mar 18 04:21:55 UTC 2010
Responsible-Changed-Why:
Over to maintainer(s).
http://www.freebsd.org/cgi/query-pr.cgi?pr=144844
------------------------------
Message: 23
Date: Thu, 18 Mar 2010 04:24:51 GMT
From: lin...@FreeBSD.org
Subject: Re: kern/66225: [netgraph] [patch] extend ng_eiface(4)
control messages
To: lin...@FreeBSD.org, freebs...@FreeBSD.org,
freeb...@FreeBSD.org
Message-ID: <201003180424....@freefall.freebsd.org>
Synopsis: [netgraph] [patch] extend ng_eiface(4) control messages
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Mar 18 04:24:15 UTC 2010
Responsible-Changed-Why:
Over to maintainer(s).
http://www.freebsd.org/cgi/query-pr.cgi?pr=66225
------------------------------
Message: 24
Date: Thu, 18 Mar 2010 04:25:24 GMT
From: lin...@FreeBSD.org
Subject: Re: kern/82881: [netgraph] [panic] ng_fec(4) causes kernel
panic after interface detach
To: lin...@FreeBSD.org, freebs...@FreeBSD.org,
freeb...@FreeBSD.org
Message-ID: <201003180425....@freefall.freebsd.org>
Synopsis: [netgraph] [panic] ng_fec(4) causes kernel panic after interface detach
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Mar 18 04:25:10 UTC 2010
Responsible-Changed-Why:
Over to maintainer(s).
http://www.freebsd.org/cgi/query-pr.cgi?pr=82881
------------------------------
Message: 25
Date: Thu, 18 Mar 2010 04:25:56 GMT
From: lin...@FreeBSD.org
Subject: Re: kern/87421: [netgraph] [panic]: ng_ether + ng_eiface +
if_bridge
To: lin...@FreeBSD.org, freebs...@FreeBSD.org,
freeb...@FreeBSD.org
Message-ID: <201003180425....@freefall.freebsd.org>
Synopsis: [netgraph] [panic]: ng_ether + ng_eiface + if_bridge
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Mar 18 04:25:38 UTC 2010
Responsible-Changed-Why:
Over to maintainer(s).
http://www.freebsd.org/cgi/query-pr.cgi?pr=87421
------------------------------
Message: 26
Date: Thu, 18 Mar 2010 04:26:15 GMT
From: lin...@FreeBSD.org
Subject: Re: kern/102540: [netgraph] [patch] supporting vlan(4) by
ng_fec(4)
To: lin...@FreeBSD.org, freebs...@FreeBSD.org,
freeb...@FreeBSD.org
Message-ID: <201003180426....@freefall.freebsd.org>
Synopsis: [netgraph] [patch] supporting vlan(4) by ng_fec(4)
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Mar 18 04:26:07 UTC 2010
Responsible-Changed-Why:
Over to maintainer(s).
http://www.freebsd.org/cgi/query-pr.cgi?pr=102540
------------------------------
Message: 27
Date: Thu, 18 Mar 2010 04:26:40 GMT
From: lin...@FreeBSD.org
Subject: Re: kern/106444: [netgraph] [panic] Kernel Panic on Binding
to an ip to a virtual atm interface(ng_atmpif)
To: lin...@FreeBSD.org, freebs...@FreeBSD.org,
freeb...@FreeBSD.org
Message-ID: <201003180426....@freefall.freebsd.org>
Old Synopsis: [netgraph] Kernel Panic on Binding to an ip to a virtual atm interface(ng_atmpif)
New Synopsis: [netgraph] [panic] Kernel Panic on Binding to an ip to a virtual atm interface(ng_atmpif)
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Mar 18 04:26:27 UTC 2010
Responsible-Changed-Why:
Over to maintainer(s).
http://www.freebsd.org/cgi/query-pr.cgi?pr=106444
------------------------------
Message: 28
Date: Thu, 18 Mar 2010 07:04:57 GMT
From: re...@FreeBSD.org
Subject: Re: kern/144808: xbox 360 unable to connect to ath in hostap
mode
To: re...@FreeBSD.org, freebs...@FreeBSD.org,
freeb...@FreeBSD.org
Message-ID: <201003180704....@freefall.freebsd.org>
Synopsis: xbox 360 unable to connect to ath in hostap mode
Responsible-Changed-From-To: freebsd-i386->freebsd-net
Responsible-Changed-By: remko
Responsible-Changed-When: Thu Mar 18 07:04:44 UTC 2010
Responsible-Changed-Why:
Reassign to -net
http://www.freebsd.org/cgi/query-pr.cgi?pr=144808
------------------------------
End of freebsd-net Digest, Vol 363, Issue 4
*******************************************