fischertechnik community forum

Hi,

I have 2 TXT controllers and use them mostly (separately) with wifi. The USB is only used for ROBOPro updates. So far I connected to 1 using my Android tablet, and the other with a laptop. However, I want to connected to both with the same laptop and both issue the same IP for the DHCP-client (the laptop) with the ssh-key being different for each TXT. The result is that I would have to change the ssh-key each time I want to connect to either one of them. Is it possible to change the client address on the TXT? I haven't found an option for this.

Thanks

hvn

The IP addresses can be changed in /etc/network/interfaces

Hi,

Maybe I wasn't clear enough, but my point is that the DHCP server on the TXT always has the IP address 192.168.8.2 and the client always has 192.168.8.100. And on normal Linux systems, the network settings indeed are in /etc/network/interfaces but as far as I can tell not on the TXT. So my question remains: is it possible to change the 192.168.8.2 into e.g. 192.168.8.3 so I won't have ssh key problems when I want to use both at the same time from the same computer?

The file on the TXT contains this:
which is exactly the setting you are asking for.

BUT: That won't help you. First you need two wireless interfaces on your PC as each TXT opens its own wlan and you'd have to connect into both of them. Them you'd have to make sure that both use different networks, not just different IPs within the same network. Etc etc ...

The TXT with the current firmware is simply not meant to be used this way. Fischertechnik has announced a firmware version that will allow the TXT to connect into your home WLAN. That would allow you to simply connect both TXTs to the same PC using the same WLAN. But that firmware has imho not been released yet.

Hi,

Ok, I didn't search good enough. Thanks for pointing this out . However, I can't change it anyway since I don't have the root rights. I previously read that the root password is out there "but what would you need it for?". Well, this is a reason: changing the default IP address.