How to change RIPE Atlas Software Probe configuration and network settings?
I have RIPE Atlas Software Probe 1000069 up and running, but it somehow made up its network settings on its own. I need to virtually “plug” it into one of my other network interfaces. Is there a way how to configure its network settings? On https://atlas.ripe.net/probes/1000069/#!tab-network I show: Local Address 192.168.1.1 Gateway 10.11.5.146 Netmask 255.255.255.0 DNS Resolvers 127.0.0.1 it works, but I don’t see any interface of 10.11.5.146 (in LUCI or ifconfig), and one of my other local LAN has assigned 192.168.1.1/24 therefore the probe itself should not have the same, and I want to have the probe connected to different Network Interface. Furthermore for IPv6 it picked all IPv6 addresses of the router - one WAN and both LAN IPv6 addresses (I have two LANs), I want it different. I tried assign probe IP address via web interface, it does not work. Any idea how to configure the probe network settings? Thank you Jiri
Hi, On 2020/01/09 13:37 , ripe@brite.cz wrote:
Local Address 192.168.1.1 Gateway 10.11.5.146 Netmask 255.255.255.0 DNS Resolvers 127.0.0.1
it works, but I don’t see any interface of 10.11.5.146 (in LUCI or ifconfig), and one of my other local LAN has assigned 192.168.1.1/24 therefore the probe itself should not have the same, and I want to have the probe connected to different Network Interface. Furthermore for IPv6 it picked all IPv6 addresses of the router - one WAN and both LAN IPv6 addresses (I have two LANs), I want it different. I tried assign probe IP address via web interface, it does not work.
Any idea how to configure the probe network settings?
The way it currently works is that the probe reports all addresses that are assigned to any of its interfaces and all routing table entries. Then the atlas backend software displays one address and default router for IPv4 and most IPv6 addresses. For hardware probes that works because only one interface is active. For anchors that mostly works. Obviously, for a software probe installed on a router that approach doesn't work. Note that this just reports what is already configured on the device. The way we want to improve reporting is to allow the probe host to select the outgoing interface. However, that requires quite a number of changes and we have not yet planned when to do that. For measurements, the probe just allows the kernel to select an outgoing interface. Measurement result contain the local IP address that was used to send the request packets. With regard the the address 10.11.5.146, this is the default route of the 'pppoe-wan' interface. Philip Homburg
Oh ok, now I can see how it works. I thought the probe will be like standalone entity - like virtual machine that has its own IP address. Now I understand the probe just lives in the heart of the router, in the router's personality... Thank you for explanation and all your hard work on this project. Jiri ______________________________________________________________
Od: "Philip Homburg" <philip.homburg@ripe.net> Komu: atlas-sw-probes@ripe.net Datum: 09.01.2020 14:01 Předmět: Re: [atlas-sw-probes] How to change RIPE Atlas Software Probe configuration and network settings?
Hi,
On 2020/01/09 13:37 , ripe@brite.cz wrote:
Local Address 192.168.1.1 Gateway 10.11.5.146 Netmask 255.255.255.0 DNS Resolvers 127.0.0.1
it works, but I don’t see any interface of 10.11.5.146 (in LUCI or ifconfig), and one of my other local LAN has assigned 192.168.1.1/24 therefore the probe itself should not have the same, and I want to have the probe connected to different Network Interface. Furthermore for IPv6 it picked all IPv6 addresses of the router - one WAN and both LAN IPv6 addresses (I have two LANs), I want it different. I tried assign probe IP address via web interface, it does not work.
Any idea how to configure the probe network settings?
The way it currently works is that the probe reports all addresses that are assigned to any of its interfaces and all routing table entries. Then the atlas backend software displays one address and default router for IPv4 and most IPv6 addresses. For hardware probes that works because only one interface is active. For anchors that mostly works.
Obviously, for a software probe installed on a router that approach doesn't work. Note that this just reports what is already configured on the device.
The way we want to improve reporting is to allow the probe host to select the outgoing interface. However, that requires quite a number of changes and we have not yet planned when to do that.
For measurements, the probe just allows the kernel to select an outgoing interface. Measurement result contain the local IP address that was used to send the request packets.
With regard the the address 10.11.5.146, this is the default route of the 'pppoe-wan' interface.
Philip Homburg
participants (2)
-
Philip Homburg -
ripe＠brite.cz