Bug 359643

Summary:	Requesting VLAN Support in yast2 lan Module
Product:	[openSUSE] openSUSE 11.0	Reporter:	Michael Glenn <mglenn>
Component:	YaST2	Assignee:	Michal Zugec <mzugec>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None	CC:	mglenn, mt
Version:	Alpha 1
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:
Bug Blocks:	359657

Description Michael Glenn 2008-02-07 16:56:27 UTC

Hi.

We often need to interface tagged VLANs to our Admin clients and Linux-based servers. Currently, the only way to do this is to hack the correct settings by hand from within the /etc/sysconfig/network folder.

We'd really like to have a method within YaST2-LAN that would allow us to configure VLAN connections and attach them to the correct network interfaces without having to meddle inside network config files. AutoYaST compatibility would be a big plus.

Thanks for reading.


Ref: http://www.novell.com/coolsolutions/feature/19152.html

Comment 1 Michal Zugec 2008-02-08 07:56:16 UTC

Hello,
this is already implemented (and works also with autoYaST as well):
http://en.opensuse.org/YaST/Network/11.0-new_features
I'll put some screenshots there today

Comment 2 Michael Glenn 2008-02-08 16:18:11 UTC

This looks really good. Can this support untagged frames as well as tagged on the same interface? 

I can't wait to see this in the SLES code base; it'll make life down on the server farm just that much easier.

:)

Comment 3 Michal Zugec 2008-02-08 16:21:45 UTC

untagged configuration

Comment 4 Michal Zugec 2008-02-08 16:23:56 UTC

>>Can this support untagged frames as well as tagged on the same interface
I don't think so

Marius, how to configure vlan for untagged frames?

>> I can't wait to see this in the SLES code base; it'll make life down on the server farm just that much easier.

Included also in SLES10-SP2

Comment 5 Marius Tomaschewski 2008-02-11 09:20:47 UTC

The vlanXXX interface just causes adding of the VLAN ID XXX tag. You can
still use the original ethN interface (ETHERDEVICE) for untagged traffic.

Comment 6 Michael Glenn 2008-02-11 14:04:23 UTC

Yes, that tests in Alpha-1 just fine.

Thanks, guys; you just made my job just a bit easier.

Comment 7 Michal Zugec 2008-02-18 09:16:23 UTC

question answered