8 May
2017
8 May
'17
7 a.m.
Hi,
I added a gateway to one of my servers and set up a packet capture
system on it. It is running a webserver inside a container with the
relevant gateway configuration. The prefix is using the "BGP routed
subnets" configuration whereby the gateway is inside the prefix, but
using a /31.
https://u4477715.ct.sendgrid.net/wf/click?upn=Ki4chJONuNfM0VomxEE-2BoZH6yGO…
It should auto-detect the client IP and captures all packets to/from
that address. If the client IP is within 44/8 then it will check the
routing table for a gateway and if so include that IP as well. I am
not sure if there would be concerns with allowing the user to type an
IP address to capture to/from, given that it's a non-production
gateway.
I have the subnet 44.131.14.252/31 registered on the portal with a
gateway address of 44.131.14.253. 252 should send encapsulated packets
and 253 should send directly. Both addresses are on the same host.
I have removed my previous route for 44.131.14.0/24 because nested
gateways don't work properly. I have tested to several destinations
and it seems to work, but if anyone finds something I've missed let me
know!
If it works properly and is useful then a hostname under ampr.org
might be more appropriate, but for now I’m just using a hostname under
my domain.
Thanks,
Mike, M6XCV