You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the install described to activate networking in Amiga from the maual, i.e. install PIP3 and tun-adapter, but after this I can't login through SSH anymore to the Pi.
How to change this so SSH keeps workinh, because it was handy for SFTP etc.?
Edit: I can see through issuing command IFCONFIG that wlan0 is still up and on the same ip-address as before, only tap0 has an address that's different, 192.168.2.1 instead of wlan0, which has 192.168.2.18, but I still can't login through SSH. It refuses connection when I try, when applying the same method as before.
Maybe I need to bridge the networks?
The text was updated successfully, but these errors were encountered:
As I am on my homenetwork with the connected Pi, 192.168.2.18 and the tap0 is configured out-of-the-box for 192.168.2.1 (from the PiStorm network-install command: sudo cp /home/pi/pistorm/a314/files_pi/eth-config-pi/tap0 /etc/network/interfaces.d/), both interfaces conflict due to being in the same ip-range, 192.168.2.0/24.
I changed the ip-address in the file 'eth-config-pi' to 192.168.3.1 before issuing the copy-command as stated above, from the manual.
Maybe someone who runs into the same problem will benefit.
After the install described to activate networking in Amiga from the maual, i.e. install PIP3 and tun-adapter, but after this I can't login through SSH anymore to the Pi.
How to change this so SSH keeps workinh, because it was handy for SFTP etc.?
Edit: I can see through issuing command IFCONFIG that wlan0 is still up and on the same ip-address as before, only tap0 has an address that's different, 192.168.2.1 instead of wlan0, which has 192.168.2.18, but I still can't login through SSH. It refuses connection when I try, when applying the same method as before.
Maybe I need to bridge the networks?
The text was updated successfully, but these errors were encountered: