On Tue 09 Jul 2002 22:02, Ronan Waide wrote:
> On July 9, johngay at eircom.net said:
> > I'm not aware of having set-up any firewalling on my box, it's just a
> > mixed bag of Debian from Progeny upto unstable. I have SmoothWall running
> > on a seperate box for my dialup, so I just don't worry about security on
> > the local side of things.
>> And there you've lost me :) I'm a RedHat zealot, you see.
>That's all right, you'll get better soon ;)
> > So, How, specifically, can I enable X to connect? I am guessing that port
> > 6000 must be opened up somehow? Also, I remember various things about X
> > having it's own protection from outside connections, but I don't remember
> > where? I've been through this before when my Daughters first PC was a 486
> > running just an X server and connecting to my box using X -query
> > 192.168.1.1, but that was many years ago.
>> Mmmm. That vaguely rings a bell. There is, I think, a way to tell X
> not to listen on anything other than the local interface. Here's a
> quick check:
>> Container-Box > netstat -ant | grep LISTEN | grep 6000
>> (The 6000 is X display 0, btw)
>returns nothing :(
debian:/home/johngay# netstat -ant |grep LISTEN
tcp 0 0 0.0.0.0:32768 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:515 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:37 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:9 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:13 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:79 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:113 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:631 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:7100 0.0.0.0:* LISTEN
debian:/home/johngay#
So it seems that X is not listening?
> If that comes back without displaying an entry for 0.0.0.0, that's
> your culprit. Being a zealot, I automatically assumed you were running
> RedHat ;) If your X server is not listening on 0.0.0.0, you can only
> connect to it from the local server. Looking at the X command-line
> options, I see "-nolisten string" which tells the server not to bother
> listening with a given protocol, which may well be how your server is
> configured. The other option, if 0.0.0.0 /is/ displayed in the list
> above, is that some sort of iptables/ipchains stuff is blocking access
> to the port. Investigating these further I'm going to have to leave to
> you, because I'm not familiar with how these things are done in debian
> or progeny. I will suggest the following: kill your X session on
> Container-Box, and restart it manually like so:
>> Container-Box> X
I suppose I can try this, but it's a bit drastic!
>> That will start a raw X session with no window manager, and more
> importantly no command line switches. Flip back to a VT and check if
> the server is now listening on 0.0.0.0. If it is, yay, you've found
> your problem. If it's not, you're gonna have to go digging in the X
> config. If this /is/ your problem, you're going to have to track down
> the scripts used to start X (startx, xinit) and find out which one is
> adding in the relevant disabling command.
>> And that's about all the help I can give you without breaking into
> your box :)
>Hopefully a Debian expert can now step in and tell me where Debian is
stopping X from listening and how to fix it so it does?
> > Thanks again for all the help for the clueless ;)
>> Hey, I get a chance to show off my l33t sk1llz, or something. *cough*
>> > Cheers,
> > John Gay
>> Cheers,
> Waider.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
