• 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.

use of mulptiple broadband routers?

xyyz

Diamond Member

i'm looking to get the Cisco 806 in a little bit...

is it possible to use this along with my Linksys DSL router? I know that the linksys supports RIP (not that i'll really be using it).

I wanted to set my servers to use a class-b internal addresses and keep the workstations on the linksys which uses the class-c internal addresses.

is it possible... anyone have any problems?
 
the Cisco 8xx series are nice boxers; a SOHO class device with support for ACLs and TunnelX, etc. nifty. What exactly do you want to do with it? Use both routers at the same time? Why do you have need for a /16 and a /24? I'm assuming these are both non routable blocks you'd like to configure behind your routers.. Can you give me some more info? Thanks.
 


<< the Cisco 8xx series are nice boxers; a SOHO class device with support for ACLs and TunnelX, etc. nifty. What exactly do you want to do with it? Use both routers at the same time? Why do you have need for a /16 and a /24? I'm assuming these are both non routable blocks you'd like to configure behind your routers.. Can you give me some more info? Thanks. >>



actually the 806 doesn't use the stripped down version of the IOS that the other 8-series routers use... it uses the full IOS.

I want to keep the servers on a seperate network than the workstations... why? well 'just to see what happens... 🙂

/16 and /24? ummm... why are you asking about subnet masks?

i want to use an internal class-b and class-c network behind my NAT... i'll keep the servers on the internal class-b network and workstations on an internal class-c network.

there will only be a single hop when it comes to the internal class-c network to the gateway.

I don't know if i've helped any by answering your questions... or even if I've answered them... :/

 
classes a, b, c, d, e dont really exist anymore. The /24 etc (CIDR?) are kinda the new standard. Its similar, but easier for assigning ip addresses out. Anyhow, what are the prices of the cisco? That looks interresting (even if I dont plan on using it for what its supposed to be used for), I think it would help me learn some cisco fu.
 
You should be able to do it, but may I ask why would you want to complicate the network....just think of the guy that have to clean up your mess after you leave the company.

If you must have /16 network concurrent with the /24 subnet range. The Gateway of the /16 network have to be in the /24 range, so all puters can see each other in the broadcast.
 
lowtech, I was under the impression this was a home network... If its not you are definitely right that this would be a pain in the tush setup that would cause the next admin in line to go bald. If it is a home network, why not do it? Could be fun 🙂

OT: When did the short hand (ie process name) for a Filesystem Sanity ChecK become a bad word? Hope no one using a UNIX-like OS is using a non-journaling FS...
 
i still don't understand why you need two different address spaces for these machines 🙂 it will make things much easier if you stick to a single network for the whole setup; use 192.168.0.0/16 and use 192.168.1.0/24 for the servers and 192.168.2.0 -> whatever for the workstations. that way it looks much cleaner and you can keep your routing tables a little neater.. btw /16 = class B and /24 = class C - that's called CIDR notation; subnet masks = mask bits 0.0.0.0 -> 255.255.255.255
 


<< i still don't understand why you need two different address spaces for these machines 🙂 it will make things much easier if you stick to a single network for the whole setup; use 192.168.0.0/16 and use 192.168.1.0/24 for the servers and 192.168.2.0 -> whatever for the workstations. that way it looks much cleaner and you can keep your routing tables a little neater.. btw /16 = class B and /24 = class C - that's called CIDR notation; subnet masks = mask bits 0.0.0.0 -> 255.255.255.255 >>



remember... this is a home network... I'll only have two routers...

if I setup different network addresses I'll need more routers. i'm looking to do this with 2 routers...

with your configuration won't I need more than two?

192.168.0.1 - router 1 (exit router?)
192.168.1.1 - router 2
192.168.2.1 - router 3?

i'm looking to do...

172.16.0.1 - router 1 (cisco - exit router)
172.16.0.100 - server 1
172.16.0.101 - server 2
172.16.0.102 - server 3
172.16.0.2 - router 2 (linksys - internal 192.168.1.1)

192.168.1.101 - wkstation 1
192.168.1.102 - wkstation 2
192.168.1.103 - wkstation 3
192.168.1.104 - wkstation 4
 


<< classes a, b, c, d, e dont really exist anymore. The /24 etc (CIDR?) are kinda the new standard. Its similar, but easier for assigning ip addresses out. Anyhow, what are the prices of the cisco? That looks interresting (even if I dont plan on using it for what its supposed to be used for), I think it would help me learn some cisco fu. >>



hmm so either you or sml have some reading material for me... link etc... that covers this CIDR stuff? I always thought that the / addressed your subnet bits... what does it do now... it addresses how many host bits?

the cisco academies have a really great special on the 806 ... $250 which includes the IP PLUS and Cisco IOS Firewall feature sets.

my academy run is about to end so i gotta jump in on this one soon. 🙂
 
xyyz,

you are never going to be satisfied until you read the RFCs. You my friend can start at 1.

Let me know when you have 'em all finished 🙂

<edit> search for the CIDR RFC, should be easy to find and actually is a quick read.
 
xyyz: you won't need more than two routers with a configuration like this:
192.168.0.1 = router #1
192.168.0.2 = server #1
192.168.0.3 = server #2
etc etc...

192.168.1.1 = router #2
192.168.1.2 = workstation #1
192.168.1.3 = workstation #3

make the default route for the workstations 192.168.1.1 and have 192.168.0.1 route out to the internet; if everything is configured properly you will have two physically separated [although you don't really require this for a home network, heh] networks that can talk to each other and are bridged by a few routers.
 


<< make the default route for the workstations 192.168.1.1 and have 192.168.0.1 route out to the internet; if everything is configured properly you will have two physically separated [although you don't really require this for a home network, heh] networks that can talk to each other and are bridged by a few routers. >>



you know... this is really pathetic since i'm about to take my ccna exam in a few weeks... but i'm unclear about something...

explain how this would work.

i thought the workstations wouldn't be able to see outside the network.... unless umm instead of a static route (I didn't know that winme and win2k machines could do this) should I assign the gateway for the systems under the second router be that second router?
 
Actually, what you're proposing to do will work just fine. Just have the Cisco be your outside router, then have the Linksys be on it's internal network. You are, essentially, doing double NAT which is perfectly acceptable.

I'd only have one word of advice.. The 805 is probably way overkill for this. If you're studying for your CCNA, I'd keep the 805 in "reserve" for study use - If it's live on your network, it will be hard to monkey with for study purposes. Grab another $50 broadband router instead of using the 805. It'll do just fine. That will give you a bit more flexibility.

(And, yes, you can use static routes on Win9X and NT - Win9X just has to be re-entered at each reboot whereas NT can be made persistent. Look at the ROUTE command in DOS)

- G
 


<< Actually, what you're proposing to do will work just fine. Just have the Cisco be your outside router, then have the Linksys be on it's internal network. You are, essentially, doing double NAT which is perfectly acceptable.

I'd only have one word of advice.. The 805 is probably way overkill for this. If you're studying for your CCNA, I'd keep the 805 in "reserve" for study use - If it's live on your network, it will be hard to monkey with for study purposes. Grab another $50 broadband router instead of using the 805. It'll do just fine. That will give you a bit more flexibility.

(And, yes, you can use static routes on Win9X and NT - Win9X just has to be re-entered at each reboot whereas NT can be made persistent. Look at the ROUTE command in DOS)

- G
>>



You can do that in ANY windows.

1. Windows 9x - edit c:\windows\hosts (look at c:\windows\hosts.sam )
2. WinNT, 2000 XP edit c:\winnt\system32\drivers\etc\hosts
 
A host file entry is a mapping of IP address to host name and doesn't have anything to do with how traffic is sent across the network. A route specifies the gateway that traffic should pass through to get to a specific network/host - Different thing.

- G
 


<< A host file entry is a mapping of IP address to host name and doesn't have anything to do with how traffic is sent across the network. A route specifies the gateway that traffic should pass through to get to a specific network/host - Different thing.

- G
>>



Sorry - my mistake. But nothing stops him from adding route to autoexec.bat or logon script.
 
Back
Top