-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello! First of all, I'd like to thank RIPE for such an interesting project, allowing to study the availability of various resources online. I have a question. If I'd like to set up a UDM, that will only be designated for my probe only, will it require credits or using my own probe is "free"? Thank you in advance. _____ Best regards, Roman A. aka BasicXP x12ozmouse@ya.ru -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJQk7vQAAoJEBjQX5UpOG9YquQP/RptIW1NbaPdOPczWUTYvjxB ZMRNHWO/VX2RWeYMIRWcoUpqVJSV2f7Sy+55hG6kkkcnWvXb+Do9ro4/MsyXocsD y+AXzgt9zgEaQMtJsgr7gjOttRp4vl9Y9RiQ/NfAV/QMZj6YH0QuoqjhpSLDYs6H bA8rmCAx2RGOTlhEvQTBnwI/K6zO8Cp9psLyQ1hzkQeUqlZbOGtD4AGpBuLOcrGR cHyckfN3Lww83oaecBEU1wjgOgUuHzTQzoJKhU7CLr0h0EeBC60Qd9CD75CW7yUD pAZA3JUHhAsYh4Bw5NDihuRhRqDYfo+Ch63JZvdNxznWgRXPgNjm8dm9BqC3rOM2 /aYo4MnglRke7VqCw9vPkw1IW/aXCfx7OoOt4Vp17dKal5iOS/FT2u58qFkzeLRT Mn90I5EdcEbB+Nuv3GsjYBI94JrrSK2KtcoV235mSTAGYyAM665c3fVR+HkOc9Eu s/msjchT3MBlEini6HVqAqdTFDaCro+mOw53lKzCch8VQSJRTrbHz1S7RgRVK9dB 89E1ij3HhUv6Tz9y3fGvWmNwFCWxgkY0qnB8erlFDcTxBtg/ou+a5oU2Yd6Pa14n HaZfXgzSjpasDSTDzxfLzpG/w7qhAluQgo2Q+fViG8yweVWvCDT9DrvbTEuUrPFq TuxIjj0uFFzfPUZrSTrW =GYfh -----END PGP SIGNATURE-----
On 2012.11.02. 13:25, Roman A. aka BasicXP wrote:
Hello!
First of all, I'd like to thank RIPE for such an interesting project, allowing to study the availability of various resources online. I have a question. If I'd like to set up a UDM, that will only be designated for my probe only, will it require credits or using my own probe is "free"? Thank you in advance.
_____ Best regards, Roman A. aka BasicXP x12ozmouse@ya.ru
Dear Roman, All UDMs require credits. If you already have a probe then you should already have an "income" which you can use do schedule your UDM. When doing so, you can pick a particular probe to use -- which can be your own. Regards, Robert Kisteleki
Hello dear ripe community, I am trying to resurrect a "down" status ripe v1 probe. Probe is connected to a router and is auto configured for both ipv4 and ipv6. For test purposes, ipv6 has been disabled. Facts: 1 - Probe ID: 98 2 - probe was down for ~ 1 year (sorry) 3 - from router I have both ipv4 and ipv6 connectivity. 4 - sniffing shows traffic: pings, dns queries, ssl. For 22 minutes 58 seconds dumped 3.7 megabytes. 5 - probe has old firmware - 4.030 (force upgrade?) 6 - probe is rebooting every 5 minutes ! 7 - ssl sessions (usually last less than 5 minutes) are finished by probe (sends FIN packet) 8 - probe is still down 9 - probe is natted, in the atlas interface the ipv4 is not updated 10 - last 25 connections show nothing for ipv4 (for test purposes we are ipv4 only now, earlier we had enabled ipv6, connections were logged but no data was updated) 11 - nothing in charts Please help me resurrect this baby. ;) Best Regards, Artur Russu PS Engineer TD / MCN / Mobile Packet Core Orange Moldova S. A. Tel.: +373 22 975381 Tel.: +373 691 98381 E-mail: artur.russu@orange.md This message and attached information may be confidential. It is intended only for the use of the individual or entity named above. If you have received this message in error you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited, and please immediately notify us by telephone or reply by e-mail and then promptly delete the message. Thank you for your cooperation.
On 11/5/12 14:09 , Artur Russu wrote:
Hello dear ripe community,
I am trying to resurrect a "down" status ripe v1 probe.
Probe is connected to a router and is auto configured for both ipv4 and ipv6. For test purposes, ipv6 has been disabled.
Facts: 1 - Probe ID: 98 2 - probe was down for ~ 1 year (sorry) 3 - from router I have both ipv4 and ipv6 connectivity. 4 - sniffing shows traffic: pings, dns queries, ssl. For 22 minutes 58 seconds dumped 3.7 megabytes. 5 - probe has old firmware - 4.030 (force upgrade?) 6 - probe is rebooting every 5 minutes ! 7 - ssl sessions (usually last less than 5 minutes) are finished by probe (sends FIN packet) 8 - probe is still down 9 - probe is natted, in the atlas interface the ipv4 is not updated 10 - last 25 connections show nothing for ipv4 (for test purposes we are ipv4 only now, earlier we had enabled ipv6, connections were logged but no data was updated) 11 - nothing in charts
Please help me resurrect this baby. ;)
The probe is continuously trying to upgrade itself. I have no idea why it doesn't succeed. After failing to upgrade, the probe continues with its normal initialization. It gets part way through and then it restarts. I now disabled the firmware upgrade, but it takes a couple of days before the probe finds out. In the mean time, the only reason we know at why the probe would reboot is if traceroute is somehow blocked. Maybe you can check where UDP based traceroute works from the network the probe is on.
Hi Philip, I will monitor it till tomorrow. Just connected my laptop instead of probe, and ran udp test ping with different ttl. Test were successful, traffic passes the firewall. Probe still rebooting. C:\Program Files\Nmap>nping.exe --udp --ttl 3 -g 54767 8.8.8.8 Starting Nping 0.5.51 ( http://nmap.org/nping ) at 2012-11-05 17:54 E. Europe Standard Time SENT (0.6090s) UDP 10.20.30.6:54767 > 8.8.8.8:40125 ttl=3 id=19712 iplen=28 RCVD (0.7960s) ICMP 10.251.0.113 > 10.20.30.6 TTL=0 during transit (type=11/code=0) ttl=253 id=30800 iplen=56 SENT (1.7810s) UDP 10.20.30.6:54767 > 8.8.8.8:40125 ttl=3 id=19712 iplen=28 RCVD (1.7810s) ICMP 10.251.0.113 > 10.20.30.6 TTL=0 during transit (type=11/code=0) ttl=253 id=30801 iplen=56 SENT (2.7810s) UDP 10.20.30.6:54767 > 8.8.8.8:40125 ttl=3 id=19712 iplen=28 RCVD (2.7810s) ICMP 10.251.0.113 > 10.20.30.6 TTL=0 during transit (type=11/code=0) ttl=253 id=30802 iplen=56 SENT (3.7810s) UDP 10.20.30.6:54767 > 8.8.8.8:40125 ttl=3 id=19712 iplen=28 RCVD (3.7810s) ICMP 10.251.0.113 > 10.20.30.6 TTL=0 during transit (type=11/code=0) ttl=253 id=30803 iplen=56 SENT (4.7810s) UDP 10.20.30.6:54767 > 8.8.8.8:40125 ttl=3 id=19712 iplen=28 RCVD (4.7810s) ICMP 10.251.0.113 > 10.20.30.6 TTL=0 during transit (type=11/code=0) ttl=253 id=30804 iplen=56 Max rtt: 15.000ms | Min rtt: 0.000ms | Avg rtt: 3.000ms Raw packets sent: 5 (210B) | Rcvd: 5 (280B) | Lost: 0 (0.00%) Tx time: 4.17200s | Tx bytes/s: 50.34 | Tx pkts/s: 1.20 Rx time: 5.17200s | Rx bytes/s: 54.14 | Rx pkts/s: 0.97 Nping done: 1 IP address pinged in 5.78 seconds
Just enabled Ipv6 back again. Now the probe has both Ipv4 and ipv6 connectivity. Behavior is the same, the tests are done in ipv4 but data is dumped using ipv6. Probe still reboots constantly every 5 minutes. UDP traceroute by probe is done for first and second hops, but till the gateway there are more hops... Any thoughts?
On 11/6/12 10:51 , Artur Russu wrote:
Just enabled Ipv6 back again.
Now the probe has both Ipv4 and ipv6 connectivity. Behavior is the same, the tests are done in ipv4 but data is dumped using ipv6. Probe still reboots constantly every 5 minutes.
UDP traceroute by probe is done for first and second hops, but till the gateway there are more hops...
The best thing is to wait until tomorrow morning when the probe should stop trying to upgrade itself.
Hi Philip, Starting with approx. 11:10 the probe stopped flapping, so no more reboots. But, I see no traffic.. the probe doesn't do any tests in ipv4 and only router advertisements in ipv6. Still down in atlas page. What are our next steps?
participants (4)
-
Artur Russu -
Philip Homburg -
Robert Kisteleki -
Roman A. aka BasicXP