route command baffles me.
- From: gl@xxxxxxxxxxxxxxxxxxxxxxxx (Jay G. Scott)
- Date: Mon, 26 Mar 2007 19:00:50 +0000 (UTC)
on solaris, i get along just fine. i set my default route
and it works. for some reason things never go so smoothly
for me on linux. my "test" linux box is working, but
it's "completely ordinary."
possibly my problem is that for the first time, i'm hooking
ripped, the new machine, to an 802.1q trunk. the box has two PHYSICAL
enets on it. for the moment, i only want to use eth0.
is there something equivalent to solaris' unplumb, so that
i can tell eth1 to drop dead? ie, w/o a reboot?
i assume if i rename the ifup (or whatever it is) script
and reboot it'll go away.
i did
vconfig add eth0 2
now, if i want the machine to respond to 10.20.30.40
well, frankly, what do i do? i read the man page for vconfig,
ifconfig, web pages on 802.1q, and so on, but when i try to
ping the gateway on 10.20 i always get destinatino host
unreachable. what do i WANT my netstat -nr output to look like?
i feel like i've tried all reasonable combinations, and same
thing every time.
just as a side point, there's always that 169.254.0.0 route,
can one safely get rid of that? what's it for?
sorry if i'm grumpy. i'm frustrated. this ought to be simple
but i'm getting nowhere.
j.
--
Jay Scott 512-835-3553 gl@xxxxxxxxxxxxxxxx
Head of Sun Support, Sr. Operating Systems Specialist
Applied Research Labs, Computer Science Div. S224
University of Texas at Austin
.
- Follow-Ups:
- Re: route command baffles me.
- From: Chris Davies
- Re: route command baffles me.
- From: Paul Colquhoun
- Re: route command baffles me.
- From: patrick
- Re: route command baffles me.
- Prev by Date: Re: Multiple vpn tunnels
- Next by Date: Re: MOUNT failed to NFS
- Previous by thread: Multiple vpn tunnels
- Next by thread: Re: route command baffles me.
- Index(es):
Relevant Pages
|
