Tested on Mageia 2 beta 2 for x86_64. I have a problem with the Ethernet configuration: When I configure a new Ethernet connection and I choose "Manual Setup" to assign a fixed IP to my Laptop , I have a very very slow connection, almost impossible to use. So if I select "Automatic assignment of IP address (BOOTP / DHCP)", there is good, no problems, and the connection speed is really correct. To reproducte : ->> CCM ->> Network & Internet ->> Set Up a new network interface (LAN,ISDN,ADSL,...) ->> Wired (Ethernet) ->> eth0 : nVidia Corporation MCP51 Ethernet Controller ->> Manual configuration ->> IP adress : 192.168.1.119 Netmask : 255.255.255.0 Gateway : 192.168.1.1 DNS server 1: 192.168.1.1 DNS server 2: 192.168.1.2 Host name : david.david ->> Allow users to manage the connection Start the connection at boot Enable traffic accounting On Mageia release 1 (Official) for x86_64 (and also Mandriva) with the same configuration there is no problem, the connection speed is correct and timely. ---------------------------------------------------- Yet another problem (yet never seen on Mageia 1): In the configuration described above, if I chose the option "Allow Interface To Be controlled by Network Manager"and indeed the ethernet connection does not work at all.
and if you use ifconfig I guess it works ? can you paste the output of lspcidrake -v ? (maybe we can found something somewhere)
CC: (none) => mageia
Summary: Ethernet connection very slow after a Manual Setup by CCM. => Ethernet connection very slow after a Manual Setup by drakconnect.Source RPM: (none) => drakx-net
$ lspcidrake -v tifm_7xx1 : Texas Instruments|5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD) [STORAGE_OTHER] (vendor:104c device:803b subv:1025 subd:0112) yenta_socket : Texas Instruments|PCIxx12 Cardbus Controller [BRIDGE_CARDBUS] (vendor:104c device:8039 subv:5400 subd:0000) ath5k : Atheros Communications Inc.|AR2413/AR2414 Wireless Network Adapter [AR5002G(S) 802.11bg] [NETWORK_ETHERNET] (vendor:168c device:001a subv:1468 subd:0418) (rev: 01) Card:NVIDIA GeForce 6100 to GeForce 360: nVidia Corporation|G72M [Quadro NVS 110M/GeForce Go 7300] [DISPLAY_VGA] (vendor:10de device:01d7 subv:1025 subd:0112) (rev: a1) k8temp : Advanced Micro Devices [AMD]|K8 [Athlon64/Opteron] Miscellaneous Control [BRIDGE_HOST] (vendor:1022 device:1103) amd64_edac_mod : Advanced Micro Devices [AMD]|K8 [Athlon64/Opteron] DRAM Controller [BRIDGE_HOST] (vendor:1022 device:1102) unknown : Advanced Micro Devices [AMD]|K8 [Athlon64/Opteron] Address Map [BRIDGE_HOST] (vendor:1022 device:1101) unknown : Advanced Micro Devices [AMD]|K8 [Athlon64/Opteron] HyperTransport Technology Configuration [BRIDGE_HOST] (vendor:1022 device:1100) forcedeth : nVidia Corporation|MCP51 Ethernet Controller [BRIDGE_OTHER] (vendor:10de device:0269 subv:1025 subd:0112) (rev: a3) snd_hda_intel : nVidia Corporation|MCP51 High Definition Audio (vendor:10de device:026c subv:1025 subd:0112) (rev: a2) unknown : nVidia Corporation|MCP51 PCI Bridge [BRIDGE_PCI] (vendor:10de device:026f) (rev: a2) sata_nv : nVidia Corporation|MCP51 Serial ATA Controller [STORAGE_IDE] (vendor:10de device:0266 subv:1025 subd:0112) (rev: f1) pata_amd : nVidia Corporation|MCP51 IDE [STORAGE_IDE] (vendor:10de device:0265 subv:1025 subd:0112) (rev: f1) ehci_hcd : nVidia Corporation|MCP51 USB Controller [SERIAL_USB] (vendor:10de device:026e subv:1025 subd:0112) (rev: a3) ohci_hcd : nVidia Corporation|MCP51 USB Controller [SERIAL_USB] (vendor:10de device:026d subv:1025 subd:0112) (rev: a3) unknown : nVidia Corporation|MCP51 PMU [PROCESSOR_CO] (vendor:10de device:0271 subv:1025 subd:0112) (rev: a3) nv_tco : nVidia Corporation|MCP51 SMBus [SERIAL_SMBUS] (vendor:10de device:0264 subv:1025 subd:0112) (rev: a3) unknown : nVidia Corporation|MCP51 LPC Bridge [BRIDGE_ISA] (vendor:10de device:0260 subv:1025 subd:0112) (rev: a3) unknown : nVidia Corporation|MCP51 Host Bridge [MEMORY_RAM] (vendor:10de device:0270 subv:1025 subd:0112) (rev: a2) shpchp : nVidia Corporation|C51 PCI Express Bridge [BRIDGE_PCI] (vendor:10de device:02fb) (rev: a1) shpchp : nVidia Corporation|C51 PCI Express Bridge [BRIDGE_PCI] (vendor:10de device:02fd) (rev: a1) shpchp : nVidia Corporation|C51 PCI Express Bridge [BRIDGE_PCI] (vendor:10de device:02fc) (rev: a1) unknown : nVidia Corporation|C51 Memory Controller 2 [MEMORY_RAM] (vendor:10de device:027e subv:1025 subd:0112) (rev: a2) unknown : nVidia Corporation|C51 Memory Controller 3 [MEMORY_RAM] (vendor:10de device:027f subv:1025 subd:0112) (rev: a2) unknown : nVidia Corporation|C51 Host Bridge [MEMORY_RAM] (vendor:10de device:02ff subv:1025 subd:0112) (rev: a2) unknown : nVidia Corporation|C51 Memory Controller 4 [MEMORY_RAM] (vendor:10de device:02f9 subv:1025 subd:0112) (rev: a2) unknown : nVidia Corporation|C51 Memory Controller 5 [MEMORY_RAM] (vendor:10de device:02f8 subv:1025 subd:0112) (rev: a2) unknown : nVidia Corporation|C51 Memory Controller 1 [MEMORY_RAM] (vendor:10de device:02fe subv:1025 subd:0112) (rev: a2) unknown : nVidia Corporation|C51 Memory Controller 0 [MEMORY_RAM] (vendor:10de device:02fa subv:1025 subd:0112) (rev: a2) unknown : nVidia Corporation|C51 Host Bridge [MEMORY_RAM] (vendor:10de device:02f7 subv:1025 subd:0112) (rev: a2)
Ifconfig with "Automatic assignment of IP address (BOOTP / DHCP)" : # ifconfig eth0 Link encap:Ethernet HWaddr 00:16:D3:54:E3:4F inet adr:192.168.1.13 Bcast:192.168.1.255 Masque:255.255.255.0 adr inet6: fe80::216:d3ff:fe54:e34f/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9173 errors:0 dropped:0 overruns:0 frame:0 TX packets:7800 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 RX bytes:8534545 (8.1 MiB) TX bytes:1751715 (1.6 MiB) Interruption:20 lo Link encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:Hôte UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:97 errors:0 dropped:0 overruns:0 frame:0 TX packets:97 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:6862 (6.7 KiB) TX bytes:6862 (6.7 KiB) wlan0 Link encap:Ethernet HWaddr 00:19:7E:02:1D:2C 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 lg file transmission:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) ----------------------------------------------------------------------- Ifconfig with "Manual Setup" : # ifconfig eth0 Link encap:Ethernet HWaddr 00:16:D3:54:E3:4F inet adr:192.168.1.119 Bcast:192.168.1.255 Masque:255.255.255.0 adr inet6: fe80::216:d3ff:fe54:e34f/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10815 errors:0 dropped:0 overruns:0 frame:0 TX packets:9444 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 RX bytes:9509681 (9.0 MiB) TX bytes:1947413 (1.8 MiB) Interruption:20 lo Link encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:Hôte UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:208 errors:0 dropped:0 overruns:0 frame:0 TX packets:208 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:15398 (15.0 KiB) TX bytes:15398 (15.0 KiB) wlan0 Link encap:Ethernet HWaddr 00:19:7E:02:1D:2C 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 lg file transmission:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
When adding the output of a command to a bug report, where the output is more than approx. 10 lines, please put the output into a file, and then add that file as a plain/text attachment to make it easier to read. Any chance you have another system connected to the router that is also assigned to 192.168.1.119 causing an ip address conflict?
CC: (none) => davidwhodgins
Oh sorry Dave for the output , No I have not conflict with IP address 192.168.1.119 because it only on the router I tried with 192.168.1.35 or 192.168.1.72 or 192.168.1.98 and always the same result. When I use Windows Vista the IP address is 192.168.1.119 = no problem and same config When I use Mageia 1 the IP adress is 192.168.1.119 = no problem and same config Just on Mageia 2 is this problem.
What are the contents of /etc/resolv.conf, with both setups? Also, what type of system is assigned 192.168.1.2? Just trying to look at things that are affected by the ip address change, which is the only real difference here.
(In reply to comment #6) > What are the contents of /etc/resolv.conf, with both setups? With "Automatic assignment of IP address (BOOTP / DHCP)": IP 192.168.1.13 $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.1.1 search home __________________________________________________________ With "Manual Setup" : IP 192.168.1.119 $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 192.168.1.1 nameserver 192.168.1.2 > Also, what type of system is assigned 192.168.1.2? Nothing DHCP assigns address from 192.168.1.10 to 192.168.1.50
If 192.168.1.2 is not running a name server, then why is it being specified as the second dns server? Try replacing it with 8.8.8.8, which is a google public dns server.
(In reply to comment #8) > > Try replacing it with 8.8.8.8, which is a google public dns server. No I have always the same problem. In fact, it's a bit more complicated than I thought : I just realized that was affected only some browsers with IP 192.168.1.119 -With Firefox browser ->> web surfing is very slow but not the speed of file download (580ko/s ,this is the maximum of my bandwidth) -With Chromium browser ->> web surfing is Ok (fast) and the speed of file download too.(580ko/s) -With Konversation ->> connecting to the server freenode is slow. -With urpmi ->> it is not affected ,the speed download is good (580ko/s) -With konqueror ->> web surfing is very slow but not the speed of file download ------------------------------------------------------- And with "Automatic assignment of IP address (BOOTP / DHCP)": IP 192.168.1.13 -With Firefox ->> web surfing is good (fast) and speed of file download is good too(580ko/s) -With Chromium browser ->> web surfing is Ok (fast) and speed of file download too. -With Konversation ->> connecting to the server freenode is good (fast). -With konqueror ->> web surfing is good (fast) and the speed of file download too. -With urpmi ->> it is not affected ,the speed download is good (580ko/s)
That sounds to me like a problem with ipv6 failing. Some browsers wait for ipv6 dns lookups to fail, before trying ipv4. In the configuration for eth0, select the advanced dialog and unselect the ipv6 option.
(In reply to comment #10) > That sounds to me like a problem with ipv6 failing. Some browsers wait > for ipv6 dns lookups to fail, before trying ipv4. > > In the configuration for eth0, select the advanced dialog and unselect > the ipv6 option. The ipv6 option is unchecked (and always was) but the problem remains the same. By cons I found the error on my configuration : on my Orange Livebox 2 the primary DNS server is 216.146.35.35 and the auxiliary DNS server is 216.146.36.36 ->> Manual configuration ->> IP adress : 192.168.1.119 Netmask : 255.255.255.0 Gateway : 192.168.1.1 DNS server 1: 216.146.35.35 DNS server 2: 216.146.36.36 Host name : david.david With this configuration, I have no slowdown and no problem on web browser it's Ok for me. You can close this bug.
Ok. Closing the bug as invalid, since it's just a dns configuration issue.
Status: NEW => RESOLVEDResolution: (none) => INVALID
I reopen this bug because I have new information rather interresting: Many French users have encountered a similar problem,and we have come to the conclusion that the bug is due to the new Livebox (Orange) the Livebox 2. I've solved the problem by replacing the DNS server but for others it does not work. By cons, for others a solution was found: Add the line "install ipv6 /bin/true" at the end of /etc/modprobe.conf file. Apparently this bug was already known with Mandriva 2009. What do you think? Is it really a problem? Is there a solution? http://www.mageialinux-online.org/forum/topic-12501+probleme-reseau-avec-firefox.php http://www.mageialinux-online.org/forum/topic-12480+probleme-reseau-ethernet-mageia-2-rc.php
Status: RESOLVED => REOPENEDResolution: INVALID => (none)
Assignee: bugsquad => mageia
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
After a new fresh install for Mageia 2 with the Mageia-2-x86_64-DVD, I can confirm that the bug is always present for me. See as Comment 13 .
Hardware: x86_64 => AllVersion: Cauldron => 2
Keywords: NEEDINFO => (none)
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: REOPENED => RESOLVEDResolution: (none) => OLD