Meraki Access Points are interesting devices.
I have found they cause issues with Linux firewalls if the merakis are not
configured "correctly".
Meraki Access Points do content inspections which I have found can cause
produce symptoms similar to yours, although I have not experienced what you
Wouldn't it be a BCP to set no-export from the Noction device too?
On 3/26/2015 6:20 PM, Nick Rose wrote:
Several people asked me off list for more details, here is what I have
regarding it.
This morning a tier2 isp that connects to our network made an error in their
router configuration cau
Thu, Mar 26, 2015 at 03:38:55PM -0700, Mike wrote:
> I have a customer however that uses our web mail system now secured
> with ssl. I myself and many others use it and get the green lock. But,
> whenever any station at the customer tries using it, they get a broken
> lock and 'your connection i
You might want to look at some of the documentation on that device.
Looks like it might be doing some proxy stuff.
Regards,
-Joe
On Thu, Mar 26, 2015 at 5:38 PM, Mike wrote:
> Hi,
>
> I have a very odd problem.
>
> We've recently gotten a 'real' ssl certificate from godaddy to cover our
On 27 Mar 2015, at 5:38, Mike wrote:
How is this possible? Can anyone comment on these devices and tell me
what might be going on here?
It's been compromised and its being used for MITM? Or has some sort of
TLS inspection capability built in which is essentially MITM, and which
is enabled?
Hi,
I have a very odd problem.
We've recently gotten a 'real' ssl certificate from godaddy to
cover our domain (*.domain.com) and have installed it in several places
where needed for email (imap/starttls and etc) and web. This works
great, seems ok according to various online TLS cer
Several people asked me off list for more details, here is what I have
regarding it.
This morning a tier2 isp that connects to our network made an error in their
router configuration causing the route leakage. The issue has been addressed
and we will be performing a full post mortem to ensure t
> Anyone from godaddy on here or have contact details for them? We are
> having a routing issue to them.
>
Tim, please contact me offlist.
Anne
Anne P. Mitchell, Esq.
CEO/President
ISIPP SuretyMail Email Reputation, Accreditation & Certification
Your mail system + SuretyMail accreditation = del
Someone with Frontier contacted me off-list and assured me they don't
block port 22, and that it could have been related to port scans,
infected PCs, etc... They are looking in to it.
Apologies for the noise and for being a prat. ;)
-A
On Wed, Mar 25, 2015 at 7:31 PM, Aaron C. de Bruyn wrote:
This should be resolved from AS18978. If you experience anything else please
let me know and I will get it addressed immediately.
Regards,
Nick Rose
CTO @ Enzu Inc.
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Randy
Sent: Thursday, March 26, 2015 12:14 PM
On 03/26/2015 9:00 am, Peter Rocca wrote:
+1
The summary below aligns with our analysis as well.
We've reached out to AS18978 to determine the status of the leak but
at this time we're not seeing any operational impact.
+2, after the morning coffee sunk in and helpful off list replies I can
Could a Charter engineer with familiarity with Michigan contact me
off-list? We have a mutual client who's having issues communicating
between sites.
Thanks
+1
The summary below aligns with our analysis as well.
We've reached out to AS18978 to determine the status of the leak but at this
time we're not seeing any operational impact.
-Original Message-
From: Andree Toonk [mailto:andree+na...@toonk.nl]
Sent: March-26-15 11:54 AM
To: Peter R
Hi List,
this morning our BGPmon system picked up many new more specific
announcements by a variety of Origin ASns, the interesting part is that
the majority of them were classified as BGP Man In The middle attacks
(MITM).
A typical alert would look like:
Hi Randy,
Assuming that your prefix is 198.98.180.0/22 (AS29889 - FSNET-1 - Fast
Serv Networks, LLC) none of the mentioned more specifics are currently
seen from the RIPE NCC's RIS network, see the Looking Glass widget:
https://stat.ripe.net/198.98.180.0/23#tabId=routing
https://stat.ripe.net/198
We are AS 10326 130.215.0.0/16 and I just received a BGPmon alert as
well:
130.215.160.0/20 4795 4795 4761 9304 40633 18978 4436 10326
130.215.176.0/20 4795 4795 4761 9304 40633 18978 4436 10326
On Thu, Mar 26, 2015 at 10:45:09AM -0400, Christopher Morrow wrote:
> On Thu, Mar 26, 2015 at 10:43 AM
Same here. These Indosat guys can't seem to catch a break =/
On 3/26/2015 午後 11:43, Peter Rocca wrote:
We just received a similar alert from bgpmon - part of 108.168.0.0/17 is being
advertised as /20's - although we're still listed as the origin. We are 40788.
108.168.64.0/20 4795 4795 4761 9
Hi,
2015-03-26 15:08 GMT+01:00 Randy :
> On Thursday March 26th 2015 at 12:18 UTC (and on-going) we are seeing more
> specifics on one of our prefixes. Anyone else seeing similar or is it just
> us?
>
> 198.98.180.0/23 4795 4795 4761 9304 40633 18978 4436 29889
> 198.98.182.0/23 4795 4795 4761
All,
Info gathered off-list indicates this may be a couple of issues in our
case - possible routing leak by 18978 (check your tables!) and more
specifics on our prefixes from 4795 that we couldn't see before the leak
hence the apparent hijack.
--
~Randy
On Thu, Mar 26, 2015 at 10:43 AM, Peter Rocca wrote:
> We just received a similar alert from bgpmon - part of 108.168.0.0/17 is
> being advertised as /20's - although we're still listed as the origin. We are
> 40788.
>
> 108.168.64.0/20 4795 4795 4761 9304 40633 18978 6939 40788
> 108.168.80.0/
On Thu, Mar 26, 2015 at 10:38 AM, Randy wrote:
> On 03/26/2015 7:27 am, Christopher Morrow wrote:
>>
>> is your AS in the path below? (what is your AS so folk can check for
>> your prefixes/customer-prefixes and attempt to help?)
>
>
> Sorry, we're 29889.
>
ok, and it looks like the path you clip
We just received a similar alert from bgpmon - part of 108.168.0.0/17 is being
advertised as /20's - although we're still listed as the origin. We are 40788.
108.168.64.0/20 4795 4795 4761 9304 40633 18978 6939 40788
108.168.80.0/20 4795 4795 4761 9304 40633 18978 6939 40788
108.168.96.0/20 47
On 03/26/2015 7:27 am, Christopher Morrow wrote:
is your AS in the path below? (what is your AS so folk can check for
your prefixes/customer-prefixes and attempt to help?)
Sorry, we're 29889.
Nothing helps promote a free and open Internet more than micromanaging
your users' download activity.
Not really sure how someone comes to the conclusion that nobody really
*needs* ssh for anything.
"Livingood, Jason" writes:
> ISPs are generally expected to disclose any port blocking. A qui
All, I have reached out to Aaron privately for details, but we do not block
port 22 traffic unless it is in direct response to an attack or related item.
Please let me know directly if you have any specific questions.
Thanks,
-Jeff
> On Mar 26, 2015, at 7:09 AM, Livingood, Jason
> wrote:
>
>
On Thu, Mar 26, 2015 at 10:08 AM, Randy wrote:
> On Thursday March 26th 2015 at 12:18 UTC (and on-going) we are seeing more
> specifics on one of our prefixes. Anyone else seeing similar or is it just
> us?
is your AS in the path below? (what is your AS so folk can check for
your prefixes/custo
ISPs are generally expected to disclose any port blocking. A quick Google
search shows this is Frontier’s list:
http://www.frontierhelp.com/faq.cfm?qstid=277
On 3/25/15, 10:31 PM, "Aaron C. de Bruyn"
mailto:aa...@heyaaron.com>> wrote:
I've had a handful of clients contact me over the last week
On Thursday March 26th 2015 at 12:18 UTC (and on-going) we are seeing
more specifics on one of our prefixes. Anyone else seeing similar or
is it just us?
198.98.180.0/23 4795 4795 4761 9304 40633 18978 4436 29889
198.98.182.0/23 4795 4795 4761 9304 40633 18978 4436 29889
--
Randy
Stephen Satchell writes:
> It's been a while since I did this, but you can select an additional
> port to accept SSH connections.
That's easy:
jens@screen:~$ grep Port /etc/ssh/sshd_config
Port 22
Port 443
> Picking the right port to use is an exercise, though, that will depend
> on what
Hi folks we have a point and have a 63km between point A to point B. We
have a sigle fiber ( only one fiber) and use a fiberstore sfp+ 10GB dibi
1270/1330 module to connect these sites. All attenuation are okI don¹t have
any trouble on fiber .
I have received this signal on my sfp+:
Receiver s
Stephen Satchell schreef op 26-3-2015 om 12:24:
> On 03/25/2015 07:31 PM, Aaron C. de Bruyn wrote:
>> After getting a few helpful users on the phone to run some quick
>> tests, we found port 22 was blocked.
>
> It's been a while since I did this, but you can select an additional
> port to accept S
On 03/25/2015 07:31 PM, Aaron C. de Bruyn wrote:
> After getting a few helpful users on the phone to run some quick
> tests, we found port 22 was blocked.
It's been a while since I did this, but you can select an additional
port to accept SSH connections. A Google search indicates you can
specify
32 matches
Mail list logo
