Working for me now on FiOS in NYC.
--
---
Joly MacFie 218 565 9365 Skype:punkcast
WWWhatsup NYC - http://wwwhatsup.com
http://pinstand.com - http://punkcast.com
VP (Admin) - ISOC-NY - http://isoc-ny.org
--
Work for me, but with awful trace.
Is it possible to arrange the direct peering with AS39138? Please
contact me off-list if there are admins of AS39138.
On 26.11.14 19:41, Javier J wrote:
> Name: thepiratebay.se
> Address: 194.71.107.27
>
> Its reachable from some places and not others.
>
> I
Thanks Phil. I guess the confusion is that during the outages, it was
reachable from everywhere except Comcast, Verizon and ATT-U-verse all at
the same time.
Every proxy, vpn etc tested worked fine. Also the fact that the traces
dropped immediately and not far off on a far network. In addition to
- Original Message -
> From: "William Herrin"
> I'm not sure I follow your complaint here. Are you saying that Comcast
> or a
> Comcast customer in Washington state stripped the STARTTLS verb from
> the
> IPv4 port 587 SMTP submission connection between you and a third
> party?
And, of c
- Original Message -
> From: "William Herrin"
> > that's essentially a downgrade attack on my ability to use
> > encryption
> > which seems to be in pretty poor taste frankly.
>
> I'm not sure I follow your complaint here. Are you saying that Comcast
> or a
> Comcast customer in Washing
Oh it depends on the numbers.
Just how many legitimate smtp submission attempts do you get from say an
access point at Joes diner in nowhere, OH?
Versus just how many password cracking and malware relay attempts across
how many of your users, from an unpatched xp box the guy is using for a
billin
No. He is a comcast customer. And some third party wifi access point
blocked his smtp submission over TLS by setting up an asa device to inspect
587 as well.
On Nov 28, 2014 6:16 AM, "William Herrin" wrote:
> On Thu, Nov 27, 2014 at 2:54 PM, joel jaeggli wrote:
> > I don't see this in my home ma
On Thu, Nov 27, 2014 at 2:54 PM, joel jaeggli wrote:
> I don't see this in my home market, but I do see it in someone else's...
> I kind of expect this for port 25 but...
>
> J@mb-aye:~$telnet 147.28.0.81 587
> Trying 147.28.0.81...
> Connected to nagasaki.bogus.com.
> Escape character is '^]'.
>
In message
, Suresh Ramasubramanian writes:
>
> Yes. Till that hotspots IP space gets blackholed by a major freemail
> because of all the nigerians and hijacked devices emitting bot traffic
> through stolen auth credentials.
Why would it black hole the address rather than the block the
compromi
Yes. Till that hotspots IP space gets blackholed by a major freemail
because of all the nigerians and hijacked devices emitting bot traffic
through stolen auth credentials.
There's other ways to stop this but they take actual hard work and rather
more gear than a rusted up old asa you pull out of
Which is why your MTA should always be setup to require the use of
STARTTLS. Additionally the CERT presented should also match the
name of the server.
There is absolutely no reason for a ISP / hotspot to inspect
submission traffic. The "stopping spam" argument doesn't wash with
submission.
Mar
It looks like they use different upstream providers for each prefix,
probably hosted in different locations.
The 194.71.107.0/24 prefix on my network was withdrawn by Ataro, and is
now reachable via this path:
194.71.107.0/24*[BGP/170] 00:04:34
AS path: 3356 3320 3
I don't see this in my home market, but I do see it in someone else's...
I kind of expect this for port 25 but...
J@mb-aye:~$telnet 147.28.0.81 587
Trying 147.28.0.81...
Connected to nagasaki.bogus.com.
Escape character is '^]'.
220 nagasaki.bogus.com ESMTP Sendmail 8.14.9/8.14.9; Thu, 27 Nov 2014
Anyone from media temple/godaddy around?
I have a site hosted in mediatemple that a customer can't reach and normal
support has been not helpful thus far.
Off-list is fine, much appreciated.
--
Sean
It was working for me a few hours ago, and now dead at hop 3 on FIOS again.
If they have 2 prefixes being advertised from AS51040
http://bgp.he.net/AS51040#_prefixes Why can I traceroute to 1 but not the
other?
[root@tor-proxy network-scripts]# mtr --report -c 5 194.14.56.1
HOST: tor-proxy.home
In the post you quoted it says:
"In my last post I pointed out the do not announce to peers
community AS5580 was sending to Cogent, Level3 and who knows who else. So
any ASN that is not a customer of Cogent or Level3 wont learn the 5580 path
from them."
Verizon, ATT, and the rest of those netwo
Never assume symetric routing (though Im almost old enough to remember
the days of.)
Wish there was some kinda bidirect traceroute protocol widely supported.
Mostly we only have lg's via www if they happen to have been setup for such
occasions :(
I know there were a few small projects with this k
On Thu, Nov 27, 2014 at 11:00:32AM -0500, Jared Mauch wrote:
> Seems your MTR sees loss within the Cogent (174) network prior
> to reaching the NTT network.
>
> I think you perhaps need cogent assistance?
This was resolved off-list. James is now engaging with his supplier.
For future reference:
Seems your MTR sees loss within the Cogent (174) network prior
to reaching the NTT network.
I think you perhaps need cogent assistance?
- Jared
On Thu, Nov 27, 2014 at 04:58:59AM -0500, james jones wrote:
> We are getting a huge amount of traffic loss while sending to J
Looks like its working now (on FIOS anyway)
Curious to know why the major networks stopped seeing it yesterday as well.
On Thu, Nov 27, 2014 at 12:45 AM, Courtney Smith
wrote:
>
> > No problem here in Los Angeles either, but seeing a lone route through
> Atrato only.
> >
> > flags destination
We are getting a huge amount of traffic loss while sending to JP. I am
trying to figure out if the problem is with cogent or NTT. Thoughts? Here
is a MTR trace:
login02.bal (0.0.0.0)
Thu Nov 27 01:58:22 2014
Keys: Help Display mode Restart statistics Order of fiel
On Thu, Nov 27, 2014 at 04:51:59AM -0500, james jones wrote:
> Looking to discuss a routing issue going through NTT's link to JP.
Feel free to contact me off-list with the details.
Kind regards,
Job
Looking to discuss a routing issue going through NTT's link to JP.
23 matches
Mail list logo
