The Issue Connecting to the RB250 WebGui
I have a RB250 connected to E4. When it had the IP address 192.168.1.4 I can access it’s web interface. When I assign it (the RB250) 192.168.0.2 I can’t reach it (The issue is only the web interface all devices connected to the switch are connecting to the network correctly). The only way I can reach it on 192.168.0.2 is if I am directly connected to the RB250. If I plug a PC in E3 of the 750GL I get a 192.168.0.x address but can’t reach the switches web GUI (only when it has the 192.168.0.x IP if it has 192.168.1.x it can reach the GUI). (I have not tried to come in direct through E5 as a wireless distribution system is setup on that port, I have attempted through the wireless and once again it only works on 192.168.1.x but not on 192.168.0.x)
The RB250 port (connected to the router) is set to:
Vlan Enabled (I have tried Optional as well)
Native 1
Force=No
Add if missing on Egress
On the switches system page accessible by Vlan is blank.
Why can’t the switches web gui be reached on 192.168.0.x??? It makes no sense to me.
I was just emailed this explanation… Someone please confirm.
When the RB250 is on 192.168.1.x WEB GUI Works
When the RB250 in on 192.168.0.x WEB GUI Fails
Request when it works
PC 192.168.0.100 to 192.168.1.4
Router InterVlan routes to Vlan 100
Vlan 100 packet enters the switch
VLan 100 packet leaves the switch
ROuter InterVlan routes back to NO VLAN
Success
Request when it fails
PC 192.168.0.100 to 192.168.0.2
Router forward the packet to the switch
Switch take the untagged packet and names it Vlan 1
Switch send packet back and tags it per the add tag if missing rule
Router catches the Vlan 1 tagged packet and drops it as their is no VLAN 1
Fail
Is this correct? Why would the R250 tag its native Vlan?
Ah figures… Now I see they are having the same issue. I assumed the issue was the router not the switch that is why I did not look into it in that forum.
I wish I would create a Vlan for 192.168.0.0/24 but I can’t… I am using some devices Ubiquiti Unifi that require the management traffic to be untagged. I will just have to use a switch that works as expected. I have never heard of a managed switch that tags the native vlan by default.