Amicygnix Tutorial questions

I try to open this topic so as not to continue writing on the topic dedicated to qemu.

I guess not all AmigaOS owners use AmiCygnix
Or maybe they don't need to.

I'd like to understand how they create their own configuration to talk to AmiCygnix is an external Linux based machine.

So I appreciate any kind of help both with key authentication and without.

I hope it will be interesting for other users as well.
Amigans is probably the only place to learn AmigaOS 4.1.
And everything I learned about AmigaOS 4.1 I learned thanks to the users of this forum.

So I hope to get help this time too.
Thank you.

Assuming that in:

/etc/ssh/sshd_config

the option is active:

X11Forwarding yes

on DISPLAY 0

I'm using Voodoo3 here with FireFox, sorry for the rough video

https://youtu.be/-jwX982AZAU

@white

I installed AmiCygnix many years ago at a time when there was active development going on with the actual AmigaOS4. I don't remember why I quit using AmiCygnix. Probably just busy with other stuff.

---
redfox

@redfox
thank you very much for your intervention.

when i was using WinUAE i was using 10.0.2.15 with RTL8029
i could only open any DISPLAY on linux
even having configured:
setenv SAVE display=localhost:0
is having assigned to the X0.host file the linux IP
because of the virtual router

so i was told it wouldn't work if i didn't have an external ip.
( fixed by installing NPCAP with winuae )

now i'm having the same problem i can only open the DISPLAY on linux.

In practice, the same problem occurs regardless of the emulator in use
( winuae or qemu )

I have seen that some people who are using qemu no one tried to see if AmiCygnix does not work.

Because if it works then I'm doing something wrong.

But again I am convinced that I am not using a real external IP address.

Or much more simply the command line I'm using is not written well to communicate with Linux.

I tried 2 command lines one is able to ping from AmigaOS to all Linux machines in use both virtual and real but then does not connect to the internet.

The other connects to the internet but is unable to ping any external Linux machines.

I can't do anything but try again or wait for someone to help me.

What I wonder is that if someone has succeeded why not show me how to do it?
Thank you

I asked Toni,
but this was already some time ago if WinUAE includes code written to be compatible with NPCAP.
He replied that WinUAE has no code written to make NPCAP compatible with WinUAE.

So the job is done entirely by NPCAP to have an external IP.

In practice if I don't install NPCAP in "Windows10"
even WinUAE is not able to use a real external IP.
And simply AmiCygnix will not open its DISPLAY and in fact it will not work.

So in conclusion NPCAP enable external IP.
And WinUAE has nothing special to make it work.

so all the suggestions that @balaton gave me
they are right.

but most likely something is missing that makes it work well with AmiCygnix

after mounting for example:
sudo ip tuntap add user white mode tap
sudo ip link set tap0 up
sudo ip addr add 192.168.0.1/24 dev tap0
sudo iptables -t nat -A POSTROUTING -s 192.168.0.2 -j MASQUERADE

this works without problems with AmigaOS
but it doesn't ping linux machines

while being able to connect to Linux machines is accessing the Linux shell via SSHTerm
and at the same time access the Internet.
but it does not open the DISPLAY on AmiCygnix.

Now I'm looking for the command that instead manages to ping the machines
I wrote it somewhere I have to find it
Linux but does not connect to the Internet.

And maybe you can find the exact command together.

I've done it so many times that I'm bored doing it

@balaton
@all

I made a video, with the classic guided configuration using RTL8139 with:
-netdev user,id=mynet0 -device rtl8139,netdev=mynet0

getting the classic IP 10.0.2.15

I then used "SYSMON" with "NETSTAT"

where you can see the various SSH requests forwarded by "AmigaOS" to the server.

I later used:
-netdev user,id=mynet0,hostfwd=tcp::6010-:6000 -device rtl8139,netdev=mynet0

always using IP 10.0.2.15

and you can always see the whole process in the video.

not created X10.host with DISPLAY=10
(I can create it once I have the right suggestions)

to get help on how to give a right command line according to the video provided.

Thank you.


Here is the video with details.
https://youtu.be/D1BFb2eryEY
​

@white

I can't help you, but I see that you have solved the problem with the incorrect colors under AmiCygnix under AmigaOs4.1.

With me it looks like this and I don't like it at all:



How did you solve the problem?

@Maijestro
Hi, I didn't solve the color problem with 7457

use -g3
and the colors are right
also other screens besides Picasso96 can be opened
it's more compatible with a lot of things for me currently.

I would like to learn more about AmiCygnix
But I see that the topic is not much followed.
And a pity, you can do many more things with amigaOS
via Amicygnix.

I can make other more advanced videos with different configurations with static IP etc.

Is there something wrong with the Gateway or something.

If the RTL 8139 driver has no problem

I think AmiCygnix should be fixed somehow (maybe)
for example I have to manually select the DISPLAY settings in AmiCygnix the graphical interface does not seem to save the settings with the relative DISPLAY.

Again only the author of AmyCygnix could do some testing at this point.
But he probably doesn't find it interesting.

@whiteQuote:

I just tested it with g3 cpu and it does not solve the problem.

use:
"picasso96clonewbdb"

and then start trying the others too

I currently use 1440x900 RGB16PC

here you can see from AmigaOS how with a simple:
export DISPLAY=:0
from shells

I open applications directly on the server
the problem is that I can't export DISPLAY inside AmiCygnix

https://youtu.be/TbQgZHoT8z4

@white

You need to export from sh, not from amiga shell.
maybe thats the problem.

@white
Almost there but still not doing what I said. With -netdev user,hostfwd like in the second attempt in the video in pos #6 but you should use export DISPLAY=localhost:10 in the ssh window. Some explanation:
- you can't accesss 10.0.2.15 from your host as that's behind the user/slirp NAT, that's why we use hostfwd to forward localhost:5010 to port 6000 of the guest and since 6010 corresponds to display 10 you'd use DISPLAY=localhost:10 but this will be forwarded to guest port 6000 so it's the same as :0 in the guest but accessed as localhost:10 from the host. If you set display to :0 on host it will connect to local display as seen in the second video.
- Ping doesn't work with -netdev user, this is mentioned in the QEMU docs so don't use that for testing
- If it still does not work with hostfwd and DISPLAY=localhost:10 it may be a problem with failed authentication that you can disable in AmiCygnix shell with xhost + but that allows everybody who can access the forwarded port to connect.

@balaton
Thank you.

@all ( because tools with AmigaOS are different )

The steps look right
Clearly the difficulty is with Amicygnix

as mentioned, WinUAE must be set aside and rightly so.

Instead let's switch to qemu because that's what we're working on

So to work better now I use real machine (LINUX)

1)launch Amicygnix
2)SSHTerm=IP user=white
3)password OK (I'm inside the terminal)
4)export DISPLAY=:10
5)xhost
access control enabled, only authorized clients can connect
YES:localuser:white


launch:
Firefox or FFPlay

is I get:
Invalid MIT-MAGIC-COOKIE-1 key
Error: cannot open display: :10

only the MAGIC-COOKIE is missing
my difficulty is understanding with AmiCygnix what I have to do is which ones

issuing commands using "SSHTerm"

README SSHTERM:

SSHTerm is SSH client with a built in (xterm-256color) terminal emulation based
on an enhanced version of libtsm.

Requirements:

- AmigaOS 4.1 update 6 or newer

- AmiSSL 4.4 or newer (https://github.com/jens-maus/amissl/releases).

Usage:

Run from CLI with commandline template:

HOSTADDR/A,PORT/N/K,USER/A,PASSWORD,NOSSHAGENT/S,KEYFILE/K,MAXSB/N/K

HOSTADDR is the IP address or domain name of the SSH server.

PORT is the port number (defaults to 22).

USER is the user name.

PASSWORD is the login password or key file passphrase depending on the
authentication method used. If this argument is left out a password requester
will be used instead.

NOSSHAGENT stops the program from attempting to connect to ssh-agent.

KEYFILE can be used to change the key file used for public key authentication
(defaults to "$HOME/.ssh/id_rsa" or "HOME:.ssh/id_rsa").

MAXSB is the maximum number of lines stored in the scrollback buffer (set to
zero to disable this feature). The default value is 2000 lines.

To connect to SSH server example.org using port 123 and user name "testuser":

SSHTerm example.org PORT 123 testuser

Known issues:

- If the backspace key is not working correctly in the sudo password prompt it
might be that the remote terminal is set to expect a different sequence for
erase than ^H which is what libtsm is sending (you can check using
"stty -a"). If so you can fix this by typing "stty erase ^H" in the client
terminal.

To Do:

- Implement a GUI configuration so that running from CLI is no longer needed.

- Implement full unicode support using the outline font engine API.

Source code:

The full source code of SSHTerm is available under GPL license on github:

https://github.com/salass00/sshterm


THEN I also have OpenSSH in AmiCygnix in the /BIN folder:

BUT IT IS DATED 03 Jul 2010

README OPENSSH (AMIGAOS):

This is a port of the OpenSSH tools to AmigaOS.

The list of tools provided includes:
ssh
scp
sftp
ssh-keygen
ssh-keyscan
ssh-keysign
ssh-agent
ssh-add

how do I proceed now side "AmigaOS" and "Linux"

Thank you.

@white
[quote]
2)SSHTerm=IP user=white
3)password OK (I'm inside the terminal)
4)export DISPLAY=:10
5)xhost
access control enabled, only authorized clients can connect
YES:localuser:white


launch:
Firefox or FFPlay

is I get:
Invalid MIT-MAGIC-COOKIE-1 key
Error: cannot open display: :10
[/qiote]

so this means network part is now sorted but you need to set up X authentication to allow client to connect your AmiCygnix screen. The easiest but least secure is to just disable authentication in AmiCignyx that you have to do in guest not in the ssh window so _before_ you run SSHTerm do xhost + still on the AmiCygnix side to allow anybody to connect. If you want to do this more properly and securely search for the Invalid MIT-MAGIC-COOKIE error message and find some docs on how to use xauth to set up X authentication.

@white
With openssh all this including hostfws should not be necessary if you use ssh -Y or ssh -X but you may need to enable X11Forwarding in the sshd_config on your host machine then ssh with -Y or -X option will forward port 6010 to 6000 and set up xauth and DISPLAY itself so you don't need to do all the steps by hand and in that case you also not need hostfwd only -netdev user. If you don't use ssh X11Forwarding then you do the same by hand as above. These are two alternatives that should not be mixed, either do one or the other.

@balaton
@LiveForIt
@all ( Worldwide )

I'll do some tests but it's from the AmigaOS side that I encounter problems

And I need some help from AmigaOS users

In theory:
ssh -X
should update the .Xauthority file with 'MAGIC COOKIE' and sets the DISPLAY variable to the 'X' server.

but i miss this step

And I would like to be corrected and guided to understand what to do.

@white
I did try to explain it to you several times now so I don't know what else to do but just as a last attempt to summarise this:

There are two ways: using ssh X11forwarding or do the same manually. Choose one and don't mix them as they do the same so will not work together.

For ssh X forwarding:
- On the host where you run your X apps make sure sshd_config has X11Forwarding enabled
- Do not use any hostfwd options, ssh should take care of that
- use ssh -X or ssh -Y (not sure what's the difference, check the man page) and see if it set up DISPLAY for you, do not change that just run an X app and see if it works. To get more info use ssh -v option and read the messages, you can add more -v for more verbosity.

For doing the same without ssh X forwarding (like using SSHTerm which may not have that functionality):
- make sure the machine where you run the X app can connect to port 6000 of AmiCygnix, to do this you can use -netdev user,hostfwd or different network options and then you have to set up routing appropriately on your host.
- make sure the X server accepts connections, either disable authenrication in AmiCygnix with xhost + run in the AmigaOS not the Linux side or use xauth to add auth cookie to allowed list

One of the above should work but you should take a more systematic approach and not mix and match parts of each solution but follow one route or the other.

@balaton
I understand your answer,
don't worry, i'm just trying to find a solution.

AmiCygnix:

xhost +
access control enabled only authorized clients can connect
INET:localhost
10.0.2.15
LOCAL:
INET: kali etc.



here my sshd_config file:

# This is the sshd server system-wide configuration file. If it's
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/local/bin:/usr/bin:/bin:/usr/games

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options override the
# default value.

Includes /etc/ssh/sshd_config.d/*.conf

#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key
#HostKey /etc/ssh/ssh_host_ed25519_key

# Ciphers and keying
#RekeyLimit default none

# Logging
#SyslogFacility AUTH
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#PubkeyAuthentication yes

# Expect .ssh/authorized_keys2 to be disregarded by default in future.
#AuthorizedKeysFile .ssh/authorized_keys .ssh/authorized_keys2

#AuthorizedPrincipals File none

#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# Host-basedAuthentication
#IgnoreUserKnownHosts doesn't
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
KbdInteractiveAuthentication no

# Kerberos options
#KerberosAuthentication does not
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
#GSSAPIStrictAcceptorCheck yes
#GSSAPIKeyExchange no

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the KbdInteractiveAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via KbdInteractiveAuthentication may bypass
# the setting of "PermitRootLogin prohibit-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and KbdInteractiveAuthentication to 'no'.
Use PAM yes

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding yes
X11DisplayOffset 0
#X11UseLocalhost yes
#PermitTTY yes
PrintMotd no
#PrintLastLogyes
#TCPKeepAlive yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS no
#PidFile /run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none

# no default banner path
#Banner none

# Allow client to pass local environment variables
AcceptEnv LANG LC_*

# override default of no subsystems
Subsystem sftp /usr/lib/openssh/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
#X11Forwarding doesn't
# AllowTcpForwarding does not
# PermitTTY no
# ForceCommand cvs server

qemu-system-ppc -cpu g3 -L pc-bios -M pegasos2 -bios /home/white/Scaricati/pegasos2.rom -m 1024 -serial stdio -device sm501 -drive if=none,id=hd,file=/ home/white/Downloads/32gb.raw,format=raw -device ide-hd,drive=hd,bus=ide.1 -netdev user,id=mynet0,hostfwd=tcp::6010-:6000 -device rtl8139,netdev =mynet0 -vga none -drive if=none,id=hd1,file=/home/white/Downloads/coffin.raw,format=raw -device ide-hd,drive=hd1,bus=ide.1

the hostfwd works
because if I don't use the MAGIC COOKIE'
it is no longer required.



with AmigaOS:
xauthlist
create the .Xauthority file in AmiCygnix

now is to transfer the MAGIC COOKIE

enough for today

already the other day it took me a couple of hours
to start Metal Gear solid 4 with rpcs3
stuck at the startup screen.
only to find out that the xbox360 "GameStop" controller was incompatible with the emulator.
While if I use the original xbox360 gamepad it works perfectly.

Mysteries of computer science