Discussion Locked

NOT GETTING IRC CHATTING ON LINUX 6.0

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

HELLO,
PLZ HELP ME TO GET OUT OF THIS PROBLEM. I HAVE CONFIGURED MY LINUX SERVER, FOR MY LOCAL INTRANET, AS A PROXY SERVER, ON MY INTEL MACHINE, MY NETWORK HAVING THE CLIENTS OF WIN95 AND NT WORKSTATIONS WITH I.E 5.0 AND NETSCAPE 4.7 BROWSERS. THE PROBLEMS IAM GETTING IN CONFIGURATION
1.WHENEVER IAM GIVING HTTP REQUEST ,ON PORT 80 OF SERVER . SERVER SENDING ITS APACHE DEFAULT PAGE, WHEN WE HAVE CHANGED THE SQUID DEFAULT PORT ADDRESS TO 80 .WHEN THE DEFAULT PORT 3128 IS IN USE , AS A DEFAULT SETTING , THE HTTP REQUEST FROM THE CLIENT BROWSER R FARWARDING TO THE INTERNET . BUT THE MOST IMPORTANT THING IS THAT IT IS NOT ALLOWING IRC CHATTING EVEN IN THE BROWSER OR SOME CHATTING APPLICATIONS, LIKE "MIRC", "YAHOO CHAT " ETC.
SO PLZ GIVE THE REMEDY FOR THIS PROBLEM, AND ALSO GIVE SOME TIPS IN SQUID CONFIGURATION FOR FASTENING MY INTERNET BROWSING AT CLIENT SIDE.WITH A GOOD CACHING CONFIGURATION.

I SHALL BE VERY THANKFUL TO UR ANSWERS.

WAITING FOR UR POSITIVE REPLY AT THE EARLIEST
MSALI

5 replies

by kent.manley

This sounds like a problem in your ipchains configuration.

The problem appears to be that your clients are requesting these things (http requests and irc sessions) to your gateway on the 'normal' ports. However, you've reconfigured them (as services) on your linux system.

Essentially, though, you really want them to pass through without really 'hitting' the server (since it's your NAT/gateway box).

You need to write your ipchains rules like so:
ipchains -A forward -s 192.168.142.0/24-d 0.0.0.0/0 -j MASQ

Substitute the ip address 192.168.142.0/24 with whatever you're using on the 'inside'. 0.0.0.0 says 'anywhere else'. The -A means all, the -j says "use Masquerading."

In this way, your server will function as it's supposed to for services off your net.

If you're trying to get to services on your server, your clients need to be configured to request on those ports. Not many windows programs I'm aware of can are configurable in this (although MIRC client may be so; also, you can modify http requests by appending :port to an http request in most browsers, i.e., http://www.myserver.com:9999 if you're running an httpd on port 9999 of the server answering up to www.myserver.com).

Good luck.

by james_randy

That was a very thoughtful and thorough first answer. Why don't you go ahead and accept that answer and close the question.

This discussion is closed to new replies.