On 15/01/2010 3:13 AM, James Peltier wrote:
--- On Thu, 1/14/10, Graeme Lee<gra...@omni.net.au> wrote:
From: Graeme Lee<gra...@omni.net.au>
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 this:
# cat /etc/hostname.vlan0
vlan 301 vlandev em0
inet 192.168.1.2 255.255.255.0 192.168.1.255 description
"Uplink"
# cat /etc/hostname.em0
up
From everything I have read in the man pages, FAQ and the great oracle Google,
my chosen syntax works too.
See http://www.openbsd.org/faq/faq6.html
"Or, you may want to use special flags specific to a certain interface. The
format of the hostname file doesn't change much!
$ cat /etc/hostname.vlan0
inet 172.21.0.31 255.255.255.0 NONE vlan 2 vlandev fxp1
"
You caught me with a migraine.
Either syntax works. However, had a re-read of your initial email, and
you were missing the "vlan 301" in your configuration line.
/etc/hostname.vlan301
------------------
inet 1.2.3.4 255.255.255.0 NONE vlandev em0 description "Uplink"
Check that you are not tagging the incoming traffic as vlan 301. The
ports need to be in trunk mode.
if your vlan interface is up, and you get the following:
# ifconfig vlan0
vlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:c0:9f:4b:6f:38
description: test link
vlan: 301 priority: 0 parent interface: em0
groups: vlan
inet 1.2.3.4 netmask 0xffffff00 broadcast 1.2.3.255
inet6 fe80::2c0:9fff:fe4b:6f38%vlan0 prefixlen 64 scopeid 0x7
Then you'll need to re-visit the configuration of your procurve.
Also, tcpdump is your friend. If your interfaces aren't doing hardware
vlan tagging/untagging, you'll get to see
# tcpdump -ni em0
10:33:13.588159 802.1Q vid 301 pri 0 ..................................
Have fun!
g
