stushug Posted January 25, 2022 Share Posted January 25, 2022 I can't get my Fujinet 1.6 to connect to my windows 10 machine, so I decided to go the Linux route. My self built desktop has multiple boot options so I booted into Linux Mint 20.2 and set up the nfs. NO LUCK. The orange light comes on and stays on until the Fujinet times out and reconnects to my gateway. One weird thing I just noticed also. If I boot my Atari 800 to the boot screen, I can connect from my desktop to the Fujinet web config page right away. That means I'm at least getting one way communication. Once I try to connect to the desktop from the Atari and the Fuji times out, I lose the ability to connect to the web server page from my desktop. My browser(Firefox) times out and gives the "timed out" error message. I have to power off and reboot the Atari to get back the ability to connect to the web config screen from my desktop. At one point, I was able to connect from the Atari/Fujinet to my Win 10 laptop, but now even that is NOT working. It is also a dual boot, so I'm going to setup an NFS on my laptop in Linux Mint 20.2 and see if I have any better luck. This is getting frustrating. Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted January 25, 2022 Share Posted January 25, 2022 (edited) outline exactly what you are doing to set this up... every step, every detail, with the flasher connected to get debug output and include that log along with all of that information. Edited January 25, 2022 by _The Doctor__ Quote Link to comment Share on other sites More sharing options...
mozzwald Posted January 25, 2022 Share Posted January 25, 2022 @stushug If you can successfully connect to an outside tnfs server like fujinet.online, then the FujiNet is working and the problem is likely with your local network and firewall. You could try verifying by running the command line python tnfs client found here. Run that on your linux machine and try connecting to your windows tnfs server. If it times out or can't connect, then you probably have a firewall issue on the windows machine. In your windows firewall you might be able to just open UDP port 16384 which is used by tnfsd. Quote Link to comment Share on other sites More sharing options...
stushug Posted January 25, 2022 Author Share Posted January 25, 2022 5 hours ago, _The Doctor__ said: outline exactly what you are doing to set this up... every step, every detail, with the flasher connected to get debug output and include that log along with all of that information. I'm not sure what you mean by the flasher. Quote Link to comment Share on other sites More sharing options...
stushug Posted January 25, 2022 Author Share Posted January 25, 2022 5 hours ago, mozzwald said: @stushug If you can successfully connect to an outside tnfs server like fujinet.online, then the FujiNet is working and the problem is likely with your local network and firewall. You could try verifying by running the command line python tnfs client found here. Run that on your linux machine and try connecting to your windows tnfs server. If it times out or can't connect, then you probably have a firewall issue on the windows machine. In your windows firewall you might be able to just open UDP port 16384 which is used by tnfsd. I ran it in Linux mint 20.2 in the terminal. When I tried to run the python script I got this error: "SyntaxError: Missing parentheses in call to 'print'. Did you mean print('Init complete.')?" I tried pinging my win 10 box from linux terminal and I got these results : stupe@stupe-HP-Pavilion-dv7-Notebook-PC:~$ ping 10.0.0.155 PING 10.0.0.155 (10.0.0.155) 56(84) bytes of data. 64 bytes from 10.0.0.155: icmp_seq=1 ttl=128 time=3.71 ms 64 bytes from 10.0.0.155: icmp_seq=2 ttl=128 time=4.21 ms 64 bytes from 10.0.0.155: icmp_seq=3 ttl=128 time=4.56 ms 64 bytes from 10.0.0.155: icmp_seq=4 ttl=128 time=3.98 ms 64 bytes from 10.0.0.155: icmp_seq=5 ttl=128 time=6.48 ms 64 bytes from 10.0.0.155: icmp_seq=6 ttl=128 time=4.54 ms 64 bytes from 10.0.0.155: icmp_seq=7 ttl=128 time=4.17 ms 64 bytes from 10.0.0.155: icmp_seq=8 ttl=128 time=4.04 ms 64 bytes from 10.0.0.155: icmp_seq=9 ttl=128 time=7.95 ms 64 bytes from 10.0.0.155: icmp_seq=10 ttl=128 time=3.89 ms 64 bytes from 10.0.0.155: icmp_seq=11 ttl=128 time=4.47 ms 64 bytes from 10.0.0.155: icmp_seq=12 ttl=128 time=3.77 ms 64 bytes from 10.0.0.155: icmp_seq=13 ttl=128 time=5.60 ms 64 bytes from 10.0.0.155: icmp_seq=14 ttl=128 time=4.74 ms Quote Link to comment Share on other sites More sharing options...
E474 Posted January 25, 2022 Share Posted January 25, 2022 It definitely sounds like a firewall issue. If you have a Linux desktop and linux laptop, can you use nmap on your laptop to see which ports are open on the desktop (assuming you are running the tnfs server on the desktop)? ufw is a good, simple firewall management tool, so you might have to play around with that (or its gui equivalent). Quote Link to comment Share on other sites More sharing options...
mozzwald Posted January 25, 2022 Share Posted January 25, 2022 3 hours ago, stushug said: I'm not sure what you mean by the flasher That is referring to the fujinet-flasher which has an option to display serial debug output from the fujinet over microusb. 1 hour ago, stushug said: When I tried to run the python script I got this error: "SyntaxError: Missing parentheses in call to 'print'. Did you mean print('Init complete.')? Lets forget the python tool for now 1 hour ago, stushug said: tried pinging my win 10 box from linux terminal and I got these results Ping just tells you the computer is there. 45 minutes ago, E474 said: use nmap on your laptop +1 for trying nmap. This will tell you what ports are open on the target machine. If 16384 is not open on the tnfsd server machine, you have a firewall issue. Quote Link to comment Share on other sites More sharing options...
E474 Posted January 26, 2022 Share Posted January 26, 2022 Also, what output do you get when you start the tnfs server in a terminal on the desktop? I haven't actually installed one myself, probably will try tomorrow as I just got FujiNet-PC up and running yesterday on a RPi 1, but if the server doesn't start, that will need fixing. Quote Link to comment Share on other sites More sharing options...
E474 Posted January 26, 2022 Share Posted January 26, 2022 Hi, Just had a quick look at the tnfs wiki page, what do you get for checking the services status on the desktop, e.g. sudo systemctl status tnfsd sudo systemctl status smbd This should highlight any problems with starting/keeping the services alive. Quote Link to comment Share on other sites More sharing options...
stushug Posted January 26, 2022 Author Share Posted January 26, 2022 14 hours ago, E474 said: Hi, Just had a quick look at the tnfs wiki page, what do you get for checking the services status on the desktop, e.g. sudo systemctl status tnfsd sudo systemctl status smbd This should highlight any problems with starting/keeping the services alive. I used nmap and ufw as suggested. I thought I had everything set up correctly. Then I ran these commands and got these results: stupe@stupe-desktop:~$ sudo systemctl status tnfsd Unit tnfsd.service could not be found. stupe@stupe-desktop:~$ sudo systemctl status smbd Unit smbd.service could not be found. I think the problem is I followed instructions to install an NFS server instead of TNFSD. Where can I find the installation instructions for TNFSD? Quote Link to comment Share on other sites More sharing options...
mozzwald Posted January 26, 2022 Share Posted January 26, 2022 14 minutes ago, stushug said: Where can I find the installation instructions for TNFSD? https://github.com/FujiNetWIFI/fujinet-platformio/wiki/Setting-up-TNFS-on-a-Raspberry-Pi Those are instructions for raspi but they should be similar for any linux. But, this wont help the issue with your windows tnfs server not being accessible. What are the results of nmap scanning your windows machine? Quote Link to comment Share on other sites More sharing options...
stushug Posted January 26, 2022 Author Share Posted January 26, 2022 2 hours ago, mozzwald said: https://github.com/FujiNetWIFI/fujinet-platformio/wiki/Setting-up-TNFS-on-a-Raspberry-Pi Those are instructions for raspi but they should be similar for any linux. But, this wont help the issue with your windows tnfs server not being accessible. What are the results of nmap scanning your windows machine? I downloaded the zip file, and extracted the img file to a folder I called /home/tnfsd. I got to the point where I'm supposed to edit the wifi setting in wpa_supplicant.cong but I don't what know what settings to use. Quote Link to comment Share on other sites More sharing options...
E474 Posted January 26, 2022 Share Posted January 26, 2022 Hi @stushug, The image you downloaded is specifically for a Raspberry Pi, so you'll have to follow the "advanced" installation instructions on the wiki on your desktop linux mint install. Skip the bits about using raspi-config, and start at: sudo -i Quote Link to comment Share on other sites More sharing options...
E474 Posted January 26, 2022 Share Posted January 26, 2022 I just worked my way through the advanced install, this is what a running tnfsd service should say (maybe add this to the wiki?): pi@pi3bp2:~/spectranet/tnfs/tnfsd $ sudo systemctl status tnfsd ● tnfsd.service - TNFS Server Loaded: loaded (/etc/systemd/system/tnfsd.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2022-01-26 22:52:53 WET; 6s ago Main PID: 10907 (tnfsd) Tasks: 1 (limit: 1597) CPU: 13ms CGroup: /system.slice/tnfsd.service └─10907 /usr/local/sbin/tnfsd /tnfs Jan 26 22:52:53 pi3bp2 systemd[1]: Started TNFS Server. Jan 26 22:52:53 pi3bp2 tnfsd[10907]: Starting tnfsd version 20.1115.2 using root directory "/tnfs" 1 Quote Link to comment Share on other sites More sharing options...
E474 Posted January 26, 2022 Share Posted January 26, 2022 Also, If you're using a firewall on the linux server, have a look at ufw, I have the following rules for allowing local area network (192.168.1.*) access: sudo ufw allow from 192.168.1.0/24 proto tcp to any port 22 sudo ufw allow from 192.168.1.0/24 to any app Samba sudo ufw allow from 192.168.1.0/24 to any port 16384 The above enables access with ssh, Windows shares (SMB protocol) and tnfs on port 16384. 1 Quote Link to comment Share on other sites More sharing options...
stushug Posted January 27, 2022 Author Share Posted January 27, 2022 I got as far as the "apt-get install samba samba-common-bin" step. I completed it, now I'm not sure what to do next. I clicked on the link for: git clone https://github.com/FujiNetWIFI/spectranet.git. I didn't know what to do with the info there. Quote Link to comment Share on other sites More sharing options...
stushug Posted January 27, 2022 Author Share Posted January 27, 2022 6 hours ago, mozzwald said: https://github.com/FujiNetWIFI/fujinet-platformio/wiki/Setting-up-TNFS-on-a-Raspberry-Pi Those are instructions for raspi but they should be similar for any linux. But, this wont help the issue with your windows tnfs server not being accessible. What are the results of nmap scanning your windows machine? This is a scan of my windows machine while running linux mint 20: Starting Nmap 7.80 ( https://nmap.org ) at 2022-01-26 19:08 EST Nmap scan report for stupe-desktop (10.0.0.155) Host is up (0.0000040s latency). Not shown: 996 closed ports PORT STATE SERVICE 111/tcp open rpcbind 139/tcp open netbios-ssn 445/tcp open microsoft-ds 2049/tcp open nfs Nmap done: 1 IP address (1 host up) scanned in 0.14 seconds Quote Link to comment Share on other sites More sharing options...
mozzwald Posted January 27, 2022 Share Posted January 27, 2022 6 minutes ago, stushug said: This is a scan of my windows machine while running linux mint 20: nmap does not scan UDP ports by default. Here is an example of testing fujinet.online and specifying the port we want to check (16384 / tnfs): $ sudo nmap -sU fujinet.online -p 16384 Starting Nmap 7.60 ( https://nmap.org ) at 2022-01-26 18:16 CST Nmap scan report for fujinet.online (157.245.127.133) Host is up (0.030s latency). PORT STATE SERVICE 16384/udp open|filtered connected Nmap done: 1 IP address (1 host up) scanned in 0.81 seconds Quote Link to comment Share on other sites More sharing options...
E474 Posted January 27, 2022 Share Posted January 27, 2022 You need to type in the git command at the command line: git clone https://github.com/FujiNetWIFI/spectranet.git without confusing matters too much (I hope), this is how I would download the latest sources for the tnfs server into a directory called "example" in my home directory: pi@pi3bp2:~ $ mkdir example pi@pi3bp2:~ $ cd example/ pi@pi3bp2:~/example $ git clone https://github.com/FujiNetWIFI/spectranet.git Cloning into 'spectranet'... remote: Enumerating objects: 5260, done. remote: Counting objects: 100% (5/5), done. remote: Compressing objects: 100% (5/5), done. remote: Total 5260 (delta 0), reused 1 (delta 0), pack-reused 5255 Receiving objects: 100% (5260/5260), 5.90 MiB | 1.68 MiB/s, done. Resolving deltas: 100% (3708/3708), done. pi@pi3bp2:~/example $ ls spectranet pi@pi3bp2:~/example $ Quote Link to comment Share on other sites More sharing options...
E474 Posted January 27, 2022 Share Posted January 27, 2022 Hi @mozzwald, Side question on tnfs server network port protocol. Is it only udp, or is tcp used as well? I had assumed it was both, but would like to tighten up my ufw rule if it is only udp? Quote Link to comment Share on other sites More sharing options...
mozzwald Posted January 27, 2022 Share Posted January 27, 2022 2 minutes ago, E474 said: Hi @mozzwald, Side question on tnfs server network port protocol. Is it only udp, or is tcp used as well? I had assumed it was both, but would like to tighten up my ufw rule if it is only udp? while tnfs can technically run over tcp, it is not implemented so you only need udp open Quote Link to comment Share on other sites More sharing options...
E474 Posted January 27, 2022 Share Posted January 27, 2022 Thanks @mozzwald! For the record, correct ufw rule would be: sudo ufw allow from 192.168.1.0/24 proto udp to any port 16384 For example: pi@pi3bp2:~ $ sudo ufw allow from 192.168.1.0/24 proto udp to any port 16384 Rule added pi@pi3bp2:~ $ sudo ufw status numbered Status: active To Action From -- ------ ---- [ 1] 22/tcp ALLOW IN 192.168.1.0/24 [ 2] Samba ALLOW IN 192.168.1.0/24 [ 3] 16384/udp ALLOW IN 192.168.1.0/24 pi@pi3bp2:~ $ Quote Link to comment Share on other sites More sharing options...
stushug Posted January 27, 2022 Author Share Posted January 27, 2022 I just ran an nmap scan in windows, here is a pdf of the results. win nmap scan.pdf Quote Link to comment Share on other sites More sharing options...
stushug Posted January 27, 2022 Author Share Posted January 27, 2022 54 minutes ago, mozzwald said: nmap does not scan UDP ports by default. Here is an example of testing fujinet.online and specifying the port we want to check (16384 / tnfs): $ sudo nmap -sU fujinet.online -p 16384 Starting Nmap 7.60 ( https://nmap.org ) at 2022-01-26 18:16 CST Nmap scan report for fujinet.online (157.245.127.133) Host is up (0.030s latency). PORT STATE SERVICE 16384/udp open|filtered connected Nmap done: 1 IP address (1 host up) scanned in 0.81 seconds I just ran the scan using the command as you posted: stupe@stupe-desktop:~$ sudo nmap -sU fujinet.online -p 16384 [sudo] password for stupe: Starting Nmap 7.80 ( https://nmap.org ) at 2022-01-26 20:12 EST Nmap scan report for fujinet.online (157.245.127.133) Host is up (0.027s latency). PORT STATE SERVICE 16384/udp open|filtered connected Nmap done: 1 IP address (1 host up) scanned in 0.63 seconds 1 Quote Link to comment Share on other sites More sharing options...
mozzwald Posted January 27, 2022 Share Posted January 27, 2022 12 minutes ago, stushug said: I just ran the scan using the command as you posted you need to change 'fujinet.online' to the ip address of your windows computer, like so: sudo nmap -sU YOUR.WINDOWS.COMPUTER.IP.ADDRESS.GOES.HERE -p 16384 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.