I got an RVS4000 which on the WAN side has a modem with PPPoE dial-in. On the LAN side, I have a pool of public IPs. The first available IP is configured on the LAN interface (subnet /29), while the next one is configured on a Fortigate firewall interface. Now, I can't get reach the public IP on the Fortigate device, but from the Fortigate itself I am able to ping to the outside world (but no ping replies are finding their way back).
The routing table on the RVS4000 looks as follows:
Dest IP Subnet Mask Gateway Interface
126.96.36.199 255.255.255.255 0.0.0.0 WAN
188.8.131.52 255.255.255.248 0.0.0.0 LAN
184.108.40.206 255.0.0.0 0.0.0.0 LAN
0.0.0.0 0.0.0.0 220.127.116.11 WAN
18.104.22.168 is the WAN IP on the RVS4000
22.214.171.124 is the network address of the public pool I got (.81 is the LAN IP of the RVS4000, .82 is the one on the Fortigate device)
I do not see why packets are not reaching the LAN-based device (Fortigate). Maybe I'm missing something very basic...
Hello, This article will describe how to configure PPTP VPN on the new
RV340/345 routers from the Small Business series. RV340/345
Configuration The first step is to enable the PPTP Server: Go to VPN ->
PPTP Server Change PPTP Server: from Off to On Selec...
Article ID:5748 Use TheGreenBow VPN Client to Connect with RV34x Series
Router Introduction A Virtual Private Network (VPN) connection allows
users to access, send, and receive data to and from a private network by
means of going through a public or share...
Article ID:5728 Configure a Teleworker VPN Client on the RV34x Series
Router Objective The Teleworker VPN Client feature minimizes the
configuration requirements at remote locations by allowing the device to
work as a Cisco VPN hardware client. When the T...