Re: VLANs, OpenBSD, Cisco HP

Previous thread: Dominios $40 por año | Resellers desde $16 | Hosting d by Mail Delivery System on Wednesday, January 13, 2010 - 6:47 pm. (1 message)

Next thread: Re: VLANs, OpenBSD, Cisco HP by James Peltier on Wednesday, January 13, 2010 - 11:33 pm. (5 messages)
From: James Peltier
Date: Wednesday, January 13, 2010 - 10:30 pm

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 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. 

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" 

/etc/mygate
------------------
1.2.3.254

So, here's what I don't expect and maybe my expectations are wrong, but anyways. This configuration doesn't work?!?  If I have

inet 1.2.3.4 255.255.255.0 NONE description "Uplink" 

in /etc/hostname.em0 it works.  Since the port is tagged on the Cisco and both HP ports I would have thought that you needed to have the VLAN 301 configuration on OpenBSD as well to properly untag the ports?

Any help would be extremely useful as I'm trying to deploy this as a VLAN router.  I'm sure it's something really simple that I'm missing here.

---
James A. Peltier     james_a_peltier@yahoo.ca


      __________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr! 

http://www.flickr.com/gift/

From: SJP Lists
Date: Thursday, January 14, 2010 - 1:02 am

It's been a while since I did this with a ProCurve and OpenBSD, but
have you tried setting A1 as a trunk?

From: David Goldsmith
Date: Thursday, January 14, 2010 - 6:46 am

Possibly the vlan hostname files need to start at 0 and increase from 
there rather then skipping directly to a higher number? From the FAQ, 
section 6.2.1, they show the vlan0 interface being associated with vlan 
2 so the file number does not need to match the vlan number:

    $ cat /etc/hostname.vlan0
    inet 172.21.0.31 255.255.255.0 NONE vlan 2 vlandev fxp1

http://www.openbsd.org/faq/faq6.html#Setup.if

David Goldsmith

From: Matthias Cramer
Date: Thursday, January 14, 2010 - 8:13 am

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



--
Matthias Cramer, Erachfeldstrasse 1b, CH-8180 BC<lach
http://www.freestone.net
GnuPG 1024D/2D208250 = DBC6 65B6 7083 1029 781E  3959 B62F DF1C 2D20 8250

[demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]

Previous thread: Dominios $40 por año | Resellers desde $16 | Hosting d by Mail Delivery System on Wednesday, January 13, 2010 - 6:47 pm. (1 message)

Next thread: Re: VLANs, OpenBSD, Cisco HP by James Peltier on Wednesday, January 13, 2010 - 11:33 pm. (5 messages)