Problems with Chelsio driver in CURRENT...

2008-02-12 Thread gnn
Hi, I have two MP/Multicore Xeon boxes with CX4 based Chelsio cards in them. If I boot 7.0-RC1 the cards can talk to each other. If I build a recent kernel/world (for instance from today) I cannot ping between them. I have tried using GENERIC as wella as a custom kernel. kodama8# ifconfig cxgb

Re: Strange resolver behavior

2008-02-12 Thread Hajimu UMEMOTO
Hi, > On Tue, 12 Feb 2008 21:51:02 -0800 > Xin LI <[EMAIL PROTECTED]> said: delphij> The problem for this is that others (Windows, CentOS) does not enforce delphij> this. Except the RFC violation, is there any other risk having this delphij> compatibility? Yes, I know that the BIND reso

Re: Strange resolver behavior

2008-02-12 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hajimu UMEMOTO wrote: > Hi, > >> On Tue, 12 Feb 2008 17:31:57 -0800 >> Xin LI <[EMAIL PROTECTED]> said: > > delphij> [EMAIL PROTECTED] ~> host ps_other.a.shifen.com > delphij> ps_other.a.shifen.com has address 202.108.22.46 > delphij> Host ps

Re: Strange resolver behavior

2008-02-12 Thread Hajimu UMEMOTO
Hi, > On Tue, 12 Feb 2008 17:31:57 -0800 > Xin LI <[EMAIL PROTECTED]> said: delphij> [EMAIL PROTECTED] ~> host ps_other.a.shifen.com delphij> ps_other.a.shifen.com has address 202.108.22.46 delphij> Host ps_other.a.shifen.com not found: 3(NXDOMAIN) `_' is not allowed in hostname. Our re

Re: Strange resolver behavior

2008-02-12 Thread Edwin Groothuis
On Tue, Feb 12, 2008 at 07:52:31PM -0800, Xin LI wrote: > Forgot to mention, this happens only with recent FreeBSD versions. With > host(1) from earlier BIND versions there is no problem... I have tried > the same command on an old Linux installation: > > $ host ps_other.a.shifen.com > ps_other.

rtsol doesn't work with bce without promisc (with fix!)

2008-02-12 Thread Kevin Day
Just in case anyone is still using 6.2-RELEASE and can't get rtsol working on a bce network card, with symptoms like this: bce0: flags=8843 mtu 1500 options=3b # rtsol -d bce0 checking if bce0 is ready... bce0 is ready send RS on bce0, whose state is 2 send RS on bce0, whose state i

Re: Strange resolver behavior

2008-02-12 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Forgot to mention, this happens only with recent FreeBSD versions. With host(1) from earlier BIND versions there is no problem... I have tried the same command on an old Linux installation: $ host ps_other.a.shifen.com ps_other.a.shifen.com has addr

Re: Strange resolver behavior

2008-02-12 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Xin LI wrote: > Edwin Groothuis wrote: >> On Tue, Feb 12, 2008 at 06:42:37PM -0800, Xin LI wrote: >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> Edwin Groothuis wrote: On Tue, Feb 12, 2008 at 05:31:57PM -0800, Xin LI wrote: > Re

Re: Strange resolver behavior

2008-02-12 Thread Edwin Groothuis
On Tue, Feb 12, 2008 at 07:09:37PM -0800, Xin LI wrote: > > Yes, but it is the MX record querying it is complaining about. > Well, so perhaps that they are different problems? > > What I think is a problem is that attempting to resolve > 'ps_other.a.shifen.com' gets "Unknown host", here is a quick

Re: Strange resolver behavior

2008-02-12 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Edwin Groothuis wrote: > On Tue, Feb 12, 2008 at 06:42:37PM -0800, Xin LI wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Edwin Groothuis wrote: >>> On Tue, Feb 12, 2008 at 05:31:57PM -0800, Xin LI wrote: Received 127 bytes from 1

Re: Strange resolver behavior

2008-02-12 Thread Edwin Groothuis
On Tue, Feb 12, 2008 at 06:42:37PM -0800, Xin LI wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Edwin Groothuis wrote: > > On Tue, Feb 12, 2008 at 05:31:57PM -0800, Xin LI wrote: > >> Received 127 bytes from 127.0.0.1#53 in 0 ms > >> [EMAIL PROTECTED] ~> host ps_other.a.shifen.com >

Re: Strange resolver behavior

2008-02-12 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Edwin Groothuis wrote: > On Tue, Feb 12, 2008 at 05:31:57PM -0800, Xin LI wrote: >> Received 127 bytes from 127.0.0.1#53 in 0 ms >> [EMAIL PROTECTED] ~> host ps_other.a.shifen.com >> ps_other.a.shifen.com has address 202.108.22.46 >> Host ps_other.a.sh

Re: Strange resolver behavior

2008-02-12 Thread Edwin Groothuis
On Tue, Feb 12, 2008 at 05:31:57PM -0800, Xin LI wrote: > Received 127 bytes from 127.0.0.1#53 in 0 ms > [EMAIL PROTECTED] ~> host ps_other.a.shifen.com > ps_other.a.shifen.com has address 202.108.22.46 > Host ps_other.a.shifen.com not found: 3(NXDOMAIN) 12:49:45.620015 IP 10.251.1.18.51852 > 202.

Strange resolver behavior

2008-02-12 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, It looks like that certain (mis)configuration by the baidu.com DNS administrators has caused this, but I have no clue why our resolver would return NXDOMAIN after it gets a positive response? (Yes, I know that _ is not appropriate for domain name

Re: Kernel compile options

2008-02-12 Thread Tom Judge
Michael Tuexen wrote: Hi George, thanks for the feedback. So I'll make sure that one can compile SCTP with only INET enabled. You mention nothing about SCTP in you original post. I belive that SCTP depends on both INET and INET6. Tom Best regards Michael On Feb 12, 2008, at 3:39 PM, [EMA

Re: if_start() and send queue question

2008-02-12 Thread Tofig Suleymanov
On 2/12/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > At Thu, 07 Feb 2008 19:45:28 +0400, > Tofig Suleymanov wrote: > > > > Hello list, > > > > I will be grateful if someone could point me to the right direction > > regarding the question below. > > > > My device driver is getting incoming pac

Re: kern/116172: [tun] [panic] Network / ipv6 recursive mutex panic

2008-02-12 Thread Bryan Drewery
The following reply was made to PR kern/116172; it has been noted by GNATS. From: Bryan Drewery <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: Subject: Re: kern/116172: [tun] [panic] Network / ipv6 recursive mutex panic Date: Tue, 12 Feb 2008 09:38:29 -0600 Hi, I've been

RE: kern/116172: [tun] [panic] Network / ipv6 recursive mutex panic

2008-02-12 Thread Gregg Czupryna
The following reply was made to PR kern/116172; it has been noted by GNATS. From: Gregg Czupryna <[EMAIL PROTECTED]> To: Bryan Drewery <[EMAIL PROTECTED]>, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> Cc: Subject: RE: kern/116172: [tun] [panic] Network

Re: Kernel compile options

2008-02-12 Thread Michael Tuexen
Hi George, thanks for the feedback. So I'll make sure that one can compile SCTP with only INET enabled. Best regards Michael On Feb 12, 2008, at 3:39 PM, [EMAIL PROTECTED] wrote: At Thu, 7 Feb 2008 15:16:44 +0100, Michael Tuexen wrote: Dear all, I was able to build an IPv4 only kernel by ha

Re: if_start() and send queue question

2008-02-12 Thread gnn
At Thu, 07 Feb 2008 19:45:28 +0400, Tofig Suleymanov wrote: > > Hello list, > > I will be grateful if someone could point me to the right direction > regarding the question below. > > My device driver is getting incoming packets fine, but for some reason I > am not able to send a single packe

Re: Kernel compile options

2008-02-12 Thread gnn
At Thu, 7 Feb 2008 15:16:44 +0100, Michael Tuexen wrote: > > Dear all, > > I was able to build an IPv4 only kernel by having > options INET > #options INET6 > in the kernel config file. > > Is it supposed to work that one can build a IPv6-only > kernel by using > #options INET > options INET6 >

[PATCH] ng_nat(4) redirects and rc.d script

2008-02-12 Thread Vadim Goncharov
Hello! Please test: http://antigreen.org/vadim/freebsd/ng_nat/ (I've ran for a week on a production 6.2 router without any problems). This is a patched version of ng_nat(4) for FreeBSD 6.x, providing support for all libalias(3) features, especially port redirections (before this moment ng_nat