5

I'm trying to get our local Sonicwall NSA 2600 to connect to a AWS VPN, within a VPC. I have the IKE portion working and AWS shows the two pipes are connected

The BGP routes show as up in the router

(config-routing)# show routing bgp summary
BGP router identifier 192.168.1.3, local AS number 65000
BGP table version is 8737
2 BGP AS-PATH entries
0 BGP community entries

Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
169.254.45.245  4  7224   51909   63298     8736    0    0 5d20h55m        1
169.254.46.161  4  7224   52390   63791     8736    0    0 5d20h55m        1

Total number of neighbors 2

What's baffling is that it appears that everything appears to be there. But attempting to get anything to route to the 174.0.0.0/16 block doesn't work (I know it's a public block but I can't change it at present)

(config-routing)# show routing nsm database

C    *> 169.254.45.244/30 is directly connected, T2
C    *> 169.254.45.247/32 is directly connected, T2
C    *> 169.254.46.160/30 is directly connected, T1
C    *> 169.254.46.163/32 is directly connected, T1
B    *> 174.0.0.0/16 [20/100] via 169.254.46.161, T1, 5d20h57m
C    *> 192.168.1.0/24 is directly connected, X0

I've never dealt with BGP so I'm at a complete loss how to debug it further, or determine how to get it to send into or out of the VPC. I cannot get pings, RDC or SSH to work through the internal IPs.

Adding the route table, as obtained from my PC

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.3    192.168.1.153    281
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
      192.168.1.0    255.255.255.0         On-link     192.168.1.153    281
    192.168.1.153  255.255.255.255         On-link     192.168.1.153    281
    192.168.1.255  255.255.255.255         On-link     192.168.1.153    281
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link     192.168.1.153    281
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link     192.168.1.153    281
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0      192.168.1.3  Default
===========================================================================

There is a route in the Sonicwall routing

I played with this some and got the BGP routes listed correctly, but still no luck on getting traffic to flow

   Network          Next Hop            Metric LocPrf Weight Path
*  174.0.0.0        169.254.45.245         200             0 7224 i
*>                  169.254.46.161         100             0 7224 i
*> 192.168.1.0      0.0.0.0                       100  32768 i
Improve this question
  • Are you using those link-local addresses based on the tutorial or from your actual configuration? I've never used AWS but that seems strange. Can you ping the BGP neighbors? – Zac67 Jun 11 '17 at 21:10
  • what is your route for 169.254.46.161 in the routing table? – john Jun 11 '17 at 22:41
  • I cannot ping the BGP neighbors. The addressing was provided directly by AWS itself – Machavity Jun 12 '17 at 12:38
  • 2
    It's hard to help you if you just keep spoon-feeding us information. Please post your router configs and the routing table from both sides. From what you've posted so far, I don't see a route from the VPC back to you. – Ron Trunk Jun 14 '17 at 17:17
  • 1
    Please post your router configuration – Ron Trunk Jun 14 '17 at 22:10