CONFIGURING REMOTE SITES TO REACH THE CORE SWITCH 4

[drbk563]

Here is the situation. The layout of the network can be found at

http://www.virgoletta.com.

What I am trying to do is connect the four sites connect to the Hub router using EIGRP so that each site can talk to each other. What should happen is that all the users behind each router at each site should be able to reach core switch to reach the internet. I need some help with the configuration to get this working. In addition, the users at each site must get an ip address assigned to them via a DHCP server(143.104.179.1) which is located at the same location as the core switch.

Below is the config so far for the Hub Router and remote site 4. Please advise on what should be added or changed to get this working correctly.

Thank you in advance

Hub Router

interface GigabitEthernet0/0
ip address 143.104.179.239 255.255.255.0
duplex auto
speed auto
media-type rj45
negotiation auto
!
interface GigabitEthernet0/1
no ip address
shutdown
duplex auto
speed auto
media-type rj45
negotiation auto
!
interface Serial0/0/0:0
ip address 2.2.2.1 255.255.255.252
!
interface Serial0/0/1:1
description Circuit 32HCGS342365
ip address 2.2.3.1 255.255.255.252
!
interface Serial0/1/0:1
description Circuit 32HCGS342436
ip address 2.2.4.1 255.255.255.252
!
interface Serial0/1/1:1
description Circuit 32HCGS342273
ip address 2.2.5.1 255.255.255.252
!
router eigrp 101
network 2.2.2.0 0.0.0.3
network 2.2.3.0 0.0.0.3
network 2.2.4.0 0.0.0.3
network 2.2.5.0 0.0.0.3
no auto-summary
!
ip route 0.0.0.0 0.0.0.0 143.104.179.254

*************************************************************

Remote Site 4

interface FastEthernet0/0
ip address 3.3.3.2 255.255.255.192
ip helper-address 143.104.179.1
speed 100
full-duplex

interface Serial0/1
ip address 2.2.2.2 255.255.255.252
service-module t1 timeslots 1-24
!
router eigrp 101
network 2.2.2.0 0.0.0.3
no auto-summary

 

[plshlpme]

the dhcp request is done from a host attached to the lan of one of the spokes...

so the helper-address takes that broadcast and sends it to the destination via unicast whereever that server may be.

so the hub router would receive the request via unicast over one of the serial links and simply forward it to the interface that the dhcp server is connected to.

it is not forwarded from the spoke to the hub as a broadcast and in turn the reply will not be a broadcast so the hub rotuer in fact never sees the dhcp "broadcast".

i hope that is making it clear?

nobody will be making dhcp requests through the hub.. the spoke routers are the only ones that will see it as a broadcast. the rest of the routers will only see it as a unicast which will be aloud to trqaverse normally through the network.

 

[Minue]

Well explained plshlpme!!Keep up the good work!
Regards

 

[burtsbees]

Got it. Thanks. Man---I remember studying it, but never went in depth, like the fact it turns it into a unicast. I always assumed it said "Ok---you are a broadcast...I have the ip helper-address which matches your source ip address in the header---you may pass". I never knew it made it a unicast.

Burt

 

[drbk563]

Thank you everyone for your input. So I am only going to put the the ip-helper address on the LAN interface of the spoke routers.

 

[burtsbees]

No--actually instead of the LAN interfaces, what you want to do is...just kidding.lol

Burt

 

[drbk563]

Thank you all for your help.

 

[Minue]

Hello
Did you get it to work?
Regards