Re: Modem Gateway
On Tue, 2002-07-23 at 00:43, dan.hunt@st.brieux.com wrote:
> --snip
> > > 4. Get the local network working, and the ppp link up.
> Check! Working good!
> > > Make sure you can access the net *from the gateway machine*.
> Check! Yes I downloaded a update from the net!
> > > Make sure each internal machine can ping the other.
> I'm not sure if this is o.k. or not. From the gateway machine, I can ping the internal machine
> fine. There is only one internal machine with the modem connected by a crossover cable to the
> gateway machine. From the internal machine I cannot ping the gateway machine. The packets
> are lost.
>
> I now have learned all about the nohup command and the "mcopy" commands.
>
> This is from the Internal Machine:
>
> "nohup ifconfig"
>
> eth0 Link encap:Ethernet HWaddr 00:10:B5:9E:5F:4A
> inet addr:192.168.0.0 Bcast:192.168.0.255 Mask:255.255.255.0
^^^^^^^^^^^
|||||||||||
This is wrong. A .0 address refers to the network itself and cannot
refer to a machine. Machines on this network will have the final number
in the range 1-254.
The reason you can ping this address from the gateway is you are pinging
the network address, which all machines on the network will receive.
However When you ping *from* this machine, return packets will not be
acknowledged because they are not destined for a host. (basically
speaking)
Change the IP number to 192.168.0.2
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:790 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1196 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:77420 (75.6 KiB) TX bytes:72064 (70.3 KiB)
> Interrupt:5 Base address:0x1000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:1549 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1549 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:152892 (149.3 KiB) TX bytes:152892 (149.3 KiB)
>
> "nohup 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
> default 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
Routing table looks fine.
> "nohup hostname"
>
> brieux.local.saint.brieux.local
>
>
> This is from the Gateway Machine:
>
> eth0 Link encap:Ethernet HWaddr 00:C0:F0:03:31:76
> inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1187 errors:0 dropped:0 overruns:0 frame:0
> TX packets:796 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:71524 (69.8 KiB) TX bytes:78008 (76.1 KiB)
> Interrupt:10 Base address:0x2000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:816 errors:0 dropped:0 overruns:0 frame:0
> TX packets:816 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:68139 (66.5 KiB) TX bytes:68139 (66.5 KiB)
>
> 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
>
> dog.localdomain.fake
>
> --
> I have read that the hostname must be similar on a network.
Hostnames are secondary. Get the IP side of things working first.
> I don't know how to adjust them to match now that everything is set up.
/etc/hostname
/etc/hosts
> Is this important? The Gateway machine has a 10 based T NIC.
> The Internal machine has a 100 based T NIC.
The 100 will operate as a 10 without any intervention.
> I cooked a custom ( 2.4.18 I think ) the kernel on the gateway machine and installed most of
> the modules from your big list.
Once you have those modules installed, And each internal machine can
ping the other, and the gateway machine can contact the net, then run
that iptables command from the previous post to set up masquerading.
Then your internal machine should be able to see the Internet.
When this is done, be aware its *not* the end of the matter, for you
will need to set up a firewall. But when you get to that stage we can go
over a firewall.
> Thank you very much for your kind assistance.
Its completely my pleasure. I don't mind at all going through this on
this list. All this is archived, and someday many others will come to
cover the same ground that you are, and they'll search on google, and
they'll find this thread, and it will help them aswell. Basically
together we are writing a manual here.
For the benefit of all living things.
With metta
Crispin Wellington
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: