Follow

Can't Ping or Access SmartServer IoT Web page due to conflict with SmartServer IoT IP-70 IP Subnet 192.168.100.x or 192.168.239.x (KB1392)

If the SmartServer IoT IP-70 backbone IP subnet is the same IP subnet as the IP network you are plugging the SmartServer into then you will not be able to ping or access the SmartServer Web pages, ssh or SFTP.

To solve this problem you will need to change the SmartServer IoT IP-70 backbone IP subnet which is changed by changing the IP-70 router address from the existing IP Address to a new IP address.

IP-70 Router IP Address:
Original IP-70 Backbone: 192.168.100.128
SmartServer Software versions 2.75+: 192.168.239.128 

Workaround:
1. Using SmartServer console: Edit the following file and change IP address 192.168.100.128 to another IP address such as 192.168.239.128
    /etc/network/interfaces
2. Reboot the SmartServer

 

For Example (Change the IP Address shown in RED below):

apollo@smartserver-17q3awh:~$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

auto lo
iface lo inet loopback

iface eth0 inet static
address 10.1.128.82
netmask 255.255.254.0
gateway 10.1.128.1
dns-nameserver 10.1.0.83
dns-nameserver 10.1.0.84
pre-up /root/.setup/ethernet/eth_mac eth0

iface eth1 inet dhcp
pre-up /root/.setup/ethernet/eth_mac eth1

auto ip70
iface ip70 inet static
pre-up ip link set name ip70 dev dummy0
pre-up ifconfig ip70 multicast
address 192.168.100.128
netmask 255.255.255.0
apollo@smartserver-17q3awh:~$

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk