With tcp, the default is pretty much always in the same subnet as at
least one interface of any given host. One can do things with VPN, and
gif's and gre's etc which can work around some oddball situations.
however.
if there is a local router that you use to get to your 'default'
gateway, I would characterize that local router as your default gateway.
how about showing us an ifconfig and a netsat -rn
Jyri Hovila [iki.fi] wrote:
Hi,
a brief follow-up.
With Linux, default gateway that resides in different subnet than the
host, all that has to be done is 1) adding a static route to the
default gateway and then 2) adding the default gateway to routing table.
With my OpenBSD test case, I already have a static route to the default
gateway (thanks to correctly configured DHCP server) but when I try to
add default gateway:
# route add default 5.166.16.254
add net default: gateway 5.166.16.254: Too many levels of symbolic links
I'm still googling but haven't found a solution yet.
Any tips, anyone?
- Jyri
--
Dag H. Richards ( no title / no lettres )
The first rule of tautology club is the first rule of tautology club.
This message may or may not contain proprietary information.
Since it is being relayed by SMTP across an unknown number of
relays to its destination, using a protocol that is traditionally
plain ASCII, it's silly to pretend it is still confidential.
If you are not the intended recipient of this message,
there is simply nothing I can do about that. Attempting to bind you
to some destruction protocol through this windbag sig paragraph is
Quixotic at best..
