Chris Jacobson writes:
>The service provider I use wants all MUDs to bind to an IP now...
>however, I know Circle doesn't do this by default. Is there a way to do
>it? Is it even necessary?
Circle doesn't do this by default. It's only necessary if the machine
you're using has more than one IP address (e.g., more than one network
interface, or a single interface with several "IP aliases"), and you
want the MUD to only respond to connections on a *single* one of those
IP addresses. By default, the MUD will reply to all of them.
In other words, lets say you're on a machine that has two different
network interfaces -- say, two Ethernet cards -- and each Ethernet
card has its own IP address. Most servers respond to requests on all
IP addresses; for example, you can telnet into the server using either
IP address and the telnet server will respond to the connection.
Similarly, if you run a MUD on that machine, telnetting into the
machine on either of its IP addresses on port 4000 will reach the
MUD.
Chances are, you're using a service provider that specializes in MUD
space and they want to be able to offer the standard port 4000 to more
than one MUD running on the same machine.
You can get Circle to bind to a specific IP address by changing the
INADDR_ANY constant in comm.c to the IP address to which you'd like
Circle to bind. For example, to bind to 1.2.3.4, I think you'd write:
sa.sin_addr.s_addr = htonl((1 << 24) | (2 << 16) | (3 << 8) | 4);
Maybe I'll add this to pl13+ if it's commonly required, but I've never
heard of anyone needing it before.
-Jeremy
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/08/00 PST