This actually assigns an ip address to the peer, so you will probably not need it, right now I'm not even sure why we are doing it.
2/ regarding the accesslists:
ip nat inside source list 105 interface Dialer700 overload
defines that all traffic matching list 105 will be NAT'ed, i.e. the source will be translated to the address (dynamically) assigned to interface dialer 700.
So list 105 defines which traffic needs to be translated when going out this interface. I don't know how you route some traffic over one dialer and other traffic over the other so I cannot determine this for you, but generally if you have a static route like this:
ip route 192.168.1.0 255.255.255.0 Dialer 700
you should have an accesslist like this:
access-list 105 permit ip any 192.168.1.0 0.0.0.255
Similarly for the other dialer:
ip nat inside source list 106 interface Dialer700 overload
ip route 172.16.0.0 255.255.0.0 Dialer 702
access-list 106 permit ip any 172.16.0.0 0.0.255.255
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.