Ah, thanks. It's been a long time since I have had to worry about that. :) On Thu, Jan 27, 2022 at 9:55 AM Tilghman Lesher <tilgh...@meg.abyt.es> wrote:
> It will, as long as both client and server support the related (raw) > commands: > > > https://unix.stackexchange.com/questions/91602/is-there-any-ftp-command-to-resume-upload > > On Thu, Jan 27, 2022 at 8:44 AM Kent Perrier <kent.perr...@gmail.com> > wrote: > > > > IIRC, sftp/ftp doesn't do resume. rsync will but I doubt you will get > support for that. > > > > On Thu, Jan 27, 2022 at 4:27 AM Paul Boniol <paul.bon...@gmail.com> > wrote: > >> > >> I did a quick search of their documentation. It appears they support > uploads via web interface, Samba, and ftp / sftp. I'd recommend sftp even > if the content will be public. The ftp protocols are very likely the most > fault tolerant option. Also command line access gives you options for > automation if desired. > >> > >> Paul > >> > >> On Thu, Jan 27, 2022 at 1:09 AM Michael L <helpwithmath...@gmail.com> > wrote: > >>> > >>> I tried uploading to https://8.39.99.30 ; it's about the same. > >>> > >>> It's a drag and drop web interface. When it interrupts, I have to > reload the web page and drag/drop again for it to continue. I would very > much like to do it via command line and auto retry which I suppose should > work since we have the IP address (I had to get it from nslookup). > >>> > >>> I tried the command line ftp, but that will probably not work without > ftp access being set up on their end, which I will ask for. > >>> > >>> On Wed, Jan 26, 2022 at 3:28 PM Paul Boniol <paul.bon...@gmail.com> > wrote: > >>>> > >>>> What command/program are you using to send the files? It may be > possible to set a parameter to automatically rerty. > >>>> > >>>> On Wed, Jan 26, 2022, 8:50 AM Michael L <helpwithmath...@gmail.com> > wrote: > >>>>> > >>>>> AS ALWAYS, THANK YOU ALL FOR THE EXCELLENT INFO. > >>>>> I did upload a lot from our 10Mbps Comcast Business connection in > the past, generally slow and historically Comcast has been a disastrous > connection. > >>>>> I should say that about July 2020 when I first uploaded to Telvue on > my newly installed AT&T Fiber connection, I could upload extremely quickly, > comparable to both Charter and Cox Media, not so in the last 6+ months. > And if I try this at night I get slightly (but noticeably) less slow > results. Particularly frustrating, the last few days it took over twice as > long to upload to Telvue. AND normally the upload is not set and forget > ... it interrupts and I (the customer) have to reload and continue the > upload, which at least picks up where it left off. This happens more when > I try to upload multiple files at once; if I could just set 10 or 12 files > to uploading and come back later to a completed job, then I wouldn't care > as much that it's slow. > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> On Wed, Jan 26, 2022 at 7:00 AM Gibson Prichard <gib...@prichard.tv> > wrote: > >>>>>> > >>>>>> First, when I connect to connect.telvue.com, it resolves as > 8.39.99.30 and NOT 35.224.46.35, as you listed. There seems to be two or > more entries in their DNS, but 8.39.99.30 seems to be on a Level3 > (CenturyLink) backbone in Philadelphia and 35.224.46.35 resolves for me as " > 35.46.224.35.bc.googleusercontent.com" on completely different IP space. > When I go to https://35.224.46.35, I do get the Telvue website, but the > SSL cert is from another entity - "giown1007.siteground.biz," which would > seem that this could be a Google-hosted content distribution network. I > will note that "telvue.com" resolves for to the 35.224.46.36 address, > while "connect.telvue.com" resolves to 8.39.99.30 instead. Can you try > uploading to Telvue through https://8.39.99.30 and see if that IP or > server is faster for you? > >>>>>> > >>>>>> Secondly, and to your question as to whether you would be helped by > a file upload service, I don't know that you would, since a file upload > service (HighTail or WeTransfer or others) is is just a repository in the > cloud to store files, which doesn't ultimately deliver your content to your > destination of connect.telvue.com. Perhaps you could try to upload > through a friend's Comcast connection as an alternative to your AT&T one to > see if there really is an interconnect or throttling issue, but I don't > think a file transfer service is your answer. It seems to me that > https://connect.telvue.com / IP 35.224.46.35 is on a low-bandwidth or > oversubscribed circuit or server farm. I don't see an interconnection issue > to either site. > >>>>>> > >>>>>> Good luck. > >>>>>> > >>>>>> Gibson Prichard > >>>>>> Nashville, TN > >>>>>> gib...@prichard.tv > >>>>>> > >>>>>> > >>>>>> > >>>>>> On Wed, Jan 26, 2022 at 2:44 AM Michael L < > helpwithmath...@gmail.com> wrote: > >>>>>> > > >>>>>> > Hello NLUG, > >>>>>> > Do I need a file transfer service? Insight and suggestions will > be much appreciated as always > >>>>>> > I upload 22GB to 31GB of video weekly to Comcast and lesser > amounts to Cox Media and Charter- > >>>>>> > For Comcast I have to upload at this > >>>>>> > URL: https://connect.telvue.com / IP 35.224.46.35 > >>>>>> > By comparison, uploading to COMCAST TAKES OVER 8 TIMES LONGER ... > ON A GOOD DAY!!! > >>>>>> > > >>>>>> > Here's a little graphic I sent them showing how slow Comcast > Telvue is compared to Charter and Cox Media on a 1.9GB test file > >>>>>> > (AND I SENT THEM THE TEST FILE SO THEY CAN TRY IT FOR THEMSELVES): > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > Charter CoxMedia Comcast Telvue > >>>>>> > IS OVER > >>>>>> > 2m47s 2m34s 22m21s <<<< 8 TIMES > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> > SLOWER > >>>>>> > > >>>>>> > > >>>>>> > I've been emailing Comcast's contact for 4 to 6 months about how > slow this is and the only response I ever get is: "seems to be working > fine" <<--- i.e., Not our problem; can't help ya. Finally Comcast > management gets out of bed after months of hibernation and tells me: > >>>>>> > > >>>>>> > > >>>>>> > >>>>>> -- > >>>>>> -- > >>>>>> You received this message because you are subscribed to the Google > Groups "NLUG" group. > >>>>>> To post to this group, send email to nlug-talk@googlegroups.com > >>>>>> To unsubscribe from this group, send email to > nlug-talk+unsubscr...@googlegroups.com > >>>>>> For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > >>>>>> > >>>>>> --- > >>>>>> You received this message because you are subscribed to the Google > Groups "NLUG" group. > >>>>>> To unsubscribe from this group and stop receiving emails from it, > send an email to nlug-talk+unsubscr...@googlegroups.com. > >>>>>> To view this discussion on the web visit > https://groups.google.com/d/msgid/nlug-talk/CA%2BJ3mBC8sN1DOukS7ogSBXUvAS8Faqh364%3Dx2ZU1vFXWcFzivw%40mail.gmail.com > . > >>>>> > >>>>> -- > >>>>> -- > >>>>> You received this message because you are subscribed to the Google > Groups "NLUG" group. > >>>>> To post to this group, send email to nlug-talk@googlegroups.com > >>>>> To unsubscribe from this group, send email to > nlug-talk+unsubscr...@googlegroups.com > >>>>> For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > >>>>> > >>>>> --- > >>>>> You received this message because you are subscribed to the Google > Groups "NLUG" group. > >>>>> To unsubscribe from this group and stop receiving emails from it, > send an email to nlug-talk+unsubscr...@googlegroups.com. > >>>>> To view this discussion on the web visit > https://groups.google.com/d/msgid/nlug-talk/CALdmzXabxzguvSszc5BZpMPm-yFKM0Ca0fJy12G6kK%2BKP4X54w%40mail.gmail.com > . > >>>> > >>>> -- > >>>> -- > >>>> You received this message because you are subscribed to the Google > Groups "NLUG" group. > >>>> To post to this group, send email to nlug-talk@googlegroups.com > >>>> To unsubscribe from this group, send email to > nlug-talk+unsubscr...@googlegroups.com > >>>> For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > >>>> > >>>> --- > >>>> You received this message because you are subscribed to the Google > Groups "NLUG" group. > >>>> To unsubscribe from this group and stop receiving emails from it, > send an email to nlug-talk+unsubscr...@googlegroups.com. > >>>> To view this discussion on the web visit > https://groups.google.com/d/msgid/nlug-talk/CAL9PgS08uaYAYQkcwDqYz3tmE7fW6WwFBZyjmWzq8eHAYAwnBQ%40mail.gmail.com > . > >>> > >>> -- > >>> -- > >>> You received this message because you are subscribed to the Google > Groups "NLUG" group. > >>> To post to this group, send email to nlug-talk@googlegroups.com > >>> To unsubscribe from this group, send email to > nlug-talk+unsubscr...@googlegroups.com > >>> For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > >>> > >>> --- > >>> You received this message because you are subscribed to the Google > Groups "NLUG" group. > >>> To unsubscribe from this group and stop receiving emails from it, send > an email to nlug-talk+unsubscr...@googlegroups.com. > >>> To view this discussion on the web visit > https://groups.google.com/d/msgid/nlug-talk/CALdmzXZpS%2Br45_OeiXW8ohan1H0vLcBACxNw0ZA6iZCsfwyWrg%40mail.gmail.com > . > >> > >> -- > >> -- > >> You received this message because you are subscribed to the Google > Groups "NLUG" group. > >> To post to this group, send email to nlug-talk@googlegroups.com > >> To unsubscribe from this group, send email to > nlug-talk+unsubscr...@googlegroups.com > >> For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > >> > >> --- > >> You received this message because you are subscribed to the Google > Groups "NLUG" group. > >> To unsubscribe from this group and stop receiving emails from it, send > an email to nlug-talk+unsubscr...@googlegroups.com. > >> To view this discussion on the web visit > https://groups.google.com/d/msgid/nlug-talk/CAL9PgS26X2yEsCqSOF6Ex22DUhSA8MHDdhFp4cSDuPrdYw42YA%40mail.gmail.com > . > > > > -- > > -- > > You received this message because you are subscribed to the Google > Groups "NLUG" group. > > To post to this group, send email to nlug-talk@googlegroups.com > > To unsubscribe from this group, send email to > nlug-talk+unsubscr...@googlegroups.com > > For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > > > > --- > > You received this message because you are subscribed to the Google > Groups "NLUG" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to nlug-talk+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/nlug-talk/CA%2B6_KC-1Xtku9UPCdQekON9EXRuTUTit0sRYXHXTNaqQQbx6HA%40mail.gmail.com > . > > > > -- > Tilghman > > -- > -- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To post to this group, send email to nlug-talk@googlegroups.com > To unsubscribe from this group, send email to > nlug-talk+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to nlug-talk+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/nlug-talk/CAHPkZcWdUVCMtjfycRqN77E0xTMYAX0EBBxkWXQxyon5WQpdBg%40mail.gmail.com > . > -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to nlug-talk@googlegroups.com To unsubscribe from this group, send email to nlug-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to nlug-talk+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nlug-talk/CA%2B6_KC8rFA4zu%2B-rePGmYbwsjHtKKgB3%2BaPsRBEUC%2BAh0-a6Kw%40mail.gmail.com.