Hello, I received my probe today and I had to disable the firewall for my box that appears connected to the site. I reactivated and after all the work area, but I would have liked to know what need had to open? How to know if everything is ok? Sorry for my English, thank you in advance
Hi, the FAQ says "The absolute minimum set is DHCP, DNS and outgoing TCP port 443 (HTTPS) in order to allow the probe to connect to the network. However, this in itself is not enough to do measurements, which is the entire focus of RIPE Atlas, so you should also allow ICMP, UDP (DNS + traceroute), TCP for traceroute and HTTP(S)." (https://atlas.ripe.net/about/faq/#so-which-services-do-i-need-for-my-probe-t...) Traceroute is port 33434 (when I am remembering right). Hope that helps. Greetings, Christian Am 13.04.2016 um 23:37 schrieb Anthony:
Hello, I received my probe today and I had to disable the firewall for my box that appears connected to the site. I reactivated and after all the work area, but I would have liked to know what need had to open?
How to know if everything is ok?
Sorry for my English,
thank you in advance
Hello, Thank you for the answer. Do you everything seems to be good there? : http://planet-upload.net/images/8cefe43963593d4ce948f8d907551fc6.jpg Because I feel it lacks a LED. thank you in advance Le 14/04/2016 19:20, Estelmann, Christian a écrit :
Hi,
the FAQ says "The absolute minimum set is DHCP, DNS and outgoing TCP port 443 (HTTPS) in order to allow the probe to connect to the network. However, this in itself is not enough to do measurements, which is the entire focus of RIPE Atlas, so you should also allow ICMP, UDP (DNS + traceroute), TCP for traceroute and HTTP(S)." (https://atlas.ripe.net/about/faq/#so-which-services-do-i-need-for-my-probe-t...)
Traceroute is port 33434 (when I am remembering right).
Hope that helps.
Greetings, Christian
Am 13.04.2016 um 23:37 schrieb Anthony:
Hello, I received my probe today and I had to disable the firewall for my box that appears connected to the site. I reactivated and after all the work area, but I would have liked to know what need had to open?
How to know if everything is ok?
Sorry for my English,
thank you in advance
I think she is: Connected on off on on undetermined So logically any good? and if nothing is blocked? Le 14/04/2016 19:20, Estelmann, Christian a écrit :
Hi,
the FAQ says "The absolute minimum set is DHCP, DNS and outgoing TCP port 443 (HTTPS) in order to allow the probe to connect to the network. However, this in itself is not enough to do measurements, which is the entire focus of RIPE Atlas, so you should also allow ICMP, UDP (DNS + traceroute), TCP for traceroute and HTTP(S)." (https://atlas.ripe.net/about/faq/#so-which-services-do-i-need-for-my-probe-t...)
Traceroute is port 33434 (when I am remembering right).
Hope that helps.
Greetings, Christian
Am 13.04.2016 um 23:37 schrieb Anthony:
Hello, I received my probe today and I had to disable the firewall for my box that appears connected to the site. I reactivated and after all the work area, but I would have liked to know what need had to open?
How to know if everything is ok?
Sorry for my English,
thank you in advance
Hi Anthony, Am 14.04.2016 um 19:20 schrieb Estelmann, Christian:
Am 13.04.2016 um 23:37 schrieb Anthony:
Hello, I received my probe today and I had to disable the firewall for my box that appears connected to the site. I reactivated and after all the work area, but I would have liked to know what need had to open?
as far as I understand the probe just needs to be able to establish _outgoing_ connections. When I connected the probe to my private DSL connection (a home router that does some NAT/firewalling) I did _not_ have to change anything in my setup. So there is usually no need to disable a Firewall as long as the firewall/NAT setup does allow _outgoing_ connections (at least for the probe). As Christian already linked the FAQ your probe should be allowed to: (1) establish outgoing TCP connections (2) establish outgoing UDP connections (3) send/receive ICMP packets So you do _not_ have to open ports for "incoming" connections / forward ports on your NAT. Just do not block outgoing connections. Also the probe can take some time before the website will list it as "connected". I just connected it and when I looked at <https://atlas.ripe.net/probes/> the next day (after registering the probe) it was working fine.
Hi,
the FAQ says "The absolute minimum set is DHCP, DNS and outgoing TCP port 443 (HTTPS) in order to allow the probe to connect to the network. However, this in itself is not enough to do measurements, which is the entire focus of RIPE Atlas, so you should also allow ICMP, UDP (DNS + traceroute), TCP for traceroute and HTTP(S)."
(https://atlas.ripe.net/about/faq/#so-which-services-do-i-need-for-my-probe-t...)
Traceroute is port 33434 (when I am remembering right).
Depending on how the probe does traceroute this may not be the only method. Depending on the implementation (AFAIK!) this might be different as different protocols might be used in a combination.
Hope that helps.
Greetings, Christian
Best regards, Andreas PS@Christian: Sorry for the spam. In my first attempt to send the email I just replied to you and not to the list. :-/ -- Andreas Boesen, BelWü-Koordination, Universität Stuttgart Industriestr. 28, 70565 Stuttgart Tel. 0711/685-65750 - Fax 0711/6788363 boesen@belwue.de - http://www.belwue.de ~cd in and find out
On 15.04.16 10:57 , Andreas Boesen wrote:
as far as I understand the probe just needs to be able to establish _outgoing_ connections. ...
That is correct. No *incoming* ports need to be opened! Daniel
participants (4)
-
Andreas Boesen -
Anthony -
Daniel Karrenberg -
Estelmann, Christian