[AusNOG] Routing Issue - Ultra Serve

[Milan Rajkovic]

Hi Guys,

Looking for some assistance with an issue with one of our IP Addresses.

I am having an issue with traffic coming from 103.50.34.194 to 203.145.46.188 I 
am able to hit 203.145.46.177.

I have confirmed there is no blocking on our end.

C:\Users\Administrator>tracert 203.145.46.188

Tracing route to sftp.apac.f4f.com [203.145.46.188]
over a maximum of 30 hops:

  1 *** Request timed out.
  2 *** Request timed out.
  3 *** Request timed out.
  4 *** Request timed out.
  5 * ^C




C:\Users\Administrator>tracert 203.145.46.177

Tracing route to test.first4farming.com.au [203.145.46.177]
over a maximum of 30 hops:

  1<1 ms<1 ms<1 ms  192.168.88.1
  2<1 ms<1 ms<1 ms  103-50-34-193-public-ip.m-i.net.au 
[103.50.34.193]
  3 1 ms 1 ms<1 ms  ve797.bdr1.m1.au.as58511.net [43.225.33.33]
  413 ms14 ms13 ms  ra100.cor1.m1.au.as58511.net [103.30.216.146]
  512 ms12 ms12 ms  te2-0-35.cor1.sy3.au.as58511.net [103.30.216.17]
  611 ms11 ms11 ms  po11-8.bdr2.sy3.au.as58511.net [103.30.216.139]
  712 ms12 ms12 ms  as17920.nsw.ix.asn.au [218.100.52.38]
  812 ms12 ms12 ms  203.145.33.136
  917 ms13 ms13 ms  203.145.32.254
1012 ms12 ms12 ms  203.145.32.185
11  ^C
C:\Users\Administrator>

Kind Regards,
Milan

___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

[AusNOG] Vodafone NZ Noc

[Joel Nath]

Hi Guys

Any one from Vodafone NZ Noc on the list, could you please ping me, having some 
routing issue for NZ customers.

Regards
Joel
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Optus issue in Broome, Sydney, Perth?

[Kai]

Not sure what media you've been watching but TC Joyce passed West of 
Broome and crossed the coast at Bidyadanga, about 200k's south of us 
around 2am today.
We got a good light show the past few days but no power failures in my 
area so the UPS didn't need to kick in.


She is a weak Cat 1 with much lower winds to what we were expecting but 
she continues to drop a lot of rain, some highways and roads are flooded 
or closed but thanks to the good work from the associated agencies we 
didn't lose any power or other essential services.


We thank police, medical personnel, SES/FESA, BoM, MRWA, ABC, Shire, 
airport, airlines and all volunteers for their efforts and regular 
updates to keep us safe and informed.


Back on topic, the Optus outage looks to now be sporadic but Optus 
status page now says:
"Incident Update - National. Cannot send SMS, users my experience 
intermittent issues sending SMS."


Not sure if they know the problem also looks to be affected their resellers.

Regards
Kai

On 12/01/2018 12:27 PM, Bradley Amm wrote:

A cyclone just went through Broome today

Get Outlook for iOS 

*From:* AusNOG  on behalf of Kai 


*Sent:* Friday, January 12, 2018 11:21:09 AM
*To:* ausnog@lists.ausnog.net
*Subject:* [AusNOG] Optus issue in Broome, Sydney, Perth?
Hi folks,

Belated Happy Christmas, and Happy New year to all!

Reports of problems making calls and sending sms from Optus users to
non-Optus users at these locations.
Looks to include Optus resellers (Virgin and OVO). Same reports from a
few Vodafone users in Sydney.

Problem started about 9:45am WST.
No known faults listed on Optus page as of five minutes ago.
Inbound calls and messages are ok so far.
Outbound calls and messages are failing.

Any feedback is appreciated.

Thanks
Kai
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Optus issue in Broome, Sydney, Perth?

[Chad Kelly]

On 1/12/2018 2:43 PM, ausnog-requ...@lists.ausnog.net wrote:


Reports of problems making calls and sending sms from Optus users to
non-Optus users at these locations.
Looks to include Optus resellers (Virgin and OVO). Same reports from a
few Vodafone users in Sydney.
Yes we have some issues hear in Colac in Vic as well, not able to make 
or receive calls through the Optus network since yesterday.

But IPrimus staff at least had info on the outage.
Regards Chad.

--
Chad Kelly
Manager
CPK Web Services
Phone 03 5273 0246
Web www.cpkws.com.au

___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Optus issue in Broome, Sydney, Perth?

[Bradley Amm]

A cyclone just went through Broome today

Get Outlook for iOS

From: AusNOG  on behalf of Kai 

Sent: Friday, January 12, 2018 11:21:09 AM
To: ausnog@lists.ausnog.net
Subject: [AusNOG] Optus issue in Broome, Sydney, Perth?

Hi folks,

Belated Happy Christmas, and Happy New year to all!

Reports of problems making calls and sending sms from Optus users to
non-Optus users at these locations.
Looks to include Optus resellers (Virgin and OVO). Same reports from a
few Vodafone users in Sydney.

Problem started about 9:45am WST.
No known faults listed on Optus page as of five minutes ago.
Inbound calls and messages are ok so far.
Outbound calls and messages are failing.

Any feedback is appreciated.

Thanks
Kai
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] NBN NWAS and Cisco PPPoE

[Nathan Brookfield]

Hi Liam,

I believe this is the result of a software upgrade on NBN NWAS towers last week 
and this is a known issue, NBN are working with Cisco and the wireless vendors 
but this was something that has occurred and is wide spread for all Cisco NWAS 
users.

Kindest Regards,
Nathan Brookfield (VK2NAB)

Chief Executive Officer
Simtronic Technologies Pty Ltd

Local: (02) 4749 4949 | Fax: (02) 4749 4950 | Direct: (02) 4749 4951
Web: http://www.simtronic.com.au | E-mail: 
nathan.brookfi...@simtronic.com.au

[cid:image001.png@01D38BB3.AEA349A0]

CONFIDENTIALITY & PRIVILEGE NOTICE

The information contained in this email and any attached files is strictly 
private and confidential. The intended recipient of this email may only use, 
reproduce, disclose or distribute the information contained in this email and 
any attached files with Simtronic Technologies Pty Ltd’s permission. If you are 
not the intended recipient, you are strictly prohibited from using, 
reproducing, adapting, disclosing or distributing the information contained in 
this email and any attached files or taking any action in reliance on it. If 
you have received this email in error, please email the sender by replying to 
this message, promptly delete and destroy any copies of this email and any 
attachments.

It is your responsibility to scan this communication and any files attached for 
computer viruses and other defects and recommend that you subject these to your 
virus checking procedures prior to use. Simtronic Technologies Pty Ltd does NOT 
accept liability for any loss or damage (whether direct, indirect, 
consequential, economic or other) however caused, whether by negligence or 
otherwise, which may result directly or indirectly from this communication or 
any files attached.

From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of Liam Best
Sent: Friday, January 12, 2018 2:38 PM
To: ausnog@lists.ausnog.net
Subject: [AusNOG] NBN NWAS and Cisco PPPoE

Reaching out to see if anyone can shed some light on an issue we are 
encountering with NBN NWAS and Cisco routers.

We have two clients on NBN NWAS services, both using Cisco 1941 routers, both 
on opposite ends of Melbourne.

The carrier is AAPT for both services.

Just over a month ago, both services stopped working with our config, however 
the service works with a Juniper SSG5 - also works with a Windows laptop 
directly connected to the NTU (and even an old D-LINK).

We have also tried a Cisco 800 series router, but same issue occurs.

From the Cisco log:

000124: *Jan 11 09:31:29.323:  Sending PADI: Interface = GigabitEthernet0/0
000125: *Jan 11 09:31:29.619: PPPoE 0: I PADO  R:f8c2.8864.e230 
L:1cdf.0ff7.c640 Gi0/0
000126: *Jan 11 09:31:31.627:  PPPOE: we've got our pado and the pado timer 
went off
000127: *Jan 11 09:31:31.627: OUT PADR from PPPoE Session
000128: *Jan 11 09:31:31.659: PPPoE 0: I PADS  R:f8c2.8864.e230 
L:1cdf.0ff7.c640 Gi0/0
000129: *Jan 11 09:31:31.659: IN PADS from PPPoE Session
000130: *Jan 11 09:31:31.659:  PPPoE : Shutting down client session
000131: *Jan 11 09:31:31.659:  PPPoE : Failed to notify platform about session 
shutdown, no vaccess swidb
000132: *Jan 11 09:31:31.659: [0]PPPoE 0:
router#O PADT  R:.. L:.. Gi0/0

All other NBN services work with this config, it just seems to be the 
combination of our Cisco config and NWAS.

These services were working with this hardware and same config for around 3-4 
months after the service was activated.

If anyone has a working sample config for Cisco routers on NBN NWAS, or any 
ideas to what might cause this, it would be much appreciated.

Liam Best

[cid:image007.png@01D38BB3.AE9EDCD0]

Centorrino Technologies Pty Ltd | 11/9 Dawson Street Coburg VIC 3058 Australia

P: 1300 852 110 | Fax: 03 9354 3060 | lb...@ct.com.au | 
www.ct.com.au



[cid:image008.jpg@01D38BB3.AE9EDCD0]  
[cid:image009.jpg@01D38BB3.AE9EDCD0] 
  
[cid:image010.jpg@01D38BB3.AE9EDCD0]   
[cid:image011.jpg@01D38BB3.AE9EDCD0] 



___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

[Matthew Moyle-Croft]

Ask them for a bilateral session then do something evil like put 7545 in
the path :)

On Thu, Jan 11, 2018 at 4:03 PM, John Alexander 
wrote:

> That's what I've done for the time being, it would be just good to
> actually use HE but anyway...
>
> On 01/12/2018 11:01 AM, Matthew Moyle-Croft wrote:
>
> https://www.megaport.com/blog/fine-tuning-route-advertisements/
>
> .. has at least how to block advertisements TO peers on the MP RS. That
> should at least stop any bad latency issues even if it does mean not being
> able to use the HE routes.
>
> On Thu, Jan 11, 2018 at 3:36 PM, John Alexander 
> wrote:
>
>> That's what I'd like to do, but TPG don't peer at NSW-IX or Megaport for
>> that matter.  They are only at Pipe, unless they are secretly there and
>> don't tell anyone...
>>
>> On 01/12/2018 10:33 AM, Mark Newton wrote:
>>
>> Bilateral peering with TPG over the NSW-IX fabric should fix that.
>>
>>   - mark
>>
>> On Jan 12, 2018, at 7:46 AM, John Alexander 
>> wrote:
>>
>> With this, does anyone know of a way of keeping HE routes, but excluding
>> a specific one, namely TPG 7545 which is a direct customer of HE. Traffic
>> from them goes from Syd -> LA -> Syd -> he peering -> me.  I'd prefer to
>> just make them stay at home so to speak instead of going around the world.
>> We don't peer at Pipe which would be the only other place to connect to tpg.
>>
>> John
>>
>> On 01/11/2018 05:55 PM, Nathan Le Nevez wrote:
>>
>> I assume it was Hurricane Electric...IPv6 routes are now at 21843 too
>>
>> Nathan
>>
>> -Original Message-
>> From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net 
>> ] On Behalf Of Paul Holmanskikh
>> Sent: Thursday, 11 January 2018 5:00 PM
>> To: ausnog@lists.ausnog.net
>> Subject: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes
>>
>> G'day,
>>
>> Number of prefixes we are receiving from Megaport IX in Sydeney suddenly 
>> jumped to 40493.
>> At lest 100% grow.  Any ideas what happened.
>>
>>
>> as_path  count
>> 36351945
>> 4739 909
>> 9443 658
>>
>>
>>
>> ___
>> AusNOG mailing list
>> AusNOG@lists.ausnog.net
>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>
>>
>>
>>
>> ___
>> AusNOG mailing list
>> AusNOG@lists.ausnog.net
>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>
>>
>
>
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

[John Alexander]

That's what I've done for the time being, it would be just good to 
actually use HE but anyway...



On 01/12/2018 11:01 AM, Matthew Moyle-Croft wrote:

https://www.megaport.com/blog/fine-tuning-route-advertisements/

.. has at least how to block advertisements TO peers on the MP RS. 
That should at least stop any bad latency issues even if it does mean 
not being able to use the HE routes.


On Thu, Jan 11, 2018 at 3:36 PM, John Alexander > wrote:


That's what I'd like to do, but TPG don't peer at NSW-IX or
Megaport for that matter. They are only at Pipe, unless they are
secretly there and don't tell anyone...


On 01/12/2018 10:33 AM, Mark Newton wrote:

Bilateral peering with TPG over the NSW-IX fabric should fix that.

  - mark


On Jan 12, 2018, at 7:46 AM, John Alexander
> wrote:

With this, does anyone know of a way of keeping HE routes, but
excluding a specific one, namely TPG 7545 which is a direct
customer of HE. Traffic from them goes from Syd -> LA -> Syd ->
he peering -> me.  I'd prefer to just make them stay at home so
to speak instead of going around the world.  We don't peer at
Pipe which would be the only other place to connect to tpg.

John


On 01/11/2018 05:55 PM, Nathan Le Nevez wrote:

I assume it was Hurricane Electric...IPv6 routes are now at 21843 too

Nathan

-Original Message-
From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net
] On Behalf Of Paul Holmanskikh
Sent: Thursday, 11 January 2018 5:00 PM
To:ausnog@lists.ausnog.net 
Subject: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

G'day,

Number of prefixes we are receiving from Megaport IX in Sydeney suddenly 
jumped to 40493.
At lest 100% grow.  Any ideas what happened.


as_path count
36351   945
4739909
9443658



___
AusNOG mailing list
AusNOG@lists.ausnog.net 
http://lists.ausnog.net/mailman/listinfo/ausnog






___
AusNOG mailing list
AusNOG@lists.ausnog.net 
http://lists.ausnog.net/mailman/listinfo/ausnog





___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

[Matthew Moyle-Croft]

https://www.megaport.com/blog/fine-tuning-route-advertisements/

.. has at least how to block advertisements TO peers on the MP RS. That
should at least stop any bad latency issues even if it does mean not being
able to use the HE routes.

On Thu, Jan 11, 2018 at 3:36 PM, John Alexander 
wrote:

> That's what I'd like to do, but TPG don't peer at NSW-IX or Megaport for
> that matter.  They are only at Pipe, unless they are secretly there and
> don't tell anyone...
>
> On 01/12/2018 10:33 AM, Mark Newton wrote:
>
> Bilateral peering with TPG over the NSW-IX fabric should fix that.
>
>   - mark
>
> On Jan 12, 2018, at 7:46 AM, John Alexander  wrote:
>
> With this, does anyone know of a way of keeping HE routes, but excluding a
> specific one, namely TPG 7545 which is a direct customer of HE. Traffic
> from them goes from Syd -> LA -> Syd -> he peering -> me.  I'd prefer to
> just make them stay at home so to speak instead of going around the world.
> We don't peer at Pipe which would be the only other place to connect to tpg.
>
> John
>
> On 01/11/2018 05:55 PM, Nathan Le Nevez wrote:
>
> I assume it was Hurricane Electric...IPv6 routes are now at 21843 too
>
> Nathan
>
> -Original Message-
> From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net 
> ] On Behalf Of Paul Holmanskikh
> Sent: Thursday, 11 January 2018 5:00 PM
> To: ausnog@lists.ausnog.net
> Subject: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes
>
> G'day,
>
> Number of prefixes we are receiving from Megaport IX in Sydeney suddenly 
> jumped to 40493.
> At lest 100% grow.  Any ideas what happened.
>
>
> as_path   count
> 36351 945
> 4739  909
> 9443  658
>
>
>
> ___
> AusNOG mailing list
> AusNOG@lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
>
>
> ___
> AusNOG mailing list
> AusNOG@lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

[Mark Newton]

Bilateral peering with TPG over the NSW-IX fabric should fix that.

  - mark

> On Jan 12, 2018, at 7:46 AM, John Alexander  wrote:
> 
> With this, does anyone know of a way of keeping HE routes, but excluding a 
> specific one, namely TPG 7545 which is a direct customer of HE. Traffic from 
> them goes from Syd -> LA -> Syd -> he peering -> me.  I'd prefer to just make 
> them stay at home so to speak instead of going around the world.  We don't 
> peer at Pipe which would be the only other place to connect to tpg.
> 
> John
> 
> On 01/11/2018 05:55 PM, Nathan Le Nevez wrote:
>> I assume it was Hurricane Electric...IPv6 routes are now at 21843 too
>> 
>> Nathan
>> 
>> -Original Message-
>> From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net 
>> ] On Behalf Of Paul Holmanskikh
>> Sent: Thursday, 11 January 2018 5:00 PM
>> To: ausnog@lists.ausnog.net 
>> Subject: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes
>> 
>> G'day,
>> 
>> Number of prefixes we are receiving from Megaport IX in Sydeney suddenly 
>> jumped to 40493.
>> At lest 100% grow.  Any ideas what happened.
>> 
>> 
>> as_path  count
>> 36351945
>> 4739 909
>> 9443 658
>> 
>> 
> ___
> AusNOG mailing list
> AusNOG@lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog

___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

[Philip Loenneker]

I was referring to the BGP route selection rules. But as someone else pointed 
out, there are things like local pref that they can use, which falls within 
those rules…

From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of McDonald 
Richards
Sent: Friday, 12 January 2018 9:14 AM
To: ausnog@lists.ausnog.net
Subject: Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

Pretty sure there are no rules

On Fri, Jan 12, 2018 at 9:08 AM, Philip Loenneker 
> 
wrote:
Traffic engineering is difficult when people don’t play by the rules…

Perhaps using the HE community strings which Jacob suggested would be more 
helpful – you may be able to prevent HE advertising your subnets to TPG. Unless 
NSW-IX remove all community strings when they go to peers….

From: AusNOG 
[mailto:ausnog-boun...@lists.ausnog.net]
 On Behalf Of John Alexander
Sent: Friday, 12 January 2018 9:04 AM
To: ausnog@lists.ausnog.net

Subject: Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes


I tried this, with 3:6939 which added 3 prepends to he (which I could see at 
HE's LG) but TPG still preferred to send traffic via he rather than transit, 
even though the path was longer...

ughhh

On 01/12/2018 08:52 AM, Philip Loenneker wrote:

Note that you can also use BGP communities to adjust how the IX advertises your 
subnets to individual peers using the documentation here:

https://www.ix.asn.au/peering-technical/

Unfortunately you can't set a community of 0:7545 to avoid advertising your 
routes to TPG, as they aren't the direct peer - you would need to block 
advertising to HE using 0:6427. It may be sufficient for you to prepend the 
routes being advertised to HE, using 3:6427, to reduce the amount of traffic 
taking that path, but still keeping it available.



-Original Message-

From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of Bill Walker

Sent: Friday, 12 January 2018 8:11 AM

To: John Alexander 

Cc: ausnog@lists.ausnog.net

Subject: Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes



Filter based on the AS Path?



If the path is:



You <- 58941 <- 6427 <- 7545



You <- MegaIXSyd <- HE <- TPG



In the Cisco world, I would use



ip as-path access-list 10 deny ^58941_6427_7545$



(The ASN's here may not be exactly what is in use, you will need to check your 
received prefixes)



On 2018-01-12 09:46, John Alexander wrote:

With this, does anyone know of a way of keeping HE routes, but

excluding a specific one, namely TPG 7545 which is a direct customer

of HE. Traffic from them goes from Syd -> LA -> Syd -> he peering ->

me.  I'd prefer to just make them stay at home so to speak instead of

going around the world.  We don't peer at Pipe which would be the only

other place to connect to tpg.



John



On 01/11/2018 05:55 PM, Nathan Le Nevez wrote:



I assume it was Hurricane Electric...IPv6 routes are now at 21843 too



Nathan



-Original Message-

From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of

Paul Holmanskikh

Sent: Thursday, 11 January 2018 5:00 PM

To: ausnog@lists.ausnog.net

Subject: [AusNOG] Megaport IX Sydney - Sudden grows in number of

prefixes



G'day,



Number of prefixes we are receiving from Megaport IX in Sydeney

suddenly jumped to 40493.

At lest 100% grow.  Any ideas what happened.



as_pathcount

36351945

4739909

9443658

___

AusNOG mailing list

AusNOG@lists.ausnog.net

http://lists.ausnog.net/mailman/listinfo/ausnog

___

AusNOG mailing list

AusNOG@lists.ausnog.net

http://lists.ausnog.net/mailman/listinfo/ausnog

___

AusNOG mailing list

AusNOG@lists.ausnog.net

http://lists.ausnog.net/mailman/listinfo/ausnog

___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

[McDonald Richards]

Pretty sure there are no rules

On Fri, Jan 12, 2018 at 9:08 AM, Philip Loenneker <
philip.loenne...@tasmanet.com.au> wrote:

> Traffic engineering is difficult when people don’t play by the rules…
>
>
>
> Perhaps using the HE community strings which Jacob suggested would be more
> helpful – you may be able to prevent HE advertising your subnets to TPG.
> Unless NSW-IX remove all community strings when they go to peers….
>
>
>
> *From:* AusNOG [mailto:ausnog-boun...@lists.ausnog.net] *On Behalf Of *John
> Alexander
> *Sent:* Friday, 12 January 2018 9:04 AM
> *To:* ausnog@lists.ausnog.net
>
> *Subject:* Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of
> prefixes
>
>
>
> I tried this, with 3:6939 which added 3 prepends to he (which I could see
> at HE's LG) but TPG still preferred to send traffic via he rather than
> transit, even though the path was longer...
>
> ughhh
>
>
>
> On 01/12/2018 08:52 AM, Philip Loenneker wrote:
>
> Note that you can also use BGP communities to adjust how the IX advertises 
> your subnets to individual peers using the documentation here:
>
> https://www.ix.asn.au/peering-technical/
>
> Unfortunately you can't set a community of 0:7545 to avoid advertising your 
> routes to TPG, as they aren't the direct peer - you would need to block 
> advertising to HE using 0:6427. It may be sufficient for you to prepend the 
> routes being advertised to HE, using 3:6427, to reduce the amount of traffic 
> taking that path, but still keeping it available.
>
>
>
> -Original Message-
>
> From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net 
> ] On Behalf Of Bill Walker
>
> Sent: Friday, 12 January 2018 8:11 AM
>
> To: John Alexander  
>
> Cc: ausnog@lists.ausnog.net
>
> Subject: Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes
>
>
>
> Filter based on the AS Path?
>
>
>
> If the path is:
>
>
>
> You <- 58941 <- 6427 <- 7545
>
>
>
> You <- MegaIXSyd <- HE <- TPG
>
>
>
> In the Cisco world, I would use
>
>
>
> ip as-path access-list 10 deny ^58941_6427_7545$
>
>
>
> (The ASN's here may not be exactly what is in use, you will need to check 
> your received prefixes)
>
>
>
> On 2018-01-12 09:46, John Alexander wrote:
>
> With this, does anyone know of a way of keeping HE routes, but
>
> excluding a specific one, namely TPG 7545 which is a direct customer
>
> of HE. Traffic from them goes from Syd -> LA -> Syd -> he peering ->
>
> me.  I'd prefer to just make them stay at home so to speak instead of
>
> going around the world.  We don't peer at Pipe which would be the only
>
> other place to connect to tpg.
>
>
>
> John
>
>
>
> On 01/11/2018 05:55 PM, Nathan Le Nevez wrote:
>
>
>
> I assume it was Hurricane Electric...IPv6 routes are now at 21843 too
>
>
>
> Nathan
>
>
>
> -Original Message-
>
> From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net 
> ] On Behalf Of
>
> Paul Holmanskikh
>
> Sent: Thursday, 11 January 2018 5:00 PM
>
> To: ausnog@lists.ausnog.net
>
> Subject: [AusNOG] Megaport IX Sydney - Sudden grows in number of
>
> prefixes
>
>
>
> G'day,
>
>
>
> Number of prefixes we are receiving from Megaport IX in Sydeney
>
> suddenly jumped to 40493.
>
> At lest 100% grow.  Any ideas what happened.
>
>
>
> as_pathcount
>
> 36351945
>
> 4739909
>
> 9443658
>
> ___
>
> AusNOG mailing list
>
> AusNOG@lists.ausnog.net
>
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
> ___
>
> AusNOG mailing list
>
> AusNOG@lists.ausnog.net
>
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
> ___
>
> AusNOG mailing list
>
> AusNOG@lists.ausnog.net
>
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
> ___
> AusNOG mailing list
> AusNOG@lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

[John Alexander]

I tried this, with 3:6939 which added 3 prepends to he (which I could 
see at HE's LG) but TPG still preferred to send traffic via he rather 
than transit, even though the path was longer...


ughhh


On 01/12/2018 08:52 AM, Philip Loenneker wrote:

Note that you can also use BGP communities to adjust how the IX advertises your 
subnets to individual peers using the documentation here:
https://www.ix.asn.au/peering-technical/
Unfortunately you can't set a community of 0:7545 to avoid advertising your 
routes to TPG, as they aren't the direct peer - you would need to block 
advertising to HE using 0:6427. It may be sufficient for you to prepend the 
routes being advertised to HE, using 3:6427, to reduce the amount of traffic 
taking that path, but still keeping it available.

-Original Message-
From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of Bill Walker
Sent: Friday, 12 January 2018 8:11 AM
To: John Alexander 
Cc: ausnog@lists.ausnog.net
Subject: Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

Filter based on the AS Path?

If the path is:

You <- 58941 <- 6427 <- 7545

You <- MegaIXSyd <- HE <- TPG

In the Cisco world, I would use

ip as-path access-list 10 deny ^58941_6427_7545$

(The ASN's here may not be exactly what is in use, you will need to check your 
received prefixes)

On 2018-01-12 09:46, John Alexander wrote:

With this, does anyone know of a way of keeping HE routes, but
excluding a specific one, namely TPG 7545 which is a direct customer
of HE. Traffic from them goes from Syd -> LA -> Syd -> he peering ->
me.  I'd prefer to just make them stay at home so to speak instead of
going around the world.  We don't peer at Pipe which would be the only
other place to connect to tpg.

John

On 01/11/2018 05:55 PM, Nathan Le Nevez wrote:


I assume it was Hurricane Electric...IPv6 routes are now at 21843 too

Nathan

-Original Message-
From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of
Paul Holmanskikh
Sent: Thursday, 11 January 2018 5:00 PM
To: ausnog@lists.ausnog.net
Subject: [AusNOG] Megaport IX Sydney - Sudden grows in number of
prefixes

G'day,

Number of prefixes we are receiving from Megaport IX in Sydeney
suddenly jumped to 40493.
At lest 100% grow.  Any ideas what happened.

as_pathcount
36351945
4739909
9443658

___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

[Jacob Taylor]

Whoops, indeed that is the case.

It was one of the first results on Google that I found, didn't look close
enough.
Haven't had my coffee yet. :)

On Fri, Jan 12, 2018 at 8:53 AM, Jacob Taylor 
wrote:

> Won't that only work for traffic going from John's AS to TPG?
>
> His example was from TPG to their AS - If they were to implement a prefix
> list filtering on ASN, then they would preference another domestic route
> (presumably transit) but TPG would still preference HE, which would make
> for some lovely asynchronous routing.
>
> You could potentially try to influence their routing policies using their
> published communities (https://bgp.he.net/irr/as-set/AS-COMMUNITIES) or
> prepending.
>
> Regards,
> Jake
>
> On Fri, Jan 12, 2018 at 8:11 AM, Bill Walker  wrote:
>
>> Filter based on the AS Path?
>>
>> If the path is:
>>
>> You <- 58941 <- 6427 <- 7545
>>
>> You <- MegaIXSyd <- HE <- TPG
>>
>> In the Cisco world, I would use
>>
>> ip as-path access-list 10 deny ^58941_6427_7545$
>>
>> (The ASN's here may not be exactly what is in use, you will need to check
>> your received prefixes)
>>
>>
>> On 2018-01-12 09:46, John Alexander wrote:
>>
>>> With this, does anyone know of a way of keeping HE routes, but
>>> excluding a specific one, namely TPG 7545 which is a direct customer
>>> of HE. Traffic from them goes from Syd -> LA -> Syd -> he peering ->
>>> me.  I'd prefer to just make them stay at home so to speak instead of
>>> going around the world.  We don't peer at Pipe which would be the only
>>> other place to connect to tpg.
>>>
>>> John
>>>
>>> On 01/11/2018 05:55 PM, Nathan Le Nevez wrote:
>>>
>>> I assume it was Hurricane Electric...IPv6 routes are now at 21843
 too

 Nathan

 -Original Message-
 From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of
 Paul Holmanskikh
 Sent: Thursday, 11 January 2018 5:00 PM
 To: ausnog@lists.ausnog.net
 Subject: [AusNOG] Megaport IX Sydney - Sudden grows in number of
 prefixes

 G'day,

 Number of prefixes we are receiving from Megaport IX in Sydeney
 suddenly jumped to 40493.
 At lest 100% grow.  Any ideas what happened.

 as_pathcount
 36351945
 4739909
 9443658

>>> ___
>>> AusNOG mailing list
>>> AusNOG@lists.ausnog.net
>>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>>
>> ___
>> AusNOG mailing list
>> AusNOG@lists.ausnog.net
>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>
>
>
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

[Jacob Taylor]

Won't that only work for traffic going from John's AS to TPG?

His example was from TPG to their AS - If they were to implement a prefix
list filtering on ASN, then they would preference another domestic route
(presumably transit) but TPG would still preference HE, which would make
for some lovely asynchronous routing.

You could potentially try to influence their routing policies using their
published communities (https://bgp.he.net/irr/as-set/AS-COMMUNITIES) or
prepending.

Regards,
Jake

On Fri, Jan 12, 2018 at 8:11 AM, Bill Walker  wrote:

> Filter based on the AS Path?
>
> If the path is:
>
> You <- 58941 <- 6427 <- 7545
>
> You <- MegaIXSyd <- HE <- TPG
>
> In the Cisco world, I would use
>
> ip as-path access-list 10 deny ^58941_6427_7545$
>
> (The ASN's here may not be exactly what is in use, you will need to check
> your received prefixes)
>
>
> On 2018-01-12 09:46, John Alexander wrote:
>
>> With this, does anyone know of a way of keeping HE routes, but
>> excluding a specific one, namely TPG 7545 which is a direct customer
>> of HE. Traffic from them goes from Syd -> LA -> Syd -> he peering ->
>> me.  I'd prefer to just make them stay at home so to speak instead of
>> going around the world.  We don't peer at Pipe which would be the only
>> other place to connect to tpg.
>>
>> John
>>
>> On 01/11/2018 05:55 PM, Nathan Le Nevez wrote:
>>
>> I assume it was Hurricane Electric...IPv6 routes are now at 21843
>>> too
>>>
>>> Nathan
>>>
>>> -Original Message-
>>> From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of
>>> Paul Holmanskikh
>>> Sent: Thursday, 11 January 2018 5:00 PM
>>> To: ausnog@lists.ausnog.net
>>> Subject: [AusNOG] Megaport IX Sydney - Sudden grows in number of
>>> prefixes
>>>
>>> G'day,
>>>
>>> Number of prefixes we are receiving from Megaport IX in Sydeney
>>> suddenly jumped to 40493.
>>> At lest 100% grow.  Any ideas what happened.
>>>
>>> as_pathcount
>>> 36351945
>>> 4739909
>>> 9443658
>>>
>> ___
>> AusNOG mailing list
>> AusNOG@lists.ausnog.net
>> http://lists.ausnog.net/mailman/listinfo/ausnog
>>
> ___
> AusNOG mailing list
> AusNOG@lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

[Philip Loenneker]

Note that you can also use BGP communities to adjust how the IX advertises your 
subnets to individual peers using the documentation here:
https://www.ix.asn.au/peering-technical/
Unfortunately you can't set a community of 0:7545 to avoid advertising your 
routes to TPG, as they aren't the direct peer - you would need to block 
advertising to HE using 0:6427. It may be sufficient for you to prepend the 
routes being advertised to HE, using 3:6427, to reduce the amount of traffic 
taking that path, but still keeping it available.

-Original Message-
From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of Bill Walker
Sent: Friday, 12 January 2018 8:11 AM
To: John Alexander 
Cc: ausnog@lists.ausnog.net
Subject: Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

Filter based on the AS Path?

If the path is:

You <- 58941 <- 6427 <- 7545

You <- MegaIXSyd <- HE <- TPG

In the Cisco world, I would use

ip as-path access-list 10 deny ^58941_6427_7545$

(The ASN's here may not be exactly what is in use, you will need to check your 
received prefixes)

On 2018-01-12 09:46, John Alexander wrote:
> With this, does anyone know of a way of keeping HE routes, but 
> excluding a specific one, namely TPG 7545 which is a direct customer 
> of HE. Traffic from them goes from Syd -> LA -> Syd -> he peering -> 
> me.  I'd prefer to just make them stay at home so to speak instead of 
> going around the world.  We don't peer at Pipe which would be the only 
> other place to connect to tpg.
> 
> John
> 
> On 01/11/2018 05:55 PM, Nathan Le Nevez wrote:
> 
>> I assume it was Hurricane Electric...IPv6 routes are now at 21843 too
>> 
>> Nathan
>> 
>> -Original Message-
>> From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of 
>> Paul Holmanskikh
>> Sent: Thursday, 11 January 2018 5:00 PM
>> To: ausnog@lists.ausnog.net
>> Subject: [AusNOG] Megaport IX Sydney - Sudden grows in number of 
>> prefixes
>> 
>> G'day,
>> 
>> Number of prefixes we are receiving from Megaport IX in Sydeney 
>> suddenly jumped to 40493.
>> At lest 100% grow.  Any ideas what happened.
>> 
>> as_pathcount
>> 36351945
>> 4739909
>> 9443658
> ___
> AusNOG mailing list
> AusNOG@lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog
___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

[Bill Walker]

Filter based on the AS Path?

If the path is:

You <- 58941 <- 6427 <- 7545

You <- MegaIXSyd <- HE <- TPG

In the Cisco world, I would use

ip as-path access-list 10 deny ^58941_6427_7545$

(The ASN's here may not be exactly what is in use, you will need to 
check your received prefixes)


On 2018-01-12 09:46, John Alexander wrote:

With this, does anyone know of a way of keeping HE routes, but
excluding a specific one, namely TPG 7545 which is a direct customer
of HE. Traffic from them goes from Syd -> LA -> Syd -> he peering ->
me.  I'd prefer to just make them stay at home so to speak instead of
going around the world.  We don't peer at Pipe which would be the only
other place to connect to tpg.

John

On 01/11/2018 05:55 PM, Nathan Le Nevez wrote:


I assume it was Hurricane Electric...IPv6 routes are now at 21843
too

Nathan

-Original Message-
From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of
Paul Holmanskikh
Sent: Thursday, 11 January 2018 5:00 PM
To: ausnog@lists.ausnog.net
Subject: [AusNOG] Megaport IX Sydney - Sudden grows in number of
prefixes

G'day,

Number of prefixes we are receiving from Megaport IX in Sydeney
suddenly jumped to 40493.
At lest 100% grow.  Any ideas what happened.

as_pathcount
36351945
4739909
9443658

___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Re: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

[John Alexander]

With this, does anyone know of a way of keeping HE routes, but excluding 
a specific one, namely TPG 7545 which is a direct customer of HE. 
Traffic from them goes from Syd -> LA -> Syd -> he peering -> me.  I'd 
prefer to just make them stay at home so to speak instead of going 
around the world.  We don't peer at Pipe which would be the only other 
place to connect to tpg.


John


On 01/11/2018 05:55 PM, Nathan Le Nevez wrote:

I assume it was Hurricane Electric...IPv6 routes are now at 21843 too

Nathan

-Original Message-
From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of Paul 
Holmanskikh
Sent: Thursday, 11 January 2018 5:00 PM
To: ausnog@lists.ausnog.net
Subject: [AusNOG] Megaport IX Sydney - Sudden grows in number of prefixes

G'day,

Number of prefixes we are receiving from Megaport IX in Sydeney suddenly jumped 
to 40493.
At lest 100% grow.  Any ideas what happened.


as_path count
36351   945
4739909
9443658


___
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog