Special notes
- FortiExtender running in local IP-passhrough mode is accessible at 192.168.1.2 over SSH or HTTPS on Port 4.
- Not all receivers can receive SMS notifications. Be sure to adjust the receiver sequence to ensure that the first receiver always gets SMS notifications.
- When upgrading to FortiExtender 7.0.0, you must also upgrade the modem firmware. You can either upgrade the entire firmware package version 19.0.0 (or later) or only the firmware/pri inside the package.
- Upon reboot, FortiExtender will try to discover the FortiGate or FortiExtender Cloud that manages it, depending on your existing configuration. Because of this, there might be a one or two minute delay before the device can reconnect to the FortiGate or FortiExtender Cloud.
- FortiExtender 201E and 211E devices come with a Bluetooth button, which is off by default. However, when it is turned on, anyone can access the devices via Bluetooth. To safeguard your network, we strongly recommend setting passwords for all your devices before deploying them in your environment.
- In order for FortiExtender to forward syslog messages to a remote syslog server, the syslog server and FortiExtender's LAN port must be part of the same subnet.
-
FortiExtender and FortiGate share the same LTE IP in WAN-extension mode. In pre-4.2.2 releases, FortiExtender does not allow access to ssh/https/http/telnet service via the LTE interface, so all the traffic to those default service goes to FortiGate. FortiExtender 4.1.7/4.2.2 adds local ssh/https/telnet/http service support via the LTE interface. To distinguish local services from FortiGate services, you must configure FortiExtender to use different ports. Otherwise, all traffic to these default services will be sent to FortiExtender locally instead of the FortiGate. Below are the configuration changes you must make after upgrading to FortiExtender 4.2.2:
config system management
config local-access
set https 22443
set ssh 2222
end
end