Re: (partly) SOLVED: tun0 not responding to ping

On Sun, 4 Jan 2009, per...@pluto.rain.com wrote: > Ian Smith wrote: > > On Fri, 2 Jan 2009, per...@pluto.rain.com wrote: > > > > > Why would a local interface, reported as up in ifconfig, not respond > > > to a ping of its own IP address? The tun0 reported below doesn't, > ... > > > $

Having problems with limited broadcast

We have a Python app that implements a DHCP-like protocol using limited broadcast using address 255.255.255.255. Our code works fine on Linux and FreeBSD but we cannot seem to get broadcast to work on FreeBSD. We've tried both Python and C under FreeBSD 7.0. I've found a lengthy discussion of t

the BACKWARD COMPTIBLITY code for the input for netstat leads to a crash

Hi, I use FreeBSD 7.0-Release and find if a mistake input for -m can make netstat crash. such as: netstat -m xxx After simple investigation, I found it is caused by the code in main.c :456 #define BACKWARD_COMPATIBILITY #ifdef BACKWARD_COMPATIBILITY if (*argv) {

Re: TCP packet out-of-order problem

Oops, we surely have kern.ipc.nmbclusters="0" in loader.conf, but I think that should not modify net.inet.tcp.reass.maxsegments to "0" since we wish unlimited nmbclusters but not zero TCP reassembly segments. On Tue, Jan 6, 2009 at 4:16 PM, Robert Watson wrote: > > On Tue, 6 Jan 2009, Lin Jui-Nan

Re: TCP packet out-of-order problem

On Tue, 6 Jan 2009, Lin Jui-Nan Eric wrote: I thought that the system auto-tune improperly in this case. Hmm. Do you have a custom setting for kern.ipc.nmbclusters in loader.conf or sysctl.conf? What does kern.ipc.nmbclusters configure itself to on your system? Also, could you send me th