- This topic has 31 replies, 4 voices, and was last updated 5 years, 9 months ago by Kiwirad.
-
AuthorPosts
-
December 27, 2017 at 4:49 am #5384KiwiradParticipant
Hi there, I noticed by unit (11000007) is showing offline since Sept.
This is about the time I put in a new router and suspect there is some firewall issue?The DHCP gives the unit an IP (static DHCP) of 192.168.1.105 and I can ping the address ok.
I can’t get any other response from the unit other than a ping
December 27, 2017 at 7:07 pm #5397Bjorn RoesbekeParticipantAssuming you’re in the same subnet:
You could start by looking up if IP 192.168.1.105 matches your unit and is still an active lease, pointing to the correct device:
The MAC address shouldn’t be different from your device.
arp -a
or try
arping 192.168.1.105
Then try to reach the webinterface with a webbrowser on port 80, you could try to probe it with nmap; the port should be in an open state.
nmap -p T:80 192.168.1.105
If it doesn’t work, try the usual power cycle.
The device needs access to uradmonitor.com, data.uradmonitor.com and 8.8.8.8 but if the webinterface is inaccessible locally, then the unit probably won’t be sending data either.
December 27, 2017 at 7:23 pm #5399KiwiradParticipantThank you, the 8.8.8.8 is the problem. I have a static route to divert this to make US Netflix work.
I’ll set up a new rule.Thank you again!
December 28, 2017 at 12:06 am #5405KiwiradParticipantHi Again, hmm no luck. I think my unit is corrupt.
I can ping the unit, nmap -p T:80 shows the unit is open for http service (tcp) on port 80, I have all the 8.8.8.8 traffic unblocked
But the unit wont respond to a local browser,December 28, 2017 at 8:52 am #5406Bjorn RoesbekeParticipantTry, try and try again.
– another browser (elinks perhaps)
– another computer
– separate router/DHCP server combo
– See if the interface activity LED is blinking
– HUB + WiresharkDoes your router accept static IPs in the active DHCP pool?
I don’t think the uradmonitor unit is defective.December 28, 2017 at 7:12 pm #5437uRADMonitorKeymasterNeither do I , if port 80 is open this shows the firmware is working (the TCP/IP stack is fairly complex by itself).
December 29, 2017 at 7:50 pm #5445KiwiradParticipantHi again
I’ve done a packet capture on my router, I can see it connecting to 8.8.8.8 and to http://data.uradmonitor.com. I’m not network expert, but I do see a HTTP: HTTP/1.1 400 Bad Request in there.
Can ping, and see port 80 is open and active but there is no browser response. Tried a few different browsers and also externally (using a port forward).
Next I need to find another network to plug into to see if that is the issue (e.g with my EdgeRouter x)Time Packet
19:44:05.329263 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
19:44:05.334620 IP 192.168.1.1.67 > 192.168.1.105.68: BOOTP/DHCP, Reply, length 300
19:44:05.337690 ARP, Request who-has 192.168.1.1 tell 192.168.1.105, length 46
19:44:05.337762 ARP, Reply 192.168.1.1 is-at f0:9f:c2:0c:ad:a2, length 28
19:44:05.339640 IP 192.168.1.105.57345 > 8.8.8.8.53: 6657+ A? data.uradmonitor.com. (38)
19:44:05.554022 IP 8.8.8.8.53 > 192.168.1.105.57345: 6657 1/0/0 A 45.79.179.145 (54)
19:44:10.559757 ARP, Request who-has 192.168.1.105 tell 192.168.1.1, length 28
19:44:10.561907 ARP, Reply 192.168.1.105 is-at 02:00:11:00:00:07, length 46
19:44:57.047705 IP 118.149.186.92.4947 > 192.168.1.105.80: Flags [S], seq 3167851305, win 4380, options [mss 1460,nop,wscale 3,nop,nop,TS val 2748266183 ecr 0,sackOK,eol], length 0
19:44:57.047846 IP 118.149.186.92.4946 > 192.168.1.105.80: Flags [S], seq 275012374, win 4380, options [mss 1460,nop,wscale 3,nop,nop,TS val 2748266183 ecr 0,sackOK,eol], length 0
19:44:57.049142 IP 192.168.1.105.80 > 118.149.186.92.4947: Flags [S.], seq 4096, ack 3167851306, win 2560, options [mss 1280], length 0
19:44:57.050218 IP 192.168.1.105.80 > 118.149.186.92.4946: Flags [S.], seq 4864, ack 275012375, win 2560, options [mss 1280], length 0
19:44:57.076489 IP 118.149.186.92.4946 > 192.168.1.105.80: Flags [.], ack 1, win 4380, length 0
19:44:57.076544 IP 118.149.186.92.4947 > 192.168.1.105.80: Flags [.], ack 1, win 4380, length 0
19:44:57.076595 IP 118.149.186.92.4946 > 192.168.1.105.80: Flags [P.], seq 1:429, ack 1, win 4380, length 428: HTTP: GET / HTTP/1.1
19:44:57.175559 IP 192.168.1.105.2850 > 45.79.179.145.80: Flags [S], seq 5632, win 768, options [mss 750], length 0
19:44:57.415060 IP 45.79.179.145.80 > 192.168.1.105.2850: Flags [S.], seq 3003330188, ack 5633, win 29200, options [mss 1460], length 0
19:44:57.418295 IP 192.168.1.105.2850 > 45.79.179.145.80: Flags [.], ack 1, win 1024, length 0
19:44:57.420358 IP 192.168.1.105.2850 > 45.79.179.145.80: Flags [P.], seq 1:172, ack 1, win 1024, length 171: HTTP: GET http://data.uradmonitor.com/upload/0.1/upload.php?id=11000007&p=82&ts=60&inv=379&ind=441&s1t=21.69&cpm=15 HTTP/1.1
19:44:57.644423 IP 45.79.179.145.80 > 192.168.1.105.2850: Flags [.], ack 172, win 30208, length 0
19:44:57.645180 IP 45.79.179.145.80 > 192.168.1.105.2850: Flags [P.], seq 1:399, ack 172, win 30208, length 398: HTTP: HTTP/1.1 400 Bad Request
19:44:57.645243 IP 45.79.179.145.80 > 192.168.1.105.2850: Flags [F.], seq 399, ack 172, win 30208, length 0
19:44:57.649476 IP 192.168.1.105.2850 > 45.79.179.145.80: Flags [.], ack 399, win 1024, length 0
19:44:57.650474 IP 192.168.1.105.2850 > 45.79.179.145.80: Flags [F.], seq 172, ack 400, win 1024, length 0
19:44:57.877332 IP 45.79.179.145.80 > 192.168.1.105.2850: Flags [.], ack 173, win 30208, length 0
19:44:58.076354 IP 118.149.186.92.4946 > 192.168.1.105.80: Flags [P.], seq 1:429, ack 1, win 4380, length 428: HTTP: GET / HTTP/1.1
19:45:00.076644 IP 118.149.186.92.4946 > 192.168.1.105.80: Flags [P.], seq 1:429, ack 1, win 4380, length 428: HTTP: GET / HTTP/1.1
19:45:02.047757 ARP, Request who-has 192.168.1.105 tell 192.168.1.1, length 28
19:45:02.050287 ARP, Reply 192.168.1.105 is-at 02:00:11:00:00:07, length 46
19:45:04.076352 IP 118.149.186.92.4946 > 192.168.1.105.80: Flags [P.], seq 1:429, ack 1, win 4380, length 428: HTTP: GET / HTTP/1.1
19:45:12.076159 IP 118.149.186.92.4946 > 192.168.1.105.80: Flags [P.], seq 1:429, ack 1, win 4380, length 428: HTTP: GET / HTTP/1.1December 30, 2017 at 1:32 pm #5447uRADMonitorKeymasterWould you like to upgrade the firmware? This will probably improve things. It’s easy: https://www.uradmonitor.com/firmware-upgrade-guide/
December 30, 2017 at 6:41 pm #5451KiwiradParticipantOK, I’ve ordered the board from eBay. Will show up in a few week and will confirm progress. Thank you, I hadn’t noticed this firmware upgrade page before
December 31, 2017 at 4:35 pm #5458uRADMonitorKeymasterSounds good, let me know when you get the usbAsp , I will assist you further.
January 20, 2018 at 7:51 pm #5492KiwiradParticipantHi there, the usbAsp arrived. If you could please help me with the latest firmware I could trying upgrading and see if the unit comes back online!
January 20, 2018 at 8:09 pm #5493uRADMonitorKeymasterHi, I just sent it via email. Please make sure your usbAsp is set to 3.3V! This is important, or you risk damaging the model A board.
July 1, 2018 at 10:00 am #5893KiwiradParticipantHi all
I’m still having trouble with my unit. Hope you can help
The unit looks offline form the URad site, with some intermittent data.
If I arp -a the IP address doesn’t show
However, if I web browser to 192.168.1.105 I get the internal webpage up (see below), after the webpage comes up arp -a starts showing the IP address.
then after a few minutes arp -a stops showing the IPthoughts?
uRADMonitor 11000007
type:1 hw:107 sw:130 SBM20
radiation:0CPM
temperature:9.25Cinverter:380V 71%
uptime:22s wdt:21s/240sip:192.168.1.105
server:45.79.179.145
interval:60 http:0 0/0July 1, 2018 at 2:46 pm #5894Bjorn RoesbekeParticipantThe device has an IP address and is able to resolve the IP of the server but it’s showing HTTP status code 0, which isn’t a valid one.
Either a firewall is blocking the requests or there’s an IP conflict or a rogue DHCP that’s providing a bad gateway IP.
You could try adding a static entry to the ARP table but then we’re getting ourselves in some other mess.
Do you happen to be using a (misconfigured) powerline adapter? Multiple routers in the network?If the following returns more than one result, then you’ve most likely found your cause.
nmap --script broadcast-dhcp-discover
I may of course be wrong.
July 1, 2018 at 5:23 pm #5895uRADMonitorKeymasterI agree with Bjorn, the http status code should be 200 . Without that, the watchdog will keep on rebooting your unit.
The next two numbers show the successful packets sent per the total packets sent. -
AuthorPosts
- You must be logged in to reply to this topic.