Need to configure a cisco 1900 series, my internal servers need be accessed over the web, was allocated a block of 6 ip addresses by my ISP which where routed to one(1) Public ip.
What's your question lol???????
A standard PPPoA config is below
interface atm0
no shut
pvc 0/38
encapsulation aal5mux ppp dialer
dialer pool-member 1
interface dialer1
ip address negotiated
ip nat outside
encapsulation ppp
dialer pool 1
ppp chap hostname <username>
ppp chap password <password>
ppp authentication chap callin
A standard PPPoA config is below
interface atm0
no shut
pvc 0/38
encapsulation aal5mux ppp dialer
dialer pool-member 1
interface dialer1
ip address negotiated
ip nat outside
encapsulation ppp
dialer pool 1
ppp chap hostname <username>
ppp chap password <password>
ppp authentication chap callin
Is the connection to the ISP in the same subnet as the block they gave you or does your connection have a different subnet.
For example say they gave you (These are random sample ip) 122.111.100.9-122.111.100.14 . There are 2 ways they can do this.
They assign you wan ip of your device 122.111.100.9 and then route the other 5 address to 122.111.100.9
They assign you wan ip of your device 200.201.123.66 and then route the 6 address to 200.201.123.66.
The second on is a little easier. On the ethernet port you are using for your servers you could assign 122.111.100.9 to the router and then assign the rest to the server directly using a subnet mask of 122.111.100.x 255.255.255.248
If it is the first case then it get messy. First you assign a private network to the lan interface say 192.168.100.1. You now put in static routes for the remaining 5 addresses and point them to the ethernet interface (this is to make nat work correctly). You define the wan interface as nat outside and the lan nat inside. You then build static nat entries mapping the other 5 addresses to the inside machines.
You can if your servers support it use only routing but it requires the server to support the concept of loopback. You would again assign the servers to a private network of say 192.168.100.1 but this time instead of using nat you would place a /32 static route for the real IP to the 192.168.100.x ip of the server who is to use it. The server in effect would be responsible for knowing that it could receive traffic for this ip on the interface that has the other IP.
For example say they gave you (These are random sample ip) 122.111.100.9-122.111.100.14 . There are 2 ways they can do this.
They assign you wan ip of your device 122.111.100.9 and then route the other 5 address to 122.111.100.9
They assign you wan ip of your device 200.201.123.66 and then route the 6 address to 200.201.123.66.
The second on is a little easier. On the ethernet port you are using for your servers you could assign 122.111.100.9 to the router and then assign the rest to the server directly using a subnet mask of 122.111.100.x 255.255.255.248
If it is the first case then it get messy. First you assign a private network to the lan interface say 192.168.100.1. You now put in static routes for the remaining 5 addresses and point them to the ethernet interface (this is to make nat work correctly). You define the wan interface as nat outside and the lan nat inside. You then build static nat entries mapping the other 5 addresses to the inside machines.
You can if your servers support it use only routing but it requires the server to support the concept of loopback. You would again assign the servers to a private network of say 192.168.100.1 but this time instead of using nat you would place a /32 static route for the real IP to the 192.168.100.x ip of the server who is to use it. The server in effect would be responsible for knowing that it could receive traffic for this ip on the interface that has the other IP.
TRENDING THREADS
-
-
Question Intel Arc A750 for around $190. Is it worth it?
- Started by Dolphing Kujog
- Replies: 1
-
Facebook
Twitter
Instagram