Re: Just an interesting note.
- From: Jeff Liebermann <jeffl@xxxxxxxxxx>
- Date: Wed, 22 Oct 2008 17:46:14 -0700
On Wed, 22 Oct 2008 22:35:12 +0000 (UTC), DanS
<t.h.i.s.n.t.h.a.t@xxxxxxxxxxxxxxxxxxxxx> wrote:
A *long* while back I asked a question here that was never answered.
Impossible. Someone always answers questions. Sometimes, the answers
are even correct.
Connected to the ISP's modem is a home rtr. In this case, a wired-only Linksys of which the m/n
escapes me now. The Linksys box is NAT'g for the internal network of 192.168.1.0/24.
Ok, you're off the hook for forgetting to supply the muddle number.
Just don't make a habit of it.
Also attached to the network is a 'real' rtr, with 2 eth interfaces.
You mean there are unreal routers out there? Try tapping the router
with a magic wand. If it disappears in a puff of smog, it's not a
real router but an illusion. Incidentally, I think your "real" router
is going to require 3 ethernet interfaces.
One of the NIC's is on the
192.168.1.0/24 subnet, the other NIC is on the 192.168.2.0/24 subnet connected to a different switch
with a couple PC's attached as well. The 'real' rtr is is configured to a bare minimum, only the IP info
of each interface set and G/W & DNS are pointing to the ISP rtr, 192.168.1.1.
Ummm.... is this in addition to the unspecified model Linksys real
router, or is this a replacement for the unspecified model Linksys
real route?
The question was........will the inexpensive consumer rtr properly NAT and pass the 'off-subnet' routed
packets ?
Sure. No problem at all. However, it won't work with your creative
IP address layout. You cannot have the ISP's router at 192.168.1.1
and also NAT one of the output ports in the same subnet. Also, if
it's coming from the ISP's modem, the common input port will probably
have a routable IP address delivered by the ISP's DHCP server.
The answer is yes, it will. (This one anyway.) But, one of the requirements is that a route needs to be
placed in the ISP rtr for the 192.168.2.0/24 gateway, being the 192.168.1.x address of the 'real' rtr.
Huh? Perhaps it would be helpful if you would describe this mythical
real router of yours. From your muddled description, my guess is that
it has 3 ports. One for the WAN going to the modem. Two other going
to two separate subnets. Unless I'm reading this wrong, the Linksys
just magically became the "real" router in your last statement.
My theory is that if the home rtr that is being used has a section in the setup for entering static routes,
the above scenario will most likely work. To be clear, these entries are not for port mapping in the ISP
rtr, and are usually entitled 'Routes' or 'Routing' in (one of) the 'Advanced' sections.
Static routes are where you want to route an entire subnet *THROUGH* a
single IP address, usually over the internet. Something like a branch
office. That will only work if the branch office has yet another
router.
Just a worthless tidbit, ignore it if you like.
Right. I should have ignored it. Too late.
(The history behind the question was that I was thinking about sharing my internet connection with a
relative, but wasn't real keen on the Layer2 bridging way of doing it and having all my LAN traffic up in
the air. Plus, I already have several complete PtP pairs of some (of The Old)Cleawire proprietary
system that operates on Layer3, which would have put the other end on a different subnet.)
Huh 2.0? *ALL* wireless is Layer 2 (MAC layer) bridging. However,
this isn't really a wireless question so you have some room to screw
things up.
You can split the network using two different class C networks, but
methinks that's too much work. It's easier with a subnet and this is
a job for routing. Split the subnet in half with two /25 networks.
Alias your default gateway (IP address of the "real" router) to two
different IP addresses, one each inside each subnet. Setup netmask
and routing so that each subnet doesn't see the other. You might be
able to avoid the aliasing trick if your PC's support a default
gateway that's not inside their netmask.
--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831-336-2558 jeffl@xxxxxxxxxxxxxxxxxxxxxx
# http://802.11junk.com jeffl@xxxxxxxxxx
# http://www.LearnByDestroying.com AE6KS
.
- Follow-Ups:
- Re: Just an interesting note.
- From: DanS
- Re: Just an interesting note.
- References:
- Just an interesting note.
- From: DanS
- Just an interesting note.
- Prev by Date: Just an interesting note.
- Next by Date: Re: LAN but no Internet
- Previous by thread: Just an interesting note.
- Next by thread: Re: Just an interesting note.
- Index(es):
Relevant Pages
|
