Re: Atheros AR5141
Hi Thanks for showing me that page, I've downloaded the latest drivers and had a look at the devid.h file and pretty much all the other files as well but I can't find any reference to the AR5414 chipset. The closest I've seen was AR5413 and AR5416 but not AR5414. Is there someone that is using this chipset? Thanks Reinhold > > The latest ath_hal is available from http://people.freebsd.org/~sam/ . > > > Tom > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Atheros AR5141
Hi I got myself a nice little R52 802.11a/b/g MiniPCI Card for our router. This card is using the Atheros AR5141 chipset. I searched everywhere to find out more info on this and came across a few pages where it said that the AR5141 chipset is supported but when I stick the card in the router and boot FreeBSD 7-STABLE it hangs when loading the Atheros drivers It stops right after this ath0: mem 0xdfff-0xdfff irq 10 at device 11.0 on pci0 ath0: [ITHREAD] Are there a new version of the ath driver somewhere that does support this chipset? Thanks Reinhold ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: After an update stable doesn't boot
Found the problem Its not Freebsd, its the pci raid controller. It was suggested to me on daemonforums.org to unplug all the drives and then plug them in one by one until it happened again, and it did, it happened when I plugged the first drive into the controller. Any ways, now I have to figure out how to get the controller to not want to boot the drives. Thanks for the suggestions On Thu, October 23, 2008 22:32, Reinhold wrote: > On Thu, October 23, 2008 22:02, Lowell Gilbert wrote: > >> >> Try reinstalling the bootloader. You can do that by going into the >> sysinstall disk partitioning screens, but not changing any slice or >> partitioning settings. >> > Hi > > > I tried to do this as well with no success, > What I did notice was that it lists all the disks starting with > ad10 ad12 ad18 ad22 ad6 and ad8 > > ad12 is where I have Freebsd installed on using UFS, the rest of the > drives are all for a zfs pool > > >>> Can any one please help >>> >>> >>> >>> Thanks >>> >>> >>> >>> On Thu, October 23, 2008 19:51, Reinhold wrote: >>> >>> >>>> Hi >>>> >>>> >>>> >>>> >>>> I just did a system update and after I've rebooted it doesn't boot >>>> up any more. All I'm getting is a blank screen with a curser >>>> blinking at the top left corner of the screen. >>>> >>>> This system was running 7.0-STABLE >>>> >>>> >>>> >>>> >>>> Any ideas as to how I can get it back up? >>>> >>>> >>>> >>>> >>>> Regards >>>> Reinhold >>>> >>>> >>>> >>>> >>>> ___ >>>> freebsd-stable@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>> To unsubscribe, send any mail to >>>> "[EMAIL PROTECTED]" >>>> >>>> >>>> >>>> >>> >>> >>> ___ >>> freebsd-stable@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to >>> "[EMAIL PROTECTED]" >>> >>> >> ___ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to >> "[EMAIL PROTECTED]" >> >> >> > > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: After an update stable doesn't boot
On Thu, October 23, 2008 22:02, Lowell Gilbert wrote: > > Try reinstalling the bootloader. You can do that by going into the > sysinstall disk partitioning screens, but not changing any slice or > partitioning settings. > Hi I tried to do this as well with no success, What I did notice was that it lists all the disks starting with ad10 ad12 ad18 ad22 ad6 and ad8 ad12 is where I have Freebsd installed on using UFS, the rest of the drives are all for a zfs pool >> Can any one please help >> >> >> Thanks >> >> >> On Thu, October 23, 2008 19:51, Reinhold wrote: >> >>> Hi >>> >>> >>> >>> I just did a system update and after I've rebooted it doesn't boot up >>> any more. All I'm getting is a blank screen with a curser blinking at >>> the top left corner of the screen. >>> >>> This system was running 7.0-STABLE >>> >>> >>> >>> Any ideas as to how I can get it back up? >>> >>> >>> >>> Regards >>> Reinhold >>> >>> >>> >>> ___ >>> freebsd-stable@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to >>> "[EMAIL PROTECTED]" >>> >>> >>> >> >> >> ___ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to >> "[EMAIL PROTECTED]" >> > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: After an update stable doesn't boot
On Thu, October 23, 2008 21:57, Torfinn Ingolfsen wrote: > > Some quick checks: > - use fdisk (for example: fdisk ad0) to check if the correct slice is > active - use boot0cfg -v to check the bootcode of the disk you are booting > from > Hi Thanks for getting back to me. Here is the info I have from fdisk and boot0cfg # fdisk ad12 *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=310101 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 312576642 (152625 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: and from # boot0cfg -v ad12 #flag start chstype end chsoffset size 10x80 0: 1: 10xa51023:254:63 63312576642 version=1.0 drive=0x80mask=0xf ticks=182 options=packet,update,nosetdrv default_selection=F1 (Slice 1) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: After an update stable doesn't boot
A little update. I can boot into freebsd using the life cd and can mount the disk when I'm in fixit. But from there on I have no idea what to do to fix this problem. Can any one please help Thanks On Thu, October 23, 2008 19:51, Reinhold wrote: > Hi > > > I just did a system update and after I've rebooted it doesn't boot up any > more. All I'm getting is a blank screen with a curser blinking at the top > left corner of the screen. > > This system was running 7.0-STABLE > > > Any ideas as to how I can get it back up? > > > Regards > Reinhold > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
After an update stable doesn't boot
Hi I just did a system update and after I've rebooted it doesn't boot up any more. All I'm getting is a blank screen with a curser blinking at the top left corner of the screen. This system was running 7.0-STABLE Any ideas as to how I can get it back up? Regards Reinhold ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
After an update stable doesn't boot
Hi I just did a system update and after I've rebooted it doesn't boot up any more. All I'm getting is a blank screen with a curser blinking at the top left corner of the screen. This system was running 7.0-STABLE Any ideas as to how I can get it back up? Regards Reinhold ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mail problems was Re: apache problems
Thanks for the tips on postfix but they don't work for me. I have my mail server behind a pf firewall box on a local ip I have attached my pf.conf file so that you can see what it looks like, I also have to tell spamd to use the hostname of the mail sever but when I use the -h flag is sops working. thanks for all the help On Thu, 16 Aug 2007 12:18:35 -0700 Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > On Thu, Aug 16, 2007 at 09:16:00PM +0200, Miroslav Lachman wrote: > > Jeremy Chadwick wrote: > > [...] > >>> I'm also getting this error when I do a gracful restart of apache > >>> [Thu Aug 16 05:12:16 2007] [warn] (22)Invalid argument: Failed to > >>> enable the 'httpready' Accept Filter > >>> [Thu Aug 16 05:12:16 2007] [warn] (22)Invalid argument: Failed to > >>> enable the 'httpready' Accept Filter > >>> > >>> and in my /boot/loader.conf I have added > >>> accf_data_load="YES" > >>> accf_http_load="YES" > >> Remove those. Here's why: > >> The apache rc.d startup script automatically will load > >> accf_http.ko. I also believe if that fails, Apache will try to > >> load it. From my experiences kldload/kldunload with accf_* is not > >> very friendly; I've seen where you can double-load the modules, > >> and where you can't unload the modules despite nothing using > >> them. If you have them built-in to your kernel, it gets even > >> worse. > > > > It is not always possible to load modules after OS startup is done > > - when securelevel is 1 or above, you can not load kernel modules. > > Okay, then the apache rc.d script needs to take this into account, > regardless of what rc.conf apache22_http_accept_enable is set to. > > That shouldn't be too hard to fix. > pf.conf Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache problems
Thanks for the reply I'm having some mail problems as well, today is not my day. I'll remove all the stuff you mentioned and change back to 4BSD Will I have to recompile all the ports as well? I don't think its a PF problem because I have used this rule set of mine for a few years with no problems at all, but I'll recheck that just to make sure. Now for the mail problem I'm having its got to do with postfix sending mail from any ip address and not from the one that I want it to, but thats a later problem and on another box, I first want to get this apache thing sorted.. On Thu, August 16, 2007 20:07, Jeremy Chadwick wrote: > On Thu, Aug 16, 2007 at 07:28:24PM +0200, Reinhold wrote: > >> Hi >> > > Hello. First off, you sent mail to the list twice. I don't know why, > but you did. Be patient. :-) > >> I am having some problems with apache22 on my box. What happens is, >> when I'm viewing loads and loads of pages, apache will stop responding >> untill I restart it again. This normally happens when the free memory >> shown by top gets to about +- 100MB. > > I'm guessing that might be due to you using the ULE scheduler in your > kernel. Try switching back to 4BSD and see if that fixes it. > >> I'm also getting this error when I do a gracful restart of apache >> [Thu Aug 16 05:12:16 2007] [warn] (22)Invalid argument: Failed to enable >> the 'httpready' Accept Filter [Thu Aug 16 05:12:16 2007] [warn] >> (22)Invalid argument: Failed to enable >> the 'httpready' Accept Filter >> >> and in my /boot/loader.conf I have added accf_data_load="YES" >> accf_http_load="YES" > > Remove those. Here's why: > > > The apache rc.d startup script automatically will load accf_http.ko. > I also believe if that fails, Apache will try to load it. From my > experiences kldload/kldunload with accf_* is not very friendly; I've seen > where you can double-load the modules, and where you can't unload the > modules despite nothing using them. If you have them built-in to your > kernel, it gets even worse. > > AFAIK, using accf_data.ko isn't recommended. accf_http.ko on the other > hand is OK. Try not loading accf_data.ko in addition to my above > recommendation (re: 4BSD scheduler). > >> device pf device pflog device pfsync > > Finally, make sure your pf rules aren't doing anything stupid. If > ultimately you think it's a problem with pf rules, unload the pf module > and/or set pf_enable="no" in rc.conf and reboot. If the problem goes away > after that, then you'll know. > > -- > | Jeremy Chadwickjdc at parodius.com | > | Parodius Networking http://www.parodius.com/ > | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB > | > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache problems
Thanks for the reply I'm having some mail problems as well, today is not my day. I'll remove all the stuff you mentioned and change back to 4BSD Will I have to recompile all the ports as well? I don't think its a PF problem because I have used this rule set of mine for a few years with no problems at all, but I'll recheck that just to make sure. Now for the mail problem I'm having its got to do with postfix sending mail from any ip address and not from the one that I want it to, but thats a later problem and on another box, I first want to get this apache thing sorted.. On Thu, August 16, 2007 20:07, Jeremy Chadwick wrote: > On Thu, Aug 16, 2007 at 07:28:24PM +0200, Reinhold wrote: > >> Hi >> > > Hello. First off, you sent mail to the list twice. I don't know why, > but you did. Be patient. :-) > >> I am having some problems with apache22 on my box. What happens is, >> when I'm viewing loads and loads of pages, apache will stop responding >> untill I restart it again. This normally happens when the free memory >> shown by top gets to about +- 100MB. > > I'm guessing that might be due to you using the ULE scheduler in your > kernel. Try switching back to 4BSD and see if that fixes it. > >> I'm also getting this error when I do a gracful restart of apache >> [Thu Aug 16 05:12:16 2007] [warn] (22)Invalid argument: Failed to enable >> the 'httpready' Accept Filter [Thu Aug 16 05:12:16 2007] [warn] >> (22)Invalid argument: Failed to enable >> the 'httpready' Accept Filter >> >> and in my /boot/loader.conf I have added accf_data_load="YES" >> accf_http_load="YES" > > Remove those. Here's why: > > > The apache rc.d startup script automatically will load accf_http.ko. > I also believe if that fails, Apache will try to load it. From my > experiences kldload/kldunload with accf_* is not very friendly; I've seen > where you can double-load the modules, and where you can't unload the > modules despite nothing using them. If you have them built-in to your > kernel, it gets even worse. > > AFAIK, using accf_data.ko isn't recommended. accf_http.ko on the other > hand is OK. Try not loading accf_data.ko in addition to my above > recommendation (re: 4BSD scheduler). > >> device pf device pflog device pfsync > > Finally, make sure your pf rules aren't doing anything stupid. If > ultimately you think it's a problem with pf rules, unload the pf module > and/or set pf_enable="no" in rc.conf and reboot. If the problem goes away > after that, then you'll know. > > -- > | Jeremy Chadwickjdc at parodius.com | > | Parodius Networking http://www.parodius.com/ > | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB > | > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: apache problems
Thanks for the reply I'm having some mail problems as well, today is not my day. I'll remove all the stuff you mentioned and change back to 4BSD Will I have to recompile all the ports as well? I don't think its a PF problem because I have used this rule set of mine for a few years with no problems at all, but I'll recheck that just to make sure. Now for the mail problem I'm having its got to do with postfix sending mail from any ip address and not from the one that I want it to, but thats a later problem and on another box, I first want to get this apache thing sorted.. On Thu, August 16, 2007 20:07, Jeremy Chadwick wrote: > On Thu, Aug 16, 2007 at 07:28:24PM +0200, Reinhold wrote: > >> Hi >> > > Hello. First off, you sent mail to the list twice. I don't know why, > but you did. Be patient. :-) > >> I am having some problems with apache22 on my box. What happens is, >> when I'm viewing loads and loads of pages, apache will stop responding >> untill I restart it again. This normally happens when the free memory >> shown by top gets to about +- 100MB. > > I'm guessing that might be due to you using the ULE scheduler in your > kernel. Try switching back to 4BSD and see if that fixes it. > >> I'm also getting this error when I do a gracful restart of apache >> [Thu Aug 16 05:12:16 2007] [warn] (22)Invalid argument: Failed to enable >> the 'httpready' Accept Filter [Thu Aug 16 05:12:16 2007] [warn] >> (22)Invalid argument: Failed to enable >> the 'httpready' Accept Filter >> >> and in my /boot/loader.conf I have added accf_data_load="YES" >> accf_http_load="YES" > > Remove those. Here's why: > > > The apache rc.d startup script automatically will load accf_http.ko. > I also believe if that fails, Apache will try to load it. From my > experiences kldload/kldunload with accf_* is not very friendly; I've seen > where you can double-load the modules, and where you can't unload the > modules despite nothing using them. If you have them built-in to your > kernel, it gets even worse. > > AFAIK, using accf_data.ko isn't recommended. accf_http.ko on the other > hand is OK. Try not loading accf_data.ko in addition to my above > recommendation (re: 4BSD scheduler). > >> device pf device pflog device pfsync > > Finally, make sure your pf rules aren't doing anything stupid. If > ultimately you think it's a problem with pf rules, unload the pf module > and/or set pf_enable="no" in rc.conf and reboot. If the problem goes away > after that, then you'll know. > > -- > | Jeremy Chadwickjdc at parodius.com | > | Parodius Networking http://www.parodius.com/ > | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB > | > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
apache problems
ot; accf_http_load="YES" and kldstat reports this Id Refs AddressSize Name 13 0x8010 611660 kernel 21 0x80712000 718 accf_data.ko 31 0x80713000 1408 accf_http.ko When I do a proper restart I'm also getting these errors [Thu Aug 16 05:10:56 2007] [warn] child process 84880 still did not exit, sending a SIGTERM [Thu Aug 16 05:10:58 2007] [warn] child process 84880 still did not exit, sending a SIGTERM [Thu Aug 16 05:11:00 2007] [warn] child process 84880 still did not exit, sending a SIGTERM [Thu Aug 16 05:11:02 2007] [error] child process 84880 still did not exit, sending a SIGKILL In my custom kernel I have added or changed the following options SCHED_ULE options SMP options IPI_PREEMPTION options SC_DISABLE_REBOOT options LINPROCFS #options ACCEPT_FILTER_DATA #options ACCEPT_FILTER_HTTP device mptable # Enable PF device pf device pflog device pfsync options ALTQ options ALTQ_CBQ options ALTQ_RED options ALTQ_RIO options ALTQ_HFSC options ALTQ_PRIQ options ALTQ_NOPCC if any other info is needed, please let me know Please help me to fix this problem Thanks Reinhold ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
apache problems
ot; accf_http_load="YES" and kldstat reports this Id Refs AddressSize Name 13 0x8010 611660 kernel 21 0x80712000 718 accf_data.ko 31 0x80713000 1408 accf_http.ko When I do a proper restart I'm also getting these errors [Thu Aug 16 05:10:56 2007] [warn] child process 84880 still did not exit, sending a SIGTERM [Thu Aug 16 05:10:58 2007] [warn] child process 84880 still did not exit, sending a SIGTERM [Thu Aug 16 05:11:00 2007] [warn] child process 84880 still did not exit, sending a SIGTERM [Thu Aug 16 05:11:02 2007] [error] child process 84880 still did not exit, sending a SIGKILL In my custom kernel I have added or changed the following options SCHED_ULE options SMP options IPI_PREEMPTION options SC_DISABLE_REBOOT options LINPROCFS #options ACCEPT_FILTER_DATA #options ACCEPT_FILTER_HTTP device mptable # Enable PF device pf device pflog device pfsync options ALTQ options ALTQ_CBQ options ALTQ_RED options ALTQ_RIO options ALTQ_HFSC options ALTQ_PRIQ options ALTQ_NOPCC if any other info is needed, please let me know Please help me to fix this problem Thanks Reinhold ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
apache problems
ot; accf_http_load="YES" and kldstat reports this Id Refs AddressSize Name 13 0x8010 611660 kernel 21 0x80712000 718 accf_data.ko 31 0x80713000 1408 accf_http.ko When I do a proper restart I'm also getting these errors [Thu Aug 16 05:10:56 2007] [warn] child process 84880 still did not exit, sending a SIGTERM [Thu Aug 16 05:10:58 2007] [warn] child process 84880 still did not exit, sending a SIGTERM [Thu Aug 16 05:11:00 2007] [warn] child process 84880 still did not exit, sending a SIGTERM [Thu Aug 16 05:11:02 2007] [error] child process 84880 still did not exit, sending a SIGKILL In my custom kernel I have added or changed the following options SCHED_ULE options SMP options IPI_PREEMPTION options SC_DISABLE_REBOOT options LINPROCFS #options ACCEPT_FILTER_DATA #options ACCEPT_FILTER_HTTP device mptable # Enable PF device pf device pflog device pfsync options ALTQ options ALTQ_CBQ options ALTQ_RED options ALTQ_RIO options ALTQ_HFSC options ALTQ_PRIQ options ALTQ_NOPCC if any other info is needed, please let me know Please help me to fix this problem Thanks Reinhold ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Symbol Wireless Card
Im trying to get my Symbol Spectrum24 Wireless card to work ( It worked about 3 months ago, Don't know what I did then to make it work ). In my /etc/pccard.conf I have card "Symbol Technologies" "LA4111 Spectrum24 Wireless LAN PC Card" config auto "wi" ? insert /etc/pccard_ether $device start remove /etc/pccard_ether $device stop When I ping my server 192.168.1.1 I get "Host is down", with a tcpdump I see it talking, but don't know what to make of it: TCPDUMP 13:40:29.847685 arp who-has 192.168.1.1 (72:70:61:0:0:c) tell 192.168.1.40 13:40:29.850384 arp reply 192.168.1.1 is-at 0:80:c6:f8:cb:b0 13:40:30.372223 802.1d config c000.00:07:4f:13:3b:40.800e root c000.00:07:4f:13: 3b:40 pathcost 0 age 0 max 20 hello 2 fdelay 15 13:40:30.643692 arp who-has 192.168.1.1 (2e:2f:30:31:32:33) tell 192.168.1.40 13:40:30.646372 arp reply 192.168.1.1 is-at 0:80:c6:f8:cb:b0 Any help would be great.. Ohh it's running -STABLE as of 03/21/02, I got the same results from 4.5-Release. Thanks, Dylan ( I hope this is not a repost!!! ) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
