Join Log in
Score:0
Ben avatar Server

ip route not respected

bd flag
Ben

I have a win10 gateway box with the following route setup.

8 ----- Adapter#1  [   10.0.1.0/24 -> 10.0.1.254 ]
                                         \--> other subnets  -> Internet ]
7 ----- Adapter#2  [192.168.1.0/24 -> 192.168.1.99 -> other subnets]
Active Routes:

IPv4 Route Table
======================================================================
Active Routes:
Network Destination    Netmask       Gateway     Interface Metric
      0.0.0.0          0.0.0.0    10.0.1.254     10.0.1.24    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
     10.0.0.0    255.255.255.0       On-link     10.0.1.24    281
    10.0.0.24  255.255.255.255       On-link     10.0.1.24    281
   10.0.0.255  255.255.255.255       On-link     10.0.1.24    281
  192.168.1.0    255.255.255.0       On-link  192.168.1.98    235
 192.168.1.98  255.255.255.255       On-link  192.168.1.98    291
 192.168.1.99  255.255.255.255       On-link  192.168.1.98    235
192.168.1.255  255.255.255.255       On-link  192.168.1.98    291
 192.168.99.0    255.255.255.0  192.168.1.99  192.168.1.98    335
    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     10.0.1.24    281
    224.0.0.0        240.0.0.0       On-link  192.168.1.98    291
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     10.0.1.24    281
255.255.255.255  255.255.255.255     On-link  192.168.1.98    291
=======================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
     192.168.99.0    255.255.255.0     192.168.1.99     300
          0.0.0.0          0.0.0.0       10.0.1.254  Default
=======================================================================

Pinging host on 192.168.1.0/24 subnet usually works fine, until that host is down. The error message becomes

C:\Users\Administrator>ping 192.168.1.2 -t

Pinging 192.168.1.2 with 32 bytes of data:
Reply from 10.0.0.1: TTL expired in transit.
Reply from 10.0.0.1: TTL expired in transit.
Reply from 10.0.0.1: TTL expired in transit.
Reply from 10.0.0.1: TTL expired in transit.
Reply from 10.0.0.1: TTL expired in transit.

which seems to suggest incorrect ip route. The metric for 192.168.1.0 rule was initially higher than default. I manually set it to 200, then it become 235 which is lower than the default 281.

If I remembered correctly, It worked right after the adjustment. But today, after 24 hours, the host went online and offline several times in between, the ping error become from 10.0.0.1 TTL expired again. I suppose this mean the packet is routed through 10.0.1.245 again, since I don't even have 10.0.0.1 in my route table.

Currently arp -a showed no entry for 192.168.1.2; is this the default behavour when no ARP entry is not available (these hosts use dhcp) ? How do I stop win10 from routing local ip packet through default gw when the target disappeared from local net?

40
0 + 0
ธงชาติไทย
Elon Musk
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.