https://bugzilla.novell.com/show_bug.cgi?id=375834 User abittner@stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c7 Summary: ppp over vlan-tagged ethernet - occasional network startup order problems (rcnetwork script doesnt properly start ethernet, vlan and dsl0 in this order, but eth dsl0 (which then fails) then vlan) Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: abittner@stud.fh-heilbronn.de QAContact: qa@suse.de Found By: --- hello opensuse team, for a while now i have tried to find the reason of my networking problems on a vdsl2 line (germany, deutsche telekom vdsl2-based broadband consumer line). deutsche telekom provides a pppoe-based vdsl2 line. the only specialty and difference to other standard adsl/adsl2+ lines is the vlan-tag on the ethernet-interface of their line. the ethernet-device needs to set/use vlan-id #7 to communicate with their vdsl2 cpe (ethernet modem/bridge). everything else is standard pppoe. i used to have many older opensuse versions on normal adsl/adsl2+ lines with simple pppoe. everything worked fine. the dsl0 device was defined with yast2. fine so far. with the vdsl2 line of deutsche telekom i needed to create the textfile ifcfg-vlan7 in /etc/sysconfig/network/ eth2 is the pci ethernetcard which connects to the vdsl2 modem/bridge. # the content of ifcfg-vlan7 is: STARTMODE=hotplug ETHERDEVICE=eth2 IPADDR=10.168.2.2 NETMASK=255.255.255.0 #ifcfg-eth2 content is: BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='192.168.1.1/24' MTU='1500' NAME='Realtek RTL-8169 Gigabit Ethernet' NETMASK='255.255.255.0' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' UNIQUE='JNkJ.oxSyVMMObW1' USERCONTROL='no' _nm_name='bus-pci-0000:04:09.0' PREFIXLEN='' # the content of ifcfg-dsl0 is: BOOTPROTO='none' DEVICE='vlan7' MODEM_IP='10.0.0.138' NAME='DSL Connection' PPPD_OPTIONS='' PPPMODE='pppoe' PROVIDER='tonline-dsl' STARTMODE='hotplug' UDI='' USERCONTROL='yes' VPIVCI='' the problem is that during the bootup of this system many times the dsl0 device fails to start (rcnetwork status after login displays "unused") and somehow i figured it is because the system sometimes wants to start dsl0 too quickly or virtually at the same time as the vlan7 device, and sometimes the vlan7 device coming up after the dsl0. which fails ofcourse as dsl0 devices depends/uses the vlan7 device. can this be fixed in a simple and easy way? also: yast doesnt really offer to handle vlan devices at all properly, i needed to do manual editing/configuration of the ifcfg-vlanX file, and you cant select/create/handle vlan devices inside yast. generally: vlan devices can only be ontop of eth devices, and pppoe can only be ontop of eth devices as the name already suggests. as vlan only exists on top of ethernet devices (if im not mistaken), and no vlan can be on top of ppp or such devices, the order of device starting needs to be ethernet -> vlan -> xxx-over-ethernet to make any sense, as vlan is only some bits/bytes inside a slightly enhanced/modded ethernet-frame. as pppoe can be ontop of ethernet, and ethernet can be ethernet or vlan-tagged-ethernet so ppp should only brought up after all ethernet and vlan-tagged-ethernet devices have started themselves. i have slightly taken a look into the /sbin/rcnetwork script and found: ###################################################################### # Get interfaces to handle # # Seperate this interfaces into several sets, not all mutually exclisive; # none of them may contain lo, because it will always handled separately # # AVAILABLE_IFACES are all interfaces from /sys/class/net # these have to be shut down when stopping # # PHYSICAL_IFACES are interfaces to present physical devices, they will be # derived from AVAILABLE_IFACES # # DIALUP_IFACES are modemX, dslX, etc., they are derived from ifcfg-* files # # TUNNEL_IFACES are interfaces that do not fit into PHYSICAL and DIALUP and # are as well derived from ifcfg-* files # # PHYSICAL, DIALUP and TUNNEL are mutually exclusive. Their union contains # AVAILABLE and MANDATORY and all of them have to be set up when starting # # MANDATORY_IFACES these must be up and well configured for success # At first get DIALUP and TUNNEL while IFS=- read a b; do test -z "$b" && continue b=`type_filter $b` case "`get_iface_type_from_config $b`" in lo|eth|tr|wlan|irda|ip6tnl|mip6mnha) continue ;; *ppp|dsl|modem|isdn) DIALUP_IFACES="$DIALUP_IFACES $b" ;; vlan|bond|bridge|ipip|sit|gre) TUNNEL_IFACES="$TUNNEL_IFACES $b" ............................ im not a programmer or networking expert, but to my undersanding the vlan needs to be closer to ethernet and way before a ppp devices as ppp can be over/on ethernet...... maybe other scenarios should also be taken into account, i didnt think about bonding, bridging, gre and so forth...... thanks for a quick fix or hint how to make my vdsl2 startup to work more reliable and to properly bring up the interfaces that depend on each other. best regards. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.