1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

RVL200 - Class B Subnet as LAN

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by R.I.P., Oct 4, 2008.

  1. R.I.P.

    R.I.P. Addicted to LI Member

    Hi folks,

    I tried to configure a Class B subnet (subnet mask 255.255.0.0) as LAN. That's not possible using the web interface because the subnet masks are /24 (255.255.255.0) and larger. Has anyone found a way to directly configure LAN as /16?

    The I tried to configure the LAN as 169.254.0.1/24 and to use the "multiple subnets" feature to add 10.19.0.1/16. The device takes and displays the data correctly (even the routing table in advanced routing) but only 10.19.0.1/24 can access the internet (so 10.19.1.3 cannot for instance). Has anyone found a way to correct that?


    Thank you for your help, Rainer

    P.S. The company only has 5 workers but has a 10.19.0.0 / 255.255.0.0 network). So the RVL200 is powerful enough, just that the firmware seems to contain bugs...
     
  2. Toxic

    Toxic Administrator Staff Member

    the RVL200 is a Class C Router thats all. why did you try the 169.254.x.x ip? this is used by Microsoft for Auto configuration only when a device does not receive a DHCP IP address.

    have you tried giving your RVL200 the default 192.168.1.1 IP address. then have the old router behind using the 10.19.x.x network for its lan. then add the 10.x.x.x subnet to the RVL200's Multiple Subnet field.

    do you need the RVL as a gateway? or did you buy it for the 5 SSL clients?
     
  3. R.I.P.

    R.I.P. Addicted to LI Member

    Dear Toxic,
    many thanks for your reply.
    We have a Watchguard Firebox X Edge which became unstable (froze up to twice a day and had to be switched off an on).
    Behind are 5 users. And an IPSec BO-VPN to a remote office with 1 worker.

    I tried the APIPA IP range (169.254.x.x) because it's "dead" on my device (just a placeholder) and that's an IP range that no thoughtful admin ever would use for productive purposes. So no harm is done. 192.168.1.x for instance is a range that IMHO only very unexperienced people use for a LAN. Whenever it comes to routing between networks and/or VPN you are almost certain in trouble because that's the most often used range in the world. Two networks of 192.168.1.x are inconnectable by VPN.
    Even the SSL-VPN of the RVL200 simply cannot work if you have a company LAN of 192.168.1.1 (because 9x% of home LANs are the same range).

    We cannot use the old router because it's dead. Besides if we did we lost the 5-user-SSL-VPN feature (which does in fact work in a /16 network- though it assigns a route 10.0.0.0/8 to the clients).

    To say it on one sentence: We liked to use the RVL200 as a full featured Router (in gateway mode as they do call it). PPPoE Client and network behind.


    Have a great day, Rainer


    P.S. a warning: RVL200-IPSec-VPNs password length max is 32! Not a problem at all, except you try to replace a 'better' VPN router and used a longer password.
     

Share This Page