RE: rc.local in debian (was: Ip Masquerading)
Hello.. I have configured my second interface as you told me (with a few changes) and it's now working fine!!! Thanks a lot for your help to you all!!! Just two more questions.. I don't know if I should place auto on it because the Windows box isn't permanently turned on, so I think that Linux might show up an error message if the connection is up when the Windows box is off, doesn´t it? Just like when I enable my other card when it doesn't have a LAN cable in it. The other thing is that, from the masqueraded PC (the windows box), I can only ping the masquerading PC (the linux box) and not the other PCs connected to the network (my brother´s windows PC and my linux box connect directly to the ADSL router and my windows PC connects to the linux box). The PC I can't ping or access is my brother´s PC. Thanks for your assistance so far.. Ronald Castillo -Original Message- From: Vineet Kumar [mailto:[EMAIL PROTECTED] Sent: martes, 04 de junio de 2002 2:26 To: debian-user@lists.debian.org Subject: Re: rc.local in debian (was: Ip Masquerading) * Colin Watson ([EMAIL PROTECTED]) [020603 16:51]: On Mon, Jun 03, 2002 at 11:49:54PM +0200, Ronald Castillo wrote: I was thinking that I should configure my secondary LAN card (the one that connects to my internal network) in the /etc/network/interfaces card, but I don't know what to place there. I have already configured the LAN card that connects me to the outside world without problems. Well, if it helps, here's an /etc/network/interfaces fragment from one of my machines: iface eth1 inet static address 192.168.42.1 network 192.168.42.0 netmask 255.255.255.0 broadcast 192.168.42.255 This brings up an interface using the second network card with IP address 192.168.42.1. Also, you'll probably want to add a line that says auto eth1 which will make eth1 come up automatically at boot, instead of only after you say ifup eth1. IIRC, though, that's new since after potato. good times, Vineet -- Currently seeking opportunities in the SF Bay Area Please see http://www.doorstop.net/resume.shtml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Update - RE: rc.local in debian (was: Ip Masquerading)
Just to update something new I have found out.. I tried pinging my ADSL router and my brother´s PC from my Linux box and it doesn't work either, but it did work from my Windows PC when I had it connected directly to my ADSL router. So, now I'm feeling pretty clueless... At least in all my PCs (incluiding the masqueraded one) internet works perfectly. Just in case you need it, here's a copy of my /etc/network/interfaces file: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # The first network card - this entry was created during the Debian installation auto eth0 iface eth0 inet static address 10.0.0.3 netmask 255.0.0.0 gateway 10.0.0.1 iface eth1 inet static address 10.0.0.4 network 10.0.0.0 netmask 255.0.0.0 broadcast 10.0.0.255 Just to make a note, 10.0.0.1 is the IP of my ADSL router. Any light on this will be appreciated. Ronald Castillo -Original Message- From: Ronald Castillo [mailto:[EMAIL PROTECTED] Sent: miércoles, 05 de junio de 2002 21:40 To: debian-user@lists.debian.org Subject: RE: rc.local in debian (was: Ip Masquerading) Hello.. I have configured my second interface as you told me (with a few changes) and it's now working fine!!! Thanks a lot for your help to you all!!! Just two more questions.. I don't know if I should place auto on it because the Windows box isn't permanently turned on, so I think that Linux might show up an error message if the connection is up when the Windows box is off, doesn´t it? Just like when I enable my other card when it doesn't have a LAN cable in it. The other thing is that, from the masqueraded PC (the windows box), I can only ping the masquerading PC (the linux box) and not the other PCs connected to the network (my brother´s windows PC and my linux box connect directly to the ADSL router and my windows PC connects to the linux box). The PC I can't ping or access is my brother´s PC. Thanks for your assistance so far.. Ronald Castillo -Original Message- From: Vineet Kumar [mailto:[EMAIL PROTECTED] Sent: martes, 04 de junio de 2002 2:26 To: debian-user@lists.debian.org Subject: Re: rc.local in debian (was: Ip Masquerading) * Colin Watson ([EMAIL PROTECTED]) [020603 16:51]: On Mon, Jun 03, 2002 at 11:49:54PM +0200, Ronald Castillo wrote: I was thinking that I should configure my secondary LAN card (the one that connects to my internal network) in the /etc/network/interfaces card, but I don't know what to place there. I have already configured the LAN card that connects me to the outside world without problems. Well, if it helps, here's an /etc/network/interfaces fragment from one of my machines: iface eth1 inet static address 192.168.42.1 network 192.168.42.0 netmask 255.255.255.0 broadcast 192.168.42.255 This brings up an interface using the second network card with IP address 192.168.42.1. Also, you'll probably want to add a line that says auto eth1 which will make eth1 come up automatically at boot, instead of only after you say ifup eth1. IIRC, though, that's new since after potato. good times, Vineet -- Currently seeking opportunities in the SF Bay Area Please see http://www.doorstop.net/resume.shtml -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Update - RE: rc.local in debian (was: Ip Masquerading)
Ronald Castillo [EMAIL PROTECTED] writes: Just to update something new I have found out.. I tried pinging my ADSL router and my brother´s PC from my Linux box and it doesn't work either, but it did work from my Windows PC when I had it connected directly to my ADSL router. So, now I'm feeling pretty clueless... At least in all my PCs (incluiding the masqueraded one) internet works perfectly. Just in case you need it, here's a copy of my /etc/network/interfaces file: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # The first network card - this entry was created during the Debian installation auto eth0 iface eth0 inet static address 10.0.0.3 netmask 255.0.0.0 gateway 10.0.0.1 iface eth1 inet static address 10.0.0.4 network 10.0.0.0 netmask 255.0.0.0 broadcast 10.0.0.255 Just to make a note, 10.0.0.1 is the IP of my ADSL router. Are both Ethernet cards plugged into the same physical network? (This would be a little weird.) If not, you get into the situation where the router tries to contact the ADSL box, and discovers it has two ways to get there (both interfaces are connected to 10.0.0.0/8), and guesses wrong. I suspect you probably want to reconfigure your ADSL box to be on some different IP address (say, 192.168.0.1), and then put in /etc/network/interfaces: auto eth0 eth1 iface eth0 inet static address 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255 gateway 192.168.0.1 iface eth1 inet static address 10.0.0.4 netmask 255.0.0.0 broadcast 10.255.255.255 This results in: 10.0.0.0/8 ++ 192.168.0.0/24 To internal network -- eth1 | Router | eth0 -- To ADSL box ++ (If you're unfamiliar, a.b.c.d/n is CIDR notation, meaning a network with network address a.b.c.d and the high n bits of the netmask set; 10.0.0.0/8 means the network 10.x.x.x, 192.168.0.0/24 is 192.168.0.x.) -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: rc.local in debian (was: Ip Masquerading)
I'M NOT MEMER OF YOUR MAILING LISTS. WHY THIS MAILS COME TO ME? EVERY DAY COME TO ME 200 MAILS FROM YOUR MAILING LISTS. CAN YOU DO SOMETHING WITH IT? THANK YOU. - Original Message - From: Colin Watson [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Tuesday, June 04, 2002 1:50 AM Subject: Re: rc.local in debian (was: Ip Masquerading) On Mon, Jun 03, 2002 at 11:49:54PM +0200, Ronald Castillo wrote: I was thinking that I should configure my secondary LAN card (the one that connects to my internal network) in the /etc/network/interfaces card, but I don't know what to place there. I have already configured the LAN card that connects me to the outside world without problems. Well, if it helps, here's an /etc/network/interfaces fragment from one of my machines: iface eth1 inet static address 192.168.42.1 network 192.168.42.0 netmask 255.255.255.0 broadcast 192.168.42.255 This brings up an interface using the second network card with IP address 192.168.42.1. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: rc.local in debian (was: Ip Masquerading)
I'M NOT MEMER OF YOUR MAILING LISTS. WHY THIS MAILS COME TO ME? EVERY DAY COME TO ME 200 MAILS FROM YOUR MAILING LISTS. CAN YOU DO SOMETHING WITH IT? THANK YOU. - Original Message - From: Vineet Kumar [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Tuesday, June 04, 2002 2:26 AM Subject: Re: rc.local in debian (was: Ip Masquerading) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: rc.local in debian (was: Ip Masquerading)
I made my own entitled local in /etc/init.d by copying /etc/init.d/skeleton to /etc/init.d/local, added what I needed it to do in the start section, and created a softlink to it in rc2.d entitled S99local. I don't know how others do it, though. Elizabeth Ronald Castillo [EMAIL PROTECTED] writes: Hello. Thanks to you all for your suggestions for trying to connect my Linux box to my Windows one via serial port, but after trying some things and not being able to make it work I decided to try to do that via network cards. On the IP Masquerading HOWTO it says I have to edit my /etc/rc.d/rc.local file, but actually I have 6 rc?.d folders in /etc, and none of them have a rc.local file. Is there an equivalent file in Debian I could use? Some help about this or a link to some Debian specific help will be appreciated. Thanks for your help.. Ronald Castillo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: rc.local in debian (was: Ip Masquerading)
On Mon, Jun 03, 2002 at 03:08:56AM -0500, Elizabeth Barham wrote: I made my own entitled local in /etc/init.d by copying /etc/init.d/skeleton to /etc/init.d/local, added what I needed it to do in the start section, and created a softlink to it in rc2.d entitled S99local. I don't know how others do it, though. That's pretty much what the FAQ advises: http://www.debian.org/doc/FAQ/ch-customizing.html#s-custombootscripts Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: rc.local in debian (was: Ip Masquerading)
On Mon, Jun 03, 2002 at 03:08:56AM -0500, Elizabeth Barham wrote: I made my own entitled local in /etc/init.d by copying /etc/init.d/skeleton to /etc/init.d/local, added what I needed it to do in the start section, and created a softlink to it in rc2.d entitled S99local. I don't know how others do it, though. The debian way of setting up the symlinks is via update-rc.d (1), it will set up the symlinks for all of the runlevels. AFAIK, the system administrator is free to create new entries in /etc/init.d and set up symlinks. However, you may want to make sure that you won't collide with any packages you set up in the future. I usually do that by prefixing the script the hostname-, but there probably are other (better) ways of avoiding collisions. -- Karl E. Jørgensen [EMAIL PROTECTED] www.karl.jorgensen.com Please study http://www.rfc855.org pgpgtIKhQ9SZq.pgp Description: PGP signature
RE: rc.local in debian (was: Ip Masquerading)
Thanks a lot for your help!! I could finally get past that step, but now I came across another problem: I have compiled the kernel with the necessary modules, installed the IP Masq script and all that, but it still doesn't work. I've tried pinging my linux box from Windows XP with no success. I was thinking that I should configure my secondary LAN card (the one that connects to my internal network) in the /etc/network/interfaces card, but I don't know what to place there. I have already configured the LAN card that connects me to the outside world without problems. I would really appreciate any help about this. Thanks a lot for helping me so far.. Ronald Castillo -Original Message- From: Colin Watson [mailto:[EMAIL PROTECTED] On Behalf Of Colin Watson Sent: lunes, 03 de junio de 2002 13:16 To: debian-user@lists.debian.org Subject: Re: rc.local in debian (was: Ip Masquerading) On Mon, Jun 03, 2002 at 03:08:56AM -0500, Elizabeth Barham wrote: I made my own entitled local in /etc/init.d by copying /etc/init.d/skeleton to /etc/init.d/local, added what I needed it to do in the start section, and created a softlink to it in rc2.d entitled S99local. I don't know how others do it, though. That's pretty much what the FAQ advises: http://www.debian.org/doc/FAQ/ch-customizing.html#s-custombootscripts Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: rc.local in debian (was: Ip Masquerading)
On Mon, Jun 03, 2002 at 11:49:54PM +0200, Ronald Castillo wrote: I was thinking that I should configure my secondary LAN card (the one that connects to my internal network) in the /etc/network/interfaces card, but I don't know what to place there. I have already configured the LAN card that connects me to the outside world without problems. Well, if it helps, here's an /etc/network/interfaces fragment from one of my machines: iface eth1 inet static address 192.168.42.1 network 192.168.42.0 netmask 255.255.255.0 broadcast 192.168.42.255 This brings up an interface using the second network card with IP address 192.168.42.1. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: rc.local in debian (was: Ip Masquerading)
* Colin Watson ([EMAIL PROTECTED]) [020603 16:51]: On Mon, Jun 03, 2002 at 11:49:54PM +0200, Ronald Castillo wrote: I was thinking that I should configure my secondary LAN card (the one that connects to my internal network) in the /etc/network/interfaces card, but I don't know what to place there. I have already configured the LAN card that connects me to the outside world without problems. Well, if it helps, here's an /etc/network/interfaces fragment from one of my machines: iface eth1 inet static address 192.168.42.1 network 192.168.42.0 netmask 255.255.255.0 broadcast 192.168.42.255 This brings up an interface using the second network card with IP address 192.168.42.1. Also, you'll probably want to add a line that says auto eth1 which will make eth1 come up automatically at boot, instead of only after you say ifup eth1. IIRC, though, that's new since after potato. good times, Vineet -- Currently seeking opportunities in the SF Bay Area Please see http://www.doorstop.net/resume.shtml pgp0lHd6ZyoJC.pgp Description: PGP signature
