HH0718

Members
  • Posts

    31
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

HH0718's Achievements

Newbie

Newbie (1/14)

3

Reputation

  1. Has anyone tried using this as a TFTP server? I have it installed and running on the right ports. However, when I try to get a file from the untracked list using a tftp command, I can't seem to get the file. Example on windows tftp client (firewall configured too): C:\Windows\system32>tftp -i 172.16.0.2 get /assets/test.txt Connect request failed I have also tried without the `/assets/` portion The file is there but can't seem to get it to download from any tftp on any device.... windows 10, cisco wlcs, cisco switches, etc. Any thoughts?
  2. Is that supposed to be funny? How to improve you’re WiFi repeater signal: Step 1: throw repeater in trash. Step 2: never buy a repeater/extender ever again. Step 3: ? Step 4: profit.
  3. You're more than welcome to contribute to it.... it is free and open source after all. https://github.com/Ombi-app/Ombi How to improve you’re WiFi repeater signal: Step 1: throw repeater in trash. Step 2: never buy a repeater/extender ever again. Step 3: ? Step 4: profit.
  4. I installed and setup the unraid side as well as my Ubiquiti firewall/network. Still no go. Currently getting PXE-E18: server response timeout. The local assets are there. I temporarily disabled my entire firewall just to make sure. Any thoughts? Start PXE over IPv4 Station IP address is 172.16.0.163 Server IP address is 192.16.0.2 NBP filename is boot.cfg NBP filesize is 0 Bytes PXE-E18: Server response timeout.
  5. I mean, if you have the money.. may as well just drop a network line for less than the cost of the mesh and commercial grade repeaters. And even with the setup you mentioned, not a good solution. Not with the available tech today. How to improve you’re WiFi repeater signal: Step 1: throw repeater in trash. Step 2: never buy a repeater/extender ever again. Step 3: ? Step 4: profit.
  6. I’d rather have people use power line adapters. But people understand WiFi better than power line adapters by name so... How to improve you’re WiFi repeater signal: Step 1: throw repeater in trash. Step 2: never buy a repeater/extender ever again. Step 3: ? Step 4: profit.
  7. As a wireless professional, this murdered my soul a bit. Don’t use WiFi repeaters. Just don’t. Lol Sent from my iPhone using Tapatalk
  8. The biggest hurdle, “half-duplex”. Sent from my iPhone using Tapatalk
  9. I can appreciate you comment. And I understand the demand for other features. But I maintain that API should have been (always) at the top of the priority list. Sent from my iPhone using Tapatalk
  10. Yes... soon TM. I have seen that many times but not roadmaps or posts about it which leads me to believe it’s not priority. Believe me me when I say I don’t mean to come off the wrong way. I’m just perplexed it’s taken so long to start implementing an API for unraid. Sent from my iPhone using Tapatalk
  11. Thanks! Sent from my iPhone using Tapatalk
  12. I am very disappointed API is not on here unless it's already seriously in development.
  13. I hate to be one of those "demanding" type of users, but I was curious if there was going to be a V4 update or a separate docker container altogether?
  14. I had ssh enabled on a certain port (not 22) and saw there were thousands of login attempts. Probably bruteforce... Not sure it has anything to do with it but I disabled it. See if it helps.
  15. Well, my unraid server is on 172.16.0.2 and i'm not certain if some of the apps are considered as 172.16.0.2 with outbound network traffic as there are a few apps that have their own IP address. But that' gave me something to look into. Thanks for your feedback. Edit: Non of the ports listed in the log map to any of my apps in docker.