I have this setup where a wireless device (openelec) is connected to my WiFi network using a static ip address. After some time I am unable to reach the device (ping) and I don't know why. Had the same problem last week but after I upgraded to the latest version of LEDE I was able to reach the device again from my Mac.
Network setup is as follows:
Linksys WRT1900AC with latest version of LEDE (Reboot (17.01.4, r3560-79f57e422d)), it gives out dynamic ip addresses in the range starting from 100 and the PI has .3 and the zotac .2 ending ip addresses)
A raspberry pi connected to the Linksys by cable with static IP
A Zotac running OpenElec with static ip connected to the Linksys via WiFi
A ping from the Linksys to both machines are successfull and I am able to access my zotac via the Linksys.
I am always able to reach the PI but I am now unable to reach my Zotac, but my Zotac can reach internet (do have the latest weather forecast)
yeah i agree, with leach, you definitely need a seperate ip address for each device whether on wifi or ethernet, unless you have wifi on another dhcp server and ethernet on another dhcp server, wifi and ethernet are both associating to the same dhcp server which would cause an ip collision.
No that's not the case (sorry for the late reply, they have .3 and .2 ending ip addresses, I was on a short holiday and when I returned it was working normal again... but it doesn't feel right as it happened twice already)
yeah did you originally allow the device dynamic dhcp for the the device to associate then set up static ip once it had already established an ip address with a lease? Did you also see hostname as originaly associtiated ip in luci after static address set?
lol this is how bored i am, so anything you can think of for me to put as an option on performance? i swear i need some kind of draft i can sit there and just save rather than constantly posting something when i make an error like that , does it send an email anytime its edited? that would be hilarious to spam people with
Anyways:
if its a dhcp lease problem:
rm /var/dhcp.leases
rm /tmp/dhcp.leases
service networking restart
ifconfig eth0.2 down
ifconfig eth0.2 up
ifconfig eth0.2
if no need to change mac address, theres no need to reboot modem.