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 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 cables and configurations. After trying to use drakconnect, a typical error log at /var/log/syslog is listed above. How exactly are you trying to connect to the Internet? - The Compaq Presario 5423 desktop has a static IP on a shared T1 line. I tried to connect the Compaq Presario 5423 directly to the Internet, and also through a Linksys BEFSX41 Firewall/Switch. What is surprising is that on March 18, 2003, and in the several weeks before this date, this computer was able to connect, and was connecting on the Internet using Mandrake 9.1rc2. The connection failed on March 19, 2003. I may have added an additional application which is causing the conflict, but cannot recall any specific applications causing the problem. The Dell C600 laptop was connecting to the Internet through a DSL router. I made a fresh install on the Dell c600 laptop, and from its install it has not been able to connect to the Internet. #route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 #ifconfig eth0 Link encap:Ethernet HWaddr 00:01:03:8C:E0:D9 inet addr:192.168.1.101 Bcast: 192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric:1 RX packets:13050 errors:0 dropped:0 overruns:0 frame:0 TX Packets:6022 errors:0 dropped:0 overruns:0 carrier:0 collisions:4 txqueuelen:100 RX bytes:3832175 (3.6 Mb) TX bytes:723719 (706.7 Kb) Interrupt:11 Base address:0xd400 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:12960 errors:0 overruns:0 frame:0 TX packets:12960 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:802492 (783.6 Kb) TX bytes 802492 (783.6 Kb) #ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.773 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.238 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.212 ms Are you running a firewall? Have you configured a firewall? - On both computers, I have attempted to connect the machines directly to the Internet, and have disabled Mandrake's firewall feature in Mandrake 9.1rc2. I have also tried to connect the computers through Linksys firewall/Switch boxes. Neither connection will work. On March 19, 2002, I brought the Dell laptop to another connection, where I had a computer with Mandrake 9.0 connected to the Internet. I removed the ethernet cable from the computer running 9.0, and plugged it into the laptop running 9.1rc2, and the laptop would not connect to the Internet. I then returned the ethernet cable to the computer running Mandrake 9.0, and that computer was still able to connect to the Internet. Walt Pennington
