13 Jul
2013
13 Jul
'13
10:44 p.m.
In the case of 44.24.240/20, we were seeing issues where traffic from some
networks (including google) wasn't making it back to our ASN for some
reason. I was theorizing that perhaps our more specific BGP announcement
wasn't being seen/honored in some circumstances in favor of the more
generic 44/8 one.
We intentionally setup the IPIP tunnels as an experiment and haven't had
that trouble since. I suppose I need to shut that down and see if the
problem returns to know for sure. Either way, we're in the encap file
intentionally and you don't need to remove it.
On Sat, Jul 13, 2013 at 4:04 PM, Bob Tenty <bobtenty(a)gmail.com> wrote:
> (Please trim inclusions from previous messages)
> _______________________________________________
> There are more subnets who are announcing themselfs over Internet with BGP
> and who are still in the encap.txt
>
> route addprivate 44.24.240/20 encap 198.178.136.80
> route addprivate 44.130.99/24 encap 193.22.2.254
> route addprivate 44.136.150/24 encap 203.55.214.21
> route addprivate 44.136.151/24 encap 203.55.214.21
> route addprivate 44.208/16 encap 94.101.48.134
>
> This will give a problem if your commercial gateway address has changed
> as in that case we can't reach your subnet.
> (If I don't remove them manually)
>
> $curl -s http://thyme.rand.apnic.net/current/data-add-ARIN | grep "
> 44\."
> 7377 44.0.0.0/8
> 226 44.16.15.0/24
> 32915 44.24.240.0/20
> 12637 44.68.52.0/24
> 8121 44.74.128.0/24
> 61337 44.127.128.0/24
> 28748 44.130.99.0/24
> 56129 44.136.150.0/24
> 56129 44.136.151.0/24
> 8973 44.140.0.0/16
> 1653 44.140.47.0/24
> 39120 44.208.0.0/16
>
>
>
> Bob/Boudewijn VE3TOK
>
>
> >It is a really a problem because that entry overrides the default.
> >Maybe Chris can remove it.
>
> >73,
>
> <Bob/Boudewijn VE3TOK
>
>
> On 13-07-13 04:59 PM, Bjorn Pehrson wrote:
> > Well, that is history and should eventually be cleaned up and
> > archived, I guess.
> > As far as I am aware, this does currently not create a problem.
> > When I pointed it out to Brian, he seemed to have the same opinion.
> > Pontus was the previous maintainer and handed it over to me.
> > If you look into the new data base at
> > https://portal.ampr.org/networks.php you will find me there.
> > Bjorn
> >
> > On 07/13/2013 10:29 PM, Bob Tenty wrote:
> >> (Please trim inclusions from previous messages)
> >> _______________________________________________
> >> There is still an entry for 44.140.0.0/16 in the encap.txt
> >> what gives a problem in that case.
> >>
> >> route addprivate 44.140/16 encap 90.225.73.203
> >> Gateway maintained by Pontus Falk SM0RUX
> >>
> >> 73,
> >>
> >> Bob/Boudewijn VE3TOK
> >>
> >>
> >
>
>