We've now compiled all needed programs for getting a connection to an access concentrator. For doing so, connect the DSL - modem into the so called UPLINK port of your switch or hub, and connect your SEGA Dreamcast, if not already done, to your switch or hub, too.
Transfer the new initial ramdisk to your SEGA Dreamcast.
Please refer to cook.sh in chapter four and chapter two.
If you've booted your SEGA Dreamcast, don't wonder
of some error messages, if you've got the setup of chapter three:
Some of the programs invoked by /etc/init.d/rcS aren't installed
yet. Now, you can check your connection with the access concentrator.
Please log in as root and type in:
root@hercules:~ # pppoe -A -I eth0 Access-Concentrator: BRAX11-erx Got a cookie: b7 33 1e cf 5e e8 05 23 e0 89 14 90 bc 27 fe 89 -------------------------------------------------- AC-Ethernet-Address: 00:90:1a:10:0f:f2 -------------------------------------------------- root@hercules:~ #
Your output may vary. If you don't get similar messages, please check your cables.
Now, that we've got a cookie from the access concentrator, we've to set up
some essential configuration files. The first file is
/etc/ppp/options and the easiest, too:
root@hercules:~ # :> /etc/ppp/options
That's all. The documentation of rp-pppoe suggest
an empty ppp configuration file. The next file
is /etc/ppp/pppoe.conf:
root@hercules:~ # cat <<. > /etc/ppp/pppoe.conf ETH=eth0 # ADSL user name. USER=your_username DEMAND=no DNSTYPE=SERVER USEPEERDNS=yes DNS1= DNS2= DEFAULTROUTE=yes CONNECT_TIMEOUT=30 CONNECT_POLL=2 ACNAME= SERVICENAME= PING="." CF_BASE=`/usr/bin/basename $CONFIG` PIDFILE="/var/run/$CF_BASE-adsl.pid" SYNCHRONOUS=no CLAMPMSS=1412 LCP_INTERVAL=20 LCP_FAILURE=3 PPPOE_TIMEOUT=80 PPPOE_EXTRA="" PPPD_EXTRA="" . root@hercules:~ # chmod 640 /etc/ppp/pppoe.conf
For further configuration options or information beyond, please read either README or the corresponding documentation file of this source package.
Later, we'll set up a configuration with an automatic dynamic local nameserver, but for now, this sample configuration will do its job.
The last file is /etc/ppp/pap-secrets:
root@hercules:~ # cat <<. > /etc/ppp/pap-secrets your_username * your_password * . root@hercules:~ # chmod 600 /etc/ppp/pap-secrets
Please ensure, the username in pppoe.conf corresponds to the one
found in the configuration file shown above.
Now, it's time for rock'n'roll. On virtual terminal 1 (ALT-F1), you start the connection:
root@hercules:~ # /usr/sbin/adsl-connect Connect: ppp0 <--> /dev/pts/0 Local IP address changed to aaa.bbb.ccc.ddd Remote IP address changed to eee.fff.ggg.hhh nameserver iii.jjj.kkk.lll nameserver mmm.nnn.ooo.ppp ...
You should get some output here about an IP change of the device ppp0
as well as the message of the nameserver that should have to be used.
On virtual terminal 2 (ALT-F2), you have to set at least one nameserver printed on virtual terminal 1:
root@hercules:~ # cat <<. > /etc/resolv.conf nameserver iii.jjj.kkk.lll .
Now, you should be able to test your connection:
root@hercules:~ # ping www.google.com PING www.google.com (216.239.39.99): 56 data bytes 64 bytes from 216.239.39.99: icmp_seq=0 ttl=53 time=126.5 ms 64 bytes from 216.239.39.99: icmp_seq=1 ttl=53 time=126.2 ms 64 bytes from 216.239.39.99: icmp_seq=2 ttl=53 time=127.8 ms 64 bytes from 216.239.39.99: icmp_seq=3 ttl=53 time=126.8 ms ...
If you get a similar output, you're on the way. Congratulations! If you don't get such an output, please check all cables and read carefully the last steps of this article or read the included README files in the ppp-2.4.1 and rp-pppoe-3.3 source package.