This fixes the breakage I saw with a carp child. This also works with a
bridge child. The routing socket sees the interface status changes, so
things that care get notified.
OK.
On 2011 Feb 16 (Wed) at 14:27:18 +0100 (+0100), Reyk Floeter wrote:
:Hi!
:
:My previous change to vlan(4) allows to
On 16-2-2011 14:27, Reyk Floeter wrote:
My previous change to vlan(4) allows to change the vlandev and vlan id
on-the-fly without re-creating the vlan interface.
I hesitated to ask this simple question, because I might be overlooking
something, but what exactly is the advantage over just using
On 2011 Feb 17 (Thu) at 12:45:35 +0100 (+0100), Camiel Dobbelaar wrote:
:On 16-2-2011 14:27, Reyk Floeter wrote:
: My previous change to vlan(4) allows to change the vlandev and vlan id
: on-the-fly without re-creating the vlan interface.
:
:I hesitated to ask this simple question, because I might
On Thu, Feb 17, 2011 at 12:45:35PM +0100, Camiel Dobbelaar wrote:
On 16-2-2011 14:27, Reyk Floeter wrote:
My previous change to vlan(4) allows to change the vlandev and vlan id
on-the-fly without re-creating the vlan interface.
I hesitated to ask this simple question, because I might be
in the simple setup, like the one described in the pr 6564,
pf won't rewrite source address for the icmp errors (like
destination unreachable) when doing rdr-to.
this diff fixes issue for me and a pr originator. comments?
do we want to put it into 4.9?
Index: pf.c
On 14 February 2011 18:36, Claudio Jeker cje...@diehard.n-r-g.com wrote:
poll() or the other mechanisms to check if a socket is writable or not
have no way to see if a ENOBUF error will be returned on the write.
The problem is that the UDP sendbuffer is always empty (it is only used to
copy
On 17.02.2011 16:22, Mike Belopuhov wrote:
Lukasz has tested the patch below and it works fine for him. I don't
have the hardware myself, so I'm not going to push it for the release,
but if someone thinks it's worth it, please speak up.
Here are some numbers:
4.8
# time tar xzf ./sys.tar.gz
On Thu, Feb 10, 2011 at 14:25 +0100, Lukasz Czarniecki wrote:
Hi
I've bought a Dell R310 with H200 raid controller reported in dmesg as:
Symbios Logic SAS2008. It uses mpii driver and has two hard drives
configured in RAID 1.
Now it seems to work fine but i still have a problem with its
On Thu, Feb 17, 2011 at 04:22:54PM +0100, Mike Belopuhov wrote:
On Thu, Feb 10, 2011 at 14:25 +0100, Lukasz Czarniecki wrote:
Hi
I've bought a Dell R310 with H200 raid controller reported in dmesg as:
Symbios Logic SAS2008. It uses mpii driver and has two hard drives
configured in RAID
Robert wrote:
Hello,
The following diff is really important because on some machines
bge(4) gets detached because of ASPM. The following diff is also
in the latest snapshots but you can also compile a kernel with it.
So if you have a bge(4) please update/compile a kernel and get
back to me
Applied on amd64 -current:
uhub7 at uhub4 port 1 ALCOR Generic USB Hub rev 1.10/3.14 addr 2
Works fine.
//Logan
C-x-C-c
this diff implements the disk cache ioctl handling in mpii so sd(4)
can drive the change rather than have mpii(4) whack everything.
modelled on the same functionality in mpi(4) and mikeb's code...
could someone test this please?
Index: mpii.c
On Fri, Feb 18, 2011 at 3:16 AM, Brynet bry...@gmail.com wrote:
No regression here, although I'm not sure if my controller is capable of
ASPM.
bge0 at pci2 dev 0 function 0 Broadcom BCM57780 rev 0x01, BCM57780 A1
(0x57780001): apic 4 int 16 (irq 7), address 88:ae:1d:0e:3a:76
Same here. No
13 matches
Mail list logo