Ok, this is a little unfortunate: I can't run traceroute from the client PC
(the service provider doesn't seem to like it). (Nor can I use ping)
The server FreeBSD kernel doesn't support tcpdump. I should recompile it then,
but not now.
So I ran the netstat tests, seeing no other suggestion. B
On 12/27/06, Rastapur Santosh <[EMAIL PROTECTED]> wrote:
Hi,
After applying 6.x TSO patch to 6.2 RELEASE, in transmit
routine, I am getting mbuf with buffer length around 2K with nttcp send.
In FreeBSD current (7.0), I get mbufs with length around 64K. Is there a
separate patch to 6.2 re
Hi,
After applying 6.x TSO patch to 6.2 RELEASE, in transmit
routine, I am getting mbuf with buffer length around 2K with nttcp send.
In FreeBSD current (7.0), I get mbufs with length around 64K. Is there a
separate patch to 6.2 release for this?
Thanks.
-Santosh
__
On Tue, Dec 26, 2006 at 06:45:39PM -0800, Stephan Wehner wrote:
> So I am thinking the problem may be with the co-location operation.
>
> How can I make sure? How can I diagnose this? The only idea I had was
> to run tcpdump on my Linux client (tcpdump host stbgo.org), and indeed
> I can see entri
Hello,
I'm trying to make wpa_supplicant work with wired drivers in FreeBSD
(see [1] too).
I copied some code from mtest (last updatet 3 years ago, but still
present by default) and ran into a problem.
When deleting a multicast address that was added with SIOCADDMULTI
FreeBSD spits up a NOENT. Al
Eugene M. Kim wrote:
[snip]
> Then, when a new address comes up (such as on a dynamically created L2TP
> tun(4) interface), BIND tries to listen on it, but fails because it is
> running setuid as bind:
>
> Dec 27 02:32:00 home named[1121]: listening on IPv4 interface tun0,
> 10.0.2.129#53
> Dec 2
Eugene M. Kim wrote:
> Greetings,
>
> I am running a VPN gateway, where interfaces come and go frequently. I
> set up BIND so that it listens on all interfaces.
> It seems that, instead of listening on a wildcard IPv4 address (*:53,
> that is), BIND monitors for address changes on all interfaces
Greetings,
I am running a VPN gateway, where interfaces come and go frequently. I
set up BIND so that it listens on all interfaces.
It seems that, instead of listening on a wildcard IPv4 address (*:53,
that is), BIND monitors for address changes on all interfaces and
creates a separate listening
On Wed, Dec 27, 2006 at 04:56:38PM +0100, Jeremie Le Hen wrote:
> On Sat, Dec 16, 2006 at 10:13:00AM +, Bjoern A. Zeeb wrote:
> > >this way it's hard to distingvish in a packet filter(let's say pf),
> > >among connections originating from within the jail itself or
> > >from the host system to t
On Sat, Dec 16, 2006 at 10:13:00AM +, Bjoern A. Zeeb wrote:
> >this way it's hard to distingvish in a packet filter(let's say pf),
> >among connections originating from within the jail itself or
> >from the host system to the jail.
>
> I won't ask why you would want to do that if you control i
Earlier in the linear time track, on approximately Tue, Dec 26, 2006 at 18:45 ,
Stephan Wehner divulged this public information:
> I just got a server and put it in a co-location.
> It runs RELEASE FreeBSD 6.1-RELEASE #0, pound, lighttpd and ruby
> on rails.
> Most of the times I find the server
> I can create VLAN attached to this interface, and this seems to work
> but is there anyway to speed up the tagging process ? (ifconfig tells
> this interface does hardware tagging)
Search for 'vlanhwtag' in ifconfig(8).
--
Eygene
___
freebsd-net@freeb
12 matches
Mail list logo
