- This topic has 16 replies, 3 voices, and was last updated Mar 28-6:19 pm by christophe.
-
AuthorPosts
-
March 25, 2019 at 12:05 pm #19703Moderator
christophe
I turned an old 18-ish years old desktop into a droopy server. It is up & running, but my other computers cannot connect. I followed the FAQ on droopy (very easy – on other computer type in the address on the window title bar), but the non-droopy-serving computer keeps trying to connect until it times out. Both computers running antiX 17.4. I’ve rebooted (my last-ditch action when everything else has failed), and reread the steps, but it just doesn’t connect. The serving computer in an old Athlon without SSE2; does that make any difference? Unfortunately the FAQ gives no troubleshooting steps. Any pointers? (And what info can I post to help you help me?)
Thanks in advance, guys!
- This topic was modified 4 years, 1 month ago by christophe.
confirmed antiX frugaler, since 2019
March 25, 2019 at 12:41 pm #19705Moderator
christophe
::I attached the full info for the droopy-server computer below.
Also, I opened a browser on the droopy server, & went to http://localhost:8800/ but there are no files shown to download (unlike the picture on thew faq). It’s got buttons at top to upload, but no files/folders listed on lower part of screen to download. I placed folders in ~/Public & droopy SAYS it is serving /home/cj/Public. (attached screenshot) I’m stuck.
- This reply was modified 4 years, 1 month ago by christophe. Reason: typo/clarification
- This reply was modified 4 years, 1 month ago by christophe.
confirmed antiX frugaler, since 2019
March 25, 2019 at 2:18 pm #19710Moderator
caprea
::It took me some time to see what’s maybe wrong.
You are trying to share folders , not files. Folders will not be shown on the http://localhost:8800/If this is not the problem, maybe you are behind a firewall from your router and the port 8800 is not open.
March 25, 2019 at 2:44 pm #19712Moderator
christophe
::ahh. I see.
1. Yep. I put a file in ~/Public & now it’s visible. So one issue solved.
2. None of my computers can connect to any of the others via droopy. They all time out. I am running ufw on each with just the default configuration.
So it looks like ufw is blocking it, right?
And if so, then how to remedy? Just remove ufw? But is that a good idea from a security viewpoint?confirmed antiX frugaler, since 2019
March 25, 2019 at 2:51 pm #19713Moderator
caprea
::Is this the adress you are typing in on the other system ?
http://10.0.0.21:8800
like shown in you screenshotMarch 25, 2019 at 2:56 pm #19714Moderator
christophe
::Yes. That address from a different computer on my home network.
confirmed antiX frugaler, since 2019
March 25, 2019 at 3:06 pm #19715Moderator
caprea
::I think it’s the firewall of your router, but SamK is the expert for droopy and file-sharing.
So maybe wate.March 25, 2019 at 3:11 pm #19716Moderator
christophe
::Gotcha. I’ll wait.
Thanks for your help thus far. Much appreciated.confirmed antiX frugaler, since 2019
March 25, 2019 at 3:13 pm #19717Moderator
caprea
::Or maybe simply try it out with ufw disabled on the systems.
If it works then, it’s not so hard to open the port in ufw.
March 25, 2019 at 4:16 pm #19719Moderator
christophe
::Yes. Good idea: I’ll disable ufw on the droopy-server, then try to connect. If works, I’ll redo ufw & open that port. This is all new but I can figure it out. I’ll update (& probably ask more help).
Thanks again!confirmed antiX frugaler, since 2019
March 25, 2019 at 4:25 pm #19720Moderator
caprea
::On both systems
you can also try
sudo ufw allow 8800
sudo ufw allow out 8800
You can look with
sudo ufw status
if everythings enabled now
March 25, 2019 at 6:59 pm #19725Moderator
christophe
::OK. I disabled ufw on server and now it works as expected.
“man ufw” is quite complex. I wasn’t sure how to proceed. Then I saw your (caprea’s) last reply – thanks for that! Be back soon…confirmed antiX frugaler, since 2019
March 25, 2019 at 7:16 pm #19726Moderator
christophe
::YES! It works as advertised!
Thanks, caprea. Big time thanks.
Now, I assume my computer is open in port 8800 ONLY to my home network, right?
One related question:
I am wondering if enabling ufw is necessary (although i have it enabled): in my searching, I came across a page from Netgear (my router manufacturer) which states that it blocks all unauthorized traffic by default. So my question is this: is that default firewall in the router enough/sufficient?
What is your opinion on this. I only know what I read on this, and every article I read seems almost “paranoid” on the subject (and i am sympathetic with that frame of mind – I don’t want any private/banking/etc info getting out there).
But maybe you (and the rest of my antiX family) have a “real-world” understanding that I don’t have. What do you think about this issue?
- This reply was modified 4 years, 1 month ago by christophe.
confirmed antiX frugaler, since 2019
March 25, 2019 at 8:19 pm #19728Moderator
caprea
::If you open gufw from the control-centre (under network), unlock it and you can see the rules the above commands created.
They are certainly not the safest rules.
If you click on one rule and then on the minus, you can remove it.
Then go to edit in gufw and chose add rule. Then click on extended (the button simple would produce the ones you already have).There you can set ip-adresses and ports and in/out.
You maybe have to fiddle a bit, till everything works.
Every not working rule you can always remove if necessary.
You will have to make a rule for each participating computer in your home network for in/out.March 26, 2019 at 6:42 pm #19764Moderator
christophe
-
AuthorPosts
- You must be logged in to reply to this topic.
