lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-Id: <201504072150.40209.wrosner@tirnet.de>
Date:	Tue, 7 Apr 2015 20:50:37 +0100
From:	Wolfgang Rosner <wrosner@...net.de>
To:	netdev@...r.kernel.org
Subject: teql and vlan not compatible?

Hello,

are teql and vlan mutually exclusive?

I've done some tests the last days that drove me crazy, until I found an an 
old (2003) message on the linux.drivers.vlan list :

"vlan + teql qdisc problem"

http://osdir.com/ml/linux.drivers.vlan/2003-02/msg00050.html

<quote>
tc qdisc add dev vlan0003 root teql0
then i can no longer ping 10.0.0.2 from 10.0.0.1.
The moment I add qdisc it stop working.
When I remove qdisc - I can ping again.
</quote>


While my setup is more complicated, the problem is the same.
I cannot even see any arp requests on the wireshark after I have a teql'd 
interface on a vlan like this
"tc qdisc replace dev eth9.42 root teql0"

Is this a fundamental impossibility or is there simply some secret magic I 
just haven't found documented?
Above thread is the only google hit for "teql & vlan"

Thanks for any hint!



Wolfgang Rosner
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ