Using Debian stable (Etch), 2.6.18-4-686 kernel on Debian Dell Inspiron
e1505. The wireless card (from lshw output is)

*-network DISABLED
description: Wireless interface
product: PRO/Wireless 3945ABG Network Connection
vendor: Intel Corporation
physical id: 0
bus info: pci@0b:00.0
logical name: eth2
version: 02
serial: 00:13:02:9e:cc:1b
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ipw3945 driverversion=1.1.2dmpr
firmware=13.0 1:0 () ip=128.84.152.138 latency=0 link=yes multicast=yes
wireless=IEEE 802.11a
resources: iomemory:dfcff000-dfcfffff irq:169


The relevant stanza in /etc/network/interfaces is

# allow-hotplug eth2
# auto eth2
# iface eth2 inet dhcp
# wireless-essid SomeThing
# wireless-mode Managed

I commented out this stanza and did

$sudo ifconfig eth2 down

Even after that, eth2 interface comes up after some time for no reason. I
believe it is due to dhclient, since I see messages like the following
in /var/log/syslog

Aug 7 12:15:10 kusumanchi dhclient: DHCPREQUEST on eth2 to 132.236.56.249
port 67

But I dont know how to prevent the automatic configuring of this wireless
device. I do not want to remove dhclient since it is essential when I do
want to bring up eth2.

$dpkg -l \*dhcp\* | grep ^ii
ii dhcp3-client 3.0.4-13 DHCP Client
ii dhcp3-common 3.0.4-13 Common files used by all the dhcp3*
packages

Any suggestions?

thanks
raju

--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tue, Aug 07, 2007 at 12:19:44PM -0400, Kamaraju S Kusumanchi wrote:
> Using Debian stable (Etch), 2.6.18-4-686 kernel on Debian Dell Inspiron
> e1505. The wireless card (from lshw output is)
>
[...]
> The relevant stanza in /etc/network/interfaces is
>
> # allow-hotplug eth2
> # auto eth2
> # iface eth2 inet dhcp
> # wireless-essid SomeThing
> # wireless-mode Managed
>
> I commented out this stanza and did
>
> $sudo ifconfig eth2 down
>
> Even after that, eth2 interface comes up after some time for no reason. I
> believe it is due to dhclient, since I see messages like the following
> in /var/log/syslog
>

is NetworkManager running? if so, surf to it on the desktop and turn
off "Enable Roaming" or whatever it is for that card.

hth


A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGuKx8aIeIEqwil4YRAqM2AKCA2RFL8SIgfC9oYnKiM2 gwAho/eQCgvg8V
chPfBGKVK1mnuVxAWzdC36Q=
=dLkT
-----END PGP SIGNATURE-----

On Tue, Aug 07, 2007 at 12:19:44PM -0400, Kamaraju S Kusumanchi wrote:
> Using Debian stable (Etch), 2.6.18-4-686 kernel on Debian Dell Inspiron
> e1505. The wireless card (from lshw output is)
>
[...]
> The relevant stanza in /etc/network/interfaces is
>
> # allow-hotplug eth2
> # auto eth2
> # iface eth2 inet dhcp
> # wireless-essid SomeThing
> # wireless-mode Managed
>
> I commented out this stanza and did
>
> $sudo ifconfig eth2 down
>
> Even after that, eth2 interface comes up after some time for no reason. I
> believe it is due to dhclient, since I see messages like the following
> in /var/log/syslog
>

is NetworkManager running? if so, surf to it on the desktop and turn
off "Enable Roaming" or whatever it is for that card.

hth


A

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGuKx8aIeIEqwil4YRAqM2AKCA2RFL8SIgfC9oYnKiM2 gwAho/eQCgvg8V
chPfBGKVK1mnuVxAWzdC36Q=
=dLkT
-----END PGP SIGNATURE-----

Andrew Sackville-West wrote:
>
> is NetworkManager running? if so, surf to it on the desktop and turn
> off "Enable Roaming" or whatever it is for that card.
>

No. NetworkManager is not installed on this system.

raju

--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Andrew Sackville-West wrote:
>
> is NetworkManager running? if so, surf to it on the desktop and turn
> off "Enable Roaming" or whatever it is for that card.
>

No. NetworkManager is not installed on this system.

raju

--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Kamaraju S Kusumanchi wrote:
> Using Debian stable (Etch), 2.6.18-4-686 kernel on Debian Dell Inspiron
> e1505. The wireless card (from lshw output is)
>
[...]
>
> But I dont know how to prevent the automatic configuring of this wireless
> device. I do not want to remove dhclient since it is essential when I do
> want to bring up eth2.
>

Have a look at section 8 of the NewbieDOC article - configure the network card
interface using the command line [1]. Comment out your non-wireless card in
/etc/network/interfaces to prevent it from coming up. Make sure that you have
installed the wireless-tools package.

[1]
http://newbiedoc.berlios.de/wiki/How...e_command_line
--
Chris.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Kamaraju S Kusumanchi wrote:
> Using Debian stable (Etch), 2.6.18-4-686 kernel on Debian Dell Inspiron
> e1505. The wireless card (from lshw output is)
>
[...]
>
> But I dont know how to prevent the automatic configuring of this wireless
> device. I do not want to remove dhclient since it is essential when I do
> want to bring up eth2.
>

Have a look at section 8 of the NewbieDOC article - configure the network card
interface using the command line [1]. Comment out your non-wireless card in
/etc/network/interfaces to prevent it from coming up. Make sure that you have
installed the wireless-tools package.

[1]
http://newbiedoc.berlios.de/wiki/How...e_command_line
--
Chris.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Chris Lale wrote:

> Kamaraju S Kusumanchi wrote:
>> Using Debian stable (Etch), 2.6.18-4-686 kernel on Debian Dell Inspiron
>> e1505. The wireless card (from lshw output is)
>>
> [...]
>>
>> But I dont know how to prevent the automatic configuring of this wireless
>> device. I do not want to remove dhclient since it is essential when I do
>> want to bring up eth2.
>>
>
> Have a look at section 8 of the NewbieDOC article - configure the network
> card interface using the command line [1]. Comment out your non-wireless
> card in /etc/network/interfaces to prevent it from coming up. Make sure
> that you have installed the wireless-tools package.
>

I mentioned this in my original post. I will say it agin. Even after the
stanza specific to wireless card is commented out, and even after doing

sudo ifconfig eth2 down

the wireless card (eth2) keeps coming up.

raju
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tue, 7 Aug 2007, Kamaraju S Kusumanchi wrote:

> Using Debian stable (Etch), 2.6.18-4-686 kernel on Debian Dell Inspiron
> e1505. The wireless card (from lshw output is)
>
>
> The relevant stanza in /etc/network/interfaces is
>
> # allow-hotplug eth2
> # auto eth2
> # iface eth2 inet dhcp
> # wireless-essid SomeThing
> # wireless-mode Managed
>
> I commented out this stanza and did
>
> $sudo ifconfig eth2 down
>
> Even after that, eth2 interface comes up after some time for no reason. I
> believe it is due to dhclient, since I see messages like the following
> in /var/log/syslog
>

Did you do a /etc/init.d/networking restart after commenting that out?
Interfaces shouldn't just come up by themselves. Also it's highly unlikely
that it's dhcpclient bringing the interface up. All you would really need
to do is leave the allow-hotplug and auto parts commented out, then you
can ifup eth2 , ifdown eth2 when you want.


-+-
8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Kamaraju S Kusumanchi wrote:
> I mentioned this in my original post. I will say it agin. Even after the
> stanza specific to wireless card is commented out, and even after doing
>
> sudo ifconfig eth2 down

Suggestion: Uncomment the eth2 stanza, 'sudo ifdown eth2', comment out
the stanza. All should be as you desire it to be then.

Alternatively kill all running dhclient processes and clean up the
state files.

> the wireless card (eth2) keeps coming up.

I believe that because ifupdown brought the interface up before you
commented it out that it left dhclient running with the previous
configuration. Bringing the interface down using ifdown will stop
those daemons and clean up the state files. Then since the interface
is commented out it shouldn't be brought up again.

Bob


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org