gre
2 TopicsGRE Tunnel Issue
Has anyone run into an issue with GRE tunnels on a BIG-IP? I have a few setup running into a TGW in AWS and something seems to break them. Config change, Module change, ?? I haven't been able to pin down an exact trigger. Sometimes I could failover and have the tunnels on the other HA member work fine and failing back would results in tunnels going down again. (The tunnels are unique to each BIG-IP) They start responding with ICMP protocol 47 unavailable. Once this happens a reboot doesn't seem to fix it. If I tear down the BIG-IP and rebuild it, I can keep them working again for X amount of time before the cycle repeats. Self-IPs are open to the protocol, also tried allow all for a bit. No NATs involved with underlay IPs.80Views0likes2CommentsGRE Tunnel From F5 to Linux Server
Hi, I have 2 redhat 6 linux servers that have a GRE tunnel configured between them as follows: GRE1 Linux Server: ONBOOT=yes DEVICE=tun0 TYPE=GRE MY_INNER_IPADDR=192.168.255.2 PEER_INNER_IPADDR=192.168.255.1 PEER_OUTER_IPADDR=1.1.1.1 MY_OUTER_IPADDR=2.2.2.2 GRE2 Linux Server: ONBOOT=yes DEVICE=tun0 TYPE=GRE MY_INNER_IPADDR=192.168.255.1 PEER_INNER_IPADDR=192.168.255.2 PEER_OUTER_IPADDR=2.2.2.2 MY_OUTER_IPADDR=1.1.1.1 This is working just fine and I can ping both inner IPs from both directions. I would like to replace GRE2 with an F5 and have it provide the exact same GRE tunnel to GRE1 I've tried creating the tunnel and assigning a self IP, however, I can't seem to get ping to work and I'm confused on where each of the IP addresses would go in the F5 configuration (MY_INNER_IPADDR, PEER_INNER_IPADDR, etc). I'm looking for advise on how to mimic the configuration in GRE2 onto the F5. Thanks!Solved850Views0likes2Comments