NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
M4100 vlan routing help
I'm working on learning more about vlan and networking in general since these days I deal more with lawyers and auditors and miss the my tech roots. With that said I know that what I'm trying to do on my home network is way more complicated then a home network needs, but for learning why not :D
I recently bought a 12 port M4100 switch along with an EdgeRouter Lite and a couple of WiFi AP's. I'm trying to segment my home network into multiple vlans and right now I'm having trouble getting the first one up and running. I've created vlan 6 untagged on port 0/6 and enabled ip routing. When I plug one of my laptops into port 6 and try to get a DHCP address, I get an IP address from my main pool and not the pool for vlan 6. To simplify things I set a static ip address of 192.168.4.2 on the laptop and at that point I can ping the switch at 192.168.4.1, but I can't ping the router at 192.168.0.1. Doing a tracert shows the first hop to 192.168.4.1 and then nothing.
Can anyone here give me a hand in understanding what I haven't configured?
!Current Configuration:
!
!System Description "M4100-D12G ProSafe 12-port Gigabit L2+ Intelligent Edge Desktop Managed Switch, 10.0.1.28, B1.0.1.0"
!System Software Version "10.0.1.28"
!System Up Time "4 days 1 hrs 53 mins 40 secs"
!Additional Packages QOS,IPv6 Management,Routing
!Current SNTP Synchronized Time: SNTP Last Attempt Status Is Not Successful
!
enable password MYPASSWORD encrypted
network protocol none
network parms 169.254.100.100 255.255.0.0 0.0.0.0
vlan database
vlan 6
vlan name 6 "roku"
vlan routing 1 1
vlan routing 6 2
vlan association subnet 192.168.4.0 255.255.255.0 6
exit
ip ssh server enable
ip ssh protocol 2
configure
time-range
ip name server 192.168.0.1
ip routing
ip route 0.0.0.0 0.0.0.0 192.168.0.1
username "admin" password MYPASSWORD2 level 15 encrypted
line console
exit
line telnet
exit
line ssh
exit
snmp-server sysname "core_switch"
snmp-server location "Basement"
snmp-server contact "Me"
!
dhcp l2relay
dhcp l2relay vlan 6
dhcp l2relay circuit-id vlan 6
dhcp l2relay remote-id rem_id vlan 6
interface 0/6
description 'Roku'
vlan pvid 6
vlan participation auto 1
vlan participation include 6
exit
interface vlan 1
routing
ip address 192.168.0.12 255.255.255.0
exit
interface vlan 6
routing
ip address 192.168.4.1 255.255.255.0
exit
exit
5 Replies
- I'm not that familiar with the M4100's but I don't see anything in that config setting out the DHCP server lease pools, I do however, see entries that relate to DHCP relay, so I'm going to guess that you are running the DHCP server elsewhere. If that is correct, does the DHCP server support multiple lease pools, and has it been correctly configured - if that has been done, I suggest taking a second look at the DHCP relay setup, because I would expect to see the ip address of the DHCP server specified, and it is not there.
- The EdgeRouter Lite appears to be configured correctly for the planned DHCP pools. I'm trying to do this as a level 2 relay, but maybe I need to do level 3 instead.
But the more fundamental issue is that the routing between vlan 6 and 1 isn't working. I expected once I put a static IP into the laptop to be able to ping 192.168.0.1 or any device on the 192.168.0.0/24 network. Instead it appears that routing isn't happening in the switch. - Be very careful with your expectations ... If I make the reasonable assumption that the devices on the 192.168.0.0/24 network are getting their ip addresses from the edge router, they most likely have the edge router as their default gateway, in which case they will send the ping reply to the edge router, which will pass it on to it's default gateway, which is most likely the ISP router. To correct this you need to configure a static route in that edge router so that it passes the 192.168.4.0/24 traffic back to the switch at 192.168.0.12 - alternatively, you can manually create a route in a PC's routing table pointing traffic for the 192.168.4.0/24 network to 192.168.0.12.
- I had time last night to work on the switch and made progress. It turned out to be pretty subtle in my mind. I had assigned the 192.168.4.1 IP to the port 0/6 when I first set things up. I re-did the setup and instead assigned the IP to the vlan 6 interface. Now I can connect to the switch on 192.168.0.12 from the laptop on vlan 6 with an ip of 192.168.4.2. Things still aren't totally working at that point because I can't access the router or internet at 192.168.0.1, but progress.
- See my second paragraph in post #4 - you should be able to access the router once that has been done - however, internet access may not be available - that will depend on whether the edge router can NAT networks other than the directly attached one. I have done what you're attempting with an FVS336G as the edge router, so I know it can be done.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
