This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Second VLAN not working
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Problem:
I completly wiped every device and even the whole site. So this is on an absolute fresh setup and default settings out of the box.
When Creating a fresh VLAN (type: interface in the UI) clients on this vlan get the correct ip, default gw and dns. but cant reach anything .. not even the default gw.
My Setup
- OC200 v1 - Firmware 5.13.30.20
- ER605 v2.0 - Firmware 2.2.3
- TL-SG2428P v4.0 - Firmware v4.0.8
- EAP615-Wall(EU) v1.0 - Firmware 1.0.12
- 2x EAP653(EU) v1.0 - Firmware 1.0.12
I have two VLANs as follows:
(CLI output just for the forum. I'm configuring only via SDN web ui )
----snip----
#show interface vlan 1
vlan1 ports:2 3 4 5
Vlan type..................lan
Routing Interface Status...UP
Proto......................static
Dhcp mode..................dhcp_server
Dhcp enable................on
Primary IP address:........192.168.0.1/255.255.255.0
Dhcp start.................192.168.0.50
Dhcp end...................192.168.0.254
Dhcp release time..........120min
Dhcp relay enable..........off
Macaddr....................5C-62-8B-30-AF-B4
Mtu........................1500
#show interface vlan 10
vlan10 ports:2t 3t 4t 5t
Vlan type..................lan
Routing Interface Status...UP
Proto......................static
Dhcp mode..................dhcp_server
Dhcp enable................on
Primary IP address:........10.0.0.1/255.255.255.0
Dhcp start.................10.0.0.10
Dhcp end...................10.0.0.254
Dhcp release time..........120min
Dhcp relay enable..........off
Macaddr....................5C-62-8B-30-AF-B4
Mtu........................1500
----snap----
I have configured a switch port only with VLAN10:
----snip---- TL-SG2428P#show running-config interface gigabitEthernet 1/0/16 !TL-SG2428P interface gigabitEthernet 1/0/16 switchport general allowed vlan 10 untagged switchport pvid 10 no switchport general allowed vlan 1 lldp med-status # ----snap----
- When I now connect a wired client to port 1/0/16, it successfully obtains the IP address 10.0.0.10.
- Sometimes the client fails to receive an ip at all. seems kinda random
- However, the client CANNOT (!) reach its advertised default GW 10.0.0.1 via ICMP ping. No network connection is possible at all.
- A client from VLAN1, on the other hand, can reach the IP 10.0.0.1 via ICMP ping.
Screenshots :
These are the routes which are created automatically. is route number 5 correct? Thought that the nexthop should be 10.0.0.1/24 instead.
Am i missing something?
MaxPowers_ wrote
Problem:
I completly wiped every device and even the whole site. So this is on an absolute fresh setup and default settings out of the box.
When Creating a fresh VLAN (type: interface in the UI) clients on this vlan get the correct ip, default gw and dns. but cant reach anything .. not even the default gw.
My Setup
- OC200 v1 - Firmware 5.13.30.20
- ER605 v2.0 - Firmware 2.2.3
- TL-SG2428P v4.0 - Firmware v4.0.8
- EAP615-Wall(EU) v1.0 - Firmware 1.0.12
- 2x EAP653(EU) v1.0 - Firmware 1.0.12
I have two VLANs as follows:
(CLI output just for the forum. I'm configuring only via SDN web ui )
----snip---- #show interface vlan 1 vlan1 ports:2 3 4 5 Vlan type..................lan Routing Interface Status...UP Proto......................static Dhcp mode..................dhcp_server Dhcp enable................on Primary IP address:........192.168.0.1/255.255.255.0 Dhcp start.................192.168.0.50 Dhcp end...................192.168.0.254 Dhcp release time..........120min Dhcp relay enable..........off Macaddr....................5C-62-8B-30-AF-B4 Mtu........................1500 #show interface vlan 10 vlan10 ports:2t 3t 4t 5t Vlan type..................lan Routing Interface Status...UP Proto......................static Dhcp mode..................dhcp_server Dhcp enable................on Primary IP address:........10.0.0.1/255.255.255.0 Dhcp start.................10.0.0.10 Dhcp end...................10.0.0.254 Dhcp release time..........120min Dhcp relay enable..........off Macaddr....................5C-62-8B-30-AF-B4 Mtu........................1500 ----snap----
I have configured a switch port only with VLAN10:
----snip---- TL-SG2428P#show running-config interface gigabitEthernet 1/0/16 !TL-SG2428P interface gigabitEthernet 1/0/16 switchport general allowed vlan 10 untagged switchport pvid 10 no switchport general allowed vlan 1 lldp med-status # ----snap----
- When I now connect a wired client to port 1/0/16, it successfully obtains the IP address 10.0.0.10.
- Sometimes the client fails to receive an ip at all. seems kinda random
- However, the client CANNOT (!) reach its advertised default GW 10.0.0.1 via ICMP ping. No network connection is possible at all.
- A client from VLAN1, on the other hand, can reach the IP 10.0.0.1 via ICMP ping.
Screenshots :
These are the routes which are created automatically. is route number 5 correct? Thought that the nexthop should be 10.0.0.1/24 instead.
Am i missing something?
Hi @MaxPowers_
As you are using the controller to configure the profile, could you please share the screenshots about the VLAN interface setting, and the page of port settings on your switch?
The key point is to confirm the port setting on the switch, including the port which is connecting to the gateway, and the port you used to test.
@Hank21
Hi Hank, thanks for your reply. Really appreaciate you looking into this. I meanwhile changed the VLan settings.. its now 1337 .. but basically the same.
VLAN1 Interface Config
VLAN1337 Interface Config
Port Profile VLAN1
Port Profile VLAN1337
Port Profile ALL
Switchport 16 Config
(from Devices -> Switch -> Ports)
Switchport Config Overview all
(from Insights-> Switch Status)
Here I notice that, in contrast to the config above, the profile is labeled "others" instead of "debug"
but maybe this is only due to the insights formatting. When checking on the CLI the port profile looks good doesnt it?
TL-SG2428P#show running-config interface gigabitEthernet 1/0/16 !TL-SG2428P interface gigabitEthernet 1/0/16 switchport general allowed vlan 1337 untagged switchport pvid 1337 no switchport general allowed vlan 1 lldp med-status # |
Hello Hank,
i've tried 2 Linux and 2 Windows 10 Machines.
Only 1 Windows Machine does get an ip adress at all. (said one who can't ping the GW). The three other machines fail to get a DHCP IP at the first place.
In addition i've added a wifi ssd with the corresponding VLAN1337 set. I wasn't able to connect a single wifi client. They all couldnt get an IP adress.
Seems more of an DHCP issue now doesnt it?
Wireless Network Config
Or is there maybe something wrong with these auto generated static routes?
Switch Routes
Gateway Routes
What wonders me the most is that I have reset the complete site and all clients and have rebuilt from scratch. And the official tutorial with 'PE_Departments' already doesnt work.
@Hank21
Based on your recommendation i startet a little sheet to test the various port-protfile-combinations. The test scenario looked as following for each port:
- physically connect to the network port
- if necessary "ipconfig /renew" on client
- ping 8.8.8.8 and default gateway
- "ipconfig /release" on client
And yes - now it works. didnt change anything .. except for back and forth switching the port profiles. Like many times before. Even wifi connect now works instantly. I dont get it.
The whole thing didn't seem very stable or trustworthy to me. So i created a new (third) random VLAN 500. And yes.the new VLAN doesnt work. I dont get an ip via DHCP.
Then i wanted to try the router LAN 1 / 2 Port. There i noticed that the new VLAN (500) is not available to choose from.
According to "Application Results -> LAN Network" the new/3rd VLAN was added correctly tho.
Long story short .. newly created vlans still not work right out of the box. Is omada buggy / broken? That can't really be an exotic combination of hardware and requirement on my part. So in the sense that the problem should occur much more often with people ... so out of the box.