17 May
2017
17 May
'17
4:32 p.m.
Thomas, thank you for your reply. So outbound non-44 destinations from
44.130.0.0/16 are routed out onto the internet at db0fhn instead of
being sent to amprgw? But the return path has to go through amprgw.
This is non-symmetric routing and I wasn't expecting it. (It's not
a problem.)
I have noted in the past that the link was often busy, and I expected
it would be busy in both directions. If it's not used for outbound
from 44.130.0.0/16, that would explain what I'm seeing for that
gateway.
I was worried that something had gone wrong somewhere because the overall
inbound encap traffic dropped by 90% or more suddenly at 19:00-19:15 on
Tuesday. Whatever happened did so quickly. I thought it was the db0fhn
gateway that malfunctioned but I could be wrong. I'll have to look
elsewhere.
You can see this sudden drop in the graph at 19:00 May 16 on
https://gw.ampr.org/router/encapinpkt.svg
- Brian
On Wed, May 17, 2017 at 09:54:47PM +0200, Thomas Osterried wrote:
What kind of traffic do you expect? The rest of 44/8
that is not ipip and not direct-bgp? Actually, db0fhn routes non-advertised 44-ipip-routes
(and non-44-hamnet-networks) to the internet (because non-ipip and non-hamnet is either
direct-bgp or not-in-use).
Perhaps, Jann has changed the 44/8 route; we need to wait for his answer.
vy 73,
- Thomas dl9sau