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] RIPE atlas probe network configuration
- Previous message (by thread): [atlas] RIPE atlas probe network configuration
- Next message (by thread): [atlas] RIPE atlas probe network configuration
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Mon Oct 20 15:24:04 CEST 2014
Hi James, On 2014/10/16 19:04 , James A. T. Rice wrote: > This means that you'd need to configure on your device, something like (assuming linux): > network: 10.a.b.0/24 > gateway: 10.a.b.1 > alias: p.q.r.s/32 > > with it configured that p.q.r.s is the default source IP address to use for any outbound packets. > > This is a relatively 'clean' way of doing things, as it doesn't involve proxy-arp or similar trickery. > > It should be possible to do this for linux based systems. What do you think? Will the atlas probe support it, or would you consider making that a feature? I guess not having to do proxy arp is attractive from a network operations point of view, but for a host having to use one specific address is not attractive at all. This would be a lot of work on the Atlas side. Not only adding the alias would require quite a few changes, but then also making sure that all network code would use the right source address. So for Atlas, it would be best if the probe could be configured as p.q.r.0/24 with p.q.r.1 as the gateway. Leaving the whole 10.a.b out of the story. Philip
- Previous message (by thread): [atlas] RIPE atlas probe network configuration
- Next message (by thread): [atlas] RIPE atlas probe network configuration
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]