All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nandan Bhat <nlbhat@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Help with Samba using iptables
Date: Thu, 01 Mar 2007 18:19:03 +0530	[thread overview]
Message-ID: <45E6CBBF.3040406@gmail.com> (raw)

Hi,

I am hoping to get some help with some iptables. I am a newbie to all 
this; please bear with my language and detail.

I have two networks 192.168.1.0 and 192.168.0.0

192.168.1.0 is my LAN. It has a Fedora Core 5 machine with 192.168.1.6 
on eth0, running  samba and iptables among other services. 192.168.1.6 
is the WINS server on the network. I don't know if it is right but I 
have made it the local master and domain master. There is no domain in 
use on the network. I have seen an improvement in the LAN browsing after 
using this setup.

I have one CAT-5 cable coming from 192.168.0.0 network and my Fedora 
machine is connected to it on eth1. It has the fixed IP 192.168.0.176. 
In my iptables setup, I have allowed TCP ports 139, 445 and UDP ports 
137, 138 (regardless of source/destination/interface/IP) to be accepted 
in INPUT chain.

The status is that I am able to see my workgroup in 192.168.1.0 from 
within 192.168.0.0 network with all machines listed, but I can access 
only my Fedora server that is part of both networks. In my network, I 
can see all workgroups in 192.168.0.0 network but not see any host on 
it. On the Fedora machine, I am able to use smbclient to browse hosts on 
192.168.0.0 network. My conclusion: nothing is routing smb packets from 
hosts (other than my server) in 192.168.0.0 to 192.168.1.0 and vice versa.


My question: Is there a way I can get hosts on 192.168.0.0 and 
192.168.1.0 by using iptables alone?

Regards,

Nandan Bhat


                 reply	other threads:[~2007-03-01 12:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45E6CBBF.3040406@gmail.com \
    --to=nlbhat@gmail.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.