• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Need some help

B

batgat

Junior Member
Hello,thank you for allowing me to post here
... since i am a rookie in the field would you please help me out on this:
i need to connect the three routers as described on the picture bellow (the ports with the question marks on them)

http://img390.imageshack.us/img390/9234/nethr9.jpg

What IP's they should get so that they connect each other and be able to send and receive packets to / from others networks
Thanks!
 
Just pick a small unused subnet of RFC1918 addresses and assign an address to each router from those.. Then you're good to go.. With 3 addresses a /29 subnet is advisable..
 
rathsach, thanks for your reply
I was thinking to assign 172.16.0.0 - 172.31.255.255 (172.16/12 prefix) (RFC1918) which gives me 16 supernets 1048574 addresses each with but would this causes me any trobles in the future?
for example:
R1-172.16.4.1
R2-172.16.8.1
R2-172.16.12.1
so that I can add hosts to each of those three new nets
And if I add the default route 172.16.0.0 in the route table would this work in this way?
I haven't tried to implement supernets so far

or it would be more beneficial if I go with /29 bits mask?

Thanks again
 
Why on earth would you want to use so many addresses for that?

I just checked out your drawing again and saw that the bottom router was connected to another side of the top-right one.. Yesterday I saw it as a 3 way cross..

You'll have to tell me exactly what you need this to do? If it's simple connectivity you should always aim to use as few addresses as possible.. /29 og even /30 if you only need 2 usable addresses..

I don't know how strong you are subnetting wise, but remember that just because 172.16.0.0/12 is an RFC1918 scope, you don't have to use it with a /12 mask..

Tighten up your subnet masks, and from experience try to keep away from the top and bottom of the rfc1918 scopes.. People tend to use those the most..
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top