Bug 83792 - initscripts-7.06 vlan 802.1q interfaces IP settings problem
initscripts-7.06 vlan 802.1q interfaces IP settings problem
Status: CLOSED NOTABUG
Product: Red Hat Raw Hide
Classification: Retired
Component: initscripts (Show other bugs)
1.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
http://www.ac.tuiasi.ro/mituc/devel/i...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-08 15:04 EST by Tarhon-Onu Victor
Modified: 2014-03-16 22:34 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-02-08 17:12:47 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
802.1Q VLAN subinterfaces support (5.56 KB, patch)
2003-02-08 15:10 EST, Tarhon-Onu Victor
no flags Details | Diff

  None (edit)
Description Tarhon-Onu Victor 2003-02-08 15:04:20 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021231

Description of problem:
8021Q VLAN subinterfaces __should__ not have 0.0.0.0/32 ip address set!!!

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Just try using vlan subinterfaces as implemented in initscripts-7.06-1 on a
router running dynamic routing protocols reflecting or (re)distributing default
route.
2.
3.
    

Additional info:

Aditionaly think that trunk ports are in a native vlan (default 1) and frames
are not tagged whithin that vlan!
Many managed switches (3Com, allied telesyn, maybe a lot other) do not support
other management vlan but vlan 1. Maybe you will want to manage those switches
from network, not only using a serial port - that's an example.
Having 0.0.0.0/32 ip set on a interface will cause dynamic routing daemons to
redistribute this as somekind of default route if redistribute static option is
enabled (bgpd, ospfd, ripd, gated, etc).

+++802.1q vlan subinterfaces should be able to have aliases (e.g.: eth7.901:0).

A realy working 802.1Q VLAN interfaces support patch (last applied on
initscripts-7.01, I'll prepare one for 7.06-1 as soon I'l rebuild glib2 on my
system, it seems I don't have it static as required) can be found at
http://www.ac.tuiasi.ro/mituc/devel/initscripts/initscripts-vlans-1.3.2.patch .
Comment 1 Tarhon-Onu Victor 2003-02-08 15:10:06 EST
Created attachment 89949 [details]
802.1Q VLAN subinterfaces support

It should require some more checks to tell more about what's happening when an
error occurs, but it works fine (tested in production for almost 6 months).
Comment 2 Tarhon-Onu Victor 2003-02-08 17:12:47 EST
Well, I took a closer look and it's seems I was terrible wrong about this.
ip add add 0.0.0.0/32 dev device does nothing, anyway it should not be there, ip
-o link set dev ${PHYSDEV} up it's enough.
Moreover vlan interfaces are now treated as normal interfaces so aliases are
added if any.

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