networking on the mac side

[Samuel Rydh]

On Tue, Oct 29, 2002 at 01:27:48AM -0500, marco wrote:
> Hi,
> MOL is installed and working nice on my g3 beige 233.
> My box is a gateway on my LAN.
> Configured with two eth devices
> eth1 --- net DHCP cable
> eth0 --- internal on 192.168.2.1
> 
> here is my molrc.net 
>                netdev:         eth0 -sheep
>                netdev:         tun1 -tun
> 
> On the mac side there are 3 interfaces in tcp/ip (1,2,3)
> 
> Here is the network part of MOL log
> 
> Ethernet Interface (port 1) 'sheep-<eth0>' @ FE:FD:DE:AD:BE:EF
> Ethernet Interface (port 2) 'tun-<tun1>' @ 00:00:0D:EA:DB:EE
> Ethernet Interface (port 3) 'sheep-<eth0>' @ FE:FD:DE:AD:BE:EF
> 
Hmm... it appears you have 'netdev: eth0 -sheep' twice in
your molrc.net file. You don't want that (sheep_net might
malfunction, although this is apparantly not your problem).

> And when I try the second interface ("2" on mac side)
> with dhcp --- my dhcp server serve me an IP address only if MOL is
> running. He says to put a subnet declaration for tun1.
> 
> tun1 provide a 192.168.2.*  address 
> tun2 provide a 192.168.3.*  address

This is the cause of the error. You DON'T want the tun
network and your local (eth0) network to be on the same
subnet. The default /etc/mol/tunconfig script uses the algorithm
tunN -> 192.168.<N>+1.*. Thus if you use tun0 instead of tun1,
then there won't be a conflict.

> ...
> the doc says :
> 
> #    - Linux and MOL must use different TCP/IP addresses (residing on
> #    the same subnet). This is a problem if you use DHCP...
> 
> and when I set tun to 1 (192.168.2.*  address) syslog says :

Yes... this is exactly what you should _not_ do. Set it to 192.168.1.* 
instead (the tunconfig script should do this for you automatically).

Cheers,

/Samuel