On Thursday 31 March 2005 13:59, Michael Nottebrock wrote:
> On Wednesday, 30. March 2005 18:22, Andy Fawcett wrote:
> > On Wednesday 30 March 2005 16:49, Raphael Langerhorst wrote:
> > > On Friday 25 March 2005 20:21, Michael Nottebrock wrote:
> > > > On Friday, 25. March 2005 19:52, Will Wainwright wrote:
> > > > > Am I crazy, or is kdm not listening on IPv4? If so, any
> > > > > idea how to fix this?
> > > >
> > > > Looks like it, indeed. I don't use remote logins with kdm,
> > > > can anybody on this list confirm? Either way, you probably
> > > > should file a bug at http://bugs.kde.org about it.
> > >
> > > I can confirm that it doesn't work. My sockstat looks like
> > > this:
> > >
> > > eagle# sockstat | grep kdm
> > > root     kdm        571   3  stream -> /tmp/.X11-unix/X0
> > > root     kdm        568   7  stream
> > > /var/run/xdmctl/dmctl-:0/socket root     kdm        568   8 
> > > udp6   *:177                 *:* root     kdm        568   10
> > > stream /var/run/xdmctl/dmctl/socket eagle#
> > >
> > >
> > > would be nice if this will be fixed. I have no idea if it's a
> > > pure KDE bug or if it's related to FreeBSD...
> >
> > net.inet6.ip6.v6only=0 fixes this for 5.x/6.x, and shouldn't be
> > needed for 4.x.
>
> There is also a defaults/rc.conf switch, ipv6_ipv4mapping="NO",
> which ISTR sets this sysctl. Can you try putting
> ipv6_ipv4mapping="YES" into /etc/rc.conf and see if it works as
> well?

This does NOT work, I was not able to connect, net.inet6.ip6.v6only 
was set to 1 and after I manually set it to 0 it worked. I don't know 
what ipv6_ipv4mapping="YES" is supposed to do, but it does not set 
the v6only value to 0 and thus KDM does not listen on IPv4.

Regards,
Raphael

>
> > Suggestion for now is to FAQ this, on our website, and maybe also
> > in UPDATING?
>
> I'd rather like to patch kdm along the lines of the code-snippet
> Thiago posted in a comment of Bug 102497. There are sound reasons
> for disabling ipv4-mapped ipv6 adresses (also see my comment on Bug
> 102497), it wouldn't be good if we required kdm users to accept
> additional security risks.
>
> I probably won't be able to look into it today however, it would be
> nice if somebody could try and come up with a working, tested patch
> for kdm which I could then commit.
_______________________________________________
kde-freebsd mailing list
[email protected]
http://freebsd.kde.org/mailman/listinfo/kde-freebsd

Reply via email to