Does anyone know what I need to do (or if I can) get identd on mIRC to work across a router? I just set up a home network to share the cable modem, but now I can't get back onto Efnet because all the servers want an identd.
Posted on 2001-06-18 19:31:00 by Ernie
Foward the ident port to the ip address of the computer you want to use.
Posted on 2001-06-19 00:04:00 by Soul~Drudge
Huh?
Posted on 2001-06-19 00:55:00 by Ernie
When you configure the router, you can forward ports to an IP address. For example, if I have a home network and a PC with IP 192.168.0.1 which I want to use as my "exposed" server, and lets say the actual IP of the router is 24.24.24.24. Well, when you configure the router, you can tell the router that "certain" or "all" ports that are incoming through the other side of the router get forwarded to 192.168.0.1. In essence, it's as if that PC is the IP itself (of the router). It's called IP forwarding. You can do that with ports and IP's. If you still have questions, let me nkow or email me directly... Cisco router IP Forwarding IP Forwarding is not just cisco... however... )_Shaw
Posted on 2001-06-19 02:02:00 by _Shawn
I have the same problem here at work :( Norwegian server doesn't need identd :)
Posted on 2001-06-19 04:01:00 by Hiroshimator
Thanks Shawn, I'll try to figure out how to do that here. Hiro, which server is that? irc.homelien.no? That one doesn't let me in either.
Posted on 2001-06-19 07:53:00 by Ernie
yes, it probably won't let you in because of the demographic difference. I'm in Europe, just like they are. It's slow but OK for me
Posted on 2001-06-19 10:36:00 by Hiroshimator
OK, I tried the forwarding thingie, and inside mIRC I saw: -irc.Prison.NET- *** Got Ident response Hey, I must have got it right!
Posted on 2001-06-19 23:07:00 by Ernie
There can be a lot of "funny" problems when running irc through a router (when you have one "global outside IP" and run LAN-only IPs like 192.168.x.x or 10.x.x.x). Ident is usually easy to fix, when you have amdin access to the router. Getting DCC transfers to work is another thing, and (in my case) involved forwarding ports 1024-5000 to my own IP -- not a very nice way of doing it, but it works, and I couldn't think of any other way. Argh :).
Posted on 2001-07-03 21:50:00 by f0dder