# About Routing

**URL:** <https://community.f5.com/t/about-routing/72003>\
**Category:** Technical Forums\
**Tags:** application-delivery\
**Created:** [March 30, 2023, 9:54am UTC](https://community.f5.com/t/about-routing/72003 "2023-03-30T09:54:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michaelyang](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/michaelyang/32/22761_2.png) [@Michaelyang](https://community.f5.com/u/Michaelyang)\
**Post date:** [March 30, 2023, 9:54am UTC](https://community.f5.com/t/about-routing/72003/1 "2023-03-30T09:54:20Z")

</div>

Hello,

Here is my structure:

 ![Michaelyang_0-1680169782386.png](https://d20hrnpixdzcsd.cloudfront.net/original/2X/3/3f7c5a0219539d622f13135adec4f04fa0bdb371.png)

My F5 can ping 192.168.1.1 through 10.10.10.254

 ![Michaelyang_1-1680169966385.png](https://d20hrnpixdzcsd.cloudfront.net/original/2X/9/9a68fe3c48a8904f818864074aacbdf5bc091470.png)

But why Win(192.168.1.1) can’t ping 10.10.10.254 ?

 ![Michaelyang_2-1680170003008.png](https://d20hrnpixdzcsd.cloudfront.net/original/2X/e/ef8934dffb9bbcfafb5a3c6b20840724377ee9aa.png)

Any help is appreciate.

---

<div class="post-metadata">

**Author:** ![mihaic](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/mihaic/32/2175_2.png) [@mihaic](https://community.f5.com/u/mihaic)\
**Post date:** [March 30, 2023, 2:51pm UTC](https://community.f5.com/t/about-routing/72003/2 "2023-03-30T14:51:03Z")

</div>

Because F5 is not a router, when you create a virtual server it accepts traffic which has the destination of that virtual server.

When you ping another interface other than where you come from it will not reply. I think it is normal.

“LTM is considered to be default deny. This means that&nbsp; **when no traffic processing objects are configured, for example, a virtual server and a pool, the BIG-IP system will not process any network traffic**. You need to configure at least one traffic processing object on the BIG-IP system to begin processing traffic.”

---

<div class="post-metadata">

**Author:** ![Rodrigo\_Albuque](https://avatars.discourse-cdn.com/v4/letter/r/8491ac/32.png) [@Rodrigo\_Albuque](https://community.f5.com/u/Rodrigo_Albuque)\
**Post date:** [March 30, 2023, 10:17pm UTC](https://community.f5.com/t/about-routing/72003/3 "2023-03-30T22:17:32Z")

</div>

You need to check F5’s routing table:

tmsh show /net route

To determine the route cause, you can take a wireshark packet capture on both interfaces:

> **[myF5](https://my.f5.com/manage/s/article/K13637)**

---

<div class="post-metadata">

**Author:** ![Brandon](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/brandon/32/826_2.png) [@Brandon](https://community.f5.com/u/Brandon)\
**Post date:** [March 30, 2023, 10:59pm UTC](https://community.f5.com/t/about-routing/72003/4 "2023-03-30T22:59:05Z")

</div>

Hello @Michaelyang ,

A selfip is only reachable when the request is received on the VLAN on which it is configured.

So you cannot ping a selfip through the BIG-IP even if you have a forwarding VS.

> **[myF5](https://my.f5.com/manage/s/article/K3475?sr=45778187)**