The setup script assumes the file share is pingable about teslausb HOT 8 CLOSED

The principal reason is because that's how it the script was written by the original author and we haven't found a need to change it.

Looking around on the internet, I could speculate that perhaps the reason it was written that way was in case the mount happened before name resolution happened. But I've read that there's a "netfs option that could also address this.

It sounds like you're saying that your archive server

1. Doesn't have a stable IP address
2. Isn't pingable

Is that right?

from teslausb.

I'm not sure how stable the IP address is, since this is fully Azure hosted, but they definitely block icmp ping on that address.

from teslausb.

it looks like the 'hping3' package can be used hping3 -c 1 -S -p 445 $hostname instead in order to test for connectivity to a cifs share.

from teslausb.

Does hping3 work for all CIFS shares, on Windows, MacOS, Samba, others? If so, it seems reasonable to replace the ping test with that test for CIFS archives.

The alternative would be to add Azure File Share as another hosting technology. The current organization of the files actually makes that option easier, but it would be nice to consolidate all the CIFS options.

from teslausb.

I have only tested with azure's file shares, but I believe it should work. It works by using a TCP SYN to test if the port is open and listening.

from teslausb.

If you'll submit a PR I'll be happy to merge it into a branch in this repo to increase the chance that someone will try out the change with a Windows share.

from teslausb.

#92

I've done some very basic testing locally with my windows 10 pc, and a freenas samba server I have running, and hping3 worked well.

from teslausb.

Merged!

from teslausb.