Hm -- how about using proxy-arp style routing? If their router has has
proxy-arp support turned on, then you can set yourself (ie your own IP) as
the default and will arp for _all_ addreeses of _all_ remote boxes you try
to connect to. Then their router sends a response to the arp-request and
your box gets an apr table entry of the router (within the local
ethernet-broacast realm) and will send stuff for whatever remote IP
address you have.
It's not the cleanest solution, but I've used it under windows, linux and
hpux to get around the foolishness of a network architecture I couldn't
change... I used this at an old job where I had non-contiguous IP
networks in the same ethernet-broacast domain so that all the machines
would find each other on the local network, and the router handled all the
off-segment connections via proxy-arp. I have NOT tried this under
FreeBSD as I thankfully dont work there any more (was converted to the
FreeBSD religion after I left...).
Alternatively, you could use an exceptionally permissive netmask so that
the local box _thought_ the other IP was in the same 'network' as yours.
Pretty much both achieve the same effect of putting the remote router on
the 'same network' as you.
Good luck.
Fred
>
> Can't assign cable modem gateway (10.17.56.12) to interface
> ed0 with assigned IP (208.59.162.242) - "network unreachable".
>
> I called RCN (my cable provider) and asked them to give me
> a gateway on the same subnet; they said they "don't do that".
...
> P.S. Alternately, how can I force the system to allow a gateway
> that is on a different subnet (like windows allows that). Who
> can I turn to for help ?
--
Fred Clift - [EMAIL PROTECTED] -- Remember: If brute
force doesn't work, you're just not using enough.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message