- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: 4109GL VLAN setup
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2009 07:49 AM
тАО03-12-2009 07:49 AM
When I try to add VLANS into the picture I get the feeling I am missing something. HEre is what I have for a setup directly from the switch terminal window:
ip default-gateway 192.168.1.1
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged A1-A24
ip address 192.168.1.10 255.255.255.0
no untagged B1-B24
exit
vlan 2
name "VLAN2"
untagged B1-B24
ip address 192.168.2.10 255.255.255.0
exit
ip route 0.0.0.0 0.0.0.0 192.168.1.1
With this if I have a PC on VLAN 2 I can ping both VLAN ips but I cannot ping 192.168.1.1 or any PC on the other VLAN. I manually se the IP on the PC to 192.168.2.100 with a gateway of 192.168.2.10. Obviously internet browsing doesn't work either.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2009 08:09 AM
тАО03-12-2009 08:09 AM
Re: 4109GL VLAN setup
you need a static route at your linksys router.
something like:
ip route 192.168.2.0 255.255.255.0 192.168.1.10
hth
alex
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2009 08:28 AM
тАО03-12-2009 08:28 AM
Re: 4109GL VLAN setup
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2009 09:05 AM
тАО03-12-2009 09:05 AM
Re: 4109GL VLAN setup
I suspect your PC's in Vlan 1 is pointing to 192.168.1.1 as their default gateway ?
So yes you need to tell 192.168.1.1 how to get to Vlan 2. Since the routes is not automatically redistributed. For that you would need a routing protocol. And well this setup is just to simple to warrant anything except a static route like ABE explained.
HTH
Gerhard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2009 09:15 AM
тАО03-12-2009 09:15 AM
Re: 4109GL VLAN setup
However. I am doing this in preperation for a much larger implementation using multiple switches and VLANS talking to our production 4108GL.
What is needed for the Procurve to do the routing? How would I have to set up my VLANS?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2009 09:24 AM
тАО03-12-2009 09:24 AM
Re: 4109GL VLAN setup
Assuming your production 4108 is the default gateway for all your devices in your lan/lans.
Something similar to the above. You might just need multiple routes, added to your linksys in stead of just the one.
Off course this depends on the scope of the network. :)
You might need to look at the nat settings on you linksys.
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2009 09:30 AM
тАО03-12-2009 09:30 AM
Re: 4109GL VLAN setup
If I wanted the 4108 to be the default gateway and forward to the SonicWall, or Linksys in the case of my test setup, would I add the routes to the 4108? Should they aready be there after I add the VLAN? That is the confusing part for me. If I am going to route with the Sonicwall anyway going through the trouble of VLANing seems like less of a necessity when the firewall is going to be doing all the work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2009 09:39 AM
тАО03-12-2009 09:39 AM
Re: 4109GL VLAN setup
Now on the SonicWall ( I have no idea of the mechanics of how ) that is where you would add the routes back.
Since the SonicWall knows how to get to the internet, but it does not know how to get to the networks in you LAN behind the 4108. So you need to tell the Sonic Wall how.
On the 4108 you would add a default route to the internet via the sonic wall.
Then you point your clients to the 4108 as their default gateway.
Now me personally ... i would put the Sonicwall in its own little vlan to avoid ICMP redirects from the 4108 :) for hosts in the same vlan as the SonicWall.
Again double check the NAT rules and FireWall rules on your SonicWall before implementing it.
Does this help?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2009 09:45 AM
тАО03-12-2009 09:45 AM
Re: 4109GL VLAN setup
So how would the CLI commands differ from what I have above?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2009 10:02 AM
тАО03-12-2009 10:02 AM
Re: 4109GL VLAN setup
The 4108 does route without the need for an external router. But it does not know how to get ourside without you adding a static default route
ip route 0.0.0.0 0.0.0.0 192.168.1.1
The Sonicwall ... you will have to figure that one wihtout my help :) But the same concept as for the linksys.
So basically you are just telling the two devices about the routes behind one another :)