So what you are saying is that with the: route add -net default -iface -interface xl0 command the system thinks there is a direct connect. Doesn't this then send all packets out, since there is no address supplied with the route command, or is this a function the the 10.*.*.* addresses are private network addresses.
If it sends all packets out, I would expect the 10.17.47.37 to receive it and forward it, since it is the gateway/modem. Having taken a quick look at the arp man page, it seems that one needs to arp each address/host rather than globally. Again, what I'm trying to do is get the system to pass all packets to the gateway/modem for forwarding over the net. Thanks Jim ---------- In Response to your message ------------- > Date: Fri, 14 Mar 2003 11:24:31 +0100 > To: "J. W. Ballantine" <[EMAIL PROTECTED]> > From: Guido van Rooij <[EMAIL PROTECTED]> > Subject: Re: route pointing to a gateway that's not on net > Sender: [EMAIL PROTECTED] > > On Thu, Mar 13, 2003 at 03:34:18PM -0500, J. W. Ballantine wrote: > > round-trip min/avg/max/stddev = 3.022/3.428/5.029/0.801 ms > > # ping 207.172.3.8 <<< one of isp's name ser ver > > PING 207.172.3.8 (207.172.3.8): 56 data bytes > > ping: sendto: Host is down > > ping: sendto: Host is down > > ping: sendto: Host is down > > ping: sendto: Host is down > > > > So this method allows my system to get to the > > modem/dhcp server/gateway, but no further. (when I ping > > from windows I get a response, so the system isn't down.) > > That is because 207.172.3.8 is not directly connected. By speficying a > route entry with -iface you specify it is directly connected. That > is the reason you can now reach the 10.*hosts. > > The problem with the 207.172.3.* hosts exists because your routing > table expects the 207.172.3.* range to be directly connected. > > So either you have to make them apear directly connected, or you must say th at > they are not directly connected. The first can be doe by having your gateway > do proxy arp, or by manually setting arp entries on your host > (for all 207.172.3.* hosts, do arp -s host MAC, where MAC is the mac address > of your gateway). > I don't know how to do the second one, except for adding single host routes > for each host, i.e.: route add host-ip-address gateway-ip-address. > > -Guido > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-net" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message