Showing results for 
Search instead for 
Did you mean: 

Replacing legacy 800 serie router by RV260




I try to replace a legacy 800 router by a brand new RV260 router. Our configuration is simple:

LAN : -> router LAN is

WAN : default gateway on -> optical fiber

In our LAN, we have an OpenVPN linux server ( tunelling to different sites. 

In the RV260, I've added these routes corresponding to each tunnel :

ip route
ip route
ip route
ip route
ip route
ip route
ip route
ip route


From the lan, pinging each machine beyonds those tunnels succeeds. But from the remote sites, the LAN does not respond.


Any idea where the problem is ?


Thanks in advance for help.


Kind regards,




3 Replies 3


The problem is not solved. But we've understood that the problem is the following : 

- inbound traffic from remote site arrives correctly to local device in our LAN

- this device use the RV260 ( as default gateway

- the routes back to remote sites configured in the router seems to be at this moment ignored.

Why ?



Finally we understood that the routes are not applied to inward traffic bouncing on the router (default gateway). With a packet sniffer, we saw those packets on the WAN interface of the router. Seems to be a bug in the router software. We do now the routing with our HPE switches. Quite disappointing.


Hi Guy


You should not get disappointed unnecessarily, so i though i will share my understanding. Rest is left to you if you accept it as correct or not based on logic and the working of standard network routing and forwarding process


Refering to your configs as described above


1. Say you have a lan-host with ipaddress and its default-gw is correctly pointed to which is the lan-ip of RV260

2. Now this lan-host sends a ping to say, so it correctly forwards this to the default-gw

3. Now the RV260 (which has the ipaddr has a static route for pointing to (the servergw), and becos the destination-ip of the ping packet is, it therefore forwards it to, which is again the correct behavior


4. Now once the server has recieved the ping-request packet with destination, it simply forwards it on to its other interface connected to the 192.168.3.x network...this is correct


so far so good...right?....iam sure you will agree that the above process is exactly as per networking standards


Now lets look at the reply-ping from to


5. The host will send the ping-reply to to the servergw...we are not concerned how it arrives upto servergw;s other interface...its not important


6. Now on the servergw it sees that there is a ping-reply packet with src-ipaddr and destination-ipaddr

since routing is majorly based on per standard behavior

a) Server gw checks that the destination ipaddess is in the same subnet as its own ipaddress why should it do routing for same subnet???? 

b) Instead as any network-connected ip-host, instead of routing it to its default-gw ipaddress (which you are saying should happen), the servergw will correctly send a ARP-REQUEST broadcast on the datalink/ethernet-link...asking what is the mac-address of the ipaddress

c) and since is also in the same subnet and datalink, it recieves the ARP-Request and since it is its own ipaddress, it replies by sending its mac-address to


7. And this is why at this point of time, the server gw is correctly behaving (and it nothing to do with the RV260 which is not at all involved any which way and not responsible for servergw behavior....which i think will very much agree) and sending the ping-reply packet directly to the lan-host 


8. Hence that is why you are seeing that any traffic initiated or replied by the subnets TO local-net would be sent directly to the lan-hosts BY THE SERVERGW...


9. The only time the traffic from the subnets 192.168.3.x/4.x/6.x/etc would be routed to again by the same Server gw would be when they are sending to Internet


would the above info help in clarifying your doubts which are good to have. You are logically thinking and trying to understand this kind of asymmetric forwarding that is happening...







Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers