Demand-Dial/VPN and Rounting Updates

[Guest]

I've tried to setup two AD servers with Demand-Dial interfaces for each
direction. The connection of the interfaces succeed and seems to work.

Following this I've tried to set up routing, first by static routes but
without success, and then by auto-static (RIP).
After setting up the auto-static routing, I tried doing Update Routes a few
times to get the tables updates, but something seems to fail.

The following is registered under the RIP list:
On server Alpha:
Inteface Update mode Responses sent Responses received
VPN_Beta auto-static 8 0

On server Beta:
Inteface Update mode Responses sent Responses received
VPN_Alpha auto-static 10 8

So it seems that routing information aren't registered at Alpha though it's
sent from Beta. To ensure the problem wasn't due to network problems, I've
loaded a packet sniffer and made sure the packets are sent and received,
which is indeed the case. So the problem seems to be at the receiving end
(Alpha).

 

[Bill Grant]

I can't think of any reason to use auto-static routing in a
straight-forward setup like that. All you need is a static route on each
router to send traffic for the "other" site through link.

When this fails it is usually because the static routes are not tied to
the demand-dial interfaces, or one interface (usually the answering router)
is not binding to the connection. Each demand-dial interface must have a
static route linked to it, no matter which end initiates the connection. The
routes are only added to the routing table when the interfaces become
active. Are the dd interfaces on both RRAS routers showing as connected?

The method which binds the interface on the answering router to the
connection is the username. When you connect, the username must match the
name of the dd interface on the answering router. The connection will then
bind to the dd interface, the interface will show in the RRAS console as
connectd and the route will be added to the routing table.