Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Prevent long delays when connecting to IRC servers Internet
I commonly use IRC, and always while using my MacBook on a wireless connection. This can be an annoyance, as some IRC servers make you wait a period of time before they will allow you to connect (sometimes over 30 seconds).

After scouring the internet and many false attempts, I found IdentD, a free neat little System Preference that handles what I need to nicely. (There's more info on the program on its MacUpdate page.)

I installed this on one of my G4 towers that was permanently connected to my network with Ethernet cables -- you cannot use this application on the computer that is using a wireless connection. I then set up the app via its preferences panel in System Preferences to return a custom string containing the IRC username (Your Shorthand name) that I was use on my MacBook.

After this, I simply configuring my router to forward port 113 (TCP) to my G4 tower, and told the firewall on my G4 to allow port 113. This resolved my connection problems to IRC servers.
    •    
  • Currently 1.89 / 5
  You rated: 2 / 5 (9 votes cast)
 
[6,357 views]  

Prevent long delays when connecting to IRC servers | 5 comments | Create New Account
Click here to return to the 'Prevent long delays when connecting to IRC servers' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Prevent long delays when connecting to IRC servers
Authored by: jcbeckman on Mar 12, '09 08:10:01AM

Some IRC clients have Identd functionality built-in. Requiring Identd is one of the stupidest things I've ever seen, since it's so easy to lie. Why are servers still asking users for this useless info?



[ Reply to This | # ]
Prevent long delays when connecting to IRC servers
Authored by: dille on Mar 12, '09 09:08:07AM

Ignorance or unwillingness to change old settings, I think.

Apart from that, I prefer fuaxident. Requires a bit more knowledge to set up, but it allows you to specify a "no user", which means that the IRC server will accept the username that the client on ANY machine in your network spits out.

This was important in my case, because there's other people using the same internet connection, and they were all getting MY ident on their IRC sessions. =]



[ Reply to This | # ]
Prevent long delays when connecting to IRC servers
Authored by: Osc on Mar 13, '09 05:14:16PM

it's mainly for shell boxes and, now, bouncers.

it's hard to fake from a shell box, which allows the server operators to remove abusive users while allowing non abusive users to connect. what isn't fun is a shell box where no one uses ident: to remove abuse, you have to remove the whole shell provider.



[ Reply to This | # ]
Prevent long delays when connecting to IRC servers
Authored by: pauljlucas on Mar 12, '09 11:14:27AM
The ethernet transport mechanism is irrelevant: you can use any server on a computer over a wireless connection. It's just that most computers that connect wirelessly are assigned a dynamic IP address.

In order for a server on a home network to work, the server machine must be able to be connected to via port 113. For that to happen, one of the following must be true:

  • The machine must be directly connected to the DSL/cable modem, i.e., no hub/switch.
  • If there is a switch, the machine must have a local static IP address and port 113 must be mapped to it in the switch.
  • If there is a switch, the machine must be marked as the DMZ host and port 113 must not be mapped elsewhere.
Again, whether a machine connects wirelessly is irrelevant. If you were to assign your laptop a staic IP and portmap 113 to it, it would work just fine.

---
- Paul

[ Reply to This | # ]

Port Triggering
Authored by: bedouin on Mar 12, '09 04:21:31PM

You need to enable port triggering on port 113; that way you will have identd on any machine behind your router.



[ Reply to This | # ]