| DHCP Question Hi
I was wondering about something.. I have a router (R1) setup on DHCP all my devices on that end funcion properly (2 PC's and a switch) on the other end I was going to connect another router (R2) via serial that has a switch and 2 other PC connected to it.
My question is how can I setup router 2 to share the DSL connection, so that the PC's on R2 can go out to the internet. Is that posible?
I wasnt able to figure it out
R1(config-if)#do sh run
Building configuration...
Current configuration : 923 bytes
!
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname R1
!
!
!
!
ip dhcp excluded-address 192.168.1.1 192.168.1.240
!
ip dhcp pool LAN_NETWORK
network 192.168.1.0 255.255.255.0
default-router 192.168.1.254
!
!
!
!
!
!
!
no ip domain-lookup
!
!
!
!
!
!
interface FastEthernet0/0
description ISP Connection
ip address dhcp
ip nat outside
duplex full
speed 100
!
interface FastEthernet0/1
description Connection to LAN Network
ip address 192.168.1.254 255.255.255.0
ip nat inside
duplex auto
speed auto
!
interface Serial0/0
no ip address
shutdown
!
interface Serial0/1
no ip address
shutdown
!
router eigrp 1
network 192.168.1.0
no auto-summary
!
ip nat inside source list 1 interface FastEthernet0/0 overload
ip classless
!
!
access-list 1 permit 192.168.1.0 0.0.0.255
!
!
!
!
!
line con 0
line vty 0 4
login
!
!
!
end
R1(config-if)# |
|
aryobaPremium,MVM
join:2002-08-22
kudos:1 | Since there are multiple routers, then there will be routing involved between multiple subnets.
There is already one subnet of 192.168.1.0/24 for the R1's LAN devices. You can assign (let's say) 192.168.2.0/24 for the R2's LAN devices.
If the R2 will be a stub router (meaning that R2 has no other connection other than connecting to R1), then you can simply use static routes to define default gateway pointing to R1. Similarly, there is a static route on R1 pointing to R2 to reach the 192.168.2.0/24.
When you setup the routers to be DHCP servers, don't forget to include the DNS server IP addresses within the dhcp pool configuration to make sure the LAN devices can resolve names to IP addresses.
I notice that the R1 also acts as NAT router. Should this be the case then make sure the R1's Serial interface you use to interconnect R1 and R2 has ip nat inside just like the one the R1's FastEthernet0/1 interface has. Note that R2 should not have ip nat command at all since the R2 will not be NAT router but just stub router.
Since there will be LAN machines within 192.168.2.0/24 that need to go out to the Internet, include the 192.168.2.0/24 in your R1's ACL 1 as permitted subnet just like the 192.168.1.0/24. |
|
| reply to krock83
Just out of curiousity, is there a specific design requirement why
you have another downstream router (R2) for additional connectivity?
Regards |
|
| reply to krock83
Thanks Aryoba, I will try that this weekend, I am litle confused about this so it may take some time to figure this out.
HELLFIRE - I was just wondering how it works on multiple routers. Since I dont work in the field of networking and still getting ready for my CCNA I am cirious how stuff liek that works, im not sure if there is anything like that in production, but I saw out network closet and we have about 30 routers connected to each other... not really sure why and what the purpose is.
Just to answer your question: I just wanted to know out of out of curiousity how stuff like that works |
|
|
|
cramer
join:2007-04-10
Raleigh, NC
kudos:5 Reviews:
 ·AT&T Southeast
| said by krock83:... not really sure why and what the purpose is. Find the person(s) in charge of the network and politely ask them. (don't expect to immediately understand the answer.  networks become messy over the years.)
In the real world (read: the whole of the internet), routers connect to routers that connect to other routers, forming a complicated web of interconnected networks. Think of it like a electronic version of the US Interstate highways. |
|
| reply to krock83
@krock83
No problems with wondering how / why things work. As cramer said, it's
all a bunch of different interstate highways connecting to other interstate
highways / road systems, and no different for someone at home connecting
two linksys / dlink / netgear / et al behind one another. I'd question
the logic of doing such a thing, but it does work.
BTW, if you were to do such a thing as above but with Cisco, you configs
may go something like:
R1
--
ip dhcp pool R1_DHCP
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
import all
ip dhcp excluded-address 192.168.1.101 192.168.1.200
int fa0/0
desc WAN CONNECTION
ip address dhcp
ip nat outside
int fa0/1
desc R1 LAN connection
ip address 192.168.1.1 255.255.255.0
ip nat inside
ip nat source list 1 int fa0/0 overload
access-list 1 permit 192.168.1.0 0.0.0.255
R2
--
ip dhcp pool R2_DHCP
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
import all
ip dhcp excluded-address 192.168.1.1 192.168.1.100
int fa0/0
desc to Upstream R1
ip address dhcp
ip nat outside
int fa0/1
desc R2 LAN connection
ip address 192.168.1.1 255.255.255.0
ip nat inside
ip nat source list 1 int fa0/0 overload
access-list 1 permit 192.168.1.0 0.0.0.255
Where R1's fe0/1 would connect to R2's fe0/0 interface via a crossover cable and
you'd get a double-NAT situation. Like I said it works, but the rationale of
such a setup is alittle screwy.
Regards |
|
| reply to krock83
Hi all and thanks for the help
HELLFIRE
That wont work because R1's fa0/1 is connected to a switch with 2 pc's on it. I was going to connect R2 via serial to R1 |
|
| reply to krock83
Thinking out loud after a long day at work krock83... adjust it as you need it
Regards |
|
