smbclient using all interfaces
Tim Winders
twinders at SPC.cc.tx.us
Tue Feb 16 20:46:05 GMT 1999
Well. I finally took the plunge and added a few static routes to my
system so that traffic to that particular network was going out the
"correct" interface. When I did that and applied the filter on the router
again, I was able to use smbclient without having any problems.
It would seem I have a network "issue" to iron out. I am going to work on
that. But, I still have the burning question... what programs are
affected by the interfaces line in the smb.conf file? I think it is just
smbd as nmbd seems to answer calls on any network interface reguardless of
the interfaces line...
hmmm....
On Wed, 17 Feb 1999, Richard Sharpe wrote:
> Hi Tim,
>
> I have started to delete context now:-)
>
> At 12:59 AM 2/16/99 -0600, you wrote:
> [Deletia]
> >Here's the poop... The relavant portion of ifconfig -a
> >
> >tu0:
> >flags=2c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX,PFCOPYALL>
> > inet 206.76.16.68 netmask fffffff0 broadcast 206.76.16.79 ipmtu 1500
> >
> >elan0:
> >flags=2c63<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,SIMPLEX,PFCOPYALL>
> > inet 206.76.17.2 netmask ffffff00 broadcast 206.76.17.255 ipmtu 1500
> > trustgrp unknown
>
> OK, these look fine.
>
> >I left off lo0, sl0 and elan1 - 3. sl0 is not configured lo0 is just
> >loopback and elan1 - 3 are the same as elan0, just with different ip
> >addresses. None of which are involved here...
> >
> >netstat -rn is much more interesting...
> >
> >Destination Gateway Flags Refs Use Interface
> >Netmasks:
> >Inet 255.255.255.0
> >Inet 255.255.255.240
> >
> >Route Tree for Protocol Family 2:
> >default 206.76.16.65 UGS 5 7361098 tu0
> >127.0.0.1 127.0.0.1 UH 1 7182479 lo0
> >204.158.18/24 206.76.16.66 UGD 1 35782 tu0
> >204.158.19/24 206.76.16.66 UGD 0 20332 tu0
> >206.76.16.64/28 206.76.16.67 U 1 588296965 tu0
> >206.76.17/24 206.76.17.2 U 31 20694064 elan0
> >
> >Again, I left off MANY other routes which just seem to confuse the issue.
> >Obviously, the default route is out tu0, but I don't know *HOW* to
> >set/change that.
>
> Well there will be a default route somewhere in one of the config files,
> but this all looks kosher actually. The default is only used if the
> destination address does not match an interface of the routing tables.
>
> So, if you send to something on 206.76.17.x, you should see it go out elan0.
>
> What you might try is running tcpdump, eg:
>
> tcpdump -i elan0 -n # or which ever interface the one you want is on
>
> and then ping the address you want to contact, and see which interface the
> packets are actually going out of.
>
> >I guess where I am confused is the interfaces and bind only directives in
> >smb.conf. Are those just for smbd and ignored otherwise?
> >
> >I will play some more in the morning. I suspect, if I add the filter back
> >into the router, everything will continue to work, but smbclient will not.
> >That is a minor annoyance as I only use it for testing...
> >
> >=== Tim
>
>
> Regards
> -------
> Richard Sharpe, sharpe at ns.aus.com, NIC-Handle:RJS96
> NS Computer Software and Services P/L,
> Ph: +61-8-8281-0063, FAX: +61-8-8250-2080,
> Samba (Team member), Linux, Apache, Digital UNIX, AIX, C, ...
>
=== 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 | |
---------------------------------------------------------------------
More information about the samba-technical
mailing list