This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Open ports?
- Previous message (by thread): [atlas] Open ports?
- Next message (by thread): [atlas] Open ports?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andreas Boesen
boesen at belwue.de
Fri Apr 15 10:57:15 CEST 2016
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-to-work) > > 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 at 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 at belwue.de - http://www.belwue.de ~cd in and find out -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 842 bytes Desc: OpenPGP digital signature URL: </ripe/mail/archives/ripe-atlas/attachments/20160415/1d4640aa/attachment.sig>
- Previous message (by thread): [atlas] Open ports?
- Next message (by thread): [atlas] Open ports?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]