Re: route command baffles me.
- From: hemphill@xxxxxxxxxxxxx
- Date: 26 Mar 2007 18:04:56 -0400
gl@xxxxxxxxxxxxxxxxxxxxxxxx (Jay G. Scott) writes:
In article <56qnkqF2aem2dU1@xxxxxxxxxxxxxxxxxx>,
patrick <ptri.c.k@xxxxxxxxxxxxxx> wrote:
In news:eu9592$7e6$1@xxxxxxxxxxxxxxxxxxxx,
Jay G. Scott <gl@xxxxxxxxxxxxxxxxxxxxxxxx> wrote:
is there something equivalent to solaris' unplumb, so that
i can tell eth1 to drop dead? ie, w/o a reboot?
# /sbin/ifconfig eth1 down
Better would be "/sbin/ifdown eth1". It is a script that does
additional cleanup in certain configurations.
Network configuration is different under different distributions of
Linux. Which one do you have?
when you do ifconfig -a under with eth1 down, it still shows
eth1. i want ifconfig -a to not show anything about eth1
at all. i've done down, and down doesn't do that.
if you unplumb on solaris, ifconfig -a won't mention it
at all.
[snip]
The man page under my version of Linux (Fedora Core 6) says that
ifconfig -a shows all interfaces. Why do you care? If it's down,
it's down. It's not in the routing tables, and it doesn't affect you.
Use ifconfig without the -a to show all the active interfaces. If
your eth0 and eth1 used different drivers, it *might* be possible to
use rmmod to remove the kernel module supporting one of the
devices--no guarantees. I've never heard of unrecognizing an ethernet
interface after booting. Maybe there's a way to do it, but it might
depend on exactly which driver you're using. So what is the content
of your "/etc/mod*.conf"? (It's usually named either
"/etc/modules.conf" of "/etc/modprobe.conf".)
You might be able to force eth1 not to be recognized at boot time by
putting the line "alias eth1 off" in your "/etc/mod*.conf". I
wouldn't count on it, since this is a command to the kernel to not
load a driver. If eth0 uses the same driver, I would expect the
driver to find both interfaces.
While you can certainly use command line tools to configure your VLAN
(and I would do it that way myself, the first time) you will probably
want to use the existing networking scripts for doing so. In my
distribution (FC6) they can be found in
"/etc/sysconfig/network-scripts". You can read the scripts to find
out what they do, grep them for "VLAN" or "vconfig" to find out how
they are used and configuration files they look at. There are also
GUI configuration tools to setup the network. I tend to use them only
at initial installation, and then tweak things by hand if necessary.
FC6 has "system-config-network".
I don't use VLANs under Linux, so I might not be able to help you
there. I do know something about routing.
Scott
--
Scott Hemphill hemphill@xxxxxxxxxxxxxxxxxx
"This isn't flying. This is falling, with style." -- Buzz Lightyear
.
- References:
- route command baffles me.
- From: Jay G. Scott
- Re: route command baffles me.
- From: patrick
- Re: route command baffles me.
- From: Jay G. Scott
- route command baffles me.
- Prev by Date: Problems creating domain for intranet
- Next by Date: Re: route command baffles me.
- Previous by thread: Re: route command baffles me.
- Next by thread: Re: route command baffles me.
- Index(es):
Relevant Pages
|
