So I have just rebooted the PI and changed one of the nameservers to the router IP which is the same as default gateway now. I did have to remove the broadcast IP that was in the config as it refused to connect to the Internet with it in when I first installed it
As I have said, up untill this week it has worked with no troubles since installing connecting locally. No new devices have been added.
.252 is a really common IP for class C router/AP interfaces. And potentially not wise to assign a local device. You sure there isn’t a 2nd one LAN side somewhere and suddenly you have an IP clash so routing issue.
No just checked the connected devices, no IP addresses are duplicated
Everything except 1 lan is wireless and the lan ends. 113
The best way to configure DHCP is to assign DNS to the router’s IP.
Do the same if you are using static IP addresses.
The end result is the first DNS lookup will be in the router.
If the router cannot resolve the address, it will ask the remote DNS server that you configured, n.b., 126.96.36.199.
Precisely what fixed my problem. Changed my DHCP range to exclude may static pi address and it’s been working fine ever since. Needed a new power supply though (thanks, @obj!).
Right so still having the issue, I have changed the DNS to include 192.168.0.1 on the PI, I have finally found the DHCP Pool settings in my router & changed the end IP to 250. so with the PI being static on 252 im hoping that should be it, as its taken the static range out of the DHCP pool range.
I will advise back if it works or not.
Well 23mins since I rebooted and could access after changing DHCP address pool. And it’s back to no local connection via ssh or browser yet its still feeding away. I am really lost now on this.
What did you reboot ? The router or the Raspberry Pi ?
Changing the DHCP scope would require a router reboot to flush the old settings.
It could be continuing feeding via an IPv6 adress maybe ? Or is IPv6 disabled ?
Was the pi, will reboot the router once I finish wfh today.
So rebooted the router and its had no effect putting the IP outside the DHCP pool,
Just a suggestion, shrink the DHCP scope to 150 devices and assign for instance number 200 to the Pi ?
Your settings in the Pi seems to be ok, did you check if IPv6 is still active and getting an DHCP address ?
Maybe that (if IPv6 is active) takes precedence over the IPv4 address ? Just trying to get to the bottom of this with you.
Just checked again and it’s back up. If it goes down again I will have a look at what you mentioned @tomvdhorst
I don’t know if this helps, the feeder stays up and reporting ( stated in the first post) but it can’t be reached on the IPv4 address. That’s why I’m thinking there might be an IPv6 DHCP lease active ( if IPv6 is activated).
Just checked the router and it doesn’t have IPV6 only 4.
Will keep an eye on it see how it goes.
Well over the past 5 days it’s been on and off for the local pages working via IP, I honestly don’t know what is going on but I think I’m going to have to just put up with it now, as nothing seams to be sorting it out.
But thanks all for your input and recommendations on trying to correct it.
So I tested something which might be of interest, the WiFi was connected to the 5ghz band so I switched it off on the router and its now back on 2.4ghz and weirdly enough, it’s not failed in the last 4 days. So it would seem it was the 5ghz band causing it for some bizarre reason.
5ghz is usually faster, but its range is shorter and it is more subject to interference. If there is a lot of distance (opposite corners of house) or many walls/ducts/etc between your pi and the wifi router, then it is totally plausible that 2.4ghz might be more stable.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.