Re: [Cooker] RC2 and Networking
On Wed, 5 Mar 2003, Charles A Edwards wrote: > > Actually it's 4 the 2 dhcp, tmdns and a lib, don't remember which. > All 4 are installed during Network or if networking is configured manually during > summary. But tmdns really does not have anything to do with dhcp (or dhcpcd vs dhclient) Buchan -- |Registered Linux User #182071-| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
Re: [Cooker] RC2 and Networking
On Wed, 05 Mar 2003 20:27:55 +0200 Buchan Milne <[EMAIL PROTECTED]> wrote: > AFAIK you need 2 instead of dhcpcd, dhcp-common and dhcp-client? Actually it's 4 the 2 dhcp, tmdns and a lib, don't remember which. All 4 are installed during Network or if networking is configured manually during summary. Charles -- "Just think of a computer as hardware you can program." -- Nigel de la Tierre - Mandrake Linux 9.1 on PurpleDragon Kernel- 2.4.21-0.11mdk - pgp0.pgp Description: PGP signature
Re: [Cooker] RC2 and Networking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles A Edwards wrote: > On Wed, 05 Mar 2003 10:59:19 +0200 > Buchan Milne <[EMAIL PROTECTED]> wrote: >>My 9.1rc1 install on my laptop works fine on 2 different networks that >>use dhcp. > > Are you using fixed or dynamic IP? Dynamic on both. Plus the machine I am writing on now runs cooker and seems to be using dhclient just fine (it has a static mapping in our dhcp server, my laptop does not). > > As happens I do know what causes the problem on my system. > /etc/resolv.conf is an empty file > If edited and 'nameserver 192.168.0.1' is added Net access works. > The same is accomplished by installing and running dhcpcd. My only issue on rc1 was that tmdns was not allowing fall-through to the real dns server, so I normally just bumped it (127.0.0.1) to the end of the list of DNS servers. This is supposedly fixed? > > To me the benefit of using dhcpcd is that I only need 1 pkg not the 4 > installed by Network set-up/drakconnect. AFAIK you need 2 instead of dhcpcd, dhcp-common and dhcp-client? > Dhcpcd is also all that was Required and installed in previous Mandrake > installations for this set-up. > I have always just used the defaults ... since 6.1 IIRC. Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+ZkGqrJK6UGDSBKcRAk/MAJ9sds6k0MGAQBPyytUmi4kJoCCvrQCeNLIl DKid04/DGbCN/y6/K1UeNeY= =wlPt -END PGP SIGNATURE-
Re: [Cooker] RC2 and Networking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles A Edwards wrote: > On Wed, 05 Mar 2003 10:59:19 +0200 > Buchan Milne <[EMAIL PROTECTED]> wrote: > > >>Sure, newbies should not need to do this, but last I checked this >>wasn't the newbie list. > > But Newbles are the ones who are going to have no idea what to do. Yes, that is why we test it here. But testing does not help if the tester throws his arms up in the air and says "It does not work". They have to give some info to find out why it does not work. > If they can install another distro;be it RH, SuSE, hell even Evil Linux; > and there LAN can connect to the NET out of the box why should they want > to use Mandrake and have to find out how to fix it. Sorry, I must have missed the bit where I said that only networking experts should use Mandrake. Maybe you can show me where I wrote that? Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+ZkJErJK6UGDSBKcRAujSAJoDsXD7WrVjCoOKdq0A/lw0AsA2tACggoSX viYL1KzJ8nJXsp9Xq1dM8e8= =8NZr -END PGP SIGNATURE-
Re: [Cooker] RC2 and Networking
On Wed, 05 Mar 2003 10:59:19 +0200 Buchan Milne <[EMAIL PROTECTED]> wrote: > Sure, newbies should not need to do this, but last I checked this > wasn't the newbie list. But Newbles are the ones who are going to have no idea what to do. I thought one of the plans was to get more people to use and support Mandrake. If they can install another distro;be it RH, SuSE, hell even Evil Linux; and there LAN can connect to the NET out of the box why should they want to use Mandrake and have to find out how to fix it. > My 9.1rc1 install on my laptop works fine on 2 different networks that > use dhcp. Are you using fixed or dynamic IP? As happens I do know what causes the problem on my system. /etc/resolv.conf is an empty file If edited and 'nameserver 192.168.0.1' is added Net access works. The same is accomplished by installing and running dhcpcd. To me the benefit of using dhcpcd is that I only need 1 pkg not the 4 installed by Network set-up/drakconnect. Dhcpcd is also all that was Required and installed in previous Mandrake installations for this set-up. Charles -- Adler's Distinction: Language is all that separates us from the lower animals, and from the bureaucrats. - Mandrake Linux 9.1 on PurpleDragon Kernel- 2.4.21-0.11mdk - pgp0.pgp Description: PGP signature
Re: [Cooker] RC2 and Networking
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles A Edwards wrote: > Same problem exist in RC2 as in RC1 and all Betas > > Home LAN > 6 systems, 5 connecting to internet though gateway system via dhcp with > each system needing a static IP. > > During clean RC installation/Networking, either automatic or if manually > configured during Summary, all hardware component are detected and > properly configured and the pkgs dhcp-common, dhcp-client, and tmdns > are installed. > > The problem is that this Does Not properly set-up this type system. > Once the new install is booted even though everything appears in order > and drakconnect even tells you that your network is properly configured > No Internet connection is possible. Great bug report. Did you get an IP? (hint: /sbin/ifconfig) Did your resolv.conf get setup right? (hint, cat /etc/resolv.conf) Did your routes get setup right? (hint, /sbin/route) Sure, newbies should not need to do this, but last I checked this wasn't the newbie list. If there really is a bug, you need to track it down. My 9.1rc1 install on my laptop works fine on 2 different networks that use dhcp. And when are we going to have a dhcp client that returns the WINS addresses? Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+ZbxmrJK6UGDSBKcRAn2HAKCSq7zjNpkUWdy45SlFNm83u0/oHACgyzK6 hQDqYxqXg82aPQzPw+rmK8k= =IWBX -END PGP SIGNATURE-
Re: [Cooker] RC2 and Networking
On Tue, 4 Mar 2003 19:59:39 -0500 Greg Meyer <[EMAIL PROTECTED]> wrote: > Be careful, because if you do this, you can no longer use drakconnect. > If > user runs drakconnect after making this change, dhcp-client and > dhcp-common will be reinstalled. It makes no difference. All are still installed on my machine, but none other than dhcpcd is needed. I can remove the others and still access the Net and test drakconnect with each release of drakxtools to see if any fix has been applied. But irregardless of what other pkgs it installs as long as I have dhcpcd installed and running I can access the Net. Drakconnect does not work with this type set-up, I stated so in my orig post and in previous as well as bugzilla reports, testing is the Only reason I would run it again. Charles -- It wasn't that she had a rose in her teeth, exactly. It was more like the rose and the teeth were in the same glass. - Mandrake Linux 9.1 on PurpleDragon Kernel- 2.4.21-0.11mdk - pgp0.pgp Description: PGP signature
Re: [Cooker] RC2 and Networking
On Tuesday 04 March 2003 06:12 pm, Charles A Edwards wrote: > Same problem exist in RC2 as in RC1 and all Betas > > Home LAN > 6 systems, 5 connecting to internet though gateway system via dhcp with > each system needing a static IP. > > During clean RC installation/Networking, either automatic or if manually > configured during Summary, all hardware component are detected and > properly configured and the pkgs dhcp-common, dhcp-client, and tmdns > are installed. > > The problem is that this Does Not properly set-up this type system. > Once the new install is booted even though everything appears in order > and drakconnect even tells you that your network is properly configured > No Internet connection is possible. > > /etc/sysconfig/network > NETWORK=yes > > /etc/host > 127.0.0.1localhost > > You can start editing files galore if you aren't a Newbie, and even have > a clue as to what files to even look for, or if you are a Newbie and > this your first taste of Linux you could and might just say fuck-it and > boot back to Windows where everything works. > > The solution is really quite simple. > For this type of network connection you do not need dhcp-common. > You do not need dhcp-client. > You do not need tmdns. > > You Need dhcpd. > Once installed you need only run > # dhcpcd -d > the system will be assigned a static IP address, in my case it is > 192.168.0.6 for machine #6 on the chain. > On subsequent boots dhcpcd will be auto started during boot. > > /etc/sysconfig/network and /etc/host will not be changed but a new > config file will be present /etc/dhcpc/dhcpcd-eth0.info > > [EMAIL PROTECTED] charles]$ cat /etc/dhcpc/dhcpcd-eth0.info > IPADDR=192.168.0.6 > NETMASK=255.255.255.0 > NETWORK=192.168.0.0 > BROADCAST=192.168.0.255 > GATEWAY=192.168.0.1 > DNS=192.168.0.1 > DHCPSID=192.168.0.1 > DHCPGIADDR=0.0.0.0 > DHCPSIADDR=192.168.0.1 > DHCPCHADDR=00:50:2C:01:64:87 > DHCPSHADDR=00:04:5A:5E:A0:85 > DHCPSNAME='ICS ' > LEASETIME=86400 > RENEWALTIME=43200 > REBINDTIME=75600 > INTERFACE='eth0' > CLASSID='Linux 2.4.21-0.11mdk i686' > CLIENTID=00:50:2C:01:64:87 > > > If the network configuration, this also applies to the stand alone > drakconnect, is not going to be fixed to resolve this issue could there > not at the least be an errata posted that addresses it. > > > Charles Be careful, because if you do this, you can no longer use drakconnect. If user runs drakconnect after making this change, dhcp-client and dhcp-common will be reinstalled. -- Greg
