9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Vester Thacker <vester.thacker@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] A short PPPOE configuration guide
Date: Sun, 28 Aug 2005 16:49:39 +0900	[thread overview]
Message-ID: <32a656c205082800491d4c362f@mail.gmail.com> (raw)

I want to show an example to those that are having problems
configuring PPPOE immediately after installing Plan 9. Of course, I am
assuming that rio is viewable.


1.  Disable permissions checking:

  fossil/conf  /dev/sdC0/fossil > /tmp/fossil.conf

  Edit /tmp/fossil.conf to look like:

     fsys main config /dev/sdC0/fossil
     fsys main -AWP -V -c 1500
   
  Then write it back to the file system:

    fossil/conf -w /dev/sdC0/fossil  /tmp/fossil.conf


2.  Edit the plan9.ini file.

  Run the following commands:

   9fat:
   cd /n/9/
   acme plan9.ini (for folks without rio, use the ed editor)

  Add an ether=type=xxx entry to ensure the NIC is recognized. See
plan9.ini(8) for  more details (
http://zertz.plan9.ipng.wakhok.ac.jp/magic/man2html/8/plan9.ini ). The
entry should look similar to:

   ether=type=i82557


3.  Edit /lib/ndb/local with acme (or ed).

   Add an ipnet entry. My example is as follows:

ipnet=asahi-net.or.jp ip=219.121.16.20 ipmask=255.255.255.255
       dns=202.224.32.1
       dns=202.224.23.1

   Add an ip entry. My example is as follows:
     
ip=219.121.16.20 sys=ns dom=asahi-net.or.jp
       proto=tcp


3.   After saving the file, reboot by running 'fshalt' and turning off
the computer.


4.   Upon reboot, sweep (open) two windows in rio.

5.   In the first window, run the following:

        bind -b '#l0' /net
        bind -a '#l0' /net
        ip/pppoe -d ether0
        (enter the ISP provided username and password)

     In the second window, run the following:

        ndb/cs
        ndb/dns -r
     
     Note: The windows can be closed or hidden after the procedures.

Disclaimer: Following the procedure above should provide for a
standard PPPOE connection for those with a static IP address and allow
for dns queries, pings, ect.  I don't expect this is the only way to
start a pppoe connection, but I hope it is a starting point for better
documentation.

Good luck to all and best wishes.

--vester


             reply	other threads:[~2005-08-28  7:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-28  7:49 Vester Thacker [this message]
2005-08-29 11:24 ` [9fans] " Vester Thacker
2005-08-29 11:54 ` [9fans] " Russ Cox
2005-08-29 13:25   ` Vester Thacker
2005-08-29 13:26   ` Enache Adrian
2005-08-29 13:28     ` Russ Cox
2005-08-29 22:02   ` Dave Eckhardt
2005-08-30  1:39     ` kokamoto
2005-08-30  1:56       ` kokamoto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=32a656c205082800491d4c362f@mail.gmail.com \
    --to=vester.thacker@gmail.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).