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, you also need to set the default gateway and dns server addresses in antMan > Network configuration > Edit Network Defaults. Enter the IP address of the default gateway. Select an interface - typically br0. And finally enter the DNS addresses. When adding the dns addresses, use the keyword 'nameserver'.. see the '?' tool tip for that field.
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 the 'edgeLinux terminal' in antMan.
Try to ping using a domain name:
ping -c 3 anthill.antsle.com
ping -c 3 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
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
If any of these addresses are incorrect, set the correct information in antMan > Network configuration
Here is a series of videos for trouble shooting anthill activation in our docs. The 4th video covers internet connectivity: