[atlas] [ripe.net #1133019] Re: Your RIPE Atlas Probe (ID: 16784) is not connected to our network
- Previous message (by thread): [atlas] [ripe.net #1133019] Re: Your RIPE Atlas Probe (ID: 16784) is not connected to our network
- Next message (by thread): [atlas] [ripe.net #1133019] Re: Your RIPE Atlas Probe (ID: 16784) is not connected to our network
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Roman Mamedov
rm at romanrm.net
Fri Aug 1 10:41:18 CEST 2014
On Fri, 01 Aug 2014 10:33:30 +0200 Daniel Suchy <danny at danysek.cz> wrote: > It's surprising, that you can't manage probe remotelly when it isn't > "connected" (even you can directly reach it on L3). Technically, probe > runs on Linux, so you can have SSH daemon with restricted IP access So do you suggest that everyone has to configure a port 22 portforward from their router/CPE to the probe? Or place the probe on its own dedicated public IP address? Nope, neither is going to happen, not feasible in perhaps 90+% of cases. -- With respect, Roman -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: <https://lists.ripe.net/ripe/mail/archives/ripe-atlas/attachments/20140801/6794c1a8/attachment.sig>
- Previous message (by thread): [atlas] [ripe.net #1133019] Re: Your RIPE Atlas Probe (ID: 16784) is not connected to our network
- Next message (by thread): [atlas] [ripe.net #1133019] Re: Your RIPE Atlas Probe (ID: 16784) is not connected to our network
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]