On Saturday 05 September 2009, Dale wrote:
> Mick wrote:

> > Have you tried pointing your browser to: http://192.168.1.254 ?
>
> Yep, did that and bookmarked it.  THAT was mistake #1.  It bookmarked a
> different part of the modem.  Therefore, it didn't give me the other
> pages you are referring too.  Going to he link you gave worked better,
> MUCH better!!  I see some stuff I can mess up now.

Careful what settings you de/select because you can lock yourself out.  Make 
sure that you disable remote admin access, unless you intend to access it 
locally and set a passwd anyway.  Also disable upnp.

> >>> Your netstat results show that you are running mdnsd and mDNSResponder.
> >>> Is this necessary?
> >>
> >> I vaguely remember something pulling that in a LONG time ago.  I have no
> >> clue what the heck that thing is, none whatsoever.  I remember checking
> >> the forums when it was installed and it being needed by something.  I
> >> don't think I have it set to start, I think it starts because something
> >> else needs it.  Should I kill that thing or what?
> >
> > I believe it is running because of zeroconf.  Unless you have use for
> > zeroconf on your LAN network I would remove them from rc-update.
>
> I don't have zeroconf in a runlevel.  Something is starting it but I
> don't know what it is.  This is a list of what I have set up to start.
>
> r...@smoker / # rc-update show
>             bootmisc | boot
>              checkfs | boot
>            checkroot | boot
>                clock | boot
>          consolefont | boot
>                cupsd |      default
>                 hald |      default
>             hostname | boot
>                ivman |      default
>              keymaps | boot
>                local |      default nonetwork
>           localmount | boot
>              modules | boot
>             net.eth0 |      default
>               net.lo | boot
>             netmount |      default
>                 ntpd |      default
>              numlock |      default
>            rmnologin | boot
>               smartd |      default
>            syslog-ng |      default
>                 upsd |      default
>               upsdrv |      default
>               upsmon |      default
>              urandom | boot
>           vixie-cron |      default
>                  xdm |      default
> r...@smoker / #

No I meant disable mDNSResponder and mdnsd, but you don't seem to have them 
there ... 

> I'd be glad to get rid of it but I don't know which one to stop and
> remove from the services to start.  Ideas?

Well, on my system it is kdelibs that pull it in:

# emerge --depclean -pv net-misc/mDNSResponder

Calculating dependencies... done!
  net-misc/mDNSResponder-107.6-r5 pulled in by:
    kde-base/kdelibs-3.5.10-r6

despite the fact that I do not have avahi and zeroconf USE flags enabled 
either in kdelibs or cups:
=======================================
# emerge -pDv kde-base/kdelibs

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] kde-base/kdelibs-3.5.10-r6  USE="acl alsa branding cups fam 
spell 
tiff -arts -avahi -bindist -debug -doc -jpeg2k -kdehiddenvisibility -kerberos 
-legacyssl -lua -openexr -utempter" 
0 kB

# emerge -pDv net-print/cups  

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] net-print/cups-1.3.10-r2  USE="X acl dbus jpeg ldap pam perl 
png ppds python ssl 
tiff -avahi -gnutls -java -kerberos -php -samba -slp -static -xinetd -zeroconf" 
LINGUAS="en -de -es -et -fr -he -id -it -ja -pl -sv -zh_TW" 0 kB
=======================================

> Well, if they can't find me, how do they break in?  LOL  Just kidding
> but you know.  It's a start.

They can find you.  The probes show 'filtered' ports instead of 'closed'.
-- 
Regards,
Mick

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to