Help me build network simulation (ISP + Home)

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

I am trying to build a network including the ISP side(DHCP, DNS and File servers) and a home LAN with 2 PCs on it and obviously the internet inbetween. In packet tracer DHCP doesn't work until you have set up a DHCP server, obvioulsy, now in my simulation i want the PCs to get assigned an IP from the ISPs DHCP server etc.... as it would happen in real life. So far i have the home LAN PCs both manually assigned IPs at the moment though that would change to being assigned IP from the ISP DHCPs server once i have the whole thing set up. So,

a) Does what i have done look anything like a real life situation can you improve on my harware setup i have it pretty basic
b) If so can you help me fill in the missing IPs (ISP side and home FE 0/0 IP etc..)





thanks

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

I doubt if it is wise to assign an IP address from a DHCP server over a WAN link.
If the WAN link goes down you will have a serious problem.

Why not set up from your local router or switch?

 

Despite it being often (mistakenly) stated - customers on ADSL don't get their IP address via DHCP.

The immediate mechanism is via PPP.

DHCP *may* be used to prime the PPP, or more usually it is driven from RADIUS via various schemes.

Harry.

 

nobody else?

I want as acurate a WAN/LAN/ISP network diagram as i can make...

 

This is where experience is vital... and why the Cisco exams shouldn't be tackled by people who haven't yet worked with Cisco gear. I know that's not the answer you want to hear... but it's the truth you need to hear.