smbclient using all interfaces

[Tim Winders]

On Tue, 16 Feb 1999, Christopher R. Hertel wrote:

> Try dropping only 139.  The -L option (if I remember correctly) connects 
> to port 139 on the remote end.  If it *does* work, then the problem was 
> name resolution packets not getting through.

OK, Chris.  I have re-applied the filter with only port 139 being blocked
and I see this:

twinders> smbclient -L atc-srv
Added interface ip=206.76.17.2 bcast=206.76.17.255 nmask=255.255.255.0
Added interface ip=206.76.20.2 bcast=206.76.20.255 nmask=255.255.255.0
Added interface ip=206.76.21.2 bcast=206.76.21.255 nmask=255.255.255.0
Added interface ip=206.76.22.2 bcast=206.76.22.255 nmask=255.255.255.0
Got a positive name query response from 127.0.0.1 ( 204.158.18.5 204.158.19.5 )

and it just hangs.  You can see that it is using the loopback address for
WINS resolution, so the filter doesn't matter.

I can only deduce that there is a kernel/routing something problem.  Using
TCPdump looking at the first interface above.  When I try to ping the
remote station indicated above, I see nothing.  If I look at the ethernet
interface (206.76.16.67, which is not listed in the interfaces option in
smb.conf) and I ping the station above, I see the pings across that
interface.

When I remove the filter from the router, the above command works and I
see the packets (with tcpdump) going over the ethernet interface, not over
one of the interfaces above...

=== Tim

---------------------------------------------------------------------
|  Tim Winders, CNE, MCSE     |  Email:  Tim.Winders at SPC.cc.tx.us   |
|  Network Administrator      |  Phone:  806-894-9611 x 2369        |
|  South Plains College       |  Fax:    806-897-4711               |
|  Levelland, TX  79336       |                                     |
---------------------------------------------------------------------