Re: BGP FlowSpec

+1 I use this to block all kinds of unwanted traffic (with prejudice, of course). > On 1 May 2016, at 11:56 AM, Roland Dobbins wrote: > >> On 30 Apr 2016, at 19:56, Pierre Lamy wrote: >> >> to null out the destination rather than the source. > > > >

Re: improving signal to noise ratio from centralized network syslogs

In addition to that, you can use some fancy awk colour coding, so you can make it highlight certain lines based on content.. I use this for my e-mail logs, but I’m sure it could be adapted: tail -n 1000 -f /var/log/mail-submission.log | grep smtp.*relay | awk ' /sent/ {print "\033[32m" $0 "\

Re: Rugged wireless bridge

I've had multiple issues with the WAP200E units in the field-- from the Internal PoE cabling being crushed and not working properly, to finding some of the internal antennas wern't even soldered to the PCB properly. I'd definitely +1 on the ubiquiti stuff. however, they've been extremely solid.

Re: 109/8 - not a BOGON

blocked still too, we've just not come across it yet. Regards, Shane Short On 09/10/2009, at 7:22 PM, Matthew Walster wrote: Hi there, A customer of mine is reporting that there are a large number of addresses he can not reach with his addresses in the 109/8 range. This was declass

Re: 109/8 - not a BOGON

I've found pinging a polite email to the whois contact on the ASN - sometimes- gives useful results, but not always. Be aware that you're not only dealing with router black-holes, but seemingly some people have applied bogon filtering to their BIND name servers also. If you can provide a n

Re: Yahoo abuse

SPAM, at a guess :) On 09/02/2010, at 10:47 PM, John Peach wrote: > Damn forms; whatever happened to abuse@ addresses? > > > > On Tue, 9 Feb 2010 07:39:20 -0700 > Jaren Angerbauer wrote: > >> On Tue, Feb 9, 2010 at 5:54 AM, John Peach >> wrote: >>> Does anyone know how to get Yahoo abuse to

Re: Intel 10Gb on VMware (AMD) ESX 4.0 intermittent problem

We had this once before on an Intel GigE ethernet adapter.. The hacky fix was to leave a ping running continuously (mtr in this case) which solved the problem. Sounds like a arp/mac learning issue-- I think it got fixed when we re-installed ESXi on that machine. -Shane On 20/02/2010, at 7:06