Can you ping 10.0.0.3? Or can you ping 10.0.0.110 from the Pi?
What does arp -an show on the Pi?
Michael - just to let you know I’ll look in to this a little later, although I think you’re in good hands presently
Sam
here is my output, what i should expected, only my router is doing ISP DNS which DHCP is giving to vero, dhcp-binding
osmc@osmc:~$ ip ro
default via 192.168.2.254 dev eth0
192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.134
192.168.2.254 dev eth0 scope link
osmc@osmc:~$ arp -an
? (192.168.2.3) at 00:11:32:08:bc:d8 [ether] on eth0
? (192.168.2.136) at 34:e6:d7:62:14:ff [ether] on eth0
? (192.168.2.254) at 9c:6f:52:36:28:a9 [ether] on eth0
osmc@osmc:~$
allthough things seems to work for your wired / wlan devices, i would suggest, to move the dhcp-scope a bit higher, for example 10.0.0.100 to start with, cause there seems to be some possible conflicts into your setup
static ip (no dhcp binding) can be used as 10.0.0.4 to 10.0.0.99
10.0.0.2 is router
10.0.0.3 is dns pi
10.0.0.110 is vero wired dhcp
10.0.0.124 is static ip, so no dhcp-binding
can’t ping 10.0.0.110 from the PI
pi@raspberrypi:~ $ arp -an
? (10.0.0.227) at 2c:f4:32:bf:25:5c [ether] on eth0
? (10.0.0.138) at 90:0e:b3:01:c7:aa [ether] on eth0
? (10.0.0.2) at 54:83:3a:12:fc:c0 [ether] on eth0
? (10.0.0.211) at 38:8c:50:6f:d3:18 [ether] on eth0
? (10.0.0.228) at 00:1e:c0:96:f4:39 [ether] on eth0
? (10.0.0.75) at 84:d6:d0:cf:e8:e7 [ether] on eth0
? (10.0.0.150) at 30:07:4d:65:b9:21 [ether] on eth0
? (10.0.0.224) at 40:a1:08:1c:17:1b [ether] on eth0
? (10.0.0.139) at 2c:f4:32:bf:23:a2 [ether] on eth0
? (10.0.0.110) at on eth0
? (10.0.0.157) at a6:2e:9d:e6:26:ef [ether] on eth0
? (10.0.0.158) at 0c:fe:45:48:ff:a0 [ether] on eth0
? (10.0.0.80) at 00:05:cd:c4:bb:78 [ether] on eth0
? (10.0.0.153) at 74:da:88:10:96:a2 [ether] on eth0
? (10.0.0.123) at 6c:21:a2:79:0d:7e [ether] on eth0
? (10.0.0.55) at 5c:80:b6:2f:1d:54 [ether] on eth0
10.0.0.110 is also incomplete on eth0 from the pi
Thanks. i’ll try this. 10.0.0.124 is my other vero
Isn’t that your other Vero???
? (10.0.0.138) at 90:0e:b3:01:c7:aa [ether] on eth0
no. i don’t know what is on .138 my router doesn’t seem to pick it up
my veros are definitely 10.0.0.123 and 10.0.0.124
for some reason the PI can’t find both vero’s, even 124 is not “registered” there.
although things seems to be working in your environment, using same IP address for WLAN and LAN, could cause some issues there, as mac address are not the same.
maybe even try at DHCP scope to use the DNS from ISP, just to see
or look into the name server whether is has some error logging or excluded some devices
how is routing working on your PI?
please provide the MAC from both vero’s WLAN and LAN.
Check the MAC of your other Vero because it looks similar to the MAC of your 110 Vero
The pi is using google or openDNS for DNS resolution.
this problem existed before the introduction of the PI. but i’ll try turn the router to use ISP DNS as well as turn the Veros to use DHCP and see.
i’ve changed my router to use lease IP addresses from 10.0.0.5 0 10.0.0.100 so i can use 120+ range for statics .
i’ll feedback later today on any progress
thanks for the help guys, i really do appreciate it
I don’t think DNS is your problem. The ARP results are clearly showing an issue on the MAC layer which is quite fundamental.
what i figured out from your pictures and logs is the following mac address resolvings:
vero 1
wlan
ip 10.0.0.124
mac 6c:21:a2:78:c4:2c
lan
mac 90:0e:b3:01:c7:49
lan
mac 90:0e:b3:01:c7:ff (was previously 49 ???)
vero 2
wlan
ip 10.0.0.123
mac 6c:21:a2:79:od:7e
? (10.0.0.123) at 6c:21:a2:79:0d:7e [ether] on eth0
lan
ip 10.0.0.110
mac 90:0e:b3:01:bc:ff
unidentified (must be vero 1, but another change in mac-adress)
? (10.0.0.138) at 90:0e:b3:01:c7:aa [ether] on eth0
what i’ve done since my last message is:
- updated DHCP on router to lease from 10.0.0.5-10.0.0.100
- updated veros to use DHCP instead of static IP
- updated router to lease static IPs to certain devices on network (other than Vero), hopefully this will ensure that the router reserves those IPs so that there is less chance of a conflict
so far, none of these have made any difference, but i’m going to reboot everything and see what happens after a reboot
Doing that generally is mys suggestion also for the Vero’s
Please list all the Vero MAC addresses as we had asked.
After reading all this … nice to read btw 
… I probably think it is an arp cache issue … rebooting the necessary devices will probably solve the issue.
Thanks. have done probably a hundred reboots between the router, and the veros.
will get the MAC address and ip mapping for you shortly
Vero 1:
inet 10.0.0.124 netmask 255.255.255.0 broadcast 10.0.0.255
ether 90:0e:b3:01:c7:49 txqueuelen 1000 (Ethernet)
Vero 2:
inet 10.0.0.123 netmask 255.255.255.0 broadcast 10.0.0.255
ether 90:0e:b3:01:bc:8b txqueuelen 1000 (Ethernet)
i’ve also updated the router to lease these IPs statically as well