Re: Netinstall via bridge
On Sun, Jan 28, 2007 at 03:36:33PM -0500, celejar wrote:
> On 1/27/07, Douglas Allan Tutty <dtutty@porchlight.ca> wrote:
> >On Mon, Jan 22, 2007 at 10:08:39AM -0500, celejar wrote:
> >>
> >> I plan to do a netinstall on a new laptop (Acer AS3960). There's
> >> internal wifi, and I have an Atheros PC card, but I have to assume
> >> that neither will be supported during installation. Ethernet directly
> >> into my gateway / router /wireless AP ('molly') is inconvenient
> >> because of the physical locations of the equipment. My current Debian
> >> (Sid) machine ('lucy') connects wirelessly to 'molly' via an Atheros
> >> PCI card supported by Madwifi.
> >>
> >> The following two solutions occur to me:
> >>
> >> A) Ethernet from the laptop (via crossover or a spare switch) to
> >> 'lucy' and bridge the wireless and wired interfaces on 'lucy'. IIUC,
> >> this will put the laptop on the wireless network, enabling it to
> >> configure itself via dhcp (from the dhcp server on 'molly') and then
> >> access the internet via 'molly' just like the other machines that are
> >> directly connected to 'molly'.
> >>
> >> B) As 'A', but instead of configuring a bridge, just set up apt-proxy
> >> or apt-cache on 'lucy.
> >
> >
> >I would go with B but don't bother with apt-proxy or a bridge. Just
> >forward through lucy. That crossover cable is its own network and lucy
> >can ip forward between the two networks. You may wish to run dnsmasq on
> >lucy so you can point the new box's resolver at it. If you need to, you
> >can also install ipmasq on lucy so molly thinks everything is coming
> >from lucy instead of the laptop. You won't need dhcp on the laptop,
> >just set it up manually.
>
> Thanks. I wasn't sure whether or not to use the same address range and
> subnet for the laptop if I do it this way. The main network is
> 192.168.0.0/24. If I use something different (e.g. 10.0.0.0/24) for
> the laptop (and wired iface of lucy), then I assume I'd have to
> masquerade (NAT) on lucy or else molly won't recognize packets with
> the 10.0.0.0 addresses. I suppose you mean I should just use
> 192.168.0.0/24 addresses on lucy and the laptop and assign them
> manually? If so, then as far as I understand it won't really be its
> own network. If I'm missing something, feel free to point it out :).
>
Hi Celejar
Let me try to draw this out and see if I've got it right:
+--------+ +--------+ +--------+
internet | molly | 192.168.1.0 | lucy | 192.168.2.0 | laptop |
|.168.1.1| 255.255.255.0 |.168.2.1| 255.255.255.0 |.168.2.2|
| | |.168.1.2| | |
+--------+ +--------+ +--------+
On lucy, you set it for ip forwarding. You install the ipmasq package
which does the masquarading out of the box. You can also install the
dnsmasq package which does caching dns service out of the box.
On the laptop you tell it that your gateway and also your dns
server is 192.168.1.1
Molly will only see traffic coming from lucy because lucy will masqurade
it.
Lucy will of course need two ethernet cards unless you're using a serial
null-modem and going ppp (been there, done that, works great).
I've done this all the time, especially when ethernet switches were
expensive and not all my boxs had ethernet cards. Don't let the NAT on
lucy bother you. The ipmasq package does its job just fine with no
tweaking. If you _want_ it can also serve dhcp but I always set up
stuff manually.
Put all three boxes into all three box's /etc/hosts file. Test it out
with ping.
Enjoy.
Doug.
Reply to: