nf18acv - LAN VLAN Setting - is this actually useful?

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › nf18acv - LAN VLAN Setting - is this actually useful?

openmedia

3449 posts

Uber Geek
+1 received by user: 877

Trusted

#251482 27-Jun-2019 12:26

Got a spare one of these knocking around at the moment I I wanted to try and isolate a network for some testing.

My R7000 running Tomato allows for tagged and untagged networks to run on the same ethernet ports.

The nf18acv has a "Lan VLAN Setting" option but there are no details or instructions on what it can actually do. Has anyone had a play with this?

My ideal would be a

tagged VLAN X from R7000 -> NF18ACV port 4.
Normal LAN untagged R7000 -> NF18ACV port 4.
Norma LAN on Port 1 of NF18ACV
Untagged access to VLAN X on ports 2 + 3 of NF18ACV

This would allow me to use the R7000 to provide all DNS and DHCP services regardless of endpoint network. It can also handle any internetwork routing.

I have a feeling my best option is to run the nf18acv as its own network with its own IP address range rather than having it run as a VLAN.

R7000 -> NF18ACV WAN Port
local private LAN X DHCP on NF18ACV
Ports 1-4 on NF18ACV on private LAN X

Damn I wish there was a ddwrt/openwrt build for the NF18ACV

Any thoughts that don't require additional hardware.

Generally known online as OpenMedia, now working for Red Hat APAC as a Technology Evangelist and Portfolio Architect. Still playing with MythTV and digital media on the side.

openmedia

3449 posts

Uber Geek
+1 received by user: 877

Trusted

#2266161 28-Jun-2019 11:18

So I'm instead trying with the NF4V older model

One thought was to accept a tagged VLAN on the WAN port and then have all of my private LAN clients on the LAN ports.

In theory it is setup correctly, but in practise only DHCP traffic appears to be making it over the VLAN.

R7000 -> tagged VLAN 4 -> NF4V WAN Port VLAN ID 4 -> LAN ports -> Client

Client DHCP requests are being serviced by the R7000, but I can't ping the NF4v or the client.

In full bridge mode the NF4V should have no firewall, and the Client can see the NF4V.

Any thoughts /ideas?

Generally known online as OpenMedia, now working for Red Hat APAC as a Technology Evangelist and Portfolio Architect. Still playing with MythTV and digital media on the side.

nitro

756 posts

Ultimate Geek
+1 received by user: 335

#2266214 28-Jun-2019 12:12

router (default firewall setting) normally block icmp, etc. from the WAN port.

some allow the option to let them through, e.g. DMZ, port forwarding...