Hi all,
On Wed, Apr 03, 2019 at 10:59:18AM -0400, Jay Borkenhagen wrote:
> I urge folks facing similar problems to publish RPKI ROAs for their IP
> resources. [snip] the verifiable statements in RPKI ROAs can be
> attributed to you as the actual resource holder, thus helping folks
> base their res
Hi nanog,
With help from China Unicom (as4837) and from folks in other key
places around the 'net, I am happy to report that this route
mis-origination has now been successfully resolved. Thanks, all!
I urge folks facing similar problems to publish RPKI ROAs for their IP
resources. I started on
Ack for NTT
On Mon, Apr 1, 2019 at 21:36 Christopher Morrow
wrote:
> (from offline chat and pokery)
>
> It looks like 701/1239/3356 are permitting 4837 to announce this prefix
> because:
> $ whois -h whois.radb.net 192.139.135.0
> route: 192.139.135.0/24
> descr: managedway company
> o
Any luck reaching AS4837?
route-views>show ip bgp 192.139.135.0/24 longer-prefixes
BGP table version is 103101215, local router ID is 128.223.51.103
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f
(from offline chat and pokery)
It looks like 701/1239/3356 are permitting 4837 to announce this prefix because:
$ whois -h whois.radb.net 192.139.135.0
route: 192.139.135.0/24
descr: managedway company
origin: AS53292
mnt-by: MAINT-AS53292
changed:rsand...@managedway.com 2018
[No attempts at 01-April humor will be attempted in this message.]
Seeking help from routing engineers around the 'net:
ARIN documents that 192.139.135.0/24 has been allocated to Metro
Wireless International:
https://whois.arin.net/rest/net/NET-192-139-135-0-1
Further, the party to whom 192.
6 matches
Mail list logo
