Timothy Bolz wrote: > Thank you Bob for answering > > I'm getting better at networking. I got them talking at least and can break > the connection and reconnect them. I had the gateway already in like you had. > I had also put in network 192.168.0.0 . I was playing around with route and > found out what that does. I wasn't able to connect to the net for a while > and now I know what that does. when I conect to the internet with dialup if > I run ifconfig there is a ppp0 which is the default gateway and has the ip > address I get assigned. Which sounds correct. Here's the configuration. > Could it be ipchains? However that looks good. All I want to do is connect > Boyle to the internet thru Tesla. I was just thinking should the gateway be > ppp0. Can I put ppp0 in /etc/network/interfaces ie. > gateway ppp0 > I notice when I connect, route has > default 1atwdialup.famv 0.0.0.0 UG 0 0 0 ppp0 > I'm just guessing here. > > This is the machine connected to the internet > > tesla:/etc/network# cat interfaces > # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) > > # The loopback interface > iface lo inet loopback > # The first ethernet interface > iface eth0 inet static > address 192.168.0.2 > network 192.168.0.0 > netmask 255.255.255.0 > broadcast 192.168.0.255 > gateway 192.168.0.1 > > > tesla:/etc# ifconfig > eth0 Link encap:Ethernet HWaddr 00:A0:24:80:20:D9 > inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:427 errors:0 dropped:0 overruns:0 frame:0 > TX packets:427 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > Interrupt:10 Base address:0x300 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:3924 Metric:1 > RX packets:76 errors:0 dropped:0 overruns:0 frame:0 > TX packets:76 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > > ppp0 Link encap:Point-to-Point Protocol > inet addr: x.x.x.x P-t-P:x.x.x.x Mask:255.255.255.255 > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:3994 errors:3 dropped:0 overruns:0 frame:3 > TX packets:3390 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:10 > > tesla:/etc# route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 1atwdialup.famv * 255.255.255.255 UH 0 0 0 ppp0 > 192.168.0.0 * 255.255.255.0 U 0 0 0 eth0 > default 1atwdialup.famv 0.0.0.0 UG 0 0 0 ppp0
You do *NOT* need the gateway line in tesla's /etc/network/iface. The gateway line says, in effect, "The whole Internet is through this gateway." The way you've set it up, tesla will think it can route to the internet through eth0. OTOH, it looks like your routing table is okay. So either ppd fixed the default gateway when you dialed in or you fixed it yourself by vhand. > This is the machine I want to connect to the internet. > > boyle:/home/timothy# ifconfig > eth0 Link encap:Ethernet HWaddr 00:C0:4F:AE:8B:39 > inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:357 errors:0 dropped:0 overruns:0 frame:0 > TX packets:387 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > Interrupt:11 Base address:0xdc80 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:3924 Metric:1 > RX packets:174 errors:0 dropped:0 overruns:0 frame:0 > TX packets:174 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > > > > boyle:/home/timothy# route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 192.168.0.0 * 255.255.255.0 U 0 0 0 eth0 > boyle:/home/timothy# On boyle, you *DO* want "gateway 192.168.0.2" on eth0's entry. From Boyle, the whole Internet is indeed through tesla's network. Once you make that change, you should be able to turn on IP forwarding on Tesla by saying "echo 1 > /proc/sys/net/ipv4/ip_forward" and you'll have connectivity for Boyle. No filtering -- Boyle will be no more protected from the big bad internet than . Segue. I like your hostnames, Tesla and Boyle. Once upon a time, SGI had a big software project code-named Fahrenheit. Fahrenheit was a cross platform (Windows and IRIX) scene graph system. The name, Fahrenheit, was chosen by marketeers who designed a nice logo with flames. "Fahrenheit is a measure of temperature, and `very hot' is a temperature, and flames are very hot, so flames naturally connote Fahrenheit" were the not-entirely-logical thoughts that went through their tiny brains. Curiously enough, about a year earlier, when the Octane workstation was launched, they thought that flames connoted octane. "Octane is in gasoline, and gasoline burns (hey, credit them with knowing it doesn't explode), and when things burn they make flames, so flames naturally connote octane." I worked on a sister project to Fahrenheit that extended it with audio spatialization. Our project was too small to have marketeers, so when it came time to name our project, we engineers reasoned, "Gabriel Fahrenheit was a scientist. Christian Huygens was a scientist contemporary with Fahrenheit. Huygens studied the propagation of light and sound and contributed basic knowledge that underlies both projects. So Huygens is a good name." Of course, the Fahrenheit marketeers thought Huygens was a stupid name. And they were right. Flames don't naturally connote Huygens. -- Bob Miller K<bob> kbobsoft software consulting http://kbobsoft.com [EMAIL PROTECTED]
