Oh... good guess...
next time I'll try with a fresh VM...
fa...@alpha ~ : cat /etc/resolv.conf
# Generated by dhcpcd from eth1
nameserver 192.168.0.254
domain faust-network
nameserver 10.242.42.254
# /etc/resolv.conf.tail can replace this line
fa...@alpha ~ : cat /etc/resolv.conf.head
nameserver 1
On 9/29/2010 4:44 PM, Samuel Martín Moro wrote:
Hi,
I'm trying to replace my (dying) gateway with a qnap ts-509 (1G DDR, celeron
m420 1.6Ghzs).
I'm using mfsBSD, based on FreeBSD-RELEASE-8.1 amd64.
It's almost ready (zfs, nfs, dns, pf, ...), I'm checking everything's OK to
swap the gate.
I n
Thanks for your quick answer.
I tried it out, but still have my slow-connect-problem...
I read somewhere (can't remember where...) that my network chip doesn't
support jumbo frames.
So, I thought I had better to disable rfc1323, and adjust send/recv/dgram
values.
Am I right? Am I doing it right?
Here are my settings for a box doing about 100 Mb/sec. I just included the
values that are different than yours.
kern.ipc.somaxconn: 32768
net.inet.ip.check_interface: 0
net.inet.ip.fastforwarding: 0
net.inet.ip.portrange.first: 49152
net.inet.ip.rtexpire: 3600
net.inet.ip.rtmaxcache: 128
net.in
Hi,
I'm trying to replace my (dying) gateway with a qnap ts-509 (1G DDR, celeron
m420 1.6Ghzs).
I'm using mfsBSD, based on FreeBSD-RELEASE-8.1 amd64.
It's almost ready (zfs, nfs, dns, pf, ...), I'm checking everything's OK to
swap the gate.
I noticed that opening a new connection to distant or
