From owner-freebsd-questions@FreeBSD.ORG Sat Jan 27 02:47:23 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3D48D16A400 for ; Sat, 27 Jan 2007 02:47:23 +0000 (UTC) (envelope-from freebsd@dfwlp.com) Received: from regulus.dfwlp.com (rrcs-64-183-212-244.sw.biz.rr.com [64.183.212.244]) by mx1.freebsd.org (Postfix) with ESMTP id 0F43E13C491 for ; Sat, 27 Jan 2007 02:47:22 +0000 (UTC) (envelope-from freebsd@dfwlp.com) Received: from athena.dfwlp.com (athena.dfwlp.com [192.168.125.83]) (authenticated bits=0) by regulus.dfwlp.com (8.13.8/8.13.8) with ESMTP id l0R2lK7G008647 for ; Fri, 26 Jan 2007 20:47:20 -0600 (CST) (envelope-from freebsd@dfwlp.com) From: Jonathan Horne To: freebsd-questions@freebsd.org Date: Fri, 26 Jan 2007 20:47:20 -0600 User-Agent: KMail/1.9.5 References: <200701261636.37517.freebsd@dfwlp.com> <200701261945.59523.freebsd@dfwlp.com> <45BAB711.7090104@wingfoot.org> In-Reply-To: <45BAB711.7090104@wingfoot.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701262047.20544.freebsd@dfwlp.com> X-Spam-Status: No, score=-4.4 required=3.6 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on regulus.dfwlp.com Subject: Re: run a command on startup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2007 02:47:23 -0000 On Friday 26 January 2007 20:21, Glenn Sieb wrote: > Try this: > > ifconfig_fxp0="ether 00:09:6b:b6:3e:d9 inet 192.168.125.71 netmask > 255.255.255.128" > > Hope that helps.. > Best, > --Glenn > unfortunately, that didnt work either. however, i just figured out something REALLY strange. the computer will still wake up, if i give the command: wakeonlan -i 192.168.125.127 00:00:00:00:00:00 *shrug* this is one of the strangest incidents ive had to troubleshoot in a long time! i guess there is no reason that 00:[...] cant be a valid mac address, and it doesnt seem to be having any trouble pkg_add -r'ing from the net so, i guess i can put this one to bed. cheers, jonathan