Re: Need testers for a network cleanup patch

2009-01-26 Thread Bjoern A. Zeeb
On Thu, 22 Jan 2009, Bjoern A. Zeeb wrote: Hi, while cleaning up protosw things I found that rip6_output was most likely never called from pr_output and after a short talk with Robert the conclusion was that the same had been true for rip_output. Before I am going to remove the initializations

Current problem reports assigned to freebsd-net@FreeBSD.org

2009-01-26 Thread FreeBSD bugmaster
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker

Re: [Patch for review] Experimental NAT-T + PFKey cleanup

2009-01-26 Thread VANHULLEBUS Yvan
On Wed, Jan 21, 2009 at 10:12:32AM +, Bjoern A. Zeeb wrote: [] > >Ipsec-tools team has still not decided how such compatibility issues > >will be handled (or not...), any (good) idea is welcome ! > > While this seems to be a big concern and there is compat breakage with > this patchset alr

Re: freebsd 7.0-RELEASE BUG ping: sendto: No buffer space available

2009-01-26 Thread gnn
At Sat, 24 Jan 2009 16:20:06 +, Rui Paulo wrote: > > > On 24 Jan 2009, at 12:54, Yony Yossef wrote: > > > Hi All, > > > > I'm facing a temporary network hang on my interfaces following a flood > > ping/stress udp test. > > > > I'm running a netperf UDP test which is giving results but does n

Re: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device notconfigured, where 199.7.83.42 is RANDOM IP address

2009-01-26 Thread Daniel O'Connor
On Sunday 25 January 2009 11:43:48 Mark Andrews wrote: > > I've never used mpd myself, but you might want to try adding the > > following line to /usr/local/etc/rc.d/mpd and see if it helps: > > > > # BEFORE: named > > mpd should also be fixed as the error code being returned is not > approprate.

Re[2]: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device notconfigured, where 199.7.83.42 is RANDOM IP address

2009-01-26 Thread Lev Serebryakov
Hello, Daniel. You wrote 24 января 2009 г., 15:10:24: >> Also, mpd5 creates two NG interfaces (ng0 and ng1) on startup to connect >> to two providers. >> >> But previous installation (on faster hardware) doesn't show these >> errors at all! > I think this is an mpd problem - I had the same issue

Re: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address

2009-01-26 Thread Doug Barton
Lev Serebryakov wrote: > Hello, Freebsd-stable. > > BIND on my new router (7.1-STABLE, BIND 9.4.3-P1) shows bunch of > errors on every start and doesn't answer on requests for 30-60 seconds > after that. Errors are like this: It's not necessary or desirable to paste in so many examples of the s

Re: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device notconfigured, where 199.7.83.42 is RANDOM IP address

2009-01-26 Thread Daniel O'Connor
On Saturday 24 January 2009 21:07:33 Lev Serebryakov wrote: > BIND on my new router (7.1-STABLE, BIND 9.4.3-P1) shows bunch of > errors on every start and doesn't answer on requests for 30-60 seconds > after that. Errors are like this: > > Jan 24 12:18:12 gateway named[1455]: > /usr/src/lib/bind/

Re: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address

2009-01-26 Thread Ian Smith
On Sun, 25 Jan 2009, Daniel O'Connor wrote: > On Sunday 25 January 2009 11:43:48 Mark Andrews wrote: Doug Barton wrote: > > > I've never used mpd myself, but you might want to try adding the > > > following line to /usr/local/etc/rc.d/mpd and see if it helps: > > > > > > # BEFORE: named

Re: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device notconfigured, where 199.7.83.42 is RANDOM IP address

2009-01-26 Thread Lev Serebryakov
Hello, Lev. You wrote 24 января 2009 г., 13:37:33: > IP addresses are RANDOM and DIFFERENT on every restart. These IP > addresses are not mentioned in ANY config file on my computer, and > addresses on my network interfaces IS NOT from these networks. Ok, I'm stupid, it is root servers. Ok. Bu

BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address

2009-01-26 Thread Lev Serebryakov
Hello, Freebsd-stable. BIND on my new router (7.1-STABLE, BIND 9.4.3-P1) shows bunch of errors on every start and doesn't answer on requests for 30-60 seconds after that. Errors are like this: Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket

Re: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device notconfigured, where 199.7.83.42 is RANDOM IP address

2009-01-26 Thread Mark Andrews
In message <497b9ff4.30...@freebsd.org>, Doug Barton writes: > Lev Serebryakov wrote: > > Hello, Freebsd-stable. > > > > BIND on my new router (7.1-STABLE, BIND 9.4.3-P1) shows bunch of > > errors on every start and doesn't answer on requests for 30-60 seconds > > after that. Errors are like th

Re: freebsd 7.0-RELEASE BUG ping: sendto: No buffer space available

2009-01-26 Thread Barney Cordoba
--- On Mon, 1/26/09, g...@freebsd.org wrote: > From: g...@freebsd.org > Subject: Re: freebsd 7.0-RELEASE BUG ping: sendto: No buffer space available > To: "Rui Paulo" > Cc: "Liran Liss" , freebsd-net@freebsd.org, "Yony > Yossef" , jo...@nocrew.org, "Amit Krig" > , "Eitan Shefi" > Date: Mo

Re: freebsd 7.0-RELEASE BUG ping: sendto: No buffer space available

2009-01-26 Thread Kip Macy
"No buffer space available" is ENOBUFS. This error is returned when the ifq is full - see IFQ_ENQUEUE in if_var.h. You'll almost certainly want to set ifq_len to larger than the default for a 10 gigabit driver. This most likely to be a combination of ifq_len being too small and inadequate txq overf

Re: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address

2009-01-26 Thread Alexander Motin
Lev Serebryakov wrote: BIND on my new router (7.1-STABLE, BIND 9.4.3-P1) shows bunch of errors on every start and doesn't answer on requests for 30-60 seconds after that. Errors are like this: Jan 24 12:18:12 gateway named[1455]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socke

Re: MTU or Fragmentation Problems on 7.0?

2009-01-26 Thread Len Gross
Ian, Thanks so much for taking the time to look at this problem. I do not have any firewall running on any of the machines, unless something "auto enables." The only rc.conf entries are ifconfig and routing. The thing that is most puzzling to me is that everything is fine on FreeBSD #2 even th

networking benchmarks for Vimage

2009-01-26 Thread Julian Elischer
I have set up a pair of machines which I can boot into either VIMAGE_GLOBAL or normal kernels (otherwise identical). with GB (bge) interfaces between them. I am looking for suggestions as to what tests I should be doing between these machines to be able to assess whether there are any performan

Re: networking benchmarks for Vimage

2009-01-26 Thread Ganbold
Julian Elischer wrote: I have set up a pair of machines which I can boot into either VIMAGE_GLOBAL or normal kernels (otherwise identical). with GB (bge) interfaces between them. I am looking for suggestions as to what tests I should be doing between these machines to be able to assess whether

Multiple ISP routing by port

2009-01-26 Thread jmaps-fbsdnet
I've read through what I could find in this list and also in the top 50 results on google... I can't find anything that'll actually make this work. My DSL ISP is too far away to give me anything faster than 1.5mbps down. In despiration I signed up for comcast to use for bulk traffic. Thus, I wa

Re: Multiple ISP routing by port

2009-01-26 Thread Max Laier
On Tuesday 27 January 2009 06:18:09 jmaps-fbsd...@fireburns.net wrote: > I've read through what I could find in this list and also in the top 50 > results on google... I can't find anything that'll actually make this work. > > My DSL ISP is too far away to give me anything faster than 1.5mbps down.

Re: MTU or Fragmentation Problems on 7.0?

2009-01-26 Thread David DeSimone
Len Gross wrote: > > If I change the MTU on 192.168.1.1 to 1450 and the corresponding MTU > on 192.168.1.2 to 1450, then Web Browsing on FreeBSD2 continues to > work, BUT browsing on FreeBSD3 "fails" (mostly.) You are running into a common TCP methodology in use these days, called "Path MTU Disco

Re: Multiple ISP routing by port

2009-01-26 Thread Julian Elischer
jmaps-fbsd...@fireburns.net wrote: I've read through what I could find in this list and also in the top 50 results on google... I can't find anything that'll actually make this work. yes this i stricky for several reasons My DSL ISP is too far away to give me anything faster than 1.5mbps dow