To do a test, disconnect the cisco router from the Protector.
The Protector uses eth0 and eth1 in bridge. Eth0 (not eth1) must be connected to the Internet modem. If the public IP of the Internet modem is IP, probably the Protector cannot reach it. In the Protector shell, try and ping or telnet IP, and see if it can be reached. If not, configure the Protector network settings with gateway = the local IP address of the Internet router.
Alternatively, temporarily bypass the Protector by connecting the cisco router to the internet router. Then , on the PC 10.10.0.5, open a DOS command prompt as administrator, type ipconfig /all and see what's the default gateway. Put the same gateway in the Protector.
Question: where is the DHCP server? I guess the PC is configured with automatic IP, and if the cisco is configured as gateway, the only possible dhcp server is the Modem, right?
In this case, what is the IP range configured for DHCP in the modem?
Is it possible to connect a PC to the modem (Protector and cisco disconnected) and see what IP address it receives?
This could be the problem. it means that the Internet modem behaves like a network switch, without a DHCP server, and the whole ISP network is like a big LAN. So, I guess that the cisco is normally configured to get the IP through DHCP.
Then, the Cisco is normally configured as a router, so it has a DHCP server inside that provides addresses in the LAN behind it in the subnet 10.10.0.x
Unfortunately the Protector can only work with a static IP, and this IP cannot be in the subnet 10.10.0.x, because this is a subnet created by the Cisco when it's configured as router. And the Cisco today is behind the Protector, not on top of it.
Solutions:
1-
Modem (variable IP) --> (Wan Port)Cisco RV325 IP 10.10.0.1 (LAN Port) --> (Eth0 Port) Protector IP10.10.0.2 (Eth1 Port) --> Another network switch -> LAN (PC IP10.10.0.106 etc.)
The Cisco is used as a DHCP server (configured like a router), and not used like a switch. Only 1 LAN port will be used on the Cisco, and it is for the Protector. The Protector must be connected to the Cisco, not to the modem, and can have IP 10.0.0.2. In this configuration, the Protector should be able to access the Internet. Then, the LAN must be connected to the Eth1 port of the Protector through another network switch.
2-
Modem (variable IP) --> A new Router (192.168.0.1) --> (Eth0 Port) Protector IP 192.168.0.2 (Eth1 Port) --> (Wan Port)Cisco RV325 IP 10.10.0.1 (LAN Port) -> LAN (PC IP10.10.0.106 etc.)
A new router must be placed behind the modem. It will receive an IP address (like it is for the Cisco today) in the subnet of the ISP (84.192...). It has a DHCP server that will create a new subnet, for example 192.168.0.x. The Protector is connected to the new router and has a static IP in the subnet 192.168.0.x. The Cisco is connected to Eth1 of the Protector and is configured as today (router), so it will receive an IP through DHCP in the subnet 192.168.0.x and will provide addresses to the LAN behind it, like today.
3-
Get a static IP address from ISP and configure the Protector with it.
In this moment the Protector is working as a transparent bridge. With the ISP restrictions in place on IP and MAC address, the solution to adopt is #1
1-
Modem (variable IP) --> (Wan Port)Cisco RV325 IP 10.10.0.1 (LAN Port) --> (Eth0 Port) Protector IP10.10.0.2 (Eth1 Port) --> Another network switch -> LAN (PC IP10.10.0.106 etc.)
The Cisco is used as a DHCP server (configured like a router), and not used like a switch. Only 1 LAN port will be used on the Cisco, and it is for the Protector. The Protector must be connected to the Cisco, not to the modem, and can have IP 10.0.0.2. In this configuration, the Protector should be able to access the Internet. Then, the LAN must be connected to the Eth1 port of the Protector through another network switch.
Comments
0 comments
Please sign in to leave a comment.