[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: daisy-chaining internet connectivity



bob@proulx.com (Bob Proulx) writes:

> Terrence Brannon wrote:
>> I have a Debian/testing machine connected to the internet via our
>> wireless lan.
>
> Check.
>
>> I want to put another machine on the internet which requires physical
>> ethernet instead of wireless.
>
> This other machine has only a wired network card, right?

yes, that is right. I also have plenty of time to do this, so I may as
well take it step by step til I get it.

>> Besides buying a wireless bridge, is there some way for the connected
>> machine to provide internet connectivity for this other machine? 
>
> Yes.  Very easily as a matter of fact.  Install a wired network card

I believe I have one. The output of lspci shows a Realtek card. Is
this what you mean? Otherwise, please recommend a popular brand.

> > in the same machine that currently has a wireless network connection.
> It can gateway the data to your wired network.  In this mode it will
> function as a router.  The wireless interface will be the WAN

WAN means wireless area network or wide area network?

> > connection and the wired interface will be the LAN connection.  You
> could also have it function as a firewall for the wired network.
>
> It really is just about as easy as configuring both network interfaces
> and then turning on internet packet forwarding between the
> interfaces.  But you will almost certainly want to install some other
> things such as a DHCP server on your wired network.  So let me outline
> a simple plan for you.
>
> * Install a wired network card as the second network interface.

Ok, either I have one per the lspci output below or just need to know
which one I can get for my Toshiba P25 high-end laptop:

http://www.pcmag.com/article2/0,1759,1616847,00.asp

This is the machine with a wireless connection. I have an itty-bitty
Thinkpad 560e that needs to get connected to the internet via the
Toshiba. 


> * Configure the second wired network card with a static IP address.
>   Use a different subnet than you have on our WAN side.  That is, if
>   you have a 10.* address 

pool-71-109-151-76:/home/metaperl# ifconfig eth2
eth2      Link encap:Ethernet  HWaddr 00:02:2D:B2:9F:B0
          inet addr:192.168.2.60  Bcast:192.168.2.255
          Mask:255.255.255.0
          inet6 addr: fe80::202:2dff:feb2:9fb0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2009980 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2512284 errors:2381 dropped:0 overruns:0
          carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:501867069 (478.6 MiB)  TX bytes:1951750595 (1.8
          GiB)
          Interrupt:185 Base address:0x100

This is the output from the P25

> use 192.168.1.1 on the LAN.  If your outside
>   address is already 192.168.* then use 10.0.0.1 on your LAN side.
>   Just make sure they are different.

Looks like 10* for the LAN side.

> >
> * Install and configure DHCP for your LAN interface.  This is probably
>   the most complicated part of the problem.  But not overly so.

Heh. I might be there by this Saturday. But no biggie on
time. Education is the key. Maybe I will type up a doc on this. In
fact I certainly will if this works out... I have seen someone else do
this with Debian 5-6 years ago, so I know it will work.

> >
> * Ensure that packet forwarding is in place.  Use either a firewall
>   package or do this yourself with low level commands.
>
>     echo 1 > /proc/sys/net/ipv4/ip_forward

I'm a KDE kiddie, so whatever tool pops up for it do this is my
preference. 

This is the lcpci output from my P25 laptop.

pool-71-109-151-76:/home/metaperl# lspci
0000:00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM
Controller/Host-Hub Interface (rev 02)
0000:00:01.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to AGP Controller
(rev 02)
0000:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB
UHCI #1 (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB
UHCI #2 (rev 02)
0000:00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB
UHCI #3 (rev 02)
0000:00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB
UHCI #4 (rev 02)
0000:00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2
EHCI Controller (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2)
0000:00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC
Bridge (rev 02)0000:00:1f.1 IDE interface: Intel Corp. 82801EB/ER
(ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02)
0000:00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus
Controller (rev 02)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER
(ICH5/ICH5R) AC'97 Audio Controller (rev 02)
0000:00:1f.6 Modem: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Modem
Controller (rev 02)
0000:01:00.0 VGA compatible controller: nVidia Corporation NV34M
[GeForce FX Go 5200] (rev a1)
0000:02:00.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21
IEEE-1394a-2000 Controller (PHY/Link)
0000:02:01.0 Ethernet controller: Realtek Semiconductor Co.,
Ltd. RTL-8139/8139C/8139C+ (rev 10)
0000:02:02.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus
Controller (rev 01)
0000:02:04.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI
to Cardbus Bridge with ZV Support (rev 32)
0000:02:04.1 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI
to Cardbus Bridge with ZV Support (rev 32)
0000:02:06.0 System peripheral: Toshiba America Info Systems SD TypA
Controller (rev 03)
pool-71-109-151-76:/home/metaperl#



Reply to: