--- On Thu, 1/14/10, Graeme Lee wrote:
>
> Check that
you are not tagging the incoming traffic as vlan
> 301. The ports need to be
in trunk mode.
>
It so funny that you should mention this, yesterday we had
a 7 hour outage due to our Cisco 6506 failing to route anything on our
network. It too
On 15/01/2010 1:25 PM, Stuart Henderson wrote:
On 2010-01-15, Graeme Lee wrote:
Either syntax works. However, had a re-read of your initial email, and
you were missing the "vlan 301" in your configuration line.
It's no longer necessary, it defaults to the number that's part of
the i
On 2010-01-15, Graeme Lee wrote:
> Either syntax works. However, had a re-read of your initial email, and
> you were missing the "vlan 301" in your configuration line.
It's no longer necessary, it defaults to the number that's part of
the interface name (e.g. vlan301 defaults to vlan 301)..
On 15/01/2010 3:13 AM, James Peltier wrote:
--- On Thu, 1/14/10, Graeme Lee wrote:
From: Graeme Lee
Subject: Re: VLANs, OpenBSD, Cisco HP
To: misc@openbsd.org
Received: Thursday, January 14, 2010, 3:27 AM
inet 1.2.3.4 255.255.255.0 NONE vlan 301 vlandev em0
description
--- On Thu, 1/14/10, Graeme Lee wrote:
> From: Graeme Lee
> Subject: Re: VLANs, OpenBSD, Cisco HP
> To: misc@openbsd.org
> Received: Thursday, January 14, 2010, 3:27 AM
> > inet 1.2.3.4 255.255.255.0 NONE vlan 301 vlandev em0
> description "Uplink"
> Like th
Hi
Having any hostname.vlanXX should work. I have eg:
# cat /etc/hostname.vlan50
inet 193.5.69.5 255.255.255.252 NONE vlan 50 vlandev em3
Regards
Matthias
David Goldsmith wrote:
> On 1/14/2010 12:30 AM, James Peltier wrote:
>
>> On the OpenBSD box I have
>>
>> /etc/hostname.em0
>> -
On 1/14/2010 12:30 AM, James Peltier wrote:
On the OpenBSD box I have
/etc/hostname.em0
-- up
/etc/hostname.vlan301
--
inet 1.2.3.4 255.255.255.0
NONE vlandev em0 description "Uplink"
Possibly the vlan hostname files need to start at 0 and increase from
there
On 14/01/2010 5:33 PM, James Peltier wrote:
--- On Thu, 1/14/10, James Peltier wrote:
/etc/hostname.vlan301
--
inet 1.2.3.4 255.255.255.0 NONE vlandev em0 description
"Uplink"
Please note that I've typed this wrong and it actually has
inet 1.2.3.4 255.255.255.0 NONE
2010/1/14 James Peltier :
> on the HP ProCurve I have added the VLANs to the switch and ports and it
> works but not the way I would expect.
>
> Port B4 has VLAN 301 tagged and A1 is the port on which the OpenBSD box is
> connected which is also tagged VLAN 301.
It's been a while since I did th
--- On Thu, 1/14/10, James Peltier wrote:
> /etc/hostname.vlan301
> --
> inet 1.2.3.4 255.255.255.0 NONE vlandev em0 description
> "Uplink"
Please note that I've typed this wrong and it actually has
inet 1.2.3.4 255.255.255.0 NONE vlan 301 vlandev em0 description "Uplink"
in /
Hi have an OpenBSD -current installation as of today that I'm trying to get
VLANs working on. I have an link from a Cisco 6506 (interface 5/8) to a HP
ProCurve 5408XL port B4. The Cisco port 5/8 is configured to the following
set trunk 5/8 on dot1q vlan 301
on the HP ProCurve I have added the
11 matches
Mail list logo
