3

I've added a persistent route to our Windows Server 2003 box using "route -p add". After a reboot the "route print" gave this:

Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric    
          0.0.0.0          0.0.0.0      10.91.131.1      10.91.131.9     20
        10.88.0.0  255.255.255.252        10.88.0.1        10.88.0.1     30
        10.88.0.1  255.255.255.255        127.0.0.1        127.0.0.1     30
      10.91.131.0    255.255.255.0      10.91.131.9      10.91.131.9     20
      10.91.131.9  255.255.255.255        127.0.0.1        127.0.0.1     20
   10.255.255.255  255.255.255.255        10.88.0.1        10.88.0.1     30
   10.255.255.255  255.255.255.255      10.91.131.9      10.91.131.9     20
        127.0.0.0        255.0.0.0        127.0.0.1        127.0.0.1      1
        224.0.0.0        240.0.0.0        10.88.0.1        10.88.0.1     30
        224.0.0.0        240.0.0.0      10.91.131.9      10.91.131.9     20
  255.255.255.255  255.255.255.255        10.88.0.1        10.88.0.1      1
  255.255.255.255  255.255.255.255      10.91.131.9      10.91.131.9      1
Default Gateway:       10.91.131.1
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
        10.88.0.0    255.255.255.0        10.88.0.2       1

The route I added is listed as a persistent route, but not an active one. Why might this be the case?

The route in question is for an OpenVPN connection, would that have anything to do with it?

Edit I should have mentioned that the route was not working. Only once it was added again did it work. After that it did show in the Active Routes table.

alnorth29
  • 395

4 Answers4

2

As far as I'm aware, the differentiation between Active and Persistent in the route command is simply to make it easier to identify which routes are learned and/or temporary, against those that you have explicitly added as persistent.

I'm sure someone will correct me if I'm wrong :)

Pulse
  • 4,589
  • 2
  • 21
  • 20
2

I'm getting a similar problem with a VPN connection. After a sleep / wake of the laptop, the persistent route over the VPN is no longer active. Add it again with route add ... -p it then is still listed as a persistent connection, but is active again.

Some possibly related / helpful links, but nothing too conclusive.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010644

https://serverfault.com/questions/193335/static-route-from-a-windows-7-client-not-working-as-expected

http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/windows-7-no-dns-or-no-network-after-resume-wake/c1253ab0-4793-449e-8975-a900ce7dec4f

http://forums.speedguide.net/showthread.php?269551-How-to-AUTOMATE-VPN-reconnection-during-PC-wake-up-from-sleep-mode

How to reconnect VPN automatically after sleep/hibernate on Vista/7?

Community
  • 1
Simon D
  • 7,061
1

Run your same add command without the -p and the route will be active.

If you run the command with -p, it will only become active after a restart.

Mogget
  • 1,353
Jose
  • 19
0

From Active Route,

10.88.0.0  255.255.255.252        10.88.0.1

From Persistent Route,

10.88.0.0    255.255.255.0        10.88.0.2

Please change (Netmask) in Persistent Route as

10.88.0.0  255.255.255.252        10.88.0.2

I guess, more specific subnet mask take precedence...

Gabe
  • 176
Zack
  • 1