Welcome to TP-LINK Tech Support Forum
+ Reply to Thread
Results 1 to 6 of 6
  1. #1

    Question Mac vlan t2600g-28ts

    Model :

    Hardware Version :

    Firmware Version :

    ISP : [/COLOR]

    I've got a T2600G-28TS when doing MAC VLAN it requires me to set the port to GENERAL, .. rather then TRUNK but when I do that it seems all traffic on that port becomes untagged traffic.

    This is especially vissible on IPv6 part of the network because when that happens, my clients receive a IPv6 from every vlan that is active on that port.

  2. #2
    Members TPTHZ is on a distinguished road
    Join Date
    Aug 2017
    Posts
    150
    Quote Originally Posted by Ofloo View Post
    Model :

    Hardware Version :

    Firmware Version :

    ISP : [/COLOR]

    I've got a T2600G-28TS when doing MAC VLAN it requires me to set the port to GENERAL, .. rather then TRUNK but when I do that it seems all traffic on that port becomes untagged traffic.

    This is especially vissible on IPv6 part of the network because when that happens, my clients receive a IPv6 from every vlan that is active on that port.
    there are one configuration guide maybe useful for you.
    http://static.tp-link.com/res/down/d...urationId=2985

  3. #3
    I've already followed that guide yet it doesn't work as it should.

    16:27:11.325339 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:14.363009 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:14.364037 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:17.402853 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:17.403944 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:20.448829 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:20.450170 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:23.493161 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:23.494050 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:26.532065 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:26.532529 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:29.574677 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:29.575140 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:32.616972 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:32.617445 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:36.541143 ARP, Request who-has 10.13.30.10 tell 10.13.30.20, length 46
    16:27:37.540952 ARP, Request who-has 10.13.30.10 tell 10.13.30.20, length 46
    16:27:38.540875 ARP, Request who-has 10.13.30.10 tell 10.13.30.20, length 46
    16:27:39.551079 ARP, Request who-has 10.13.30.10 tell 10.13.30.20, length 46
    16:27:40.550884 ARP, Request who-has 10.13.30.10 tell 10.13.30.20, length 46
    10.13.30.20 is the fall back IPv4 basically this means it didn't set the IPv4, which isn't reachable either btw

    the vlan i'm refering to is vlan 300 port 4 is in GENERAL mode

    #sh vlan id 300
    VLAN Name Status Ports
    ----- -------------------- --------- ----------------------------------------
    300 VIDEO active Gi1/0/4, Gi1/0/8, Gi1/0/9, Gi1/0/10,
    Gi1/0/25, Gi1/0/26, Gi1/0/27, Gi1/0/28,
    Po1, Po2, Po3, Po4
    #sh mac-vlan int
    Port STATUS
    ---- -------
    Gi1/0/1 Disable
    Gi1/0/2 Disable
    Gi1/0/3 Disable
    Gi1/0/4 Enable
    ....
    #sh mac-vlan all
    MAC-Addr Name VLAN-ID
    --------------------- ------------------ -------
    04:186:x:x:x NAME 300

  4. #4
    I did follow those instructions yet it's not working as expected.

  5. #5
    I did follow those instructions yet it's not working as expected.

    Code:
    16:26:26.210111 IP 192.168.1.31.57582 > 10.13.30.10.7442: Flags [S], seq 3503129506, win 14600, options [mss 1460,sackOK,TS val 423960 ecr 0,nop,wscale 3], length 0
    16:26:29.216216 IP 192.168.1.31.57582 > 10.13.30.10.7442: Flags [S], seq 3503129506, win 14600, options [mss 1460,sackOK,TS val 424261 ecr 0,nop,wscale 3], length 0
    16:27:08.263672 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:08.264621 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:11.323519 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:11.325339 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:14.363009 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:14.364037 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:17.402853 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:17.403944 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:20.448829 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:20.450170 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:23.493161 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:23.494050 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:26.532065 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:26.532529 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:29.574677 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:29.575140 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:32.616972 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 04:18:d6:x:x:x, length 370
    16:27:32.617445 IP 10.13.30.1.67 > 10.13.30.21.68: BOOTP/DHCP, Reply, length 300
    16:27:36.541143 ARP, Request who-has 10.13.30.10 tell 10.13.30.20, length 46
    16:27:37.540952 ARP, Request who-has 10.13.30.10 tell 10.13.30.20, length 46
    16:27:38.540875 ARP, Request who-has 10.13.30.10 tell 10.13.30.20, length 46
    16:27:39.551079 ARP, Request who-has 10.13.30.10 tell 10.13.30.20, length 46
    16:27:40.550884 ARP, Request who-has 10.13.30.10 tell 10.13.30.20, length 46
    16:27:41.550838 ARP, Request who-has 10.13.30.10 tell 10.13.30.20, length 46
    16:27:45.620393 ARP, Request who-has 10.13.30.10 tell 10.13.30.20, length 46
    16:27:46.620285 ARP, Request who-has 10.13.30.10 tell 10.13.30.20, length 46
    Fall back IPv4 is 10.13.30.20 and even so it's not reachable. Some how the traffic is broken, .. because the dhcp works to a certain point, since it's providing the right IPv4 but then the client doesn't set it.

  6. #6
    For some reason it worked again after I changed the port (4) from GENERAL to TRUNK and right after that I changed it back to GENERAL and now it works?


 

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Copyright 1996-2018 TP-LINK Technologies Co., Ltd. All rights reserved.