On Mon, Aug 10, 2009 at 11:56 AM, Jeff Isaac wrote:
> /etc/network/interfaces, I can now properly use all of my NICs. The bigger
> mystery to me, then, is why the installer didn't install NetworkManager in
> the first place. The installer detected both cards, so I am somewhat at
l of my posts got onto the board. With his help, the issue has
been resolved. The problem was that for some reason unbeknownst to me, the
default Debian 5.0.2 installer failed to install the Network Manager service
on THREE consecutive installs. I had to manually apt-get install it and put
together
On Sat, Aug 8, 2009 at 10:07 AM, Jeff Isaac wrote:
> Hello all!
>
> the only interface listed is the loopback lo. I find this odd as the
> wireless can correctly detect the available networks in my area, so I have
> to believe that some part of the networking system is behaving correctly.
> ifco
Jeff Isaac wrote:
When I pull up the gnome network status panel (I have it pinned to the
bar), the only interface listed is the loopback lo. I find this odd as
the wireless can correctly detect the available networks in my area,
so I have to believe that some part of the networking system is
b
ig per the man
page instructions, and have tried putting the settings directly into
/etc/network/interfaces, but cannot seem to get it to show up as a valid
interface, let alone connect.
From what I have found in my searches, others are having no trouble
with getting the D600 up and running. I hav
On Mon, May 15, 2006 at 03:52:31PM +0200, Andr? Wendt wrote:
> I'm using ifplugd to connect to a network. Whenever there's wireless and
> wired networks available, I usually prefer the wired connection
The replies already posted are good, but you might also want to take a
look at http://www.debi
he wired interface when both are available.
>>
>> There are, as far as I know, three ways to do this :
>> - dirty hack to automatically ifdown wlan0 before eth0 goes up (using
>> pre-up stanzas in /etc/network/interfaces). There may be more
>> complicated things using
ar as I know, three ways to do this :
> - dirty hack to automatically ifdown wlan0 before eth0 goes up (using
> pre-up stanzas in /etc/network/interfaces). There may be more
> complicated things using a lockfile for example.
> - using ifmetric to route traffic through the cable instead of the
&g
e the wired interface when both are available.
>
> There are, as far as I know, three ways to do this :
> - dirty hack to automatically ifdown wlan0 before eth0 goes up (using
> pre-up stanzas in /etc/network/interfaces). There may be more
> complicated things using a lockfile for ex
wlan0 before eth0 goes up (using
pre-up stanzas in /etc/network/interfaces). There may be more
complicated things using a lockfile for example.
- using ifmetric to route traffic through the cable instead of the wireless NIC.
- using the bonding kernel driver as suggested[1] once to prioritize
the cab
Hi,
I'm using ifplugd to connect to a network. Whenever there's wireless and
wired networks available, I usually prefer the wired connection -- it's
faster and works mostly without additional setup (think WPA or VPN). But
when any wireless network is available, Debian wants to use it, no matter
if
sounds good. i knew it'd be something easy, I just couldn't think of
where to attack it from.
chris
John Schmidt wrote:
On Friday 07 April 2006 14:02, chris jackson wrote:
why, after working just fine for over a month, would my computer start
assigning different numbers to
On Friday 07 April 2006 14:02, chris jackson wrote:
> why, after working just fine for over a month, would my computer start
> assigning different numbers to my network interfaces? My wireless, that
> always used to be eth1 is now eth2, my pci card that used to be eth2 is
> now eth3,
why, after working just fine for over a month, would my computer start
assigning different numbers to my network interfaces? My wireless, that
always used to be eth1 is now eth2, my pci card that used to be eth2 is
now eth3, even though eth0 is still my ethernet connection. I had to
change
Dear Sven
Am Mon, Apr 03, 2006 at 06:25:35PM +0100 hat Sven Huster getippert:
> I got this configured in my /etc/udev/local.rules :
>
> BUS=="pci", KERNEL=="eth[0-9]", SYSFS{address}=="00:0c:f1:98:2e:ac" \
> NAME="wifi0"
>
> BUS=="pci", KERNEL=="eth[0-9]", SYSFS{address}=="00:0f:1f:34:01
Hi.
Related to the recent question about ordering multiple network cards: I
am having troubles getting both network cards to be detected. The system
is a Toshiba Satellite M50 (that's the .AU model name; not sure what
it's called elsewhere) running kernel 2.6.14. It's a Centrino, so that's
the sou
Sven Huster wrote:
* Philipp Frauenfelder <[EMAIL PROTECTED]> [2006-03-31 22:29:41 +0200]:
Hi
I have a Fujitsu Siemens Lifebook E 4010D with a wlan and
ethernet adapter (the one where you have to plug in a cable
before being online). Most stuff works fine, also both network
inte
* Philipp Frauenfelder <[EMAIL PROTECTED]> [2006-03-31 22:29:41 +0200]:
> Hi
>
> I have a Fujitsu Siemens Lifebook E 4010D with a wlan and
> ethernet adapter (the one where you have to plug in a cable
> before being online). Most stuff works fine, also both network
On Friday 31 March 2006 13:29, Philipp Frauenfelder wrote:
> Hi
>
> I have a Fujitsu Siemens Lifebook E 4010D with a wlan and
> ethernet adapter (the one where you have to plug in a cable
> before being online). Most stuff works fine, also both network
> interfaces. However, so
Hi
I have a Fujitsu Siemens Lifebook E 4010D with a wlan and
ethernet adapter (the one where you have to plug in a cable
before being online). Most stuff works fine, also both network
interfaces. However, sometimes my wlan is eth0 (and ethernet is
eth1) sometimes the ethernet is eth0 (and wlan is
why you think ifplugd could be
>>>
>>>I don't know for sure. But in the past, I had a similar problem (boot
>>>stall) and the problem was solved by putting HOTPLUG_INTERFACES="eth0" in
>>>/etc/default/ifplugd.
>
>
> If it's
n't know for sure. But in the past, I had a similar problem (boot
>> stall) and the problem was solved by putting HOTPLUG_INTERFACES="eth0" in
>> /etc/default/ifplugd.
If it's really a hotplug interface (ie, PC-card or USB),
then /etc/init.d/networking may stall i
John O'Hagan wrote:
>
>
>>auto eth0
>
>
> Most likely, the "auto eth0" entry is making the system try to bring up the
> interface too early...in one case I removed that line, and boot returned to
> normal; it will still come up automatically later if you have ifplugd and/or
> some kind of n
H.S. wrote:
>After the upgrade(I recall hotplug was uninstalled
>and udev upgraded), the laptop boot process now stalls at the
>"Configuring network interfaces ..." step. Any idea what could be the
>problem?
I had a similar problem...
>~# cat /etc/network/interfa
to know what it's waitingfor. If there's any way to make guessnet verbose, it would help.
Here is what the boot process, that has hanged while using interfaces.guessnet based interfaces script, show on the screen:
Configureing network interfaces... guessnet: Missing mac at line 26: on
ny way to make guessnet verbose, it would help.
Here is what the boot process, that has hanged while using interfaces.guessnet based interfaces script, show on the screen:
Configureing network interfaces... guessnet: Missing mac at line 26: only check for the ip
guessnet: Missing mac at line 29: only
H.S. wrote:
> Hi,
>
> I just dist-upgraded a Dell Inspiron 5160 that was running 2.6.12 kernel
> and Debian Unstable. After the upgrade(I recall hotplug was uninstalled
> and udev upgraded), the laptop boot process now stalls at the
> "Configuring network interfaces .
Hi,
I just dist-upgraded a Dell Inspiron 5160 that was running 2.6.12 kernel
and Debian Unstable. After the upgrade(I recall hotplug was uninstalled
and udev upgraded), the laptop boot process now stalls at the
"Configuring network interfaces ..." step. Any idea what could be the
p
On Thu, Feb 20, 2003 at 01:33:50AM -0800, Adam Lydick wrote:
> Is there a way to associate a MAC or device type (wireless vs. ethernet)
> with entries in /etc/network/interfaces? My laptop is configured to
> disable the ethernet hardware onboard if the cable is disconnected, thus
> e
Is there a way to associate a MAC or device type (wireless vs. ethernet)
with entries in /etc/network/interfaces? My laptop is configured to
disable the ethernet hardware onboard if the cable is disconnected, thus
eth0 and eth1 are often interchanged. Also, the driver used for a given
card will
On Thu, Feb 20, 2003 at 01:33:50AM -0800, Adam Lydick wrote:
> Is there a way to associate a MAC or device type (wireless vs. ethernet)
> with entries in /etc/network/interfaces? My laptop is configured to
> disable the ethernet hardware onboard if the cable is disconnected, thus
> e
Is there a way to associate a MAC or device type (wireless vs. ethernet)
with entries in /etc/network/interfaces? My laptop is configured to
disable the ethernet hardware onboard if the cable is disconnected, thus
eth0 and eth1 are often interchanged. Also, the driver used for a given
card will
On Fri, 13 Dec 2002, Larry Colen wrote:
> I've been having a devil of a time trying to get
> /etc/network/interfaces working with mapping. The manpage
> theoretically shows how to set it up, but says that it needs a script
> in order to work. I can't find any documentation
I've been having a devil of a time trying to get
/etc/network/interfaces working with mapping. The manpage
theoretically shows how to set it up, but says that it needs a script
in order to work. I can't find any documentation on what the script is
supposed to do, or how to mak
On Fri, 13 Dec 2002, Larry Colen wrote:
> I've been having a devil of a time trying to get
> /etc/network/interfaces working with mapping. The manpage
> theoretically shows how to set it up, but says that it needs a script
> in order to work. I can't find any documentation
I've been having a devil of a time trying to get
/etc/network/interfaces working with mapping. The manpage
theoretically shows how to set it up, but says that it needs a script
in order to work. I can't find any documentation on what the script is
supposed to do, or how to mak
On Tue, 2002-10-08 at 03:18, Bruce Best (CRO) wrote:
>
> Another problem (which also existed using the /etc/pcmcia/network.opts) is
> that the wireless card will not work if the onboard (wired) card is up; I
> _have_ to disable eth0 in order to get wlan0 to work. Generally, this isn't
> a big deal
On Tue, 2002-10-08 at 03:18, Bruce Best (CRO) wrote:
>
> Another problem (which also existed using the /etc/pcmcia/network.opts) is
> that the wireless card will not work if the onboard (wired) card is up; I
> _have_ to disable eth0 in order to get wlan0 to work. Generally, this isn't
> a big dea
Yes, I switched to pump as well, but only because dhclient stopped working
one day (after I did something it didn't like, no doubt). For some unknown
reason, pump worked where dhclient didn't, so I stuck with it.
I'll post back if I figure it out.
B.
>if you are using pump for dhcp you should
"Bruce" == Bruce Best <(CRO)" <[EMAIL PROTECTED]>> writes:
Bruce> Another problem (which also existed using the
Bruce> /etc/pcmcia/network.opts) is that the wireless card will
Bruce> not work if the onboard (wired) card is up; I _have_ to
Bruce> disable eth0 in order to get wla
Yes, I switched to pump as well, but only because dhclient stopped working
one day (after I did something it didn't like, no doubt). For some unknown
reason, pump worked where dhclient didn't, so I stuck with it.
I'll post back if I figure it out.
B.
>if you are using pump for dhcp you should
"Bruce" == Bruce Best <(CRO)" <[EMAIL PROTECTED]>> writes:
Bruce> Another problem (which also existed using the
Bruce> /etc/pcmcia/network.opts) is that the wireless card will
Bruce> not work if the onboard (wired) card is up; I _have_ to
Bruce> disable eth0 in order to get wl
>-Original Message-
>From: Shyamal Prasad [mailto:[EMAIL PROTECTED]
>
>I don't use my Linux laptop much anymore. However, I did set it up
>with /etc/network/interfaces. The one thing I do have is have the
>hotplug interface installed
Thanks; I do have hotplug
>-Original Message-
>From: Shyamal Prasad [mailto:[EMAIL PROTECTED]]
>
>I don't use my Linux laptop much anymore. However, I did set it up
>with /etc/network/interfaces. The one thing I do have is have the
>hotplug interface installed
Thanks; I do have ho
"Bruce" == bestb writes:
Bruce> Should it?? Is there a way to use the
Bruce> /etc/network/interfaces to bring the card back up
Bruce> automatically when resuming?? Or should I just go back to
Bruce> using the /etc/pcmcia/network.opts for configurin
suspend
and up on resume, without my ever having to worry about it.
I understand (mentioned in the docs for the linux-wlan-ng wireless drivers)
that Debian is now moving to control all network cards, including pcmcia,
from /etc/network/interfaces, and that /etc/pcmcia/network.opts is being kept
for
"Bruce" == bestb writes:
Bruce> Should it?? Is there a way to use the
Bruce> /etc/network/interfaces to bring the card back up
Bruce> automatically when resuming?? Or should I just go back to
Bruce> using the /etc/pcmcia/network.opts for configurin
suspend
and up on resume, without my ever having to worry about it.
I understand (mentioned in the docs for the linux-wlan-ng wireless drivers)
that Debian is now moving to control all network cards, including pcmcia,
from /etc/network/interfaces, and that /etc/pcmcia/network.opts is being kept
for
uld have what I want.
This is because the docking station card gets eth0 if it exists (as the
kernel module loads first) and then the PCMCIA card gets eth1 if the machine
is docked (and eth0 is taken) otherwise it gets eth0.
If the PCMCIA stuff used /etc/network/interfaces, this would be trivial. But
uld have what I want.
This is because the docking station card gets eth0 if it exists (as the
kernel module loads first) and then the PCMCIA card gets eth1 if the machine
is docked (and eth0 is taken) otherwise it gets eth0.
If the PCMCIA stuff used /etc/network/interfaces, this would be trivial. But
r the PCMCIA card) to reflect my network
settings, and I have added an entry for eth0 to /etc/network/interfaces (for
the docking station card).
If I boot normally, with the PCMCIA card connected, everything is fine and I
see the network. If I then do the following
cardctl eject
[ switch the
r the PCMCIA card) to reflect my network
settings, and I have added an entry for eth0 to /etc/network/interfaces (for
the docking station card).
If I boot normally, with the PCMCIA card connected, everything is fine and I
see the network. If I then do the following
cardctl eject
[ switch the
52 matches
Mail list logo
