It seems that the box still supports it because if you go to http://192.168.1.1/sysinfo123.htm?ConsoleSimulation=1 it does enable telnet. However when I enter the username and password it doesn't work which makes me think cisco changed the password. Does anyone know what it is? This may depend on the version of the firmware, it does work as expected on a RV082 which is the only model I have used, and the user/password are the same you use to authenticate to the Web interface (which can be changed on said Web interface, in Setup / Password). ... View more

anamaria.fuentes wrote: I want to know if is possible configure a VPN router model RV082 for following two functions at the same time or if only is possible configure one of two: 1. Access to internet from LAN 2. Access by VPN Client from remote network Both simultaneously. My question because if I configure as router mode only works VPN access and if I  configure as gateway mode only works access to internet from LAN but never works with two functions. Assuming you have a simple network, meaning only one gateway connected to your ISP(s) and only one LAN (no other routers inside or outside) then the correct configuration is as gateway. Now why is VPN not working in that configuration?  You have to check the settings on the VPN client, start by the essential: IP address, net mask, gateway (the client will have 2 of each, one associated with the network card, and another associated with the VPN; they should be in different networks.) The first test on the client should be a 'ping ', and make sure LAN_IP is used, not WAN_IP. ... View more

All good points. techstylegroup wrote: We've been using RV042's .. (RV's in general).. for years and have at many small biz customers. How can we differentiate the 'old' from the 'new'? The new already has firmware version 4.  That only helps if you have access to the Web interface and see the firmware version. Also, how can we ensure when ordering units from distribution we're getting the latest hardware version? I've seen supplier stock that still is the older box and assume version? Yes, that's expected, every vendor will sell the old stuff first, or get rid of it somewhere else.  The only way to ensure anything is making the vendor guarantee you get the new version. I hope Cisco pays attention to this and the existing base of RV customers and keeps the support and firmware updates for both paths current! ALso, it would be 'smart' to build a common update image which could differentiate the two versions of hardware so we can correctly keep in sync with our customer base and new installs. I think I read in the product description that the new models are using a different processor.  That or the different OpenRG version (the actual software this routers are running) probably makes it unlikely that they can use the same code base. So, is there a different SKU or something to ID the v3+ units.  We buy from Ingram and D&H -- neither of which could tell me they have v3 hw routers? I don't know. ... View more

No.   HW is the processor, mainboard, etc. the only way to "upgrade" is to buy a new router. ... View more

You probably don't have version 3 hardware, the router's firmware upgrade is failing. The hardware version can be found in the code bar sticker, on the bottom of the unit, where the serial number is. ... View more

Elviszopa wrote: I wrote i previous post that I've connected it directly to computer and it did connect. What you wrote is clear, the problem is that with a DSL modem you don't "only connect it directly to a computer" and it works, the only thing that does that is a Gateway or router, not a modem... but what you said next does show that it is working, so never mind, I was just trying to get a clear picture. I've tried to physically disconnect WAN1 and WAN2 did connect, but when I connect it back it automatically disconnect. That is interesting, it looks like the RV is in fail-over mode, only when WAN1 fails does WAN2 connect. Looks like a bug on the RV, but as I said, I've never used the firmware version you have so I don't really know. For the upgrade, i tried to upgrade to version 4 but i could load firmware do router by browser. Is there some kind of software to do this? Version 4?   We are talking about different things, the latest version is 2.0.0.19-tm; and there is no software to load it. Edit 1:  My mistake, I just learned that version 4.0.0.7 was out last month.  I didn't know that. Edit 2: Version 4.0.0.7 is not for my RV, the release notes say its only for hardware version 3, and not compatible with earlier hardware versions. ... View more

What your images show is that the cable is connected and has a link, but pppoe never did connect with your ISP -- that is why the IP is all zeros. I don't know how you tested the modem, but either the test did not use pppoe, or the RV doesn't have the correct data, or has missing data, or something else. Have you considered upgrading the firmware?  I've never used that old version, so there might be details I don't know (like bugs that have been corrected). ... View more

Elviszopa wrote: But main problem is with connection with WAN2. How are you testing this? It can not connect. Even even I manually trying to do this it's always disconnected. So, please someone explain it to me. Can you try to explain clearly the current state of your RV configuration.  If you didn't disable service detection (and reset the RV, or at least the port), it will not work, if you never tested your pppoe settings then, perhaps, it never has worked. ... View more

marksbond wrote: Do they share the same switch? No, the WAN ports are separate from the LAN (switch) ports. I do know that although the DSL modem is configured in the bridge mode,  it's web configuration page remains accessible at 192.168.1.1 if it is accessed directly from a PC while both are off of the network. This is also the address of the RV042 when accessed from the LAN side. That could be the problem.  Have you tried changing IP address on the modem? I have a similar situation, but I haven't enabled the modem in bridge mode.  The modem is used also as AP, so I gave it an address on a different network, disabled DHCP, and connected it from switch to switch on the RV.  Yes, 2 cables from the modem switch to the RV, one to the WAN2 port, another to the switch.  I also gave the modem a second IP, one in the LAN space, that way I can configure and have general access to its Web interface from the LAN.  There's probably a better solution. I did note in another discussion that Network Service Detection should not be enabled on WAN2 as it is a bridged PPPoE connection. I should note that the only devices connected to the LAN when this issue is occurring are a wireless access point with 2 or 3 clients and a PC wired to the RV042. There are differences between modems, some can be accessed when they are in bridge mode, some not.  But sending pings shouldn't work, the RV is configured to connect to a modem and use pppoe to the ISP, no modem IP defined anywhere (from the RV point of view) so there is no way to send a ping when the IP address is unknown. ... View more

Your settings look wrong: If WAN2 is using pppoe, then your ISP modem is in bridge mode, then it will not respond to pings which you configured by enabling "Network Service Detection". ... View more

When using double WAN there is always the issue of "sessions", it occurs when using https, once you have been validated with one (WAN) IP address, if your traffic goes out the other the site will complain. The main point is the word "complain", not a time-out, or any other error, just your session will be invalid.  The fix is to give priority to one WAN for handling such traffic (both http and https). What you are seeing is a different problem, and my guess is that it is unrelated to the use of double WAN, the main clue for this being that you have the problem even inside your LAN, that traffic doesn't go through the WAN ports. Usually those problems mean that you have a failure somewhere, the usual way to find out is to look at the network statistics on every device (servers, workstations, switches) looking for errors but statistics on the RV are unreliable (both: Web pages like the port info, and SNMP), the latest firmware has bugs on those statistics or, to be precise, in some of those stats (the LAN traffic through SNMP is fine, both WAN traffics are not; I haven't looked into detail of the switch ports). Another possibility is that you have too much traffic (enough to make the RV CPU not being able to handle it).  I haven't seen this problem so its just a speculation, in fact the RV CPU is very lightly loaded from what I've seen, but I haven't used the VPN capabilities which probably could put some stress. ... View more

That's easy, just put an "allow rule" on top that allows traffic from Any(Any) to Singe IP (the internal Web server) for service HTTP. Then add "deny rules" for each IP or range of IPs that shouldn't have Web access; source LAN, single or range IP, destination Any, service HTTP.  Notice that this rule doesn't stop HTTPS and many other services that could be abused: messenger, torrent, even http using a proxy on a different port; but it stops any direct connection to port 80 not allowed by the first rule. To fix the "user workarounds" (like using a proxy to by-pass the deny on port 80) you can add rules blocking traffic from WAN1 (and similar for WAN2) to the specific LAN IP; source WAN1(Any), destination LAN (IP or range), service All Traffic. ... View more

Your description and your firewall rules don't match. Since your description is not... precise (actually I don't understand what you are trying to say, deny all WAN traffic, but allow access to one server on port 80? or deny almost all WAN traffic except port 80 traffic?) its hard to say how to fix things, several problems are evident: the POP3 and SMTP rules are in the wrong order, I assume you wanted to allow all mail traffic, then put them first, i.e. the way they are now, if one of the deny rules hit then the other rules won't even be evaluated. ... View more

You are going about it the wrong way, you don't need to configure NAT at all, its port forwarding what needs to be configured. I assume a full mail server, then in Setup - Forwarding add all the required services forwarded to your mail server.  That is, for a "full mail server" SMTP, SMTPS, SUBMISSION, IMAP, IMAPS, POP3, POP3S (yes, some of these are already defined, others you have to define first with "Service Management" which doesn't allways work, you have to keep trying until it works -- yep one of the many bugs on the RVs). Don't forget to undo any NAT configuration you did.  With port forwarding mail will go in and out through either WAN; but of course you need a DNS configuration to make that available by name and MX, I use both addresses with the same priority as MX, with a random response, but that is another subject not pertinent to the RV router. ... View more

Mr. Carr, I don't have any issue, except you not reading the messages and addressing me over something that I didn't ask. ... View more