Forum Discussion

Goldz_180077's avatar
Goldz_180077
Icon for Nimbostratus rankNimbostratus
Jun 09, 2016

routing Issues on F5

Hi F5 Team,

 

How can this 2 ip segment communicate on F5.

 

Config Details: F5 port 1 with self ip 192.168.50.1/26 with direct client pc ip 192.168.50.10/26 gateway to F5 192.168.50.1 F5 port 2 with self ip 192.168.51.1/26 with direct client pc ip 192.168.51.10/26 gateway to F5 192.168.51.1

 

Testing: On 192.168.50.10 PC, i want to ping the 192.168.51.1 self ip of port 2 and PC 192.168.51.10 On 192.168.51.10 PC, i want to ping the 192.168.50.1 self ip of port 2 and PC 192.168.50.10

 

Thanks!

 

Goldz

 

application delivery
BIG-IP
LTM

4 Replies

Sort By
  • DevBabu's avatar
    DevBabu
    Icon for Cirrus rankCirrus
    Jun 09, 2016
    What's your issue ? Is icmp packet not reaching F5 box or the packet is not getting out ? How does your routing table looks like in the box ? I hope they should communicate with default settings if icmp is not blocked. Still have issues, I would try creating wildcard forwarding virtual server with all protocols enabled. Thanks
  • Goldz_180077's avatar
    Goldz_180077
    Icon for Nimbostratus rankNimbostratus
    Jun 09, 2016
    i have no routing, i only created forwarding ip vs any any. the issues is, ping from pc to pc.
  • Arnaud_Lemaire's avatar
    Arnaud_Lemaire
    Icon for Employee rankEmployee
    Jun 09, 2016

    Could you check on the forwarding virtual server that protocol is set to All protocol, bu default it's tcp only.

     

    then a pcap on the bigip could probably help.

     

  • DevBabu's avatar
    DevBabu
    Icon for Cirrus rankCirrus
    Jun 09, 2016

    captures will definitely help. Please take capture to share.