Home LAN access to a device...

[Harry Bloomfield]

I have a weather station. The station is located at the back, of the back garden, which then forwards its data to a display, located in the house, which it does wirelessly. That part works fine.

The display, then connects by USB, to forward data to a Raspberry Pi. The Pi runs some software, which turns the data, into webpages, it also stores the recorded data on a memory card, and also updates the Met Office with my live data. All normally works just fine, if it's left alone to get on with it.... The problem is that the webpage in the Pi, becomes inaccessible, or difficult to access. The weather station continues to send data, the Pi continues to record the data, just the webpage fails, and no data sent to the Met Office.

Similar to this has happened before, on previous routers - Last week, I moved from copper, to fibre, which involved a replacement main router, the router to which the Pi is directly connected. I set the new router up, the weather page appeared as normal, after which access to the page gradually became more difficult, slow, then eventually was completely lost. Access to the pages were then missing for two days. I tried rebooting the Pi, changed the LAN cable, moved it to a different router port, nothing made much difference, but I was able to ping it. The first ping slow, but subsequent pings much faster. Then the web page became accessible, at first sluggish to load, and speeding up, the more frequently I loaded it. The Pi is on a DHCP allocated address.

 

[omega015]

I wonder if you are experiencing some memory leak issues or just the amount of data is causing the pi to show and crash or the webserver? Would a scheduled reboot of the pi say at 1am everyday or every 12 hours potentially be a short term workaround until you can optomise the code? Could you try using a alternative to the pi just to rule out this being the bottleneck / issue?

 

[Harry Bloomfield]

I wonder if you are experiencing some memory leak issues or just the amount of data is causing the pi to show and crash or the webserver? Would a scheduled reboot of the pi say at 1am everyday or every 12 hours potentially be a short term workaround until you can optomise the code? Could you try using a alternative to the pi just to rule out this being the bottleneck / issue?

That would not seem to fit, with what I'm seeing - It ran fine for the couple of years, up until swapping the router last week. Rebooting it, doesn't necessarily get it working again. It's almost as if - the more I try to visit its web page, the better the access to it improves, which makes no sense to me.

 

[omega015]

How are you accessing the webserver? Is this via a local address/ip just wondering if your able to access the pi locally without having to go via the router (well kinda). What router are you using btw?

 

[Harry Bloomfield]

Is this via a local address/ip just wondering if your able to access the pi locally without having to go via the router (well kinda). What router are you using btw?

I can type in cumulusmx:8998/ or enter its IP address, either work equally well, or equally badly when there is the access issue..

 

[Harry Bloomfield]

It's an Arris NVG578LX, after loosing access to the website yet again, it continued to ping repeatedly, with no issues, with the Pi on x.x.x.102, so I changed the DHCP range in the router - it was on x.x.x.100 to 253. I then changed it to 150 to 253. Pi came up on 245, and its website worked fine once again.

It has to be some issue with the IP, or DHCP, but what? My next test, will be to allocate a fixed IP to it.

 

[flameport]

It will be the router.
Plenty of routers designed for home use will fall down and break if used for moderate to large numbers of incoming connections.

 

[davelx]

Not clear to me that there are any "incoming" connections. If the PI and the browser are on the same local subnet, then after the initial ARP query to determine the local MAC address of the Pi, no traffic goes through the routing function, only through the built-in wifi AP and switch.

If the Pi is sending data to the Met Office that should be via an outgoing connection to their server.

Where, network wise, is the browser that is connecting to the internal webserver in the Pi?

 

[Harry Bloomfield]

Early days, but what seems to have resolved it, is allocating in the router, a fixed IP from the MAC. The router only allowed you to set it to allocate IP's, within the range it sets aside for DHCP addresses. So far, access to the Pi, has survived uninterrupted, for 24 hours.