Bug 624752 - Enhancement Request: add VLAN tagging to anaconda
Summary: Enhancement Request: add VLAN tagging to anaconda
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 757911 815081 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-17 16:27 UTC by Randy Goddard
Modified: 2013-06-14 13:46 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-06-14 13:46:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Randy Goddard 2010-08-17 16:27:02 UTC
Please reference https://bugzilla.redhat.com/show_bug.cgi?id=431915 comment #5 for details.

Description of problem:
In order to network install Fedora or RHEL onto a blade whose NICs are configured with a native non-routeable network, but a routeable VLAN, the VLAN tagging must be added to the initial kickstart file.  However, while the 8021q.ko module has been added to the initrd, anaconda and pykickstart still don't utilize the 'vlanid' parameter.  Could we please add this?

Additional info:
The initial kickstart (and subsequent final ks) would include something like:
label newdiz
  kernel vmlinuz
  append ks=http://rhelinstall.obfuscated.org/server/software/os/linux/rhel5.5/64bitks_newdiz.cfg initrd=initrd.img latecfload noipv6 ip=192.168.48.17 netmask=255.255.255.0 gateway=192.168.48.1 dns=192.168.160.160 vlanid=848

Comment 1 Manuel Faux 2010-08-19 16:37:54 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Radek Vykydal 2011-11-29 10:01:29 UTC
*** Bug 757911 has been marked as a duplicate of this bug. ***

Comment 3 Dan Winship 2012-04-23 14:36:58 UTC
*** Bug 815081 has been marked as a duplicate of this bug. ***

Comment 4 Radek Vykydal 2013-06-14 13:46:47 UTC
Support for vlan has been added to F19.


Note You need to log in before you can comment on or make changes to this bug.