August 2018 - mice-discuss - lists.micemn.net

Re: Routing of non-IX traffic

by Richard Laager

On 08/21/2018 02:08 PM, Richard Laager wrote: > On 08/21/2018 08:04 AM, Frank Bulk wrote: >> Since we already have a list of which MACs have proxy ARP on, I would >> suggest the MICE leadership team privately contact those MICE >> participants and ask them to turn off proxy ARP. > > Sure thing. I've emailed them all off-list. As of this afternoon, no MICE participants are doing proxy ARP. Thanks to those participants for responding quickly and reconfiguring their routers. Thanks to Matthew Beckwell for repeated testing to confirm the progress. -- Richard

Aug. 23, 2018

Re: Routing of non-IX traffic

by Richard Laager

On 08/21/2018 08:04 AM, Frank Bulk wrote: > Since we already have a list of which MACs have proxy ARP on, I would > suggest the MICE leadership team privately contact those MICE > participants and ask them to turn off proxy ARP. Sure thing. I've emailed them all off-list. -- Richard

Aug. 21, 2018

Re: Routing of non-IX traffic

by Frank Bulk

Since we already have a list of which MACs have proxy ARP on, I would suggest the MICE leadership team privately contact those MICE participants and ask them to turn off proxy ARP. Frank From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Andrew Hoyos Sent: Saturday, August 18, 2018 5:36 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Routing of non-IX traffic Relavent: https://ripe63.ripe.net/presentations/130-Proxy_ARP_RIPE_Nov2011.pdf Seems like quite a few participants on MICE with proxy ARP still on. I know some IX’s toss you in a quarantine VLAN for initial turn-up - maybe this is something that needs to start, so this sort of thing can be checked? — Andrew Hoyos hoyosa(a)gmail.com<mailto:hoyosa@gmail.com> On Aug 16, 2018, at 9:52 PM, Frank Bulk <fbulk(a)mypremieronline.com<mailto:fbulk@mypremieronline.com>> wrote: Thanks, Matthew, for explaining why ARP might be happening. Now that CNS has its proxy ARP turned off, it’s AS393639 that’s responding: SiouxCenter-Arista-North(s1)#traceroute ip www.yamaha-dealers.com<http://www.yamaha-dealers.com/> source et 3/24 traceroute to www.yamaha-dealers.com<http://www.yamaha-dealers.com/> (45.60.73.16), 30 hops max, 60 byte packets 1 AS393639.micemn.net<http://as393639.micemn.net/> (206.108.255.47) 13.936 ms 14.004 ms 13.998 ms 2 v415.core1.msp1.he.net<http://v415.core1.msp1.he.net/> (184.105.25.93) 14.146 ms 14.205 ms 14.274 ms 3 100ge13-1.core2.chi1.he.net<http://100ge13-1.core2.chi1.he.net/> (184.105.223.177) 22.533 ms 22.369 ms 22.538 ms 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 *^CSiouxCenter-Arista-North(s1)# Can an ACL be created on the Arista that discards in/outbound ARP requests for the non-MICE address space? Frank From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> On Behalf Of Steve Howard Sent: Thursday, August 16, 2018 9:32 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET<mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> Subject: Re: [MICE-DISCUSS] Routing of non-IX traffic I've disabled proxy arp on the CNS router... Has the behavior changed? On 08/16/2018 05:00 PM, Matthew Beckwell wrote: I'm getting similar behavior as Frank. Like Doug, I only have 45.60.73.0/24<http://45.60.73.0/24> from transit connections. So a traceroute from my MICE interface should ARP and die (I would think).... When I traceroute to 45.60.73.16-- my router sends out an ARP request, as expected. But...I get ARP replies for 45.60.73.16 from these Cisco MACs (in the order they came into my interface): 00:23:33:c6:a0:c0 206.108.255.50 Cooperative Network Services (CNS) 32609 e4:aa:5d:83:73:06 206.108.255.47 IVDesk 393639 88:43:e1:00:f2:10 206.108.255.18 Consolidated Communications 12042 b0:aa:77:33:7b:03 206.108.255.79 Gigamonster, LLC 31939 3c:08:f6:81:6e:a5 206.108.255.46 OneNetUSA 46131 00:1d:e5:c0:78:c3 206.108.255.5 Implex 21709 54:75:d0:e6:08:30 206.108.255.106 Nuvera Communications 23465 00:11:5d:82:6c:00 206.108.255.80 Future Technologies 26451 Proxy ARP (or something like it)? CNS seems to be consistently coming in first place when I clear my ARP entry. ~Matthew matthewb(a)aitech.net<mailto:matthewb@aitech.net> AS13746 On Thu, Aug 16, 2018 at 3:25 PM, Frank Bulk <fbulk(a)mypremieronline.com<mailto:fbulk@mypremieronline.com>> wrote: When I force a traceroute to originate from our MICE-facing connection, the first hop is 206.108.255.50 (AS32609 aka CNS). Any reason why? To making things more interesting, Incapsula-destined traffic goes via Paul Bunyan. Here's just one example: traceroute to www.yamaha-dealers.com<http://www.yamaha-dealers.com/> (45.60.73.16), 30 hops max, 60 byte packets 1 AS32609.micemn.net<http://as32609.micemn.net/> (206.108.255.50) 14.059 ms 14.084 ms 14.076 ms 2 cns70.cnsllc.net<http://cns70.cnsllc.net/> (205.149.150.9) 18.484 ms 18.434 ms 18.507 ms 3 fg30.ips.cnsllc.net<http://fg30.ips.cnsllc.net/> (205.149.150.30) 20.254 ms 20.346 ms 20.267 ms 4 crss2.PaulBunyan.net<http://crss2.paulbunyan.net/> (205.149.159.197) 20.527 ms 20.562 ms 20.619 ms 5 cra.PaulBunyan.net<http://cra.paulbunyan.net/> (205.149.159.181) 23.398 ms fp233.ips.PaulBunyan.net<http://fp233.ips.paulbunyan.net/> (205.149.159.233) 22.669 ms cra.PaulBunyan.net<http://cra.paulbunyan.net/> (205.149.159.181) 23.393 ms 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * SiouxCenter-Arista-North(s1) The reason I stumbled across this is because we've had more than a dozen customers over the last month complain about access to Incapsula-protected sites. Packet captures show TCP RSTs coming from the far side. Regards, Frank Bulk AS53347 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Aug. 21, 2018

Re: Direct peering to Yahoo! unstable over the last few days

by Frank Bulk

Thanks, Jeremy. I had always assumed Yahoo!'s gear was colo'd at MICE. Frank -----Original Message----- From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Jeremy Lumby Sent: Saturday, August 18, 2018 11:29 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Direct peering to Yahoo! unstable over the last few days I can confirm the same on my router. I also happen to know that Yahoo is connected via a longhaul circuit into MICE. I have a wavelength with the same provider that would logically take the same path based on the same endpoint locations, and they have been having intermittent DC power issues in one of their huts for over a week now. They currently have an electrician on site to try to determine the intermittent piece of equipment. -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Frank Bulk Sent: Saturday, August 18, 2018 11:12 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Direct peering to Yahoo! unstable over the last few days Anyone else seeing the same as us? Aug 17 17:55:10 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor 206.108.255.58 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Aug 17 17:55:10 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 17 17:55:14 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor 206.108.255.59 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Aug 17 17:55:14 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 17 17:55:17 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor 2001:504:27::2846:0:2 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Aug 17 17:55:17 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 17 18:02:13 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 18:02:19 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 18:02:48 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 21:30:59 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 17 21:31:03 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 17 21:31:06 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 17 21:38:05 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 21:38:12 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 21:38:20 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 00:54:55 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 18 00:54:57 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 18 00:54:59 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 18 01:02:41 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 01:02:49 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 01:02:53 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 02:01:30 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 18 02:01:32 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 18 02:01:35 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 18 02:15:55 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 02:16:00 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 02:16:00 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 05:36:50 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 18 05:36:53 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 18 05:36:56 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 18 05:47:17 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 05:47:21 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 05:47:24 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established

Aug. 21, 2018

Re: Direct peering to Yahoo! unstable over the last few days

by Michael Hare

In short, yes, and at slightly different times than you it would seem. Things are stable here at this time. -Michael =============/================ Aug 15 13:27:17 :%DAEMON-4-RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer 206.108.255.58 (External AS 10310) changed state from Established to Idle (event RecvNotify) (instance master) Aug 15 13:27:18 :%DAEMON-4-RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer 2001:504:27::2846:0:1 (External AS 10310) changed state from Established to Idle (event RecvNotify) (instance master) Aug 17 11:01:07 :%DAEMON-4-RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer 206.108.255.58 (External AS 10310) changed state from Established to Idle (event Stop) (instance master) Aug 17 11:01:07 :%DAEMON-4-RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer 206.108.255.59 (External AS 10310) changed state from Established to Idle (event Stop) (instance master) Aug 17 11:01:08 :%DAEMON-4-RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer 2001:504:27::2846:0:1 (External AS 10310) changed state from Established to Idle (event Stop) (instance master) Aug 17 11:01:08 :%DAEMON-4-RPD_BGP_NEIGHBOR_STATE_CHANGED: BGP peer 2001:504:27::2846:0:2 (External AS 10310) changed state from Established to Idle (event Stop) (instance master) > -----Original Message----- > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of > Frank Bulk > Sent: Saturday, August 18, 2018 11:12 AM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET > Subject: [MICE-DISCUSS] Direct peering to Yahoo! unstable over the last few > days > > Anyone else seeing the same as us? > > Aug 17 17:55:10 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor > 206.108.255.58 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) 0 > bytes > Aug 17 17:55:10 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 > (AS 10310) old state Established event HoldTime new state Idle > Aug 17 17:55:14 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor > 206.108.255.59 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) 0 > bytes > Aug 17 17:55:14 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 > (AS 10310) old state Established event HoldTime new state Idle > Aug 17 17:55:17 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor > 2001:504:27::2846:0:2 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) > 0 bytes > Aug 17 17:55:17 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer > 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new > state Idle > Aug 17 18:02:13 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 > (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established > Aug 17 18:02:19 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 > (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established > Aug 17 18:02:48 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer > 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event > RecvKeepAlive new state Established > > Aug 17 21:30:59 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 > (AS 10310) old state Established event HoldTime new state Idle > Aug 17 21:31:03 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer > 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new > state Idle > Aug 17 21:31:06 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 > (AS 10310) old state Established event HoldTime new state Idle > Aug 17 21:38:05 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 > (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established > Aug 17 21:38:12 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer > 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event > RecvKeepAlive new state Established > Aug 17 21:38:20 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 > (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established > > Aug 18 00:54:55 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 > (AS 10310) old state Established event HoldTime new state Idle > Aug 18 00:54:57 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer > 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new > state Idle > Aug 18 00:54:59 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 > (AS 10310) old state Established event HoldTime new state Idle > Aug 18 01:02:41 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 > (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established > Aug 18 01:02:49 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 > (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established > Aug 18 01:02:53 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer > 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event > RecvKeepAlive new state Established > > Aug 18 02:01:30 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 > (AS 10310) old state Established event HoldTime new state Idle > Aug 18 02:01:32 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 > (AS 10310) old state Established event HoldTime new state Idle > Aug 18 02:01:35 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer > 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new > state Idle > Aug 18 02:15:55 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 > (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established > Aug 18 02:16:00 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 > (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established > Aug 18 02:16:00 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer > 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event > RecvKeepAlive new state Established > > Aug 18 05:36:50 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 > (AS 10310) old state Established event HoldTime new state Idle > Aug 18 05:36:53 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer > 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new > state Idle > Aug 18 05:36:56 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 > (AS 10310) old state Established event HoldTime new state Idle > Aug 18 05:47:17 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 > (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established > Aug 18 05:47:21 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 > (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established > Aug 18 05:47:24 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer > 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event > RecvKeepAlive new state Established

Aug. 20, 2018

Re: Routing of non-IX traffic

by Andrew Hoyos

Relavent: https://ripe63.ripe.net/presentations/130-Proxy_ARP_RIPE_Nov2011.pdf <https://ripe63.ripe.net/presentations/130-Proxy_ARP_RIPE_Nov2011.pdf> Seems like quite a few participants on MICE with proxy ARP still on. I know some IX’s toss you in a quarantine VLAN for initial turn-up - maybe this is something that needs to start, so this sort of thing can be checked? — Andrew Hoyos hoyosa(a)gmail.com > On Aug 16, 2018, at 9:52 PM, Frank Bulk <fbulk(a)mypremieronline.com> wrote: > > Thanks, Matthew, for explaining why ARP might be happening. > > Now that CNS has its proxy ARP turned off, it’s AS393639 that’s responding: > > SiouxCenter-Arista-North(s1)#traceroute ip www.yamaha-dealers.com <http://www.yamaha-dealers.com/> source et 3/24 > traceroute to www.yamaha-dealers.com <http://www.yamaha-dealers.com/> (45.60.73.16), 30 hops max, 60 byte packets > 1 AS393639.micemn.net <http://as393639.micemn.net/> (206.108.255.47) 13.936 ms 14.004 ms 13.998 ms > 2 v415.core1.msp1.he.net <http://v415.core1.msp1.he.net/> (184.105.25.93) 14.146 ms 14.205 ms 14.274 ms > 3 100ge13-1.core2.chi1.he.net <http://100ge13-1.core2.chi1.he.net/> (184.105.223.177) 22.533 ms 22.369 ms 22.538 ms > 4 * * * > 5 * * * > 6 * * * > 7 * * * > 8 * * * > 9 *^CSiouxCenter-Arista-North(s1)# > > Can an ACL be created on the Arista that discards in/outbound ARP requests for the non-MICE address space? > > Frank > > From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET>> On Behalf Of Steve Howard > Sent: Thursday, August 16, 2018 9:32 PM > To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET <mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET> > Subject: Re: [MICE-DISCUSS] Routing of non-IX traffic > > I've disabled proxy arp on the CNS router... Has the behavior changed? > > On 08/16/2018 05:00 PM, Matthew Beckwell wrote: > I'm getting similar behavior as Frank. > > Like Doug, I only have 45.60.73.0/24 <http://45.60.73.0/24> from transit connections. > So a traceroute from my MICE interface should ARP and die (I would think).... > > When I traceroute to 45.60.73.16-- my router sends out an ARP request, as expected. > But...I get ARP replies for 45.60.73.16 from these Cisco MACs (in the order they came into my interface): > > > 00:23:33:c6:a0:c0 > 206.108.255.50 > Cooperative Network Services (CNS) > 32609 > e4:aa:5d:83:73:06 > 206.108.255.47 > IVDesk > 393639 > 88:43:e1:00:f2:10 > 206.108.255.18 > Consolidated Communications > 12042 > b0:aa:77:33:7b:03 > 206.108.255.79 > Gigamonster, LLC > 31939 > 3c:08:f6:81:6e:a5 > 206.108.255.46 > OneNetUSA > 46131 > 00:1d:e5:c0:78:c3 > 206.108.255.5 > Implex > 21709 > 54:75:d0:e6:08:30 > 206.108.255.106 > Nuvera Communications > 23465 > 00:11:5d:82:6c:00 > 206.108.255.80 > Future Technologies > 26451 > > > Proxy ARP (or something like it)? > CNS seems to be consistently coming in first place when I clear my ARP entry. > > ~Matthew > matthewb(a)aitech.net <mailto:matthewb@aitech.net> > AS13746 > > > > > On Thu, Aug 16, 2018 at 3:25 PM, Frank Bulk <fbulk(a)mypremieronline.com <mailto:fbulk@mypremieronline.com>> wrote: > When I force a traceroute to originate from our MICE-facing connection, the first hop is 206.108.255.50 (AS32609 aka CNS). Any reason why? > > To making things more interesting, Incapsula-destined traffic goes via Paul Bunyan. Here's just one example: > > traceroute to www.yamaha-dealers.com <http://www.yamaha-dealers.com/> (45.60.73.16), 30 hops max, 60 byte packets > 1 AS32609.micemn.net <http://as32609.micemn.net/> (206.108.255.50) 14.059 ms 14.084 ms 14.076 ms > 2 cns70.cnsllc.net <http://cns70.cnsllc.net/> (205.149.150.9) 18.484 ms 18.434 ms 18.507 ms > 3 fg30.ips.cnsllc.net <http://fg30.ips.cnsllc.net/> (205.149.150.30) 20.254 ms 20.346 ms 20.267 ms > 4 crss2.PaulBunyan.net <http://crss2.paulbunyan.net/> (205.149.159.197) 20.527 ms 20.562 ms 20.619 ms > 5 cra.PaulBunyan.net <http://cra.paulbunyan.net/> (205.149.159.181) 23.398 ms fp233.ips.PaulBunyan.net <http://fp233.ips.paulbunyan.net/> (205.149.159.233) 22.669 ms cra.PaulBunyan.net <http://cra.paulbunyan.net/> (205.149.159.181) 23.393 ms > 6 * * * > 7 * * * > 8 * * * > 9 * * * > 10 * * * > 11 * * * > 12 * * * > 13 * * * > 14 * * * > 15 * * * > 16 * * * > 17 * * * > 18 * * * > 19 * * * > 20 * * * > 21 * * * > 22 * * * > 23 * * * > 24 * * * > 25 * * * > 26 * * * > 27 * * * > 28 * * * > 29 * * * > 30 * * * > SiouxCenter-Arista-North(s1) > > The reason I stumbled across this is because we've had more than a dozen customers over the last month complain about access to Incapsula-protected sites. Packet captures show TCP RSTs coming from the far side. > > Regards, > > Frank Bulk > AS53347 > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> > > > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1> > To unsubscribe from the MICE-DISCUSS list, click the following link: > http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 <http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1>

Aug. 18, 2018

Re: Direct peering to Yahoo! unstable over the last few days

by Jeremy Lumby

I can confirm the same on my router. I also happen to know that Yahoo is connected via a longhaul circuit into MICE. I have a wavelength with the same provider that would logically take the same path based on the same endpoint locations, and they have been having intermittent DC power issues in one of their huts for over a week now. They currently have an electrician on site to try to determine the intermittent piece of equipment. -----Original Message----- From: MICE Discuss [mailto:MICE-DISCUSS@LISTS.IPHOUSE.NET] On Behalf Of Frank Bulk Sent: Saturday, August 18, 2018 11:12 AM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: [MICE-DISCUSS] Direct peering to Yahoo! unstable over the last few days Anyone else seeing the same as us? Aug 17 17:55:10 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor 206.108.255.58 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Aug 17 17:55:10 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 17 17:55:14 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor 206.108.255.59 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Aug 17 17:55:14 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 17 17:55:17 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor 2001:504:27::2846:0:2 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Aug 17 17:55:17 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 17 18:02:13 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 18:02:19 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 18:02:48 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 21:30:59 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 17 21:31:03 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 17 21:31:06 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 17 21:38:05 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 21:38:12 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 21:38:20 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 00:54:55 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 18 00:54:57 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 18 00:54:59 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 18 01:02:41 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 01:02:49 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 01:02:53 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 02:01:30 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 18 02:01:32 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 18 02:01:35 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 18 02:15:55 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 02:16:00 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 02:16:00 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 05:36:50 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 18 05:36:53 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 18 05:36:56 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 18 05:47:17 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 05:47:21 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 05:47:24 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established

Aug. 18, 2018

Re: Subscription Mail: Re: [MICE-DISCUSS] Routing of non-IX traffic

by Mike Horwath

On Thu, Aug 16, 2018 at 10:25:13PM +0000, Ryan Goldberg wrote: > Proxy arp enabled by default is the silliest thing Cisco ever did. I'd say the constant 8:1 overcommit is the silliest thing ever, followed by proxy arp enablement by default. -- Mike Horwath, reachable via drechsau(a)Geeks.ORG

Aug. 18, 2018

Direct peering to Yahoo! unstable over the last few days

by Frank Bulk

Anyone else seeing the same as us? Aug 17 17:55:10 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor 206.108.255.58 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Aug 17 17:55:10 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 17 17:55:14 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor 206.108.255.59 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Aug 17 17:55:14 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 17 17:55:17 207.32.15.28 Rib: %BGP-3-NOTIFICATION: sent to neighbor 2001:504:27::2846:0:2 (AS 10310) 4/0 (Hold Timer Expired Error/Unspecified) 0 bytes Aug 17 17:55:17 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 17 18:02:13 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 18:02:19 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 18:02:48 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 21:30:59 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 17 21:31:03 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 17 21:31:06 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 17 21:38:05 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 21:38:12 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 17 21:38:20 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 00:54:55 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 18 00:54:57 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 18 00:54:59 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 18 01:02:41 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 01:02:49 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 01:02:53 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 02:01:30 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 18 02:01:32 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 18 02:01:35 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 18 02:15:55 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 02:16:00 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 02:16:00 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 05:36:50 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state Established event HoldTime new state Idle Aug 18 05:36:53 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state Established event HoldTime new state Idle Aug 18 05:36:56 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state Established event HoldTime new state Idle Aug 18 05:47:17 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.58 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 05:47:21 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 206.108.255.59 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established Aug 18 05:47:24 207.32.15.28 Rib: %BGP-5-ADJCHANGE: peer 2001:504:27::2846:0:2 (AS 10310) old state OpenConfirm event RecvKeepAlive new state Established

Aug. 18, 2018

Re: Routing of non-IX traffic

by Frank Bulk

Thanks, Matthew, for explaining why ARP might be happening. Now that CNS has its proxy ARP turned off, it’s AS393639 that’s responding: SiouxCenter-Arista-North(s1)#traceroute ip www.yamaha-dealers.com source et 3/24 traceroute to www.yamaha-dealers.com (45.60.73.16), 30 hops max, 60 byte packets 1 AS393639.micemn.net (206.108.255.47) 13.936 ms 14.004 ms 13.998 ms 2 v415.core1.msp1.he.net (184.105.25.93) 14.146 ms 14.205 ms 14.274 ms 3 100ge13-1.core2.chi1.he.net (184.105.223.177) 22.533 ms 22.369 ms 22.538 ms 4 * * * 5 * * * 6 * * * 7 * * * 8 * * * 9 *^CSiouxCenter-Arista-North(s1)# Can an ACL be created on the Arista that discards in/outbound ARP requests for the non-MICE address space? Frank From: MICE Discuss <MICE-DISCUSS(a)LISTS.IPHOUSE.NET> On Behalf Of Steve Howard Sent: Thursday, August 16, 2018 9:32 PM To: MICE-DISCUSS(a)LISTS.IPHOUSE.NET Subject: Re: [MICE-DISCUSS] Routing of non-IX traffic I've disabled proxy arp on the CNS router... Has the behavior changed? On 08/16/2018 05:00 PM, Matthew Beckwell wrote: I'm getting similar behavior as Frank. Like Doug, I only have 45.60.73.0/24<http://45.60.73.0/24> from transit connections. So a traceroute from my MICE interface should ARP and die (I would think).... When I traceroute to 45.60.73.16-- my router sends out an ARP request, as expected. But...I get ARP replies for 45.60.73.16 from these Cisco MACs (in the order they came into my interface): 00:23:33:c6:a0:c0 206.108.255.50 Cooperative Network Services (CNS) 32609 e4:aa:5d:83:73:06 206.108.255.47 IVDesk 393639 88:43:e1:00:f2:10 206.108.255.18 Consolidated Communications 12042 b0:aa:77:33:7b:03 206.108.255.79 Gigamonster, LLC 31939 3c:08:f6:81:6e:a5 206.108.255.46 OneNetUSA 46131 00:1d:e5:c0:78:c3 206.108.255.5 Implex 21709 54:75:d0:e6:08:30 206.108.255.106 Nuvera Communications 23465 00:11:5d:82:6c:00 206.108.255.80 Future Technologies 26451 Proxy ARP (or something like it)? CNS seems to be consistently coming in first place when I clear my ARP entry. ~Matthew matthewb(a)aitech.net<mailto:matthewb@aitech.net> AS13746 On Thu, Aug 16, 2018 at 3:25 PM, Frank Bulk <fbulk(a)mypremieronline.com<mailto:fbulk@mypremieronline.com>> wrote: When I force a traceroute to originate from our MICE-facing connection, the first hop is 206.108.255.50 (AS32609 aka CNS). Any reason why? To making things more interesting, Incapsula-destined traffic goes via Paul Bunyan. Here's just one example: traceroute to www.yamaha-dealers.com<http://www.yamaha-dealers.com> (45.60.73.16), 30 hops max, 60 byte packets 1 AS32609.micemn.net<http://AS32609.micemn.net> (206.108.255.50) 14.059 ms 14.084 ms 14.076 ms 2 cns70.cnsllc.net<http://cns70.cnsllc.net> (205.149.150.9) 18.484 ms 18.434 ms 18.507 ms 3 fg30.ips.cnsllc.net<http://fg30.ips.cnsllc.net> (205.149.150.30) 20.254 ms 20.346 ms 20.267 ms 4 crss2.PaulBunyan.net<http://crss2.PaulBunyan.net> (205.149.159.197) 20.527 ms 20.562 ms 20.619 ms 5 cra.PaulBunyan.net<http://cra.PaulBunyan.net> (205.149.159.181) 23.398 ms fp233.ips.PaulBunyan.net<http://fp233.ips.PaulBunyan.net> (205.149.159.233) 22.669 ms cra.PaulBunyan.net<http://cra.PaulBunyan.net> (205.149.159.181) 23.393 ms 6 * * * 7 * * * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * SiouxCenter-Arista-North(s1) The reason I stumbled across this is because we've had more than a dozen customers over the last month complain about access to Incapsula-protected sites. Packet captures show TCP RSTs coming from the far side. Regards, Frank Bulk AS53347 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1 ________________________________ To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1

Aug. 17, 2018