...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Info |
|---|
For SmartServer 3.4 to 4.1, see Configuring the SmartServer IP Address and Hostname (Release 3.4 to 4.1) For SmartServer 3.3 and prior, see Configure Your SmartServer (Release 3.3 and Prior). |
You can configure IP network settings for the SmartServer from the SmartServer Configuration page Network tab as described in this section. The Network tab appears as the default SmartServer Configuration page. Once Once the network settings are configured for the SmartServer system, then the System tab will appear as the default.
If you cannot access the SmartServer Configuration page, you can configure the SmartServer IP address using the SmartServer console, SSH or SFTP. See Configuring the SmartServer IP Address Using the Console for more details on making the changes using the console, SSH or SFTP.
This section consists of the following:
| Table of Contents | ||
|---|---|---|
|
Setting the SmartServer Hostname
The SmartServer Network Configuration page displays the SmartServer hostname in the Hostname field and can be updated as needed if you are using self-signed certificates (not if you are using built-in, signed certificates). If you change the hostname, you must also get new SSL certificates, since they are linked to the hostname. Refer to the Security Setting - Signed Certificates section for more information about using certificates.
...
Click Update to save changes. A system reboot is required for changes to take effect.
...
The SmartServer Network Configuration page displays the LAN and WAN interface, current IP address, network mask (also known as the subnet mask), and default gateway. It also provides the option to set the network mode: Startup Mode Mode - DHCP with rapid fallback to static, DHCP, or Static IP Address. The default setting is Startup Mode - DHCP with rapid fallback to static. Click the mode setting to change the network mode.
...
The Startup Mode - DHCP with rapid fallback to static is global for eth0 and eth1. Therefore, if you configure the eth0/eth1 to DHCP, then eth1/eth0 is no longer in Startup Mode - DHCP with rapid fallback to static. Changing one to DHCP, automatically sets the other to DHCP, and similarly for Startup Mode. Both LAN and WAN interfaces must be changed so neither is in Startup Mode - DHCP with rapid fallback to static.
...
If you are only using a single Ethernet port (the LAN or WAN port, not both ports), and you are using a LON U60 interface with a static IP address for eth0 or eth1, then you must set the LAN Interface Gateway field for that port (LAN or WAN). For example, if you are using the LAN port, then set the unused port to Startup Mode (see the example below).
...
If you are using both the LAN and WAN port, then you need to assign a default gateway IP address only when needed. At least one gateway IP address needs to be used (either assigned by DHCP or by manually adding to a static IP address). Assigning gateway IP addresses to both ports may cause issues with Ethernet communication. Some Ethernet communications will work properly and others may not.
...
Only the ports that you are using need to be changed. For example, if you are using only the LAN port, then you only need to change the LAN port and not the WAN port. Refer to the table below when using both LAN and WAN ports.
WAN | LAN | Support |
|---|---|---|
Static Set up a gateway IP address | Static Do not specify a gateway IP address (see Note 1) Specify routing paths only if you need to work with devices that are not on the same IP subnet as this port | Supported |
DHCP (see Note 2) | Static Do not specify default gateway IP address (see Note 1) Specify routing paths only if you need to work with devices that are not on the same IP subnet as this port | Supported |
DHCP (see Note 2) | DHCP (see Note 2) | Supported |
Startup | Startup | NOT supported |
Startup | DHCP (see Note 2) or Static | NOT supported |
DHCP (see Note 2) or Static | Startup | NOT supported |
| Note |
|---|
1. If you are using a static IP address for both WAN and LAN, and you configured a gateway IP address for both, then the SmartServer will use the last gateway IP address as the gateway IP address. In this case, you may experience communication issues as messages intended for the WAN port may get mistakenly re-directed to the LAN port. 2. In most cases, DHCP will automatically assign a gateway IP address. In some cases, you may need to manually add a gateway IP address when using DHCP. If you experience any problems, contact your IT department. 3. Do not use the same IP subnet for both the WAN and LAN ports. 4. In some cases, you may need to specify static routes. In this case, you may need to re-add the routes when you re-image or restore to factory settings. |
...
To check the SmartServer's current routing table entries, enter the following command:
...
Print current routing table entries
| Code Block |
|---|
route -n |
To add a routing table entry, enter the following command:
...
Example: Adding a routing table entry
| Code Block |
|---|
route add -net 192.167.3.0 netmask 255.255.254.0 gw 192.167.3.10 eth1 |
To delete a routing table entry, enter the following command:
...
Example: Deleting a routing table entry
| Code Block |
|---|
route del -net 192.167.3.0 netmask 255.255.254.0 |
...