[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

samba/win95 network over ip-masquerading



I'm running Debian/Linux "potato" kernel 2.2.10 with Samba 2.0.4b and I'm
trying to setup a Linux box to masquerade and allow browsing across the
Linux box.  Currently, IP Masquerading is working and I'm using the default
Debian auto-configuration.  More specifically, I want the machines on the
local network to see and be able to access the machines on the outside
network and vice-versa.  And, if possible I'd like the Linux box to only be
seen/accessible by the local network (not as important).

Here's the situation:  There are 3 win95 machines behind the Linux box and a
WINS server on the outside, which I'm not in control of.  Right now the
local network is 192.168.1.x on eth0 and the outside is 192.168.100.x on
eth1 (which will be changed to a non-private IP in the future).

I've tried setting up the Linux box as a WINS server and having the local
machines point to it, but then there is no link to the outside machines.  If
the local machines point to the outside WINS server, nothing seems to work.
If I telnet into the Linux box, smbclient -L {machine} is able to locate the
clients without any problems or help from DNS, yet the machines don't report
a browse list containing machines from the other network.

---

Just recently I changed the firewall rules so the default policy is ACCEPT
for input, output, and forward and I deleted the DENY rule from the input
and output chains just to make things a little easier.  Now, the local
machines are set to the WINS server on the outside network and are able to
browse and connect to those machines + the inside machines.  So, one
direction is working.  Now, how can I get it to work the other way?

I think it should be possible because I think the WINS server stores the IP
and port of the clients machines, thus is the Linux ip masq box manipulated
the WINS connections from the inside to the outside network so that the
machine was the Linux box outside IP and changed the ports, everything
should work fine.  --- do I need more MASQ/firewall rules?


What can I do?

Thanks,
-Paul


Reply to: