We help IT Professionals succeed at work.

How do I configure my WRT54G(Talisman Basic) to route my VLAN traffic?

Medium Priority
1,459 Views
Last Modified: 2012-05-06
I am setting up multiple VLANs on a HP Procurve 1700-24 switch.  Each VLAN needs to be able to access the internet through a shared port.  I have received help on the switch configuration, but still cannot communicate between my VLANs and the internet.  

My VLAN Configuration is as follows:
     VLAN 1:  Default VLAN     192.168.1.0/24 subnet
     VLAN 5:  Ports 2, 3, 4, 5 and 24     192.168.5.0/24 subnet
     VLAN 10: Ports 6,7,8,9 and 24     192.168.10.0/24 subnet

The router is connected to port 24.  It is a WRT54G running Talisman Basic Firmware.  Since all the configuration I have done has failed to date, I have reset the router to Factory settings and have provided the following screenshots for your review.

I have also provided screenshots of my Procurve Switch VLAN settings as well so you can review those.  Any help would be appreciated.

Thank you in advance.
Procurve-Port-Config.doc
VLAN-1-Config.doc
VLAN-5-Config.doc
VLAN-10-Config.doc
Talisman-Setup.doc
Comment
Watch Question

CERTIFIED EXPERT
Top Expert 2014

Commented:
It looks like you have your VLAN mixed up.

On the WRT54G you have VLAN0 mapped to 192.168.1.0/24, but you state that 192.168.1.0/24 is VLAN1.  You are using tagged vlan mode, which means each Ethernet frame is tagged with what VLAN it is supposed to be.  So you have one side tagging the VLAN id as 1, while the other side is tagging it as 0.

The VLAN's tag must match.

Author

Commented:
I appreciate your response, giltjr.  The router has, in fact been set back to factory defaults.  This is one of the issues I have been having.  The Talisman firmware automatically assigns the VLAN0 to be the internal LAN.  The VLAN1 is the WAN.  I can change (using the interface) VLAN0 to any other VLAN, but I can't seem to change VLAN1 from being the WAN interface.

Having said that, I have tried, by command line, to initiate VLANs on the Talisman firmware, but my command of CLI for this firmware and for VLANs in general is limited.  I always ended up having to reset the router back to factory standards and start over.

Any thoughts?
CERTIFIED EXPERT
Top Expert 2014
Commented:
Since you are limited as to what VLAN's you can assign in Talisman I beleie you need to change the VLAN numbering on the HP switch.  You should only need to change VLAN1 to something other than VLAN1 or VLAN0.  Say VLAN 2 or 20.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Author

Commented:
I will try that an dpost the results.  Thank you.

Author

Commented:
I still have not been able to get this going. My problem is I can't seem to define the vlans. Were or how do I input the ip addresses for the different vlans using the wrt54g. I only have one cable connected to the switch from the router. I can get it to work if I plug multiple Cables from the router into the different vlans. But that defeats the purpose. It just turns my 24 port switch in to little 5 port switches.  
CERTIFIED EXPERT
Top Expert 2014

Commented:
Are you having problems defining the VLANs on the WRT54G or on the HP Pro-Curve?

Author

Commented:
I am having problems maintaining management control on the HP Pro-Curve.  

I am trying to take a random VLAN, say VLAN2, and configure the switch to operate across VLAN 2 on every port.  That way I can set port 1 on the router (the first LAN port on the back of the router) to be VLAN 2.  If I can get this BASIC configuration to work, I can then tweak it so that I can add VLAN 5 and VLAN 10 to the switch and to the router, both, then create static routes (if needed) between the VLAN 5 and 10 interface and the public WAN interface (VLAN1).

However, every time I switch all the ports to VLAN 2, and make sure that i have management set to VLAN 2, I lose my connection to the switch and I have to reset the switch to factory settings.  

Here's the deal, though.  I am only configuring these switches (we bought 5 of them) to work with this Router (the WRT54G) so that I can test my VLANs before implementation.  The real router is a Cisco with 2 T1 ports connected to it that is already pre-configured to route VLANs.  These switches are replacing two 3COM 48-port switches that are stacked and VERY old.   I just hate to put anything into production without having tested it first.  And it kills me that I cannot get this toy to play my games... lol.

I can provide the Cisco Routers config file if you wish to see it.  Maybe we CAN skip testing and move straight to implementation.

Author

Commented:
I am closing this question.  We have moved to using a Cisco 871 with Advanced IP Services Firmware to test our VLAN configuration.  Thank you for helping me.

Author

Commented:
While I never did get the router configured properly, I believe if I could have gotten the switches reconfigured we would have been good.  As it stands, I need to move on so am using a different router.
CERTIFIED EXPERT
Top Expert 2014

Commented:
Thanks for the points.  Setting up the VLANs so that the id match should make everything work.
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.