No containers in either case. On the Router it is running as an app, similar as if you run "ping" or "traceroute" manually on command-line. The SW Probe does not create its own interface or IP address, it makes use of one of the present, but not the one of best choice. Yes the WAN interface run PPPoE, but I believe the probe should be able to detect and use is: pppoe-wan Link encap:Point-to-Point Protocol inet addr:95.85.xxx.xxx P-t-P:10.11.5.146 Mask:255.255.255.255 inet6 addr: fe80::xxxx:xxxx:xxxx:xxxx/10 Scope:Link inet6 addr: 2a01:510:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 Scope:Global while the Probe config [atlas.ripe.net/probes/...] shows: IPv4 Current Configuration Internet Address 95.85.xxx.xxx ASN 43708 (METRONET - METRONET s.r.o.) Local Address 192.168.1.1 Gateway 10.11.5.146 Netmask 255.255.255.0 DNS Resolvers 127.0.0.1 so it uses the Local Address instead of public IP present on WAN interface. For IPv6: root@Om:~# ifconfig br-lan Link encap:Ethernet HWaddr 04:F0:21:23:2A:CE inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::xxxx:xxxx:xxxx:xxxx/64 Scope:Link inet6 addr: 2a01:510:xxxx:xx00::1/64 Scope:Global lan1 Link encap:Ethernet HWaddr D8:58:D7:00:32:01 inet addr:192.168.222.222 Bcast:192.168.222.223 Mask:255.255.255.248 inet6 addr: fe80::xxxx:xxxx:xxxx:xxxx/64 Scope:Link inet6 addr: 2a01:510:xxxx:xx88::1/64 Scope:Global lan0.2 Link encap:Ethernet HWaddr D8:58:D7:00:32:01 inet addr:10.1.1.1 Bcast:10.1.1.255 Mask:255.255.255.0 inet6 addr: fe80::xxxx:xxxx:xxxx:xxxx/64 Scope:Link inet6 addr: 2a01:510:xxxx:xxff::1/64 Scope:Global pppoe-wan Link encap:Point-to-Point Protocol inet addr:95.85.xxx.xxx P-t-P:10.11.5.146 Mask:255.255.255.255 inet6 addr: fe80::xxxx:xxxx:xxxx:xxxx/10 Scope:Link inet6 addr: 2a01:510:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64 Scope:Global While the Probe config page shows all the IPv6 addresses, it uses the "lan1" = 2a01:510:xxxx:xx88::1 for Connection and outgoing traffic, instead of pppoe-wan that should be used. ----------------------------------------- CentOS: it is not container, it is fullsize virtual machine running in large datacentre, it has its own public IPv4 and 6 on eth0, and other apps successfully make use of those, at the moment I have removed the other interface with 10.0.0.1 address so now the SW Probe do use the public IPv4. But once I create such 10.0.0.1 interface, the probe starts to use that private one for Connection and outgoing traffic. So what I was hoping for is, that I could make the software to use one particular interface for its outgoing communication. ______________________________________________________________
Od: "Michael Richardson" <mcr@sandelman.ca> Komu: ripe@brite.cz Datum: 24.05.2020 18:07 Předmět: Re: [atlas-sw-probes] How to force the SW Probe to use particular IP Interface / IP Address?
CC: <atlas-sw-probes@ripe.net>
<ripe@brite.cz> wrote:
is there a way how to force the SW Probe to use particular IP Interface / IP Address?
Isn't it running as a container? If so, the container has it's own IP address, and it would be bridged to the LAN interface, since the WAN interface would have only one IPv4. (and might be PPPoE!)
1. Turris Omnia Router: 1a - there is public IPv4 on WAN interface, but the probe choose LAN interface that is behind NAT, what is not necessary and would be better to choose the WAN.
1b - I have multiple IPv6 interfaces, the probe keeps choosing the one I use for testing and therefore is not as stable as the others. I would like the probe to use WAN6 interface instead.
Can you detail your network configuration here?
2. CentOS virtual machine - there is public IPv4 and local IPv4 RFC1918, again, the probe choose the local instead of the public IP. It's a pity, the probe better use the public one.
But, again, it can't use the IPv4 of the host.
-- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | IoT architect [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [