At 12:34 PM 8/23/2010, Xavier HUMBERT wrote:
Mike Tancsa wrote:
> I dont understand, why is 10.75.2.1 going out your default interface
> ? It should look for packets on the same subnet that the vlan3
interface is on
E According to the interfaces status and the routing table,
this is
Aleksandr A Babaylov <"."@babolo.ru> wrote:
> I had similar prolem in 8.0-STABLE. Try
>
> sysctl net.inet.flowtable.enable=0
Tried it with no success. Tks anyway
Mike Tancsa wrote:
> I dont understand, why is 10.75.2.1 going out your default interface
> ? It should look for packets on the s
At 11:52 AM 8/20/2010, Xavier HUMBERT wrote:
vlan3: flags=8843 metric 0 mtu 1500
description: Chateau
options=3
ether 00:e0:81:2d:62:3e
inet 10.75.2.251 netmask 0xff00 broadcast 10.75.2.255
media: Ethernet autoselect (1000baseT )
status: active
vlan: 30 parent inte
Aleksandr A Babaylov <"."@babolo.ru> wrote:
> On Fri, Aug 20, 2010 at 05:52:50PM +0200, Xavier HUMBERT wrote:
> > I've got some trouble routing vlans through FreeBSD 8.1-RELEASE.
>
> I had similar prolem in 8.0-STABLE. Try
>
> sysctl net.inet.flowtable.enable=0
I tried net.link.vlan.soft_pad wi
On Fri, Aug 20, 2010 at 05:52:50PM +0200, Xavier HUMBERT wrote:
> I've got some trouble routing vlans through FreeBSD 8.1-RELEASE.
I had similar prolem in 8.0-STABLE. Try
sysctl net.inet.flowtable.enable=0
___
freebsd-net@freebsd.org mailing list
http:
Hi all,
I've got some trouble routing vlans through FreeBSD 8.1-RELEASE.
The core backbone of our network is a Nortel 5520-48T-PWR stack, configured
L2/L3, with 470-24T-PWR stacks in each building (5 including core), fiber
connected.
Since the company who built our network is unable to make the
