I don't know how to help you. The only options I see, are : -Wifi security protocol from your router not handled by minibian (distrib used for the Linux layer)-Incompatibility of the Pi 3 wifi chipset with your router.Try to google "Raspberry Pi wifi not working with the name of your router" and may be you'll find something. Is the Ethernet connection working at least?

I hadn't seen your dmesg screenshot and I believe you found the issue by yourself.For whatever reason, Linux is renaming the ethernet and Wifi port from eth0 and wlan0 to eth1 and wlan1.My dmseg print is different, so I guess that they may have updated the chipset.As I wrongly assumed that this naming convention was not going to change, a Pi 3 having basically only 1 ethernet and 1 wifi port, I have limited the setup to these 2 ports.So it should be easy to fix and you can do it from Aranym :In h:/.system/ you have 3 files :interfaces which the active setup file for network connectioninterfaces.eth which is the template for ethernet connectioninterfaces.wifi which is the template for wifi connection

Edit these 3 files with QED and change all references to eth0 by eth1 and wlan0 by wlan1, do a cold reboot and you should be ok.

Faucon2001 wrote:I hadn't seen your dmesg screenshot and I believe you found the issue by yourself.For whatever reason, Linux is renaming the ethernet and Wifi port from eth0 and wlan0 to eth1 and wlan1.My dmseg print is different, so I guess that they may have updated the chipset.As I wrongly assumed that this naming convention was not going to change, a Pi 3 having basically only 1 ethernet and 1 wifi port, I have limited the setup to these 2 ports.So it should be easy to fix and you can do it from Aranym :In h:/.system/ you have 3 files :interfaces which the active setup file for network connectioninterfaces.eth which is the template for ethernet connectioninterfaces.wifi which is the template for wifi connection

Edit these 3 files with QED and change all references to eth0 by eth1 and wlan0 by wlan1, do a cold reboot and you should be ok.

It's strange that on the aranym side ifconfig lists eth0 and it comes up fine. On the linux side is eth1 and wlan1. If I change the references in those files to eth1, I think the aranym side might not work.

Anyway, I have it working as I mentioned in the post above. I'm using a ethernet to wifi adapter so in effect I have a wireless connection running.

No it's not strange, the name of the interface in Aranym has nothing to do with the name of Linux interface. They are 2 differents machines. They have the same name, but it's pure coincidence.Remember the bridge is done on tap0, Aranym doesn't know anything of the name of the Linux interface and don't care. What is importante are the addresses of the bridge, in this case 192.168.1.50, 192.168.1.51The files interfaces.* are the setup files of Linux network, not Aranym network. They are visible from Aranym because I made a simlinks for that purpose. h:/.system/interfaces is linked to /etc/network/interfaces on the Linux side.Modify the files as indicated and it will work.Now, I may have found the route cause of this issue; I'll look at it tomorrow, time to go to bed now.

Yes, web browsing it's sloooow. As said before, no improvement to expect from Netsurf as today web rendering need a hell of power way out of the reach of vintage computer, even with JIT emulation, and its getting worse everyday with the recent generalization of https use instead of http. Web rendering proxy is an option that I must investigate, especially if it can run on the Linux host. Anyway, network for BeePi is useful to mount external network shares, ftp and mails, and as network shares are managed by the host you have the full bandwidth. I use it a lot and I have mounted my Mac download folder which is the mos practical way to transfer files.

Use Linux side address. But I don't understand what you want to achieve.If you want to connect Aranym to your others machines, you'd better share a folder on your mac or PC via SMS and mount it in Aranym, than doing the opposite, it will be much faster and easier.

BeeKey distribution is very nice and user-friendly! Congratulations, Faucon2001.I wanted to see if it would also work with my current hobby project, Amiga + Vampire V2 + EmuTOS. So I extracted the FreeMiNT distribution from BeeKey (maybe I could just have used EasyAraMiNT?), reorganized partitions, updated FreeMiNT kernel and fVDI driver... and it just worked See result there.

For those who are interested, I posted more details on the Apollo Forum.

Have you done this, as explained previously?In h:/.system/ you have 3 files :interfaces which the active setup file for network connectioninterfaces.eth which is the template for ethernet connectioninterfaces.wifi which is the template for wifi connectionEdit these 3 files with QED and change all references to eth0 by eth1 and wlan0 by wlan1, do a cold reboot and you should be ok.

Normally /etc/network/interfaces is linked to "interfaces" file in h:/system/, may be the link is broken?

Gaiyan, I forgot to answer your TT installation question ; yes it's possible but it won't be easy to do as EasyAraMint is specifically setup for Aranym.The easiest way may be to install first easymint : http://atari.st-katharina-apotheke.de/h ... texte=newsInstall nvdi and then copy manually and selectively the content of C and H (you can use a USB key to transfer files from BeePi disk images), but don't copy directly Auto, Gemsys and Mint directories to your TT as they are specific to Aranym. You may have also to edit mint and xaaes configuration files, based on the one in EasyAraMint. So quite a lot to do indeed.I should receive my CT60e soon, so may be I will do a specific install for 030 machines.