Cannot disable link local addresses on bridge or lagg members

2014-07-29 Thread Clint Armstrong
Is there any known issue that prevents disabling ipv6 and auto_linklocal on members of a lagg or bridge that is using ipv6? I have em0 and em1 which are members of lagg0 and lagg0 is a member of bridge0. This is for a server that runs man jails, including some vnet jails that have tap devices that

Re: nfsd spam in /var/log/messages

2014-07-29 Thread Russell L. Carter
On 07/29/14 13:48, Rick Macklem wrote: > Russell L. Carter: > > The "directories within a file system" exports are only enforced by > the Mount protocol that NFSv3 uses to talk to mountd. (NFSv4 does not > use the Mount protocol.) These are considered "administrative controls", > which is a nic

Re: nfsd spam in /var/log/messages

2014-07-29 Thread Rick Macklem
Russell L. Carter: > > > On 07/29/14 11:21, John-Mark Gurney wrote: > > Rick Macklem wrote this message on Mon, Jul 28, 2014 at 18:47 > > -0400: > >> Russell L. Carter wrote: > >>> On 07/28/14 05:55, Rick Macklem wrote: > >>> > Assuming /export is one file system on the server, put all > >>>

Re: nfsd spam in /var/log/messages

2014-07-29 Thread Russell L. Carter
On 07/29/14 11:21, John-Mark Gurney wrote: > Rick Macklem wrote this message on Mon, Jul 28, 2014 at 18:47 -0400: >> Russell L. Carter wrote: >>> On 07/28/14 05:55, Rick Macklem wrote: >>> Assuming /export is one file system on the server, put all the exports in a single entry, somethin

Re: nfsd spam in /var/log/messages

2014-07-29 Thread Rick Macklem
John-Mark Gurney wrote: > Rick Macklem wrote this message on Mon, Jul 28, 2014 at 18:47 -0400: > > Russell L. Carter wrote: > > > On 07/28/14 05:55, Rick Macklem wrote: > > > > > > > Assuming /export is one file system on the server, put all > > > > the exports in a single entry, something like: >

Re: nfsd spam in /var/log/messages

2014-07-29 Thread John-Mark Gurney
Rick Macklem wrote this message on Mon, Jul 28, 2014 at 18:47 -0400: > Russell L. Carter wrote: > > On 07/28/14 05:55, Rick Macklem wrote: > > > > > Assuming /export is one file system on the server, put all > > > the exports in a single entry, something like: > > > V4: /export -sec=sys -network 1

RE: FreeBSD 10.0-R connected to Cisco switch (in 'trunk' mode with native VLAN) - doesn't work?

2014-07-29 Thread David DeSimone
We use exactly the sort of configuration you showed, and it works perfectly with our FreeBSD systems. It is possible you are running afoul of spanning-tree behavior on the port. Access ports are treated as "edge" ports and can activate right away, while trunk ports must go through the full lis

Re: FreeBSD 10.0-R connected to Cisco switch (in 'trunk' mode with native VLAN) - doesn't work?

2014-07-29 Thread Karl Pielorz
--On 29 July 2014 09:24 -0400 Mike Tancsa wrote: Would it not be better to have switchport trunk allowed vlan 2200-2300 otherwise its not clear to me what would be tagged and what would not be tagged as vlan 2000, no ? I don't think that's the issue - I've had a couple of emails from other

Re: FreeBSD 10.0-R connected to Cisco switch (in 'trunk' mode with native VLAN) - doesn't work?

2014-07-29 Thread Mike Tancsa
On 7/29/2014 9:02 AM, Karl Pielorz wrote: Switch side - the port is configured with: switchport trunk encapsulation dot1q switchport trunk native vlan 2000 switchport trunk allowed vlan 2000,2200-2300 switchport mode trunk Would it not be better to have switchport trunk allowed vlan 2200-2300

FreeBSD 10.0-R connected to Cisco switch (in 'trunk' mode with native VLAN) - doesn't work?

2014-07-29 Thread Karl Pielorz
Hi, I've got a Cisco 3750X switch a colleague is setting up. We've got this configured - but it doesn't seem to talk nicely to our FBSD 10.0-R box, looks like some kind of VLAN issue (but shouldn't be). Switch side - the port is configured with: switchport trunk encapsulation dot1q switchp