The snowflakes indicate that there is no default route (some other router) to the networks associated with the local interfaces. That is, any IP packet going to any of those networks (subnets) can be reached via the indicated interface (eth0, wlan0, lo).
$ (route ;echo; route -n ) | grep -v '^[KD]'
10.3.0.0 * 255.255.255.224 U 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 2004 0 0 wlan0
link-local * 255.255.0.0 U 2 0 0 eth0
loopback localhost.local 255.0.0.0 UG 0 0 0 lo
default 192.168.0.1 0.0.0.0 UG 2004 0 0 wlan0
10.3.0.0 0.0.0.0 255.255.255.224 U 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 2004 0 0 wlan0
169.254.0.0 0.0.0.0 255.255.0.0 U 2 0 0 eth0
127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo
0.0.0.0 192.168.0.1 0.0.0.0 UG 2004 0 0 wlan0
In other words 10.3.0.0/27 is on eth0 and 192.168.0.0/24 is on wlan0, but to reach anyone else (excluding 127.*), this machine must send stuff to 192.168.0.1
Unrelated, but I'd suggest using the
-n
option to avoid doing DNS lookups, thus making it faster. – lorenzog – 2014-02-03T16:59:19.300