[gentoo-user] problems with ifplugd

[gentoo-user] problems with ifplugd

[Sven Köhler]

[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]

Hi,

does anybody use ifplugd successfully?

Assume a cable is inserted. Then i perform the following commands:

- ifconfig eth0 up
- mii-tool eth0 => works, shows infos about the link
- ifconfig eth0 down
- mii-tool eth0 => shows "no-link" even though cable is inserted!

The problem:

So assume i unplug the cable. ifplugd calls "/etc/init.d/net.eth0 stop"
and the interface goes down (same as ifconfig eth0 down above)
Now ifplugd polls the interface and waits until the a cable is inserted,
but this will never be detected, because mii-tool always reports "no-link".

So i assume that ifplugd was written to detect the when the cable is
reinserted - but in my case, it can't.

Is that a proper behaviour? I mean: is mii-tool supposed to report the
link infos when a cable is inserted and the interface is down?
I may have found a bug in the network-driver (bcm4400).

Can you perform those three steps with your network card?
- ifconfig eth0 up
- ifconfig eth0 down
- mii-tool eth0

What does the mii-tool report?


Greetings
  Sven


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

Re: [gentoo-user] problems with ifplugd

[Richard Fish]

On 4/1/06, Sven Köhler <skoehler@upb.de> wrote:
> Hi,
>
> does anybody use ifplugd successfully?

I have had it working with my last 3 laptops.

Probably what is happening is that the interface needs to be "up" in
order for mii-tool (or ethtool) to work correctly.

Try adding the following to /etc/conf.d/net:

postdown() {
        test "${IFACE}" = "eth0" && /sbin/ifconfig eth0 0.0.0.0 up
        return 0
}

This will make sure that when the interface is brought down by the
init script, that it is really kept up, but with no address.

> I may have found a bug in the network-driver (bcm4400).

I have this same driver, although I prefer ethtool:

>
> Can you perform those three steps with your network card?
> - ifconfig eth0 up
> - ifconfig eth0 down
> - mii-tool eth0

No, the interface needs to be up for mii stuff to work.

But as proof that it works:

Without cable:
carcharias rjf # ifconfig eth0 ; ethtool eth0
eth0      Link encap:Ethernet  HWaddr 00:14:22:EA:37:60
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:89 errors:1 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6756 (6.5 Kb)  TX bytes:948 (948.0 b)
          Interrupt:177

Settings for eth0:
        Supported ports: [ MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised auto-negotiation: No
        Speed: 10Mb/s
        Duplex: Half
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Current message level: 0x000000ff (255)
        Link detected: no

Plugging in a cable:
carcharias rjf # ifconfig eth0 ; ethtool eth0
eth0      Link encap:Ethernet  HWaddr 00:14:22:EA:37:60
          inet addr:192.168.2.101  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:96 errors:1 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8264 (8.0 Kb)  TX bytes:1896 (1.8 Kb)
          Interrupt:177

Settings for eth0:
        Supported ports: [ MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised auto-negotiation: No
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Current message level: 0x000000ff (255)
        Link detected: yes

Removing the cable:
carcharias rjf # ifconfig eth0 ; ethtool eth0
eth0      Link encap:Ethernet  HWaddr 00:14:22:EA:37:60
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:98 errors:1 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8392 (8.1 Kb)  TX bytes:1896 (1.8 Kb)
          Interrupt:177

Settings for eth0:
        Supported ports: [ MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
        Advertised auto-negotiation: No
        Speed: 10Mb/s
        Duplex: Half
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Current message level: 0x000000ff (255)
        Link detected: no

-Richard

-- 
gentoo-user@gentoo.org mailing list

[gentoo-user] Re: problems with ifplugd

[Sven Köhler]

[-- Attachment #1: Type: text/plain, Size: 624 bytes --]

> Try adding the following to /etc/conf.d/net:
> 
> postdown() {
>         test "${IFACE}" = "eth0" && /sbin/ifconfig eth0 0.0.0.0 up
>         return 0
> }

Thank you. That was a big help, but somehow disappointing.

I would rather like, if ifplugd would automatically do the "ifconfig up"
so that no configuration tweaks are needed.

Of course, i also got to put the interface in the "up" state on boot,
because i don't want to put net.eth0 in the default-runlevel for the
case where there is no cable plugged in ...

Therefor, at the moment, i also do a "ifconfig eth0 up" in
/etc/conf.d/local.start.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

[gentoo-user] Re: problems with ifplugd

[Sven Köhler]

[-- Attachment #1: Type: text/plain, Size: 189 bytes --]

> No, the interface needs to be up for mii stuff to work.

Well, the proper sollution is: set AUTO="yes" in /etc/conf.d/ifplugd,
and ifplugd sets the interface to "up" automatically.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

Re: [gentoo-user] Re: problems with ifplugd

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]

On Sun, 02 Apr 2006 20:47:18 +0200, Sven Köhler wrote:

> I would rather like, if ifplugd would automatically do the "ifconfig up"
> so that no configuration tweaks are needed.
> 
> Of course, i also got to put the interface in the "up" state on boot,
> because i don't want to put net.eth0 in the default-runlevel for the
> case where there is no cable plugged in ...

That's what you're doing wrong. The net.eth* scripts will detect ifplugd
and use it. Put net.eth0 in the default runlevel. there is no
configuration to do, it "just works" [tm]. I have my laptop set up like
this, even though it usually starts up with no network cable connected

# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0D:93:3C:76:26
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:41 Base address:0xf000

eth1      Link encap:Ethernet  HWaddr 00:0D:93:EF:F2:C0
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:188558 errors:0 dropped:0 overruns:0 frame:0
          TX packets:124422 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:106398782 (101.4 Mb)  TX bytes:40234605 (38.3 Mb)
          Interrupt:52 Base address:0x4000

eth0 is the wired interface. The only configuration I have down is
edit the postup function on conf.d/net to bring down/up eth1 (the
wireless interface) when eth0 comes up/down.


-- 
Neil Bothwick

Okay, I pulled the pin. Now what? Hey, where are you going?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

[gentoo-user] X-server does not start with nvidia TNT2

[Ondra Zahradnik]

Hello,
please help with this problem.
I have nVidia TNT2, emerged nvidia-kernel-1.0.6629-r5 and
nvidia-glx-1.0.6629-r5 and followed up instructions in Gentoo Linux nVidia
Guide. Module loads successfuly to kernel but X does not start. 
"glxinfo" output is like:
glxinfo: error while loading shared libraries: libnvidia-tls.so.1: cannot
handle TLS data

I tried NVmakedevices.sh, than the nVidia splash screen occurs but X
server does not start because it was unable to load GLX with error
mentioned before.

thank you
Ondra

xorg.conf relevant sections are:
Section "Module"
 #Load "dri"
 Load "glx"

Section "Device"
 Identifier "Card0"
 Driver "nvidia"
 VendorName "nVidia Corporation"
 BoardName "NV5 [RIVA TNT2/TNT2 Pro]"
 BusID "PCI:1:0:0"
 VideoRam 32768

Section "Screen"
 Identifier "Screen0"
 Device "Card0"
 Monitor "Monitor0"
 DefaultDepth 16 

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: problems with ifplugd

[Sergio Polini]

Neil Bothwick:
> On Sun, 02 Apr 2006 20:47:18 +0200, Sven Köhler wrote:
> > I would rather like, if ifplugd would automatically do the
> > "ifconfig up" so that no configuration tweaks are needed.
> >
> > Of course, i also got to put the interface in the "up" state on
> > boot, because i don't want to put net.eth0 in the
> > default-runlevel for the case where there is no cable plugged in
> > ...
>
> That's what you're doing wrong.

Well... what is wrong?
I think that putting the interface in the "up" state on boot is wrong, 
but perhaps removing net.eth0 from the default runlevel is not, even 
if there is a cable plugged in.
I mean that net.eth0 is executed by /etc/iflugd/ifplugd.action.
At least, this is how my laptop is working ;-)
Is there anything wrong with this setting?

Sergio

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: problems with ifplugd

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]

On Mon, 3 Apr 2006 20:25:40 +0200, Sergio Polini wrote:

> > > Of course, i also got to put the interface in the "up" state on
> > > boot, because i don't want to put net.eth0 in the
> > > default-runlevel for the case where there is no cable plugged in
> > > ...
> >
> > That's what you're doing wrong.
> 
> Well... what is wrong?
> I think that putting the interface in the "up" state on boot is wrong, 

It is not wrong.

> but perhaps removing net.eth0 from the default runlevel is not, even 

That is wrong too.

> if there is a cable plugged in.
> I mean that net.eth0 is executed by /etc/iflugd/ifplugd.action.
> At least, this is how my laptop is working ;-)
> Is there anything wrong with this setting?

Yes, it's all the wrong way round. read the comments
in /etc/conf.d/net.example. Forget about running ifplugd, just put
net.eth0 in your default runlevel. The Gentoo rc scripts will take car
of all the ifplugd stuff.


-- 
Neil Bothwick

When you choke a smurf, what color does it turn?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

[gentoo-user] Re: problems with ifplugd

[Sven Köhler]

[-- Attachment #1: Type: text/plain, Size: 722 bytes --]

> Well... what is wrong?
> I think that putting the interface in the "up" state on boot is wrong, 
> but perhaps removing net.eth0 from the default runlevel is not, even 
> if there is a cable plugged in.

Saying AUTO=yes in /etc/conf.d/ifplugd is one way to keep the interface
up - and at least for now, it's my preferred way.
I don't see, why should write "dirty" hacks like the postdown()-thing in
/etc/conf.d/net to keep the interface up.

> I mean that net.eth0 is executed by /etc/iflugd/ifplugd.action.

Yes, it is. And if a start ifplugd on boot, and if it puts the interface
in "up" state, and if it then executes "net.eth0 start", then i can't
think of anything that should be wrong about it.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

[gentoo-user] Re: problems with ifplugd

[Sven Köhler]

[-- Attachment #1: Type: text/plain, Size: 589 bytes --]

>> Of course, i also got to put the interface in the "up" state on boot,
>> because i don't want to put net.eth0 in the default-runlevel for the
>> case where there is no cable plugged in ...
> 
> That's what you're doing wrong. The net.eth* scripts will detect ifplugd
> and use it. Put net.eth0 in the default runlevel. there is no
> configuration to do, it "just works" [tm]. I have my laptop set up like
> this, even though it usually starts up with no network cable connected

net.eth0 detects ifplugd? Are you sure?
Do i need to set anything special in /etc/conf.d/net?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

Re: [gentoo-user] Re: problems with ifplugd

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 723 bytes --]

On Mon, 03 Apr 2006 21:56:40 +0200, Sven Köhler wrote:

> Saying AUTO=yes in /etc/conf.d/ifplugd is one way to keep the interface
> up - and at least for now, it's my preferred way.
> I don't see, why should write "dirty" hacks like the postdown()-thing in
> /etc/conf.d/net to keep the interface up.

There are no hacks and no need to use postdown(). As is says
in /etc/conf.d/net.example

# emerge sys-apps/ifplugd
# and you're done :)

I used to have to mess around with setting up ifplugd etc, but there's
absolutely no need to do anything other than emerge it now. The rc
scripts take care of EVERYTHING else.


-- 
Neil Bothwick

The number one cause of computer problems is computer solutions.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

Re: [gentoo-user] Re: problems with ifplugd

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 413 bytes --]

On Mon, 03 Apr 2006 21:57:54 +0200, Sven Köhler wrote:

> net.eth0 detects ifplugd? Are you sure?

Yes. As I said, I've been using it.

> Do i need to set anything special in /etc/conf.d/net?

Yes, read the example config file I mentioned.


-- 
Neil Bothwick

WORM: (n.) acronym for Write Once, Read Mangled. Used to describe a
      normally-functioning computer disk of the very latest design.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

[gentoo-user] Re: problems with ifplugd

[Sven Köhler]

[-- Attachment #1: Type: text/plain, Size: 414 bytes --]

>> net.eth0 detects ifplugd? Are you sure?
> 
> Yes. As I said, I've been using it.
> 
>> Do i need to set anything special in /etc/conf.d/net?
> 
> Yes, read the example config file I mentioned.

Which version baselayout do you have installed?

My version is 1.11.14-r6, and that does not include that support yet -
IMHO. Also my /etc/conf.d/net.example does not contain any hint about
ifplugd :-(


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

Re: [gentoo-user] Re: problems with ifplugd

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 632 bytes --]

On Mon, 03 Apr 2006 23:06:25 +0200, Sven Köhler wrote:

> > Yes, read the example config file I mentioned.
> 
> Which version baselayout do you have installed?
> 
> My version is 1.11.14-r6, and that does not include that support yet -
> IMHO. Also my /etc/conf.d/net.example does not contain any hint about
> ifplugd :-(

I'm using 1.12.0_pre16-r3, but this has been around for a while in the
testing baselayout, probably since the early 1.12.0 releases; definitely
since last year, going by the date my ifplugd config file was last
changed.


-- 
Neil Bothwick

Fasten your seatbelt ... I wanna try something.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 191 bytes --]