Mailinglist Archive: opensuse (2702 mails)

[mmips@xxxxxxxxxx (Michael Demeter)]

TCPDump did not show the device that was handling the packets...Just try
it...It showed that the eth0 device was handling all of the packets...Maybe
this is due to the dummy device capturing after the eth0 driver had handled
it...and why Samba doesn't complain it thinks it is being handled
correctly..

Mike Demeter
Senior Design Engineer
Oresis Communications, Inc.
14670 NW Greenbrier Pkwy
Beaverton, OR 97006

email1: mdemeter@xxxxxxxxxx
email2: mmips@xxxxxxxxxx

> -----Original Message-----
> From: owner-suse-linux-e@xxxxxxxx [<A HREF="mailto:owner-suse-linux-e@xxxxxxxx]On";>mailto:owner-suse-linux-e@xxxxxxxx]On</A>
> Behalf Of JHammer609@xxxxxxx
> Sent: Sunday, June 27, 1999 5:04 AM
> To: suse-linux-e@xxxxxxxx
> Subject: Re: [SuSE Linux] Samba Solutions...maybe
>
>
>
> In a message dated 6/26/1999 6:27:22 PM Eastern Daylight Time,
> mmips@xxxxxxxxxx writes:
>
> <<
>  To all who have recently had Samba problems since 6.1
> installs...After much
>  investigation I believe I have found the problem with the
> disappearing act
>  of SuSE samba boxes from NT network neighborhood...
>
>  First and formost After debugging for a week between 2 identical
> machines I
>  found that the SuSe machine was never sending broadcast packets...Setting
>  the log level to 5 allowed me to see that the SuSE server was sending
>  broadcast packets to itself...what you say???
>
>  It seems that the standard rc.config has the dummy device configured to
>  yes...Well the ifconfig (netmask=255.255.255.255)for dummy captures all
>  broadcast packets...so...Samba only sent broadcast packets to itself and
>  they never made it to the network...This also includes responses to
>  broadcast packets from other machines on the same subnet.
>
>  To see if this may be your problem type lsmod -a...if dummyX is
> listed then
>  reconfigure rc.config to dummy=no and either reboot or go to
> /etc/rc.d/rcX.d
>  directory and type the command ./S04dummy stop...
>
>  If you have dummy built in to the kernel just check the rc.config dummy
>  parameter and set it to no and stop the dummy service as above.
>
>  This completely fixed all Samba problems on my machines and I was able to
>  drop all but the plainest of configuration parameters for Samba...And the
>  world has returned to normal(I think)...
>
>   >>
> Good going. I don't use the dummy device so I didn't have this problem.
> Another solution might be to ifconfig down the dummy device. Also,
> tcpdump device will show you what messages are being sent and
> received by any
> particular interface device. That might be easier than the log
> file route for
> debugging this problem.
> Joel
> --
> To get out of this list, please send email to majordomo@xxxxxxxx with
> this text in its body: unsubscribe suse-linux-e
> Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/";><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the
> archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html";><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
>


--
To get out of this list, please send email to majordomo@xxxxxxxx with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/";><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the
archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html";><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>