Routing Question Rip/NAT

crazyben21

New Member
Reaction score
0
Hello Guys, I have a small home wireless and wired networking. I have a Router A and a Router B.

Router A is the one connected directly to the modem and sharing the internet to Router B and other computers on its network. Router B has his own separate network.

Router A is on the 192.168.0.x network (Cisco Valet N)
Router B is on the 192.168.1.x network (D-Link N)

The question is, should Router A be a NAT Router and Router B be a RIP(Dynamic Routing) router?

I having a hard time understanding both. I'm guessing I want Router B to be rip so it should share it's routing table with Router A. I'm confused on this part. Any help will be greatly appreciated.
 
Hello Guys, I have a small home wireless and wired networking. I have a Router A and a Router B.

Router A is the one connected directly to the modem and sharing the internet to Router B and other computers on its network. Router B has his own separate network.

Router A is on the 192.168.0.x network (Cisco Valet N)
Router B is on the 192.168.1.x network (D-Link N)

The question is, should Router A be a NAT Router and Router B be a RIP(Dynamic Routing) router?

I having a hard time understanding both. I'm guessing I want Router B to be rip so it should share it's routing table with Router A. I'm confused on this part. Any help will be greatly appreciated.

You want the traffic between networks to communicate? What was the purpose of subnetting them separately?
 
Well I was sub netting them separately because I want to keep the privacy between them. I don't want them both to communicate. It was just a question of NAT or RIP. Would Router A see the routing table from Router B if I enable RIP on Router B. I need help understanding NAT and RIP.
 
Last edited:
Don't know these routers but if one was a server you would just bind 2 ip addresses to the one card and make each one a default gateway to their corresponding networks. i.e. 192.168.0.1 & 192.168.1.1 with a subnet mask of 255.255.255.0. Do these routers have advanced configuration that will do that?
 
RIP and NAT really don't matter for what you're asking. If you don't want router B to communicate with anything on Router A, you need to set up a VLAN on router A, and put router B on it.
If you want a super easy way to divide the network traffic, just buy another router and use "A" to branch off to the other two. "B" would be its own network and the new "C" would be its own network. "B" and "C" would not communicate at all.
 
Sorry guys I don't really want them both to communicate. I just want know the technology between NAT and RIP. The questions were brainstorming questions. Sorry to confuse you guys. My grammar sucks so that makes even worse for you guys to understand me. I google or wikipedia NAT and RIP.

Thanks You
Sorry for the confusions.
 
Sorry guys I don't really want them both to communicate. I just want know the technology between NAT and RIP. The questions were brainstorming questions. Sorry to confuse you guys. My grammar sucks so that makes even worse for you guys to understand me. I google or wikipedia NAT and RIP.

Thanks You
Sorry for the confusions.


Hmmm..so...you're trying to learn about two things that you don't know much about....by using a specific example about how to use those two things, in a way that wouldn't apply to the question you asked....in an attempt to learn.

Makes sense.

If you only want to learn about NAT and RIP, just read all about them. You're probably going to need to read a lot more, though, because you need to have a base understanding to build upon. Try reading up on some Network+ studies guides or something.
 
Okay, time for my newbie question. (I think I'm allowed one). I am not familiar at all with more advanced networking other than basic home networking (ie. router, file sharing, switches, ICS, printer sharing, range extenders, etc.). I also have set up LANs that have client at more than one location via the internet, along with remote desktop back in the XP glory days. I replaced a dll file that allowed multiple concurrent remote sessions on a single XP machine. So, I've done some of the more basic stuff, just nothing like what a larger business would have. I've tried reading up on some things but I'm having trouble finding specific information because it seems that some of the terms and acronyms have more than one meaning (I could be wrong here). So, I have a question that will help guide me on what to read up on.

Acronyms are what gets me, because when I search for them, I don't always get the results I'm looking for. So,

What does NAS stand for? I know 'Network Attached Storage', simple enough. But I thought I've seen it refer to something else before.

What does RIP and NAT stand for?

There's a couple more, but I can't think of them right now. Thanks.
 
RIP is routing information protocol. It is a basic distance vector routing protocol used a lot on home networks and very small business networks.
The many purpose of a routing protocol is to broadcast routes between routers and other networking equipment. The more advanced routing protocols also can assist with load balancing and automatic failover. You don't see much RIP on larger networks. Mostly OSPF and EIGRP for Cisco shops.

NAT is network address translation. The primary application of NAT is to map a private network space like 192.168.1.0 to a routable public Internet IP address. Using NAT you can have many devices on a network "sharing" one or more public IP addresses. Almost every home class Internet router uses NAT but you usually don't realize it because it is already configured.
 
What does RIP and NAT stand for?

NAT is network address translation. It basically means that the router is sending traffic, then determining where it goes to and from, based on information from the packet. So, computer "A" sends a ping request to www.google.com, the router knows to send the result back to "A" instead of computer "B".

RIP is routing information protocol. It's basically just a method of routing traffic through a network. The idea is that it's dynamic, so if one node goes down, it can figure out another route to send the data.
 
Back
Top