Re: Wireless network at home

Replies:

Parents:

Hugo Haas wrote:
>
> I have installed a wireless network at home. I have a laptop which is
> connected to my cable modem and which does masquerading.
[snip]
> If people want to do the same, I described the system at:
>
>            http://larve.net/people/hugo/2000/10/wireless-lan

Hi Hugo,

Gerald and I were at the QA meeting earlier this week,
and tried to set up a wireless network following your
instructions. We had only limited success. Gerald should
be able to fill in more of the details than I, but here
is what I recall:

- Gerald and I were able to have our Linux machines talk
  to each other, and we used iptables to do masquerading
  (Linux kernel 2.4.5; I had to recompile to have the
   proper support).  The iptables command we used was:

      iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE

  You might want to add iptables to your page since apparently ipchains
  is now deprecated.

- We had little luck with getting dhcpd to work on my
  machine. It was very flaky - it seemed to work once (i.e.,
  Gerald got an IP address) but after that, we only had
  success with static IPs. Here's my /etc/dhcpd.conf:

   subnet 192.168.1.0 netmask 255.255.255.0 {
      range 192.168.1.2 192.168.1.20;
      option routers 192.168.1.1;
      option domain-name-servers 18.29.0.200;
      option domain-name "localhost";
      option subnet-mask 255.255.255.0;
      default-lease-time 600;
      max-lease-time 7200;
      }

- The other machines around the table were a Mac (Karl) and two Windows
  machines. Try as we might, we could not get those machines to join
our
  network. However, they seemed to recognize each other (i.e., detect
  other cards, but no luck with IP addresses, etc.).

- We weren't clear on the significance of the ESSID and CHANNEL
parameters
  of the wireless interfaces. In the end, the config that seemed to
work was
  when the value of ESSID was "any" (and not, for example, "Chaos").
There
  was some question about whether ad-hoc mode was appropriate with the
  Windows and Mac systems. All of this part of the configuration
escapes
  me.

So, while we had minor successes, it was on the whole a frustrating
experience. Gerald and I had a little IRC chat going locally, but we
couldn't get everyone connected. Which may have been a good thing as
(1) it would have been a distraction from the meeting and (2) I would
have had less bandwidth for myself over the 56k line. :)

- Ian

--
Ian Jacobs (ij@w3.org)   http://www.w3.org/People/Jacobs
Tel:                     +1 718 260-9447

Re: Wireless network at home

Replies:

  • None.

Parents:

Alternative instructions for doing it from a Mac:

Turn on the airport (wireless card) and open the control panel (in OS X you
can have its status on teh menu bar or dock if you like, and do everything
from there).

In OS 9 select "software base station" and then start the base station (you
can change the network name/channel by editing the boxes).

In OS X select "Create network".

and away you go....

On Thu, 15 Nov 2001, Ian B. Jacobs wrote:

 Hugo Haas wrote:
 >
 > I have installed a wireless network at home. I have a laptop which is
 > connected to my cable modem and which does masquerading.
 [snip]
 > If people want to do the same, I described the system at:
 >
 >            http://larve.net/people/hugo/2000/10/wireless-lan

 Hi Hugo,

 Gerald and I were at the QA meeting earlier this week,
 and tried to set up a wireless network following your
 instructions. We had only limited success. Gerald should
 be able to fill in more of the details than I, but here
 is what I recall:

  - Gerald and I were able to have our Linux machines talk
    to each other, and we used iptables to do masquerading
    (Linux kernel 2.4.5; I had to recompile to have the
     proper support).  The iptables command we used was:

        iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE

    You might want to add iptables to your page since apparently ipchains
    is now deprecated.

  - We had little luck with getting dhcpd to work on my
    machine. It was very flaky - it seemed to work once (i.e.,
    Gerald got an IP address) but after that, we only had
    success with static IPs. Here's my /etc/dhcpd.conf:

     subnet 192.168.1.0 netmask 255.255.255.0 {
        range 192.168.1.2 192.168.1.20;
        option routers 192.168.1.1;
        option domain-name-servers 18.29.0.200;
        option domain-name "localhost";
        option subnet-mask 255.255.255.0;
        default-lease-time 600;
        max-lease-time 7200;
        }

  - The other machines around the table were a Mac (Karl) and two Windows
    machines. Try as we might, we could not get those machines to join
 our
    network. However, they seemed to recognize each other (i.e., detect
    other cards, but no luck with IP addresses, etc.).

  - We weren't clear on the significance of the ESSID and CHANNEL
 parameters
    of the wireless interfaces. In the end, the config that seemed to
 work was
    when the value of ESSID was "any" (and not, for example, "Chaos").
 There
    was some question about whether ad-hoc mode was appropriate with the
    Windows and Mac systems. All of this part of the configuration
 escapes
    me.

 So, while we had minor successes, it was on the whole a frustrating
 experience. Gerald and I had a little IRC chat going locally, but we
 couldn't get everyone connected. Which may have been a good thing as
 (1) it would have been a distraction from the meeting and (2) I would
 have had less bandwidth for myself over the 56k line. :)

  - Ian



--
Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)

HURL: fogo mailing list archives, maintained by Gerald Oskoboiny