VLAN on TP Link smart Switch

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › VLAN on TP Link smart Switch - and Hyper V

davidcole

6099 posts

Uber Geek
+1 received by user: 1465

Trusted

#217737 10-Jul-2017 18:02

So I'm trying to use a port of my TP Link SG1024DE to be on a lan side of my NVR. This nvr sticks the cameras on a 192.168.20.x network. My Regular network is 192.168.10.

On the switch, 1 of the options I have are a port based VLAN. Which I put port 15 into vlan 20.

Then I went only my Hyper-V management and on one of my VMs I changed it network settings to use VLAN ID 20. Then in the guest I manually set the network to 192.168.20.100, but no joy.

Should this work? I've done this sort of thing on my USG iwth my guest network which has a vlan.

I can also create a 802.1Q VLAN - and I tried that. As tagged and untagged. Still nothing.

Is there something I might need to do on the lan side of the NVR? to get it to accept the vlan 20?

Previously known as psycik

Home Assistant: Gigabyte AMD A8 Brix, Home Assistant with Aeotech ZWave Controller, Raspberry PI, Wemos D1 Mini, Zwave, Shelly Humidity and Temperature sensors
Media:Chromecast v2, ATV4 4k, ATV4, HDHomeRun Dual
Server Host Plex Server 3x3TB, 4x4TB using MergerFS, Samsung 850 evo 512 GB SSD, Proxmox Server with 1xW10, 2xUbuntu 22.04 LTS, Backblaze Backups, usenetprime.com fastmail.com Sharesies Trakt.TV Sharesight

richms

29098 posts

Uber Geek
+1 received by user: 10208

Trusted

Lifetime subscriber

#1819061 10-Jul-2017 19:06

The nvr will probably not support anything to do with tagging.

I had mine run into a second port of the switch from the camera side (hikvision with an inbuilt 8 port POE switch) and on my tenda POE/smart switches gave that port a default vlan of 10 - that means it would tag anything untagged with 10. It was also only selected with vlan 10, so the default vlan of 1 was not presented to that port.

On my desktop PC I used the realtek software to enable vlan, and made one for 10. I also put TCPIP back enabled on the physical adapter. It "helpfully" turned that off for me. Put that port onto both 1 and 10 vlans and it all worked fine. PC on an IP in the NVR range, and was able to directly hit my non hikvision cameras to configure them.

Richard rich.ms

davidcole

6099 posts

Uber Geek
+1 received by user: 1465

Trusted

#1819064 10-Jul-2017 19:08

So in theory what I'm doing should work if I knew what vlan the NVR would have natively?

Should I use the port based?

richms

29098 posts

Uber Geek
+1 received by user: 10208

Trusted

Lifetime subscriber

#1819070 10-Jul-2017 19:12

The nvr has no native vlan, it has 2 sets of untagged ports, as seperate interfaces to the network stack inside it. It may internally use vlans to deliver both interfaces to the CPU but you cannot get to those vlans at all. Real shame since it means I wasted 2 ports on my switch for it to get out to some other cameras that I couldnt run straight to the NVR.

What you are doing should work fine. plug the cable going to the NVR into a spare router or something else and see if the computer can see it, if it can then your switch config is all good.

Richard rich.ms

vulcannz

436 posts

Ultimate Geek
+1 received by user: 136
Inactive user

#1819394 11-Jul-2017 09:55

For the NVR and cameras connect them to ports configured as untagged VLAN 20.

For the VM define the port as tagged VLAN 20.

Also for that switch use the software utility to configure it... the web gui is rubbish/flakey/buggy.

davidcole

6099 posts

Uber Geek
+1 received by user: 1465

Trusted

#1819408 11-Jul-2017 10:09

vulcannz:

For the NVR and cameras connect them to ports configured as untagged VLAN 20.

For the VM define the port as tagged VLAN 20.

Also for that switch use the software utility to configure it... the web gui is rubbish/flakey/buggy.

Cool I'll try that tonight. Not sure if I tried that particular combination. I know I tried port based (to port 15). And I know I tried tagged. Not sure about untagged.