Cisco 827 ADSL with 2 sets of public ip addresses

I have seen this before. Some ISPs give you a single static and a range when you ask for more than one static address.

It does not matter which addresses you give to which interfaces.

Just don't worry about it.

The ISP will route ANY traffic to ANY of your addresses to you and if you have say

ip route 0.0.0.0 0.0.0.0 dialer x

then you will route all trafic to the internet corectly.

Point to point links on non-broadcast media such as DSL don't care about the IP address of the far end - AT ALL.

If you have a specific requirement then please elaborate it.

Post full details of what you want to do and someone may come up with something to assist.

i.e. mail server on this address outbound traffic from this address

...

If you have somehitng working post that too. There are many ways of carving the DSL stick.

This sounds like you have asked for more than one static and the ISP has given you a the range

• an extra static.

Basically and fortunately you don't need to worry about it.

Traffic to your addresses will be routed appropriately and if you have say ip route 0.0.0.0 0.0.0.0 dialer x traffic will be to the ISP.

Point to point non-broadcast links do not care if the addresses match on the two ends. (no arp).

If you want to NAT the various addresses just do it. If you wanted to real devices in the range on the inside you could put a secondary address on eth0 of one of the range and use that as a def gateway for your hosts.

It doesn't matter what address you allocate for the dialer just pick one.

Unusually for this field just pick an address stop worrying and it will all work.

Thanks, that totally worked... I thought it would be more complicated than that.

Here's the outline of my working config:

====

ip subnet-zero ip classless

interface Ethernet0 ip address 10.10.10.1 255.255.255.192 ip nat inside ip tcp adjust-mss 1452

interface ATM0 no ip address no atm ilmi-keepalive bundle-enable dsl operating-mode auto

interface ATM0.1 point-to-point pvc 0/35 pppoe-client dial-pool-number 1

interface Dialer1 bandwidth 7000 ip address *PrimaryIP* 255.255.255.254 ip address */29 #1* 255.255.255.248 secondary ip address */29 #2* 255.255.255.248 secondary ip address */29 #3* 255.255.255.248 secondary ip address */29 #4* 255.255.255.248 secondary ip address */29 #5* 255.255.255.248 secondary ip address */29 #6* 255.255.255.248 secondary ip mtu 1492 ip nat outside encapsulation ppp ip tcp adjust-mss 1452 dialer pool 1 no cdp enable ppp chap hostname *DSL LOGIN* ppp chap password 0 *DSL PASS* ppp pap sent-username *DSL LOGIN* password 0 *DSL PASS*

ip nat inside source route-map nonat interface Dialer1 overload

• STATIC PAT / NAT here * ip nat inside sources static tcp 10.10.10.2 25 *PrimaryIP* 25 extendable

- and / or - ip nat inside source static 10.10.10.3 */29 #1* ip nat inside source static 10.10.10.4 */29 #2*

ip route 0.0.0.0 0.0.0.0 Dialer1 permanent ip route 10.10.10.0 255.255.255.192 Ethernet0

access-list 1 permit 0.0.0.0 access-list 1 permit 10.10.10.0 0.0.0.63

====

Jack Baker NeuStyle Solutios Ltd.

As long as it is working that's OK.

You will I am pretty (very:) sure that you don't need to bother with the secondary addresses on the interface. NAT is happy with addresses that don't have any physical presence.

Of course if you want to be able to manage the router from the internet on these addresses then you will need the secondaries.

int di 0 ip address 1.1.1.1 255.255.255.255 ! ip address 2.2.2.2 255.255.255.248 sec !! NOT NEEDED ! ip address 2.2.2.3 255.255.255.248 sec !! NOT NEEDED

ip nat inside source static 192.168.1.2 2.2.2.2 ip nat inside source static 192.168.1.3 2.2.2.3 =2E....

That is all you need.