SimRush with No static IP service add-on
⚠️A SimRush with No Static Public IP add-on service, there is no option to place the system into bridge mode.
However, if you choose to you use your own router / mesh hardware (e.g. Orbi, Eero etc) then having the WAN port set to DHCP will continue to work which you can then manage your own hardware for settings (excluding port forwarding which requires a static IP service).
SimRush with a Static IP service add-on
With a SimRush with a Public IP service add-on there is no “bridge-mode” setting as such.
However, if you are simply looking to have your own router perform the port-forwarding we can enable settings to DMZ the traffic which is destined for Public IP (185.25.14x.xxx) to go straight to your own router which in effect is the similar method to how bridge-mode works.
Method
For this to work the setting on your own router WAN port/interface which is directly connected to the SimRush controller you will need to set this to DHCP.
On the SimRush controller we’ll mark that IP which the router is assigned from the DHCP server as static which we can then force (DMZ) all traffic to your router.
Example
Using a DrayTek router (since it’s a common router for some Technical installations).
When access the DrayTek webgui from the public address on its assigned port e.g 185.25.14x.xxx:8080, the response is passed through the SimRush and straight to the DrayTek or any other port forwarding rules that you have have setup directly onto the DrayTek.
Complex Example
Using a DrayTek router but requiring the public to present directly on the WAN interface
If there is a requirement to have the Public address present directly onto the DrayTek, that’s a completely different story as this will have to be setup as a /31 subnet which will require an additional IP.
If there is already a Public address allocated this may change depending on adjacent IP availability
e.g. if the system was allocated a single static address (/32 IP address) but at a later date required an additional IP address for a /31,
In that example 1 Public address is configured on the SimRush controller’s LAN port and the other half of the /31 subnet is statically configured on the DrayTek’s WAN interface.
We don’t often configure the above method since there is an additional cost to the user for the additional IP address,
The only examples when there has been a requirement for this method is when the router (DrayTek in this example) has to generate SSL certificates with the WAN port IP matching the generated certificate (the Public IP address) an example of this would be the router needing a certificate with the public address listed for use in a IPSec tunnel.
