is this possible?
Posted: Wed Jun 30, 2004 8:02 pm
think its possible to make the binding ip (ie: where my ip would be), an ip of a different place / machine or even a website????
Page 1 of 1
Posted: Wed Jun 30, 2004 8:08 pm
Not directly. There is a thing called NAT (Network Address Translation) that can probably do what you want, but that's not directly related to UnrealIRCd. Google is your friend
Posted: Wed Jun 30, 2004 8:25 pm
If your machine does not have access to the IP, it will not let you bind to it. A NAT would let you *use* other IPs, but it would not let you bind to them.
Posted: Wed Jun 30, 2004 10:02 pm
Yes. NAT is a whole 'nother beast.
As an example: my home network, where the cable modem host computer is one machine, and the computer running the IRCd is a different one.
The public address of the host computer is 24-*.cpe.cableone.net (24.*). We use Internet Connection Sharing to allow 3 others (including the IRCd host) to connect to the internet. Thus, the host also has a LAN-internal IP of 192.168.0.1. The IRCd host is 192.168.0.3 and NAT is configured to forward 6667 and 6601 to that machine (which is the very machine I'm writing this post from: mine). (It also forwards some DCC ports, but that's another story.)
Thus, to listen for outside connections, the IRCd binds to the machine's most public address of 192.168.0.3. The NAT machine has already bound 6667/6601 on the internet-public IP (24.117.98.156) and is configured to forward requests to the appropriate internal address.
So to bind to a NAT'd IP, you would actually bind to the IP it forwards to, which is usually 192.168.*.
As an example: my home network, where the cable modem host computer is one machine, and the computer running the IRCd is a different one.
The public address of the host computer is 24-*.cpe.cableone.net (24.*). We use Internet Connection Sharing to allow 3 others (including the IRCd host) to connect to the internet. Thus, the host also has a LAN-internal IP of 192.168.0.1. The IRCd host is 192.168.0.3 and NAT is configured to forward 6667 and 6601 to that machine (which is the very machine I'm writing this post from: mine). (It also forwards some DCC ports, but that's another story.)
Thus, to listen for outside connections, the IRCd binds to the machine's most public address of 192.168.0.3. The NAT machine has already bound 6667/6601 on the internet-public IP (24.117.98.156) and is configured to forward requests to the appropriate internal address.
So to bind to a NAT'd IP, you would actually bind to the IP it forwards to, which is usually 192.168.*.