-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Taharni Duggan wrote:
> how do i host custom game on warcraft 3
You aren't on the same subnet as your other machine. You need to
configure your network for all machines properly.
BTW, this isn't a warcraft 3 support group and your information you
pro
how do i host custom game on warcraft 3
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ok what doing you tell me how doing setting the ip address and fail
network local network
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTEC
Mark Edwards <[EMAIL PROTECTED]> writes:
> On Mar 1, 2005, at 12:53 PM, Lowell Gilbert wrote:
>
> Looking on the net, I found the following suggestion, which does
> cure
> the errors:
>
> /sbin/route add -net 192.168.1.254 -netmask 255.255.255.0
> -interface 1
>
On Mar 1, 2005, at 12:53 PM, Lowell Gilbert wrote:
Looking on the net, I found the following suggestion, which does
cure
the errors:
/sbin/route add -net 192.168.1.254 -netmask 255.255.255.0
-interface 1
My question is, is that the proper way to deal with this?
It's not bad. I would use -host
Anyway, the DHCP server gives a fixed public internet
> >> IP to my server, but it communicates on 192.168.1.254, which angers
> >> FreeBSD (4.11). I get a lot of the following:
> >>
> >> arplookup 192.168.1.254 failed: host is not on local network
> >
.254, which angers
FreeBSD (4.11). I get a lot of the following:
arplookup 192.168.1.254 failed: host is not on local network
Which makes sense, because as far as FreeBSD is concerned, interface
ep1 is on the internet not on a LAN.
Exactly.
Looking on the net, I found the following suggestion, which do
1). I get a lot of the following:
>
> arplookup 192.168.1.254 failed: host is not on local network
>
> Which makes sense, because as far as FreeBSD is concerned, interface
> ep1 is on the internet not on a LAN.
Exactly.
> Looking on the net, I found the following suggestion, which
I've just put my server on a new connection that requires DHCP, even
for a fixed IP. Anyway, the DHCP server gives a fixed public internet
IP to my server, but it communicates on 192.168.1.254, which angers
FreeBSD (4.11). I get a lot of the following:
arplookup 192.168.1.254 failed: ho
