On Wed, 6 Nov 2019 at 11:55, Dave Collier-Brown via talk
wrote:
> Tek Savvy is still relatively small and non-stupid, so customers can
> probably escalate and get a response. I'd call by voice, write down the
> person's name when they answer, and when they say "no", ask to speak to
> their escal
On 2019-11-05 12:13 p.m., Giles Orr via talk wrote:
Wouldn't it be great if they said WHAT had caused it rather than just
"we fixed it?"
That might've been what Teksavvy got from Rogers. Or at least, what the
person on Teksavvy's technical social media account heard. They've come
on a bit f
On 2019-11-06 11:55 AM, Dave Collier-Brown via talk wrote:
Having owned a customer support team in the past (Interleaf), they had
a mission from management to "make you happy with what you have", and
to close tickets as soon as possible. Less than good.
Having worked in the telecom and net
On 2019-11-05 12:13 p.m., Giles Orr via talk wrote:
Teksavvy have done something on their end:
https://twitter.com/TekSavvyCSR/status/1191486635764068355
Wouldn't it be great if they said WHAT had caused it rather than just "we fixed
it?" If you told us the how, we might have more faith that y
I've seen this before on a fortigate firewall.
The FW will detect "apt" as app:XMLRPC rather than app:HTTP for the
purposes of "Application Detection" and if the "allow port 80 rules" is
infact an "Allow only app:HTTP on port 80" rule , then XMLRPC over port 80
is disallowed.
David
On Mon, Nov 4
On Mon, 4 Nov 2019 at 21:27, Jamon Camisso via talk wrote:
> On 04/11/2019 21:24, D. Hugh Redelmeier via talk wrote:
> > Is this happening to you? I will assume so.
> >
> > - my main internet connection is directly through Rogers.
> >
> > - I use Ubuntu infrequently.
> >
> > - when I do update i
On 04/11/2019 21:24, D. Hugh Redelmeier via talk wrote:
> Is this happening to you? I will assume so.
>
> - my main internet connection is directly through Rogers.
>
> - I use Ubuntu infrequently.
>
> - when I do update it, I have had no issue. Most recently: a couple
> of days ago.
>
> The
| From: Jamon Camisso via talk
| Well this is a new low:
|
|
https://askubuntu.com/questions/1185612/apt-get-stuck-on-waiting-for-headers/1185713
|
| Mind-boggling that it is/was even an issue at an ISP & HTTP level.
|
| Either they have a giant whitelist of browser agents to maintain, or a
|
What does Wireshark show? That article shows "Connection reset by peer".
On 2019-11-04 04:13 PM, Jamon Camisso via talk wrote:
Well this is a new low:
https://askubuntu.com/questions/1185612/apt-get-stuck-on-waiting-for-headers/1185713
Mind-boggling that it is/was even an issue at an ISP & HT
Well this is a new low:
https://askubuntu.com/questions/1185612/apt-get-stuck-on-waiting-for-headers/1185713
Mind-boggling that it is/was even an issue at an ISP & HTTP level.
Either they have a giant whitelist of browser agents to maintain, or a
blacklist to update and added apt to it.
In eith
10 matches
Mail list logo
