Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
As promised, here are the settings that I used. Also note that this works when your dhclient device is the _0 device since that is hard coded in sbin/init.d/dhclient. /etc/rc.config. Note that netconfig specifies interface 1 only. I placed bogus parameters in IPADDR_0 and IFCONFIG_0 (dhclient sets the correct address). # # number of network cards: "_0" for one, "_0 _1 _2 _3" for four cards # NETCONFIG="_1" # # IP Adresses # IPADDR_0="192.168.0.6" IPADDR_1="192.168.0.1" # # network device names (e.g. "eth0") # NETDEV_0="eth0" NETDEV_1="eth1" # # parameteres for ifconfig, if you put "bootp" into it, bootp will # be used to configure it # sample entry for ethernet: # IFCONFIG_0="192.168.81.38 broadcast 192.168.81.63 netmask 255.255.255.224" # IFCONFIG_0="192.168.0.6 broadcast 192.168.0.255 netmask 255.255.255.0" IFCONFIG_1="192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0" CREATE_RESOLVCONF=yes DHCLIENT="yes" --------------------- The other change is in /sbin/init.d/network. This will allow network to start devices listed in NETCONFIG. Comment out the following line: #test -n "$DHCLIENT" -a "$DHCLIENT" = "yes" && exit 0 No other changes. I don't know why it did not work when I initially installed 6.1 -- Jerry - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |