Antsle Forum
Welcome to our Antsle community! This forum is to connect all Antsle users to post experiences, make user-generated content available for the entire community and more.
Please note: This forum is about discussing one specific issue at a time. No generalizations. No judgments. Please check the Forum Rules before posting. If you have specific questions about your Antsle and expect a response from our team directly, please continue to use the appropriate channels (email: [email protected]) so every inquiry is tracked.
antHill can't find antsle
Quote from Mario on March 21, 2018, 2:42 pmThere are a few reasons antHill may not be able to find your antsle
1. antHilld service may not be running.
check in antMan > settings (gear icon) > System servicesor from the command line run
service anthilld status
service anthilld restart2. The antsle cannot communicate with the public internet.
This can happen if the antsle does not acquire an IP from DHCP but is typically a misconfigured default gateway or DNS server address.
If you configured a static IP address on the antsle make sure you also set the default gateway and DNS server addresses in antMan > Network configuration > Edit Network Defaults
The DNS field requires the 'nameserver' keyword. Seee the '?' tooltip for that field.
First, is your ethernet cable plugged into the correct ethernet port (br0)? as shown here: http://docs.antsle.com/setup/#2-connect-power-and-network
And do you see a link light on both the antsle's ethernet port and your router/switch?
Next lets check if the antsleOS can talk to the internet. SSH to the antsle's command line or use 'show console' in antMan.
Try to ping using a domain name:
ping -c 4 anthill.antsle.com
ping -c 4 google.comIf the pings are successful then the network settings are good.
If the pings fail, lets check the IP addresses. The three addresses required are the private IP address on br0, default gateway and dns addresses.
You can check the antsle's private IP address with: ifconfig br0
root@myantsle:~ # ifconfig br0
br0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
inet 192.168.1.77 netmask 255.255.255.0 broadcast 192.168.1.255
...Check the default gateway with: route -n
root@myantsle:~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 8 0 0 br0
10.1.7.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr2
...the line with a destination of '0.0.0.0' should show the correct gateway address in the gateway column.
And check the DNS server addresses in the resolv.conf file with: cat /etc/resolv.conf
root@myantsle:~ # cat /etc/resolv.conf
# Generated by dhcpcd from br0.dhcp
# /etc/resolv.conf.head can replace this line
nameserver 192.168.1.1
nameserver 8.8.8.8
...If any of these addresses are incorrect, set the correct information in antMan > Network configuration
3. If purchased somewhere other than antsle.com/shop before 12/12/17
Then your antsle's serial number may not be in the antHill database. Please send your serial number and email address to [email protected].
There are a few reasons antHill may not be able to find your antsle
1. antHilld service may not be running.
check in antMan > settings (gear icon) > System services
or from the command line run
service anthilld status
service anthilld restart
2. The antsle cannot communicate with the public internet.
This can happen if the antsle does not acquire an IP from DHCP but is typically a misconfigured default gateway or DNS server address.
If you configured a static IP address on the antsle make sure you also set the default gateway and DNS server addresses in antMan > Network configuration > Edit Network Defaults
The DNS field requires the 'nameserver' keyword. Seee the '?' tooltip for that field.
First, is your ethernet cable plugged into the correct ethernet port (br0)? as shown here: http://docs.antsle.com/setup/#2-connect-power-and-network
And do you see a link light on both the antsle's ethernet port and your router/switch?
Next lets check if the antsleOS can talk to the internet. SSH to the antsle's command line or use 'show console' in antMan.
Try to ping using a domain name:
ping -c 4 anthill.antsle.com
ping -c 4 google.com
If the pings are successful then the network settings are good.
If the pings fail, lets check the IP addresses. The three addresses required are the private IP address on br0, default gateway and dns addresses.
You can check the antsle's private IP address with: ifconfig br0
root@myantsle:~ # ifconfig br0
br0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
inet 192.168.1.77 netmask 255.255.255.0 broadcast 192.168.1.255
...
Check the default gateway with: route -n
root@myantsle:~ # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 8 0 0 br0
10.1.7.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr2
...
the line with a destination of '0.0.0.0' should show the correct gateway address in the gateway column.
And check the DNS server addresses in the resolv.conf file with: cat /etc/resolv.conf
root@myantsle:~ # cat /etc/resolv.conf
# Generated by dhcpcd from br0.dhcp
# /etc/resolv.conf.head can replace this line
nameserver 192.168.1.1
nameserver 8.8.8.8
...
If any of these addresses are incorrect, set the correct information in antMan > Network configuration
3. If purchased somewhere other than antsle.com/shop before 12/12/17
Then your antsle's serial number may not be in the antHill database. Please send your serial number and email address to support@antsle.com.