Samba Blocked? (repost)

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

 



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
>
>
>
>




[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux