On Thu, 1 Sep 2005, Igor Sysoev wrote:
On Thu, 1 Sep 2005, Igor Sysoev wrote:
I found strange timeout errors returned by kevent() in 6.0 using
my http server named nginx. The nginx's run on three machines:
two 4.10-RELEASE and one 6.0-BETA3. All machines serve the same
content (simple cluste
I am reading 'soisconnected' function in 'Uipc_socket2.c' file.
I find this lines. But I cannot find accf's mean. can you explain to me?thank
you very much!
if ((so->so_options & SO_ACCEPTFILTER) == 0) {
...
} else {
ACCEPT_UNLOCK();
SOCK_LOCK(so);
so->so_upcall =
head->so_
Jon wrote:
>
> I am reading 'soisconnected' function in 'Uipc_socket2.c' file.
> I find this lines. But I cannot find accf's mean. can you explain to me?thank
> you very much!
This is the accept filter stuff we have. Take a look at setsockopt(2)
and accept_filter(9).
--
Andre
> if ((so->s
Hello,
previous patches had problem with quagga/zebra.
here are set of patches for 5.4 that work fine.
I also have patch for quagga to show interface descriptions
in "sh int" command
Best regards,
Alex Bartolomey___
freebsd-net@freebsd.org mailing list
Imrani writes:
[ Charset ISO-8859-1 unsupported, converting... ]
| Hi,
|
| I am trying to configure Cisco Aironet 350 wireless PCI card but I
| get an error which I am unable to find much details for that. Following
| is description of ifconfing:
|
| > ifconfig an0
| an0: flags=884
I ported 'jitter' from WinPcap 3.1 to FreeBSD for i386 and wrote amd64
support:
http://people.freebsd.org/~jkim/bpf_jitter.diff
I didn't do much testing but it seems working pretty well for me so
far. ;-)
You need the following line in the kernel configuration:
options BPF_JITTER
You
*** sys/net/if.c.orig Fri Apr 15 07:52:03 2005
--- sys/net/if.cSat Nov 26 17:34:41 2005
***
*** 1072,1077
--- 1072,1078
{
struct ifreq *ifr;
struct ifstat *ifs;
+ struct ifdescreq *ifrd;
int error = 0;
int new_flags;
s
Sam Leffler wrote:
> I believe the attached change plugs the leak.
I gave it a shot, and the problem is still there. I've checked to make
sure this is in fact the right kernel:
> # strings /boot/kernel/kernel | grep ieee80211_init_neighbor
> ieee80211_init_neighbor
Is there further information
Jung-uk Kim wrote:
I ported 'jitter' from WinPcap 3.1 to FreeBSD for i386 and wrote amd64
support:
http://people.freebsd.org/~jkim/bpf_jitter.diff
I didn't do much testing but it seems working pretty well for me so
far. ;-)
shades of DPF.
Cheers,
Jung-uk Kim
__
On Thursday 01 December 2005 06:17 pm, Julian Elischer wrote:
> Jung-uk Kim wrote:
> >I ported 'jitter' from WinPcap 3.1 to FreeBSD for i386 and wrote
> > amd64 support:
> >
> >http://people.freebsd.org/~jkim/bpf_jitter.diff
> >
> >I didn't do much testing but it seems working pretty well for me
>
Andre Oppermann writes:
| Jack Vogel wrote:
|
| Dear Jack,
|
| > I wanted to introduce myself to the list. I am now the primary contact
| > at Intel for our drivers. There was some earlier email I saw in the archive
| > about 82571/2 support, and I want to confirm that that code is coming.
|
| f
Does the latest release support linksys wireless pcmcia cards??
Thanks.
--
Sent from my BlackBerry Wireless Handheld
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe,
Hi,
I'm not sure what I did wrong. My carp setup with 2 machines sharing 1
virtual ip is working perfect for 3 days now, until today, I got these
messages in /var/log/messages
kernel: carp: incorrect hash
arp_rtrequest:bad gateway 10.10.8.146 (!AF_LINK)
googling brought me to this lin
13 matches
Mail list logo