Re: possibly found a BUG in NM 3.3.1 cvs 20050112.3
- From: Paul Ionescu <i_p_a_u_l yahoo com>
- To: networkmanager-list gnome org
- Subject: Re: possibly found a BUG in NM 3.3.1 cvs 20050112.3
- Date: Mon, 17 Jan 2005 16:04:58 +0200
Spoke too soon.
Was not pcmcia's fault but hotplug's.
Edited /etc/hotplug/net.agent and put a big "exit" at the top.
On Mon, 17 Jan 2005 05:48:02 -0800, Paul Ionescu wrote:
> Hi Dan,
>
> My card is not set to be configured at boot. But of course cardmgr does
> its part of ifup/ifdown it when hotplugged, I almost forgot it.
> What intrigues me is that cardmgr does it for both static and dhcp, and NM
> is affected only when is static.
> I just put a blank /etc/pcmcia/network instead of default, and now it Just
> Works (TM) :) Thansk for the tip.
> But I think this should be taken care of in more places, not only PCMCIA
> but also USB, maybe hotplug, etc.
>
>
> Paul
>
>
> --- Dan Williams <dcbw redhat com> wrote:
>
>> On Mon, 2005-01-17 at 14:01 +0200, Paul Ionescu wrote:
>> > Hi Dan,
>> >
>> > I have a notebook with 2 wired lan cards, one
>> onboard and one PCMCIA.
>> > Both cards have static IP addresses and static
>> default gateways.
>> > NM is active by default.
>> > If I start the computer with both cards, it
>> behaves as expected, choosing
>> > one card as preferred and using it.
>> > If I start with only the onboard card, then NM
>> detects it and properly
>> > configure the net, and everything is working until
>> I plug the second card
>> > (PCMCIA).
>> > When I plug this PCMCIA card, I loose the default
>> gateway already set up
>> > for the onboard connection. So the primary link is
>> still on onboard card
>> > but I have no more default gw.
>> > If this PCMCIA card is not configured with statics
>> (IP/GW/a.s.o) but with
>> > DHCP, it works just fine.
>>
>> Paul,
>>
>> Are you sure you haven't got something on the system set up to bring up
>> that second device automatically? On fedora core 3, for example you
>> would have to make sure the
>> /etc/sysconfig/network-scripts/ifcfg-eth[x] file doesn't have
>> "ONBOOT=yes", or uncheck the "Activate on boot"
>> checkbox in system-config-network.
>>
>> If your system isn't set to activate these on boot, then its most
>> probably a NetworkManager bug. (remember though that stuff like cardmgr
>> may call ifup/ifdown scripts as well, which don't play well with
>> NetworkManager at all).
>>
>> Dan
>>
>>
>>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - Find what you need with new enhanced search.
> http://info.mail.yahoo.com/mail_250
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]