On Thu, Dec 1, 2016 at 5:34 PM, David Lang <[email protected]> wrote:
>
> On Thu, 1 Dec 2016, Mauricio Tavares wrote:
>
>>>
>>> When I connect to my switch, the switch claims it can see traffic on
>>> vlan 2 at that port but nothing on vlan 3. What kind of traffic?
>
>
> remember that it will only send traffic out after it resolves the IP to a mac
> address. so on VLAN 3 it may very well be that the only thing that is going
> out is the ARP traffic.
>
I see what you mean: the switch will only know there is a
certain MAC associated with the device in that port if someone asks
for who owns that IP.
> what do you have hooked up to port 3? is it setup to handle vlan tagged
> traffic? or should you have defined vlan3 ports to be "3 5t" instead of "3t
> 5t"?
>
By design (requirements) all routed traffic in any of the 4
switch ports configured as 802.1q trunks is tagged (the devices
attached to the other 3 ports seem to be communicating fine). No
default vlans have been set. Only untagged traffic is on switch ports
that are configured to connect to just one vlan; which is similar to
how I configured the vlan2 ports in the openwrt router ("0 1 2 3t
5t").
> do a tcpdump on eth0.3, I'll bet that all you are seeing is ARP traffic.
>
I just connected my laptop to the router port 3 (yanked cable
from switch and connected to laptop) and ran wireshark. On the 200
packets it capture there was not a single bit of ARP traffic from
vlan3. vlan2 traffic (ARP, DHCP requests, etc) was there and properly
identified as 802.1q format.
> David Lang
> _______________________________________________
> openwrt-users mailing list
> [email protected]
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
