Re: kern/181388: [route] Routes not updated on mtu change

2013-08-21 Thread Lev Serebryakov
Hello, Joe. You wrote 21 августа 2013 г., 2:23:49: JH You have a good point wrt VLANs on Windows but everyone uses Intel nics JH right? :P On desktops? Wrong. At least till Haswell. Now, MoBos on Z87 chjipset, are often equipped with new Intel desktop NICs (like V217 or something like

Re: kern/181388: [route] Routes not updated on mtu change

2013-08-20 Thread Joe Holden
. From: Julian Elischer jul...@elischer.org To: bug-follo...@freebsd.org, j...@rewt.org.uk Cc: Subject: Re: kern/181388: [route] Routes not updated on mtu change Date: Mon, 19 Aug 2013 14:57:22 +0800 The problem is that this is not as simple as it seems. The route MTU MIGHT have been set

Re: kern/181388: [route] Routes not updated on mtu change

2013-08-20 Thread Lev Serebryakov
Hello, Joe. You wrote 20 августа 2013 г., 12:25:15: JH vlan interfaces achieve the same thing without having to mess about with JH mtus on routes and also give you an interface to work with, a much nicer JH method comparatively. But it could put huge load on routing between these two segments

Re: kern/181388: [route] Routes not updated on mtu change

2013-08-20 Thread Joe Holden
On 20/08/2013 09:46, Lev Serebryakov wrote: Hello, Joe. You wrote 20 августа 2013 г., 12:25:15: JH vlan interfaces achieve the same thing without having to mess about with JH mtus on routes and also give you an interface to work with, a much nicer JH method comparatively. But it could put

Re: kern/181388: [route] Routes not updated on mtu change

2013-08-20 Thread Lev Serebryakov
Hello, Joe. You wrote 20 августа 2013 г., 18:21:22: JH vlan interfaces achieve the same thing without having to mess about with JH mtus on routes and also give you an interface to work with, a much nicer JH method comparatively. But it could put huge load on routing between these two

RE: kern/181388: [route] Routes not updated on mtu change

2013-08-20 Thread Joe Holden
You have a good point wrt VLANs on Windows but everyone uses Intel nics right? :P -Original Message- From: Lev Serebryakov [mailto:l...@freebsd.org] Sent: 20 August 2013 23:07 To: Joe Holden Cc: freebsd-net@freebsd.org Subject: Re: kern/181388: [route] Routes not updated on mtu

Re: kern/181388: [route] Routes not updated on mtu change

2013-08-19 Thread Julian Elischer
The following reply was made to PR kern/181388; it has been noted by GNATS. From: Julian Elischer jul...@elischer.org To: bug-follo...@freebsd.org, j...@rewt.org.uk Cc: Subject: Re: kern/181388: [route] Routes not updated on mtu change Date: Mon, 19 Aug 2013 14:57:22 +0800 The problem

Re: kern/181388: [route] Routes not updated on mtu change

2013-08-19 Thread Joe Holden
...@rewt.org.uk Cc: Subject: Re: kern/181388: [route] Routes not updated on mtu change Date: Mon, 19 Aug 2013 14:57:22 +0800 The problem is that this is not as simple as it seems. The route MTU MIGHT have been set by something other than the interface MTU in the first place. The interface MTU

Re: kern/181388: [route] Routes not updated on mtu change

2013-08-19 Thread jmg
Synopsis: [route] Routes not updated on mtu change State-Changed-From-To: open-closed State-Changed-By: jmg State-Changed-When: Tue Aug 20 01:07:27 UTC 2013 State-Changed-Why: per response on mailing list, this is as designed so that the person running the box can control the MTU to specific

Re: kern/181388: [route] Routes not updated on mtu change

2013-08-19 Thread John-Mark Gurney
Elischer jul...@elischer.org To: bug-follo...@freebsd.org, j...@rewt.org.uk Cc: Subject: Re: kern/181388: [route] Routes not updated on mtu change Date: Mon, 19 Aug 2013 14:57:22 +0800 The problem is that this is not as simple as it seems. The route MTU MIGHT have been set by something

Re: kern/181388: [route] Routes not updated on mtu change

2013-08-18 Thread linimon
Old Synopsis: Routes not updated on mtu change New Synopsis: [route] Routes not updated on mtu change Responsible-Changed-From-To: freebsd-bugs-freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Aug 19 00:59:13 UTC 2013 Responsible-Changed-Why: Over to maintainer(s).