From: "Dan Egli" <dan@shortcircuit.dyndns.org>
To: Michael <mutk@iprimus.com.au>, netfilter@lists.netfilter.org
Subject: Re: Samba Blocked? (repost)
Date: Wed, 27 Nov 2002 11:17:43 -0700 [thread overview]
Message-ID: <003f01c29642$22a08bb0$1e00a8c0@yamatto> (raw)
In-Reply-To: 3DE47D0D.9060702@iprimus.com.au
I will try this one then. Thanks!
----- Original Message -----
From: "Michael" <mutk@iprimus.com.au>
To: <netfilter@lists.netfilter.org>
Sent: Wednesday, November 27, 2002 1:06 AM
Subject: Re: Samba Blocked? (repost)
> Joel Newkirk wrote:
>
> >On Tuesday 26 November 2002 09:30 pm, Dan Egli wrote:
> >
> >
> >>that is correct. And I know for a fact that NetBIOS-ns is in the
services
> >>file because I've seen it, and I did try it both ways. Every time I try
to
> >>connect using //myserver/shared1 I get the following log lines:
> >>
> >>
> >
> >Very strange. the only packets caught here with --dport 137 are on lo
with lo IP, then
> >--sport 137 with 64.x.x.x on lo, and --sport 137 with local 192.x x.x on
lo. It looks like the
> >'real' --dport 137 packets get through (they're not listed here) but the
machine tries to
> >query itself on lo to resolve the names. shot in the dark, try:
> >
> >/sbin/iptables -A INPUT -i lo -j ACCEPT
> >/sbin/iptables -A OUTPUT -o lo -j ACCEPT
> >
> >to let these through. I've only done minimal work with samba, so I don't
know if this self-request
> >is normal or not...
> >
> >
>
> I think it's due to smbd talking to nmbd via lo when it receives a bcast
> ?? Something like that.
> Something like this is generally needed anyway:
>
> iptables -A INPUT -i lo -j ACCEPT
> iptables -A OUTPUT -o lo -j ACCEPT
>
>
> Cheers,
> Michael
>
>
>
>
prev parent reply other threads:[~2002-11-27 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 22:10 Samba Blocked? (repost) Dan Egli
2002-11-27 0:24 ` Joel Newkirk
2002-11-27 2:30 ` Dan Egli
2002-11-27 5:00 ` Joel Newkirk
2002-11-27 8:06 ` Michael
2002-11-27 18:17 ` Dan Egli [this message]
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='003f01c29642$22a08bb0$1e00a8c0@yamatto' \
--to=dan@shortcircuit.dyndns.org \
--cc=mutk@iprimus.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox