weewx reported the log at 3:15am so i checked the last time that bt updated the router firmware that was 1-july 23 so i cant blame the router
On Sunday, 23 July 2023 at 14:58:47 UTC+1 [email protected] wrote: > hi > laptop can ping PI > Pi cannot ping laptop > > connected up a second PI (created with a different image file) > Laptop can ping PI > Pi cannot ping laptop > PI cannot ping 192.168.1.248 the GW1000 > > i can SSH into both PI's > > > > > > On Sunday, 23 July 2023 at 13:22:51 UTC+1 Graham Eddy wrote: > >> laptop can ping gw1000. >> pi cannot ping gw1000. >> can laptop ping pi? and pi ping laptop? >> *⊣GE⊢* >> >> On 23 Jul 2023, at 9:56 pm, [email protected] <[email protected]> wrote: >> >> i have pinged other IP address on my net work and the PI gets response >> its only the GW1000 its have an issue with >> >> On Sunday, 23 July 2023 at 12:51:15 UTC+1 [email protected] wrote: >> >>> hi >>> >>> from my weewx.confg >>> >>> [GW1000] >>> # This section is for the Ecowitt Gateway driver. >>> >>> # How often to poll the API, default is every 20 seconds: >>> poll_interval = 20 >>> >>> # The driver to use: >>> driver = user.gw1000 >>> ip_address = 192.168.1.248 >>> port = 45000 >>> [[field_map_extensions]] >>> extraTemp10 = temp10 >>> wxSensor30 = light >>> >>> however you are correct its a network issue >>> >>> if i ping from my laptop >>> C:\Windows\System32>ping 192.168.1.248 >>> >>> Pinging 192.168.1.248 with 32 bytes of data: >>> Reply from 192.168.1.248: bytes=32 time=5ms TTL=255 >>> Reply from 192.168.1.248: bytes=32 time=3ms TTL=255 >>> Reply from 192.168.1.248: bytes=32 time=3ms TTL=255 >>> Reply from 192.168.1.248: bytes=32 time=3ms TTL=255 >>> >>> Ping statistics for 192.168.1.248: >>> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), >>> Approximate round trip times in milli-seconds: >>> Minimum = 3ms, Maximum = 5ms, Average = 3ms >>> >>> if i ping from my PI >>> >>> pi@raspberrypiwx:~ $ ping -n 192.168.1.248 >>> PING 192.168.1.248 (192.168.1.248) 56(84) bytes of data. >>> From 192.168.1.242 icmp_seq=1 Destination Host Unreachable >>> From 192.168.1.242 icmp_seq=2 Destination Host Unreachable >>> From 192.168.1.242 icmp_seq=3 Destination Host Unreachable >>> From 192.168.1.242 icmp_seq=4 Destination Host Unreachable >>> From 192.168.1.242 icmp_seq=5 Destination Host Unreachable >>> From 192.168.1.242 icmp_seq=6 Destination Host Unreachable >>> From 192.168.1.242 icmp_seq=7 Destination Host Unreachable >>> From 192.168.1.242 icmp_seq=8 Destination Host Unreachable >>> From 192.168.1.242 icmp_seq=9 Destination Host Unreachable >>> >>> >>> i have no idea why laptop can ping the GW1000 but my PI cant >>> >>> On Saturday, 22 July 2023 at 21:19:13 UTC+1 vince wrote: >>> >>>> Lets see your [GW1000] stanza from weewx.conf please. If your >>>> 'gateway' address is 192.168.1.148 then it should look something like the >>>> following: >>>> >>>> [GW1000] >>>> ip_address = 192.168.1.148 >>>> port = 45000 >>>> poll_interval = 20 >>>> driver = user.gw1000 >>>> >>>> Your gateway should also respond to a ping from your weewx box. Log >>>> into the weewx box and try "ping -n 192.168.1.148" and verify that you >>>> can get a response. >>>> >>>> >> -- >> You received this message because you are subscribed to the Google Groups >> "weewx-user" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/131679f4-e4fa-4c90-9baa-712b9cb14f70n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/131679f4-e4fa-4c90-9baa-712b9cb14f70n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> >> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/380a3fc7-f924-410c-8658-3eff5c43591en%40googlegroups.com.
