Wave - @Home Upgrade for Linux

These pages are moving to the @Home server

Wave - @Home Upgrade for Linux

Some notes on the Wave to @Home upgrade for Linux users.

DHCP

@Home is using DHCP. You need version 0.70 which supports hostname requests. Given a user ID (aka hostname) crNNNN-a, the command dhcpcd -h crNNNN-a will connect with the DHCP server and create some data files in /etc/dhcpc/. If you are running RedHat you may need to edit /etc/sysconfig/network-scripts/ifup to include a line such as

/sbin/dhcpcd -h `hostname` -c /etc/sysconfig/network-scripts/ifdhcpc-done ${DEVICE}

Otherwise you may need to make a symbolic link from /etc/resolv.conf to /etc/dhcpc/resolv.conf. See the dhcpcd manpage and DHCPcd HOWTO

You will get a domain like rchmd1.bc.wave.home.com. This must be searched as there are now useful things in this domain. Currently it seems that you get your old static IP address back and the old gateway address.

Note:
I'm told (Grady Park) that in Linux 2.1.x you need dhcpcd 1.3.6 and use the -I option. It's available from ftp://phystech.dyn.ml.org/pub/dhcpcd-1.3.6.tar.gz

Note:
Steven Yap (writes:

(dhcpcd-0.70) (is) not glibc friendly. Comment out #include  and
replace all "#include " directives with the equivalent libc
versions. For example, replace "#include " with "#include
".

2. One of the .c files is missing an "#include . It's the one
that gcc complains about strlen() being an implicit function.

Note:
Glenn Guthrie writes:
I had to download a patched-up version of dhcpcd 0.7 for Linux RedHat 5.x ... I found it at acm.csres.utexas.edu/siglinux/dorm.html

WWW

@Home uses proxy caches. Theoretically this can improve Web page loading from distant popular sites by a huge amount. In practice, distant unpopular sites may be slightly slower. Most problems with the proxy in terms of speed should be fixable by throwing more horsepower at the cache.

Proxy Autoconfig: @Home serves an autoconfig script at http://www:8080. This attempts to balance the load between available proxies, tells Netscape to go direct to https: URLs (secure servers) and some CGI sites, etc. To use this method, in Netscape select Edit -> Preferences -> Advanced -> Proxies, check Automatic Proxy Configuration and enter this URL.
In Netscape 3 select Options -> Network Preferences -> Proxies.

To manually set the proxy, check Manual proxy configuration, View, and enter the HTTP proxy as "proxy" Port "8080". To use the proxy for other applications using the libwww library,

setenv http_proxy http://proxy:8080

The proxy seems to be an SGI Irix machine running Netscape proxy server.

MAIL

Receiving Mail

You have various choices:

Run sendmail locally and use your hostname as your email address
Forward mail from some other system to your host
Use e.g. Netscape POP3 client to connect to the @Home POP3 server "mail"
Run sendmail locally and run fetchmail from cron at regular intervals to retrieve mail via POP3.
One or more of the above

If you run sendmail or equivalent you can run e.g. procmail to handle mailing list subscriptions, run things like majordomo, forward specific user's mail elsewhere, etc. Sendmail can also be configured to reject certain spam outright if the headers are incorrect, or reject mail from certain domains.
Your old POP username and password seems to still work.

Sending Mail

You can

Run sendmail locally and use it for outgoing mail.
Send outgoing mail directly from applicaitons.
Send outgoing mail through the @Home server.

If you don't use the @Home server, your machine must remain connected in order to handle rejected mail.

NEWS

The NNTP server is now "news". Typically,

setenv NNTPSERVER news

in your login script, and/or configure Netscape appropriately. The old Wave NNTP servers are no longer available.

DNS

The nameservers may change from the Wave ones. dhcpcd will retrieve new values. If you are running named in cacheing mode you may like to update /etc/named.boot.

TIME

The @Home server "proxy" may be used with netdate or xntpd. Currently I see

proxy1.rdc1.bc.wave.home.com: stratum 3, offset -0.006783, synch distance 0.06792
ha1.rdc1.bc.wave.home.com: stratum 2, offset -0.012098, synch distance 0.06270
clock.home.net: stratum 1, offset 0.001110, synch distance 0.00000, refid 'GPS'

SECURITY

Usual stuff here. Read the mailing lists (Bugtraq, Linux Security, CERT etc.) and pay attention to anything that looks like a network vulnerability. Disable services in /etc/inetd.conf you don't need. Be careful with NFS and Samba exports

PERSONAL WEB PAGES

http://home.bc.rogers.wave.ca/ will die sometime. Go to http://www.rchmd1.bc.wave.home.com ( or equivalent for your local domain ) and select the WebSpace feature. Member's pages are now on http://members.home.net/

IRC

Try irc.home.com. Requires identd server running.

REFERENCES

Andrew Daviel