Philippe Moutarlier wrote:
> Now the question : can I (and if yes, how) setup the thing so a machine M2 on
>network A can access files on machine M3 on network B and vice-versa ??
First, I believe it was covered that you should probably run WINS
service on your samba server. I recommend turning on SWAT temporarily,
to configure samba. It's run from inetd, and probably has an entry at
the bottom. SWAT rocks!
Second, before your ipchains rule (that probably looks like):
ipchains -A forward -s NETB/24 -j MASQ
you will need one like:
ipchains -A forward -s NETB/24 -d NETA/24 -j ACCEPT
This will tell your masq firewall to allow NETB to speak directly to
NETA without masquerading. Now, if the policy for the forward chain is
set to DENY (as described in the masq-howto, this means that routing
isn't the default behavior), then you will also need a rule like:
ipchains -A forward -s NETA/24 -d NETB/24 -j ACCEPT
so that NETA can speak to NETB directly.
Now, if M1 isn't the default router for NETA (public network), then all
of the machines on NETA will have to be told that NETB is behind M1. Or
you can do arp proxying... Of course, if it is the default router, ignor
the last two statements.
With those ipchains rules, NETA and NETB should be able to converse, and
while they may not see each other in network neighborhood (I think this
depends on the samba server being a master browser, but I don't know for
certain) they _will_ be able to speak to each other if you know their
IP's.
MSG
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.