Thanks much, guitarlynn & victor. Additional questions inline.

Victor McAllisteer wrote:
"Dr. Richard W. Tibbs" wrote:

Dear list:
I am wondering if backup ramdisk options b, 5 (backup modules) ,
which is recommended in the README on the Dachstein images page,
saves all these changes I mention below.
Should I also back up dhclient, and etc? What else to completely save
the lrcfg changes?
I have used lrcfg to update:
options
1 Networks Settings > 1 , Network Configuration
CONFIG_DNS=YES
....
eth1 ipaddr = 192.168.1.2 (internal net)
eth1 masklen = 24


if you change the default IP address of 192.168.1.254 you will need to
make other changes
all of these changes get backup up with etc
I also recommend using dhcpd to assign ips to all your internal
workstations. You can assign static ips via dhcp, Windows can then use
dhcp to find other boxes on your network.
How does one use dhcp this way?
I see under lrcfg, 3 > Package settings 6> dhcpd > 1> dhcpd daemon config
there is indeed the magic address 192.168.1.254.... why 254? I am not aware this is a special addr.
Also, I see th edomain name is "private.network" -- should this domain  replace the "lab" name I used in
the lrcfg >Network settings> networks section?




                     ....
DNS0=<bellsouths primary dns>
DNS1 = bellsouth secondary dns --- these in
anticipation of pppoe for dsl


recommend not changing primary dns from 192.168.1.254. Dachstein has its
own secure caching dns server. Since it keeps the ip addresses of the
sites you normally use, it is much faster than querying you bellsouth DNS
server. The caching dns queries the root servers.
OK. Interesting -- I asked about configuring dnscache a while back on the list....
I am thinking that leaving
CONFIG_DNS = NO
activates the dachstein DNS server; otherwise it is disabled. RIght?
BTW, I will read further on pppoe under Dachstein, but a first thought was:
why not use roaring penguin no-gui client? Requires linux 2.2.9 or better (should be ok for LRP, right?)
Worked like a champ on Suse 7.0 which is kernel 2.2.16.



1 Networks Settings > 6 , Networks
lab 192.168.1.0
3 Package Settings > 3 modules >1 modules
uncomment natsemi
comment tulip

remember that you will need to use pci-scan before tullip now. Didn't
need to do that before, but there have been changes made to the network
device scripts.
then backup modules
Check.   pci-scan is before natsemi in /etc/modules.






Reply via email to