[mythtv-users] Multiple boxes on different networks

[Lucas James]

On Wednesday 08 November 2006 12:27, Jawaad Ahmad wrote:
> Lucas,
> I'm not familiar with routed. I'll research it before I do anything else in
> order to digest your post. I know it's not running; I just did a ps on both
> hosts and got nothing (...well, except of course the grep).

It is a simple RIPv2 daemon.  any routing daemon would do.  I just looked on 
my linux box, and it didn't appear there. I usually use FreeBSD, and it comes 
with the base system.

> > sysctl net.ipv4.ip_forward=1
>
> I'm guessing this would stay in-effect until the next reboot. I'll have to
> figure out how to make it persist, if necessary.

this is only necessary if the gateway is just a normal host, and seeing as 
your gateway is a proper router, you don't need this sysctl.

> > if you post the copy of the netstat -r for the following hosts, we can
> > get
>
> a > > good look at what is actually happening:
> > 192.168.1.3
> > 192.168.1.2
> > 192.168.0.2
> >
> > and the output of
> >
> > sysctl net.ipv4.ip_forward
> >
> > on the internal gateway.
>
> Alright! I confess!! There is no host with IP address 192.168.0.2; I lied
> to try to keep things simple. The true IP address is 192.168.0.76, subnet
> mask 255.255.255.192, with gateway 192.168.0.65. I had this set up from a
> prior exercise and have left it alone, but the rest of it is as I stated.

Aha! the truth :-)  always better to start with (assuming it doesn't reveal 
any security sensitive info)

> Here is the real conceptual diagram:
>
>             [ ] 192.168.1.1/24
>
>     +--------+---------+
>
>     |                  |  192.168.1.3/24
>
>    [ ] 192.168.1.2/24 [ ] 192.168.0.65/26
>
>               +--------+---------+
>
>              [ ]                [ ] 192.168.0.76/26
>
> So take your pick - the simple setup with the 24 netmask, or the complex
> setup with the 26 netmask. I apologize for any confusion.

no worries. some level of confusion is a natural state for me ;-)

> The tables I provided below have been copied unaltered.
>
> [user at 192.168.1.2]$ netstat -r
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt
> Iface
> 192.168.1.0     *               255.255.255.0   U         0 0          0
> eth0
> default         192.168.1.1     0.0.0.0         UG        0 0          0
> eth0

Ok, 192.168.1.2 can't "see" the 192.168.0.64/26 network. Try and add:

route add 192.168.0.64 netmask 255.255.255.192 gw 192.168.1.3

This will probably "fix" most of the problems

> [user at 192.168.0.76]$ netstat -r
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt
> Iface
> 192.168.0.64    *               255.255.255.192 U         0 0          0
> eth0
> default         192.168.0.1     0.0.0.0         UG        0 0          0
> eth0

this is good.


> [user at 192.168.1.3]$ netstat -r
> (From the router's Web interface...)
>
> Routing Table Entry List
>
> Destination LAN IP  Default Gateway  Subnet Mask      Interface
> 192.168.0.64        0.0.0.0          255.255.255.192  LAN
> 192.168.1.0         0.0.0.0          255.255.255.0    WAN(Internet)
> 239.0.0.0           0.0.0.0          255.0.0.0        LAN
> 0.0.0.0             192.168.1.1      0.0.0.0          WAN(Internet)

this is correct


> [user at internal_gateway]$ sysctl net.ipv4.ip_forward
>
> If this is my poor li'l Linksys WRTP54G, I have no idea how to get/set this
> information...unless someone's figured out how to ssh into it by now. ;)
>

if it is a proper router (as opposed to a host with two network interfaces), 
it would have already been set (or not requried)

> Sorry I can't provide more info!
>
> > if the internal gateway is not a computer, you could just set it up in
>
> bridged
>
> > mode, and have everything on the same subnet (much easier)
>
> I'll research this and see if I can set it to bridged mode. If I remember
> correctly, this goes by another name, correct?
>
> Thanks for the help!

No worries,

Lucas


-- 
Reactor error - core dumped!