Re: Still missing something on vlan - F19

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09/09/2014 02:11 PM, Robert Moskowitz issued this missive:
I am working on a system that has a stable MACaddr (an issue with many
arm SOC), so I don't suspect that as an issue.

cat /etc/udev/rules.d/70-persistent-net.rules

# Added by 'write_udev' for detected device 'eth0'.
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="02:c4:03:82:c1:53", NAME="eth0"

cat /etc/sysconfig/network

NETWORKING=yes
HOSTNAME=test.htt-consult.com

cat /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE="eth0"
BOOTPROTO="none"
ONBOOT="yes"
TYPE="Ethernet"
NAME="System eth0"

cat /etc/sysconfig/network-scripts/ifcfg-eth0.16

DEVICE="eth0.16"
BOOTPROTO="dhcp"
vlan="yes"
ONBOOT="yes"
TYPE="Ethernet"
NAME="System eth0.16"
HOSTNAME="test.htt-consult.com"
IPV6INIT="yes"

ip addr show

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
     inet 127.0.0.1/8 scope host lo
     inet6 ::1/128 scope host
        valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UNKNOWN qlen 1000
     link/ether 02:c4:03:82:c1:53 brd ff:ff:ff:ff:ff:ff
     inet6 fe80::c4:3ff:fe82:c153/64 scope link
        valid_lft forever preferred_lft forever

Note I have set up the switch port so that ALL my vlans are accessable
from this port as 'tagged'.  There are no 'untagged'. VALN 16 is one of
the available labels.  I had earlier tried this with only VALN 16
available, and that did not work; I enabled all vlans then.  None of the
vlans are untagged, so nothing is reachable the eth0.

It bothers me that eth0.16 does not even show in the 'ip addr show'
command output.

Have you verified that the driver for that NIC supports VLAN tagging?
Some don't.

Have you tried a manual config, e.g. "vconfig add eth0 16"? If that
works, could you add

	KERNEL="eth*"

to the line in your /etc/udev/rules.d/70-persistent-net.rules file and
see if that helps? It may be that the kernel isn't recognizing the
device's name.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-           Lottery: A tax on people who are bad at math.            -
----------------------------------------------------------------------
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org




[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux