Messages

16

Beta / Re: version 2.4

« on: May 26, 2020, 09:37:50 AM »

First results are in:

I couldn't get it to run on Windows 2000 SP4, so far. Have to check what the fresh system still lacks, in comparison to the established one that runs HFS fine. Maybe it is the IPv6 TP.

Important hint for Windows XP users:

On a standard Windows XP installation with SP3, HFS will start, no problem, but it will be disabled and unable to be put online. That's because a standard install is missing the IPv6 component.
Server will be permanently OFFLINE until you:
1. Open a command prompt,
2. issue a

Code: [Select]

netsh int ipv6 install command, and
3. reboot.

With activated IPv6, HFS will  be started and online.

17

Beta / Re: version 2.4

« on: May 26, 2020, 05:19:16 AM »

hi MarkV! win98? wow thanks for reporting.
I'm glad we are still ok with XP, since some people here still use it. I'll do my best without killing me tho. Time is short.

I hope you've seen the smileys. Just checked some old VMs and PCs and noticed. Personally, I'll start complaining when it stops working on Windows 7, OK?

Currently, Windows 2000 and up are still OK (last tested 2.4beta1). Please note that IPv6 support is an addon package for Windows 2000 and Windows XP. No idea how HFS will perform if the IPv6 package is not installed on these OS.
Might check it out. That's what we did in the old days, correct?

18

Beta / Re: version 2.4

« on: May 24, 2020, 03:27:33 AM »

Hi,

thanks for the IPv6 support, think I was one of the folks bringing up the subject, some time ago.  Great to see that there is still progress and the project alive.
Github repo is another nice addon, no need to search the whole forums for the one download you might have missed... 

However, there is no light without shadow, so I have to announce that the 2.4 versions of HFS finally, and officially, stopped working on Windows 98 SE! 
Absolutely nothing needs to be done about this, it was inevitable. 2.3m works fine on 98SE, and it's amazing that it outlived the OS by many years. 
Just FYI, 2.4beta1 still runs fine on Windows 2000 SP4.

Gotta stop now, running out of smileys.  Keep up the good work and stay safe! Bye for now.

19

Beta / Re: version 2.4

« on: November 08, 2018, 10:37:16 PM »

Hi, just passing by, and I see you are all still busy. HFS has come a long way (I still remember the good old days when it started). No reason to stop it.

20

HFS ~ HTTP File Server / Re: New version: 2.3i

« on: June 15, 2016, 11:07:07 PM »

First time I've seen a warning message at update time. Unfortunately that very warning message blocks the auto-update that would have brought HFS up to date without much adoe! 

Gratz for fixing that fast.

21

router & port problems / Re: Port 80 cannot be open (After update to Win 10)

« on: April 02, 2016, 04:59:44 AM »

Although the topic is old, here's one addendum: Port 80/443 might also be blocked by the Skype application.

22

router & port problems / Re: How to run Apache and HTTPFileServer both on port 80?

« on: April 02, 2016, 04:55:29 AM »

One problem is semantics here. You can technically run many applications on port 80 if you want, but you can't run more than one per socket. Network applications listen on sockets, not ports.

In Windows, you can apply multiple IPs to one NIC. So you can run one process per IP+port (=socket). If you apply IPs 192.168.0.10 and 192.168.0.11 to the NIC, you can run Apache on 192.168.0.10:80 and HFS on 192.168.0.11:80.

Sadly, there is one major blocking issue: Anyone behind a router can only forward each port once - to one dedicated target IP. Forwarding the same port to multiple IPs would be ambiguous.
So the Apache Forward/Reverse Proxy thing is still the best solution.

Disclaimer: IPv6 ought to solve all of this by restoring the network end-to-end principle.

23

Bug reports / Re: Zero filesize and Unauthorized

« on: March 18, 2016, 10:27:09 AM »

Little Addendum: Seeing a zero-Byte sized file in Explorer does not necessarily mean that the file doesn't have any contents or meaning.

1. Might be write-opened by any process. File size information might not be updated immediately.
2. The file's main data stream might be empty, indeed, but further data can also hide in Alternate Data Streams.
3. It may encode information through its attributes like timestamp or size, also its mere presence might be a switch (flagfile).

Just something to consider.

24

Bug reports / Re: [SOLVED] Uploading a MD5 file is forbidden?...

« on: March 18, 2016, 09:54:50 AM »

I'm reasonably sure it's in order to not allow uploading of fake MD5 files that would confuse users and might even hide dangerous malware.

Besides, MD5 is broken for a long time. HFS should change to SHA512.

25

HFS ~ HTTP File Server / Re: IPv6 not possible

« on: September 20, 2015, 07:55:33 PM »

For testing IPv6 in LAN:
- All adapters in Windows should have their respective fe80:: addresses already. One of the strengths of IPv6 - self configuration of at least the basic IP addresses.
- You can distribute ULAs (equvalent to LAN IPs in IPv4) via tools like dibbler or Jagornet. Use IPv6 addresses in the fd00::1 to fdff:ffff:ffff:ffff:ffff:ffff:ffff:ffff range.
- Many Routers can already distribute ULAs even if the ISP doesn't support IPv6, yet. So you can test in LAN without using one of the tools mentioned above.

Check IPv6 addresses:

Code: [Select]

netsh int ipv6 show addr or

Code: [Select]

ipconfig /all

26

HFS ~ HTTP File Server / Re: This page can’t be displayed

« on: September 20, 2015, 07:45:53 PM »

Also, some Network Cards and WiFi equipment might go into a "link down power save" mode after being idle.

Next possibility: The router at the server side does hang up the Internet connection after being idle for xx minutes. Note that, in case that happens, only connection attempts from the inside will cause the router to re-dial, connections from the outside will be dropped instead.

27

HFS ~ HTTP File Server / Re: This page can’t be displayed

« on: September 17, 2015, 11:46:58 PM »

Do you see anything logged, server-side, when the side appears to be offline? Could be a firewall blocking so the client doesn't even make it to the server.

28

HFS ~ HTTP File Server / Re: This page can’t be displayed

« on: September 17, 2015, 11:20:50 PM »

@bmartino1: Terayon is a "RAWR Designs" Template. Obviously, rejetto and TSG would be the right people to speak to.
http://www.rejetto.com/forum/rawr-designs/latest-releases/

@DigitaLWizarD: The VFS (Virtual File System) is the tree of resources people can access. It is stored as a *.vfs file. It can become corrupted so you were asked if you have a backup.

29

HFS ~ HTTP File Server / Re: IPv6 not possible

« on: September 15, 2015, 08:41:11 PM »

There is *much* more than just a difference in number of possible IPs. The restoration of the "end-to-end" principle, requiring no more NAT or port forwarding, for example. No requirement of DHCP due to automatic self-configuration of IP addresses, another one.

There's even the problem of transitioning technologies like DS-Lite. With DS-Lite, HFS users are out of luck since they won't get any public IPv4 address anymore, only an IPv6. That makes HFS unreachable in those environments.

30

HFS ~ HTTP File Server / Re: IPv6 not possible

« on: September 14, 2015, 09:33:16 PM »

Currently HFS either doesn't bind to IPv6 sockets (like [::1]:80 or [2001:db8:1::2ac]:80), or it can't respond. Trying http://[::1] in Firefox gets me a 'Problem loading page' error, even if I set it as custom IP (might also mean HFS can't handle the IPv6 address format).

Unfortunately I know nothing about coding. But, for testing, as per the IPv6 definition, every system since Vista does have at least the ::1 (localhost) and the fe80:: (Interface) IPv6 addresses.