[Cooker] [Bug 3452] [ifplugd] Drakconnect fails Internet connection - Internal Network Access Available

2003-09-24 Thread [knocte]
http://qa.mandrakesoft.com/show_bug.cgi?id=3452


[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]




--- Additional Comments From [EMAIL PROTECTED]  2003-24-09 11:32 ---
I am in the same case as Robert Goldman. The line
MII_NOT_SUPPORTED=yes has made my eth0 is working now.

But my case was a little more strange, because if I wanted to ping, the
network was unreachable, and if I wrote two lines (ifconfig ... and
route add...) the connection was OK! This is the behavior I got:

# ping 192.168.0.1
connect: Network is unreachable

# ifconfig eth0 inet 192.168.0.99 netmask 255.255.255.0

# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=1.17 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=255 time=0.691 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=255 time=0.650 ms

--- 192.168.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2008ms
rtt min/avg/max/mdev = 0.650/0.839/1.177/0.240 ms

# ping www.mandrakelinux.com
connect: Network is unreachable

# route add default gw 192.168.0.1

# ping www.mandrakelinux.com
PING www.mandrakelinux.com (80.67.180.164) 56(84) bytes of data.
64 bytes from 80.67.180.164: icmp_seq=1 ttl=47 time=106 ms
64 bytes from 80.67.180.164: icmp_seq=2 ttl=47 time=106 ms
64 bytes from 80.67.180.164: icmp_seq=3 ttl=47 time=103 ms

--- www.mandrakelinux.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 5633ms
rtt min/avg/max/mdev = 103.233/105.372/106.508/1.536 ms

# service network restart
Desactivando interfaz eth0: [  OK  ]
Desactivando interfaz loopback: [  OK  ]
Configurando parĂ¡metros de red: [  OK  ]
Activando interfaz loopback:[  OK  ]
Activando interfaz eth0:[FALLO ]

# ping 192.168.0.1
connect: Network is unreachable

# cat /etc/sysconfig/network
HOSTNAME=maestro
NETWORKING=yes
GATEWAY=192.168.0.1
GATEWAYDEV=eth0

# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO=static
IPADDR=192.168.0.99
NETMASK=255.255.255.0
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
ONBOOT=yes

#tail -15 /var/log/messages
sep 23 20:21:38 maestro su(pam_unix)[5273]: session opened for user root
by (uid=501 euid=0 tty= ruser=knocte rhost=  user=root
Sep 23 20:22:01 maestro CROND[5321]: (root) CMD (
/usr/share/msec/promisc_check.sh)
Sep 23 20:23:00 maestro CROND[5345]: (root) CMD (
/usr/share/msec/promisc_check.sh)
Sep 23 20:24:00 maestro CROND[5355]: (root) CMD (
/usr/share/msec/promisc_check.sh)
Sep 23 20:25:00 maestro CROND[5367]: (root) CMD (
/usr/share/msec/promisc_check.sh)
sep 23 20:25:12 maestro ifdown: RTNETLINK answers: Network is
unreachable
sep 23 20:25:12 maestro network: Desactivando interfaz eth0:  succeeded
Sep 23 20:25:13 maestro ifplugd(eth0)[3610]: Exiting.
sep 23 20:25:14 maestro network: Desactivando interfaz loopback:
succeeded
sep 23 20:25:14 maestro network: Configurando parĂ¡metros de red:
succeeded
sep 23 20:25:16 maestro network: Activando interfaz loopback:  succeeded
Sep 23 20:25:16 maestro ifplugd(eth0)[5945]: Using interface
eth0/00:60:08:5D:B9:DB with driver 3c59x (version: LK1.1.18-ac)
Sep 23 20:25:16 maestro ifplugd(eth0)[5945]: Using detection mode:
SIOCGMIIPHY
Sep 23 20:25:16 maestro ifplugd(eth0)[5945]: ifplugd 0.15 successfully
initialized, link beat not detected.
sep 23 20:25:16 maestro network: Activando interfaz eth0:  failed

So, my network only was working when I typed the manual configuration
with ifconfig and route, but when the system starts the eth0 didn't
work.

Most users would be expected to try this route first, before messing
with a config file for ifplugd.

Well, I don't know if I am a most user, but I am relatively new to
Linux (and my first time installing Mandrake), and I have been
investigating this problem for 2 days, and finally I have found the
solution of MII_NOT_SUPPORTED=yes before messing with the expert
mode.

The version I have installed is Mandrake 9.2 RC2, and one of the things
that avoided me to find information is that, if I go to the menu
Documentation, submenu Help, the help:/khelpcenter/index.html is
launched, with the followin result: The requested help file could not
be found. Check that you have installed the documentation. And I can
answer that, on the installation, I am sure I checked to install the
documentation.

Other thing that happens to me about this is that, if I click on the
link to Documentation placed on the window titled  Welcome to
Mandrake Linux that opens at the beggining of the session, the systems
asks me if I want to install the documentation because it is not
installed on my system. If I answer yes, I have to enter the 

[Cooker] [Bug 3452] [ifplugd] Drakconnect fails Internet connection - Internal Network Access Available

2003-06-30 Thread [bgmilne]
http://qa.mandrakesoft.com/show_bug.cgi?id=3452





--- Additional Comments From [EMAIL PROTECTED]  2003-30-06 14:52 ---
 1.  Improve the documentation.  The documentation for ifcfg does not mention
 MII_NOT_SUPPORTED.  This should change.

See /usr/share/doc/initscripts-7.06/sysconfig.txt

 
 2.  /etc/rc.d/init.d/network currently greps
 /etc/sysconfig/network-scripts/ifcfg-devicename for the above flag.  This
 means that we're violating the announced structure of that file, since we're
 just looking for a key, instead of loading the file and evaluating the
 variables.  This is probably not a good thing.  Can we change how the network
 script checks for this feature?  I realize that loading the ifcfg file might be
 inconvenient, since the network file maps over all interfaces, but still this
 approach is no good.  Perhaps have a command that will load the file and check
 the value of this variable (a la is_wireless_interface)?
 
 3.  Add something to drakconnect to verify that ifplugd will work on an
 interface and deactivate it if not.
 

This can't be done programatically, since in some cases ifplugd will think it
can tell, but it doesn't (ie it reports that the cable is connected when it is
not). There is a blacklist of cards that don't support ifplugd, which actually
should include the card the original poster was using.

 As an aside, I was a little nonplussed to find that removing eth0 from
 ifplugd.conf had no effect on this problem.  I.e., /etc/rc.d/init.d/network and
 ifplugd can actually be in a state where they disagree about whether or not
 ifplugd is responsible for a given interface.  That's probably not a good thing.
 

If the user managed to do this themselves, they should be able to undo it. No
tool changes this file, so it is unlikely that a user would get these files out
of sync without knowing it.

 This may be more than just a normal severity bug, since you have to be
 relatively familiar with the networking scripts to work around it.

I don't agree.

Have you tried to use drakconnect in expert mode? You will see an option
network hotplugging which adds or removes MII_UNSUPPORTED to the config file
for the interface.

Most users would be expected to try this route first, before messing with a
config file for ifplugd.

IMHO, this bug is invalid, unless someone has new insight ...

-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.


--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
Version - Mandrake 9.1rc2

This bug is similar to bug 2088 and 2932.  With two different computers, I can ping 
and access other computers on the network, but cannot connect to the Internet.  The 
appropriate tool for correction is drakconnect.  Mandrake Control Center-Network  
Internet-Connection.  

In /var/log/syslog, when trying to run drakconnect, the log file shows:
network:  Shutting down loopback interface:  succeeded
network: Setting network parameters: succeeded
ifup: RTNETLINK answers: no such device
network: Bringing up loopback interface: succeeded
ifplugd [9073] Warning: Could not get interface address
ifplugd [9073] Using interface eth0/00:01:03:8C:E0:D9 with driver 3c59x LK1.1.18-ac
ifplugd [9073] ETHTOOL_GLINK failed: Operation not supported
ifplugd [9073] Executing '/etc/ifplugd/ifplugd.action eth0 up'.
CROND [9114] (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/grunner)
CROND [9114] (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/gate_news)
dhclient DHCPREQUEST on eth0 to 255.255.255.255 port 67
dhclient DHCPACK from 192.168.1.1
dhclient bout to 192.168.1.101 -- renewal in 32953 seconds
ifplugd [9073] client: Determining IP information for eth0 ... done.
ifplugd [9073] Program executed successfully.
network: Bringing up interface eth0: succeeded
CROND[9216] (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner)
CROND[9231] (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner)
ifplugd [9073] Link beat lost
ifplugd [9073] Executing '/etc/ifplugd/ifplugd.action eth0 down'.
ifplugd [9073] Program executed successfully.


Does it establish a connection at all?  - I have two computers, a laptop and a desktop 
both running Mandrake 9.1rc2.  Yesterday, and for a few weeks, the Compaq Presario 
desktop was connected to the Internet using Mandrake 9.1rc2.  Today the desktop will 
no longer connect to the Internet.  Yesterday, I loaded the laptop running Mandrake 
9.0, with Mandrake 9.1rc2, and the Dell C600 laptop can no longer connect to the 
Internet, although both computers can access, and ping other computers running on an 
internal network.  I was able to connect and use a VNC with the Dell C600 laptop 
running Mandrake 9.1rc2.  This bug is limited to establishing an Internet connection.

In which situation does it fail?  - Currently both my Dell C600 Laptop 

[Cooker] [Bug 3452] [ifplugd] Drakconnect fails Internet connection - Internal Network Access Available

2003-06-27 Thread [robert.p.goldman]
http://qa.mandrakesoft.com/show_bug.cgi?id=3452





--- Additional Comments From [EMAIL PROTECTED]  2003-27-06 19:05 ---
I can confirm this behavior, having also see it on a Mandrake 9.1 machine  Here
are relevant lines from the logs:

Jun 26 22:19:56 jukebox ifplugd[661]: Warning: Could not get interface address. 
Jun 26 22:19:56 jukebox ifplugd[661]: Using interface eth0/00:C0:4F:B2:93:FD
with driver 3c59x LK1.1.18-ac 
Jun 26 22:19:56 jukebox ifplugd[661]: ETHTOOL_GLINK failed: Operation not supported 
Jun 26 22:19:56 jukebox ifplugd[661]: ifplugd 0.13 successfully initialized,
link beat not detected. 
Jun 26 22:19:56 jukebox network: Bringing up interface eth0:  failed 

For me, the solution was to add 

MII_NOT_SUPPORTED=yes

to /etc/sysconfig/network-scripts/ifcfg-eth0

Let me suggest three things that might be done to help this:

1.  Improve the documentation.  The documentation for ifcfg does not mention
MII_NOT_SUPPORTED.  This should change.

2.  /etc/rc.d/init.d/network currently greps
/etc/sysconfig/network-scripts/ifcfg-devicename for the above flag.  This
means that we're violating the announced structure of that file, since we're
just looking for a key, instead of loading the file and evaluating the
variables.  This is probably not a good thing.  Can we change how the network
script checks for this feature?  I realize that loading the ifcfg file might be
inconvenient, since the network file maps over all interfaces, but still this
approach is no good.  Perhaps have a command that will load the file and check
the value of this variable (a la is_wireless_interface)?

3.  Add something to drakconnect to verify that ifplugd will work on an
interface and deactivate it if not.

As an aside, I was a little nonplussed to find that removing eth0 from
ifplugd.conf had no effect on this problem.  I.e., /etc/rc.d/init.d/network and
ifplugd can actually be in a state where they disagree about whether or not
ifplugd is responsible for a given interface.  That's probably not a good thing.

This may be more than just a normal severity bug, since you have to be
relatively familiar with the networking scripts to work around it.

-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.


--- Reminder: ---
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date: 
description: 
Version - Mandrake 9.1rc2

This bug is similar to bug 2088 and 2932.  With two different computers, I can ping 
and access other computers on the network, but cannot connect to the Internet.  The 
appropriate tool for correction is drakconnect.  Mandrake Control Center-Network  
Internet-Connection.  

In /var/log/syslog, when trying to run drakconnect, the log file shows:
network:  Shutting down loopback interface:  succeeded
network: Setting network parameters: succeeded
ifup: RTNETLINK answers: no such device
network: Bringing up loopback interface: succeeded
ifplugd [9073] Warning: Could not get interface address
ifplugd [9073] Using interface eth0/00:01:03:8C:E0:D9 with driver 3c59x LK1.1.18-ac
ifplugd [9073] ETHTOOL_GLINK failed: Operation not supported
ifplugd [9073] Executing '/etc/ifplugd/ifplugd.action eth0 up'.
CROND [9114] (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/grunner)
CROND [9114] (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/gate_news)
dhclient DHCPREQUEST on eth0 to 255.255.255.255 port 67
dhclient DHCPACK from 192.168.1.1
dhclient bout to 192.168.1.101 -- renewal in 32953 seconds
ifplugd [9073] client: Determining IP information for eth0 ... done.
ifplugd [9073] Program executed successfully.
network: Bringing up interface eth0: succeeded
CROND[9216] (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner)
CROND[9231] (mail) CMD (/usr/bin/python -S /var/lib/mailman/cron/qrunner)
ifplugd [9073] Link beat lost
ifplugd [9073] Executing '/etc/ifplugd/ifplugd.action eth0 down'.
ifplugd [9073] Program executed successfully.


Does it establish a connection at all?  - I have two computers, a laptop and a desktop 
both running Mandrake 9.1rc2.  Yesterday, and for a few weeks, the Compaq Presario 
desktop was connected to the Internet using Mandrake 9.1rc2.  Today the desktop will 
no longer connect to the Internet.  Yesterday, I loaded the laptop running Mandrake 
9.0, with Mandrake 9.1rc2, and the Dell C600 laptop can no longer connect to the 
Internet, although both computers can access, and ping other computers running on an 
internal network.  I was able to connect and use a VNC with the Dell C600 laptop 
running Mandrake 9.1rc2.  This bug is limited to establishing an Internet connection.

In which situation does it fail?  - Currently both my Dell C600 Laptop and on the 
Compaq Presario 5423 desktop systems fail on every occasion in trying to connect to 
the Internet.  I have tried at least 10 times on both machines, with a variety of