"interface VLAN" on WAN/LAN3 port? What am i doing wrong?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

"interface VLAN" on WAN/LAN3 port? What am i doing wrong?

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
"interface VLAN" on WAN/LAN3 port? What am i doing wrong?
"interface VLAN" on WAN/LAN3 port? What am i doing wrong?
2021-03-10 15:28:56 - last edited 2021-03-10 15:30:18
Model: ER605 (TL-R605)  
Hardware Version:
Firmware Version:

Hi,

 

First of all, great product line up!

 

In this situation i use a R605 and TL1500G switch, both controlled by the software version of the Omada controller on a linux machine behind the switch.

The R605 is connected to the internet. The switch is connected to the R605.

 

Also, i have a client connected directly to the WAN/LAN3 port of the R605.

 

In this scenario, all clients get a IP in the range of 192.168.0.x.

(that is the range of the default LAN profile)

 

I would like to have the client connected to port 3 of the R605 get ip's in range of 192.168.20.x.

Creating a VLAN interface on the WAN/LAN3 port of the R605 i would expect to work.

Unfortunately, it does not.

 

I cán get this to work of i connect the client to one of the switches ports  (an not directly to the R605) and actively assign the profile to the port.

This however is not available for the R605.

 

I cán get this to work wihtout using the OMADA SDN controller and directly configure this in the R605.

And, if configured as above, the R605 is responding (also) on 192.168.20.1 (so that is expected)

 

Secondly, it seems i'm missing the mac-vlan options in the omada controller?

 

What am i doing wrong here?

 

Thanks.

 

 

  0      
  0      
#1
Options
5 Reply
Re:"interface VLAN" on WAN/LAN3 port? What am i doing wrong?
2021-03-10 16:40:09

@_user 

 

Interesting,

I just tried and I don't get IP ADD from new VLAN Interface but I am able to ping the new subnet gw....

 

@Fae Could you chek it, please?

Thanks

Best Regards

  0  
  0  
#2
Options
Re:"interface VLAN" on WAN/LAN3 port? What am i doing wrong?
2021-03-10 19:51:43

@_user 

 

I believe the ER605 is only capable of providing DHCP for one subnet. 

  0  
  0  
#3
Options
Re:"interface VLAN" on WAN/LAN3 port? What am i doing wrong?
2021-03-10 19:54:23 - last edited 2021-03-10 19:55:46

@1207 

 

No because with a single cable and Omada switch is possible create different VLAN interface with also multi dhcp server for the subnets.

 

Regards

  0  
  0  
#4
Options
Re:"interface VLAN" on WAN/LAN3 port? What am i doing wrong?
2021-03-10 20:28:09

@_user 

 

 

"I cán get this to work wihtout using the OMADA SDN controller and directly configure this in the R605.

And, if configured as above, the R605 is responding (also) on 192.168.20.1 (so that is expected)"

 

Are you saying you can configure the ER605 in stand-alone mode to DHCP on different subnets using the ports on the router?  It is my understanding the switch provides the DHCP function for the vlan subnet and the vlan clients need to be connected to the assigned switch port, not the router port. There doesn't seems to be anyway to assign router ports to vlans through Omada.  Maybe this can be resolved through a firmware update. Let's see what the experts say.

  0  
  0  
#5
Options
Re:"interface VLAN" on WAN/LAN3 port? What am i doing wrong?
2021-03-12 12:56:22

Thanks for the quick replies. Good to see an active forum. 

This line-up already has great potential!

 

@Emitplink correct, i'm able to ping the R605 on both the subnets under 192.168.20.1 and 192.168.0.1 (as expected) from behind the switch.

 

If the client behind the R605 is set to a fixed ip in the .20 subnet, it cannot ping the R605 0n 20.1 

If set to fixed (or DHCP) in the .0 range, it can do both.

 

I'll post my non-SDN config.

  0  
  0  
#6
Options