Potato networking
Well, I've done a complete clean installation of potato from the five floppy images over a cable connection. Thanks for all the help. I'm in the process of recompiling my kernel to enable IP Masq, but I have another problem. I cannot get my computer to use more than one interface at a time with potato's interface setup. I've read the interfaces manpage, and that helped me to create this /etc/network/interfaces file: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface iface lo inet loopback # The first network card iface eth0 inet dhcp # The second network card iface eth1 inet static address 172.16.1.1 netmask 255.255.255.0 broadcast 172.16.1.255 network 172.16.1.0 gateway 172.16.1.1 I can use ifup for only one of my ethernet interfaces at a time. If both are running, I can't ping anything, either local (eth1) or non-local (eth0). I have to have dhcpcd runnning to send this, and ifconfig -a shows: eth0 Link encap:Ethernet HWaddr 00:A0:C9:91:19:B1 inet addr:24.124.60.7 Bcast:255.255.255.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:34073 errors:0 dropped:0 overruns:0 frame:0 TX packets:18195 errors:0 dropped:0 overruns:0 carrier:0 collisions:4 txqueuelen:100 Interrupt:10 Base address:0xc000 eth1 Link encap:Ethernet HWaddr 00:40:95:42:55:3B inet addr:172.16.1.1 Bcast:172.16.1.255 Mask:255.255.255.0 BROADCAST MTU:1500 Metric:1 RX packets:12 errors:0 dropped:0 overruns:0 frame:0 TX packets:59 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Interrupt:11 Base address:0xe800 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 LOOPBACK MTU:3924 Metric:1 RX packets:17 errors:0 dropped:0 overruns:0 frame:0 TX packets:17 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 Thanks for any suggestions, once again. I promised my wife I'd have the network back up and online this evening. ;-) John
RE: Potato networking
-Original Message- From: John Reinke [mailto:[EMAIL PROTECTED] Sent: Sunday, August 13, 2000 12:38 AM To: debian-user@lists.debian.org Subject: Potato networking Well, I've done a complete clean installation of potato from the five floppy images over a cable connection. Thanks for all the help. I'm in the process of recompiling my kernel to enable IP Masq, but I have another problem. I cannot get my computer to use more than one interface at a time with potato's interface setup. snip My multihomed setup (similar to yours) didn't work until I removed pump and substituted dhcp-client. This seem to be a pump bug. whine I filed this as #64092 but nobody seems to care /whine Christian
Re: Potato networking
On Sat, Aug 12, 2000 at 05:38:15PM -0500, John Reinke wrote: Well, I've done a complete clean installation of potato from the five floppy images over a cable connection. Thanks for all the help. I'm in the process of recompiling my kernel to enable IP Masq, but I have another problem. I cannot get my computer to use more than one interface at a time with potato's interface setup. I've read the interfaces manpage, and that helped me to create this /etc/network/interfaces file: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface iface lo inet loopback # The first network card iface eth0 inet dhcp # The second network card iface eth1 inet static address 172.16.1.1 netmask 255.255.255.0 broadcast 172.16.1.255 network 172.16.1.0 gateway 172.16.1.1 I can use ifup for only one of my ethernet interfaces at a time. If both are running, I can't ping anything, either local (eth1) or non-local (eth0). I have to have dhcpcd runnning to send this, and ifconfig -a shows: Remove the 'gateway' line for eth1. -- Brian Moore | Of course vi is God's editor. Sysadmin, C/Perl Hacker | If He used Emacs, He'd still be waiting Usenet Vandal | for it to load on the seventh day. Netscum, Bane of Elves.
Re: Potato networking
On Sun, May 07, 2000 at 11:48:24AM -0700, [EMAIL PROTECTED] wrote: Ethan == Ethan Benson [EMAIL PROTECTED] writes: Ethan you still can do it the old way, just comment out everything in Ethan /etc/networking/interfaces (or maybe just delete it) and add Ethan you own /etc/init.d/network script using update-rc.d to add the Ethan links. It seems you can just edit /etc/network/interfaces (format documented in TFM) to use static for the relevant stanzas; this feels like a more potatoesque way of doing it. `if it's not broke, don't fix it' is the axim i a going by on my current systems. when i install a new potato system ill revisit that setup but for now my networking is fine and i see no reason to `fix' it. ;-) -- Ethan Benson http://www.alaska.net/~erbenson/ pgp9iqsYNPVIP.pgp Description: PGP signature
Re: Potato networking
Ethan == Ethan Benson [EMAIL PROTECTED] writes: Ethan you still can do it the old way, just comment out everything in Ethan /etc/networking/interfaces (or maybe just delete it) and add Ethan you own /etc/init.d/network script using update-rc.d to add the Ethan links. It seems you can just edit /etc/network/interfaces (format documented in TFM) to use static for the relevant stanzas; this feels like a more potatoesque way of doing it. -- Ian Zimmerman, Oakland, California, U.S.A. In his own soul a man bears the source from which he draws all his sorrows and his joys. Sophocles.
Re: Potato networking
On Sun, Apr 30, 2000 at 06:24:34PM -0400, Alec Smith wrote: I just installed Potato using the Potato boot disks, and found there's no more /etc/init.d/network for setting things up. As it stands now, the machine is using DHCP to get settings. It appears this also overwrites custom changes to /etc/resolv.conf at the very least. Does someone have a sample of /etc/networking/interfaces which allows for static configuration similar to what used to be done in /etc/init.d/network? If I were in charge of Debian, I'd go back to doing this the old way you still can do it the old way, just comment out everything in /etc/networking/interfaces (or maybe just delete it) and add you own /etc/init.d/network script using update-rc.d to add the links. i installed potato before this was changed and never `converted' all is working fine for me. the reason it was changed was to allow for easier upgrading of the network configuration, this is not very easy with the flat script so for example when you upgrade a slink system to kernel 2.2 you start getting SIOCCATTR (something like that) errors at boot because the route command requires different arguments. (that and you don't really need the route command anymore on 2.2, except for the localhost route which never gets created (not that it seems to matter, i just prefer to see a route for localhost)) at the risk of joey throwing something at me... ;-) i still prefer the old way. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpe0jXpbs0X4.pgp Description: PGP signature
Potato networking
I just installed Potato using the Potato boot disks, and found there's no more /etc/init.d/network for setting things up. As it stands now, the machine is using DHCP to get settings. It appears this also overwrites custom changes to /etc/resolv.conf at the very least. Does someone have a sample of /etc/networking/interfaces which allows for static configuration similar to what used to be done in /etc/init.d/network? If I were in charge of Debian, I'd go back to doing this the old way Thanks
Potato networking problem
I have potato 2.2.13 running on an AMD Athlon box. Looks good, but the network interface dies under pressure. Typically, an ftp of a large file from a remote machine to this new box will kill the network: an ifdown/ifup will kickstart it again. The card is a Netgear 310tx, tulip driver. Any suggestions? __ Greg Quinn Informatics Specialist CAMBIA - Center for the Application of Molecular Biology to International Agriculture http://cambia.org Canberra, Australia 61 2 62464506
Re: Potato networking problem
George Bonser [EMAIL PROTECTED] writes: On Wed, 5 Apr 2000, Greg Quinn wrote: I have potato 2.2.13 running on an AMD Athlon box. Looks good, but the network interface dies under pressure. Typically, an ftp of a large file from a remote machine to this new box will kill the network: an ifdown/ifup will kickstart it again. The card is a Netgear 310tx, tulip driver. Any suggestions? Where did you get the driver? Try the latest tulip driver from Alan Cox's 2.2.15pre17 tree. There have been several changes to it. Or wait a couple of days ... 2.2.15 should be released RSN. I can send you the driver source for the new one if you are interested. Have a look at http://cesdis.gsfc.nasa.gov/linux/drivers/tulip.html This page belongs to the guy that develops the tulip driver (at least the last time I checked he was still the developer) and has the latest tulip.c Gary
