Re: arplookup 192.168.1.254 failed: host is not on local network
-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 provided was lacking at best. /sbin/ifconfig and /usr/bin/netstat -nr output would be helpful, to say the least. - -Garrett -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.1 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFo+ZuEnKyINQw/HARAtzjAKCrFhSgF+IOQYPJS/DSB8/zDIBrjgCeI7kd Qph/dqoEMwv9u2gOdM0LtYA= =wEKo -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
arplookup 192.168.1.254 failed: host is not on local network
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]"
arplookup 192.168.1.254 failed: host is not on local network
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 PROTECTED]"
Re: arplookup 192.168.1.254 failed: host is not on local network
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 > > My question is, is that the proper way to deal with this? > >>> > >>> It's not bad. I would use -host instead of -net and -netmask, and it > >>> will fail if the DHCP server ever changes its address, but what you > >>> are doing is is working and fairly likely to stay that way. > >> > >> How would you phrase the command? I just tried -host and couldn't get > >> it to work. > > > > e.g., > > route add -host 172.10.212.2 -interface bge0 > > I tried that syntax and I get errors like this: > > Mar 1 13:12:37 lilbuddy /kernel: arp: 00:0d:72:d7:d9:a1 attempts to > modify permanent entry for 192.168.1.254 on ep1 > > If I use the -net -netmask syntax I don't get the errors. "permanent entry"? Did you put in a static ARP? At any rate, I'd try a /32 mask instead of /24. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: arplookup 192.168.1.254 failed: host is not on local network
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 instead of -net and -netmask, and it will fail if the DHCP server ever changes its address, but what you are doing is is working and fairly likely to stay that way. How would you phrase the command? I just tried -host and couldn't get it to work. e.g., route add -host 172.10.212.2 -interface bge0 I tried that syntax and I get errors like this: Mar 1 13:12:37 lilbuddy /kernel: arp: 00:0d:72:d7:d9:a1 attempts to modify permanent entry for 192.168.1.254 on ep1 If I use the -net -netmask syntax I don't get the errors. -- Mark Edwards [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: arplookup 192.168.1.254 failed: host is not on local network
Mark Edwards <[EMAIL PROTECTED]> writes: > On Mar 1, 2005, at 11:21 AM, Lowell Gilbert wrote: > > > Mark Edwards <[EMAIL PROTECTED]> writes: > > > >> 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: 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 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 instead of -net and -netmask, and it > > will fail if the DHCP server ever changes its address, but what you > > are doing is is working and fairly likely to stay that way. > > How would you phrase the command? I just tried -host and couldn't get > it to work. e.g., route add -host 172.10.212.2 -interface bge0 > >>I have to > >> issue this statement whenever the dhclient is restarted. I've > >> currently placed it in my firewall script, but is there a proper or > >> more elegant way to achieve this? > > > > If you want something more elegant, you could specify a script for one > > of the dhclient-script(8) hooks, and put the route in there. You > > would be able to refer to the interface and server address by > > variables which dhclient-script provides... > > Great! I put the command in /etc/dhclient-exit-hooks and it works > great on a reboot. I don't really see which variables I can use in > the dhclient-script man page though. Do you know which variables > would do this? $interface $new_ip_address I can't seem to find anywhere that the server address is passed along, though. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: arplookup 192.168.1.254 failed: host is not on local network
On Mar 1, 2005, at 11:21 AM, Lowell Gilbert wrote: Mark Edwards <[EMAIL PROTECTED]> writes: 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: 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 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 instead of -net and -netmask, and it will fail if the DHCP server ever changes its address, but what you are doing is is working and fairly likely to stay that way. How would you phrase the command? I just tried -host and couldn't get it to work. I have to issue this statement whenever the dhclient is restarted. I've currently placed it in my firewall script, but is there a proper or more elegant way to achieve this? If you want something more elegant, you could specify a script for one of the dhclient-script(8) hooks, and put the route in there. You would be able to refer to the interface and server address by variables which dhclient-script provides... Great! I put the command in /etc/dhclient-exit-hooks and it works great on a reboot. I don't really see which variables I can use in the dhclient-script man page though. Do you know which variables would do this? Thanks! -- Mark Edwards [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: arplookup 192.168.1.254 failed: host is not on local network
Mark Edwards <[EMAIL PROTECTED]> writes: > 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: 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 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 instead of -net and -netmask, and it will fail if the DHCP server ever changes its address, but what you are doing is is working and fairly likely to stay that way. >I have to > issue this statement whenever the dhclient is restarted. I've > currently placed it in my firewall script, but is there a proper or > more elegant way to achieve this? If you want something more elegant, you could specify a script for one of the dhclient-script(8) hooks, and put the route in there. You would be able to refer to the interface and server address by variables which dhclient-script provides... -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
arplookup 192.168.1.254 failed: host is not on local network
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: 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. 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? I have to issue this statement whenever the dhclient is restarted. I've currently placed it in my firewall script, but is there a proper or more elegant way to achieve this? Thanks! -- Mark Edwards [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
