time based dialer string [7:31596]

[Chris Read]

What is the best way of managing a dial up interface
which needs to dial a different telephone number,
dependent upon the time of day? (same IP address
for both)

I have tried policy routing through 2 dialer interfaces,
each with time-based ACL's referenced through the
dialer-group statement. This which works fine
except that I also have an encrypted tunnel to which
the policy does not get applied.

Chris Read




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=31596t=31596
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

dialer interface: dial string and time-range [7:30681]

[Chris Read]

With reference to archive entry:

RE: Fail over to 2 ISDN Provider. [7:9899] posted 06/26/2001

I am trying to configure a VPN edge router (801/12.0.7T as it happens). The
router has been assigned a static, public IP address for the dialer
interface.
It is running an encrypted tunnel to another public IP address, as well as
NAT
between the internet and the internal ethernet interface.

I need to optimise the dialing, such that different numbers are dialed at
different times of the day.

The example quoted above will not work, as the policy routing only applies to
the e0 interface, and not to the packets generated by the tunnel.

My thoughts are as follows:-

1) Use loopback0 as the fixed IP address. Use 2 dialer interfaces with ip
unnumbered loopback0 and  dialer-groups using access lists with time-range.
How does the routing process cope with this?

2) Use loopback0 as the fixed IP address. Use policy routing on loopback0 to
2
dialer interfaces. Can policy routing be applied to loopback interfaces ??

3) Use 2 dialer interfaces, each with ip address negotiated, but with
different dialer-group and dialer string statements. Then use 2 equal cost
static routes. I suspect that this will result in 50% packet loss, as both
interfaces spoof as being up. Does Cisco do anything clever here?

4) Use 2 dialer interfaces etc. as before. Use 2 static routes with high
metric(AD) as floating statics. Run another routing protocol. Redistribute
static routes into the routing protocol, using a distribute-list with an
access-list containing time-range statements to perform the filtering.

I will try these in my lab this evening. Any thoughts or comments?

Chris Read




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=30681t=30681
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Ip precedence of GRE packets [7:19125]

[Chris Read]

Is it possible to cause the IP precedence of a GRE packet to be the same as
the IP precedence of the packet which it encapsulates?

I have a client who is passing real-time as well as normal data over a 3DES
encrypted tunnel. I have had to resort to using separate
tunnels for the two data streams, but I consider this to be a sub-optimal
solution.

For reference, I am using a 2621 at one end and a 3640 at the other with
12.1.5 images.

This is a real world problem for me. Would this kind of thing possibly come
up on the CCIE R/S exams?

Chris Read




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=19125t=19125
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]