

I fixed the typo on the FiOS router, thanks for the catch. I haven't looked into it deeply yet, but I doubt the Verizon router will do multiple DHCPs, but I could be surprised. I'll try the VLAN10 dhcp setup after I get the cross VLAN thing working, I agree that it's probably easier to do that part on the switch. Yes, the GUI forces you to reboot when switching from the default L2 mode to 元 and it wipes the config as well, so I did that first (the 2nd time around, heheh). Hopefully that covers everything I've done so far.I feel like I'm missing a simple piece of the puzzle but can't quite put my finger on it. scheduling and chart notes), so VLAN10 must access PCs on VLAN1. The Docs need to access shared drives on the Office PCs from the Scope PCs (i.e.The Docs need to access the Internet from the Scope PCs, so VLAN10 must get to the FIOS Router on VLAN1 and then out to the Internet.image files and notes), so VLAN1 must talk to VLAN10. The office needs to access shared drives on the Scope PCs from the Office PCs (i.e.The Vendor needs to access VLAN10 from the Internet to provide helpdesk support for the new Scope PCs (using their Teamview account, which will be installed on the Scope PCs).What IS a dealbreaker is not being able to reach the Internet from VLAN10 or not being able to pass info across the two VLANs. So, while that might be nice to figure out if I could DHCP addresses in the 192.168.4.x range on VLAN10, it's not a deal breaker unless for some reason the Cisco Collective deems it necessary :) Note: all DHCP addressing is being done from the FIOS router, and I suspect that it will only provide addressing to the 192.168.1.1 network that is the basic network, but that's okay as I plan to static IP the devices on VLAN10 anyway (as they are now). I can *Ping* VLAN10 (192.168.4.1) from the laptop on VLAN1, however, I can't ping the laptop on VLAN10.įrom the VLAN10 laptop, I can only ping VLAN10's IP, I can't reach anything outside of VLAN10, whether DNS or IP based (i.e.


My home network that I'm using for testing is a 192.168.1.1 subnet, so from the VLAN1 laptop I can reach everything (Internet and anything else) on the 192.168.1.x network. I have a laptop plugged into both VLAN1 and VLAN10 for testing, and the switch is trunked to my FIOS Router. (Note: This is on my router at home as I'm pre-testing this here). A route is set up on the FIOS Router to VLAN4 using VLAN1 as the Gateway.

#Verizon router removem vlan driver
They also have an isolated network for a few PCs serving medical scope imaging equipment that is the driver for the upgrade as the PC equipment/software is being upgraded and needs to be on the Internet for vendor remote support. Currently they have Verizon FIOS for Internet/Switching (FiOS G1100 Router), which serves the few office PCs and Printers via the onboard LAN jacks and a couple of D-link 5 port GB switches. I have an SG300-28PP I'm configuring to upgrade my wife's clinic's outdated network and am having some issues with getting my added VLAN to see anything outside of itself.
