headers
Brian Feldman | 1 Jun 2004 01:17
Picon
Favicon

Re: Project Evil APs

On Mon, May 31, 2004 at 09:48:55AM +0100, Doug Rabson wrote:
> On Sunday 30 May 2004 20:06, Bill Paul wrote:
> > > > <jedi mind trick>
> > > > You want to use ad-hoc mode. You don't want to bother me with
> > > > silly questions about hostap mode because it doesn't really let
> > > > you do anything you can't do with ad-hoc mode anyway. Use IPSec
> > > > with ad-hoc mode and you'll probably get better security than any
> > > > access point can give you in the first place.
> > > > </jedi mind trick>
> > >
> > > Probably. Only if I can get this silly little WinME laptop to do
> > > ad-hoc as well though. The main reason for doing this is that my AP
> > > died and my gf wants to use the laptop in the garden :-).
> >
> > Did you... read the little booklet that came with the card in your
> > gf's computer? Sometimes there's a special control panel snap-in or
> > custom utility to configure the card. If not, go to the control
> > panel, click "system" and look for the device manager. Select the
> > wireless device and check for driver settings. You might be able to
> > set ad-hoc mode there.
> 
> I managed to find new drivers for the laptop's card and it works fine 
> now. Now I just have to put some kind of tunnelling thing together (I 
> guess pptp is the only option for WinMe) so that the neighbours can't 
> 'borrow' our service.

Doing a Windows-style VPN is pretty darn easy on FreeBSD:
1. Install ports/net/poptop.
2. Set up pptpd.conf (pretty much just the remoteip and localip options).
3. Set up ppp(8) with a "pptp" section, much like the following:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Drew Broadley | 1 Jun 2004 02:21
Picon

Re: ndis - NetGear HA501 - kernel panic

Bump.

Drew Broadley wrote:

> This is what comes up when I  use the XP and 2k drivers for the 
> NetGear HA501 802.11a card and insert:
> >>>>>>>>>>>>>>>>>>>
> ndis0: <NETGEAR HA501 Wireless Adapter> mem 0x80000000-0x8000ffff irq 
> 11 at device 0.0 on cardbus0
> ndis0: [GIANT-LOCKED]
> >>>>>>>>>>>>>>>>>>>
>
> This is when I perform "ifconfig ndis0 up SSID GUYAVE"
> >>>>>>>>>>>>>>>>>>>
> can't re-use a leaf (MapRegisters)!
> can't re-use a leaf (clist)!
> can't re-use a leaf (QoS)!
> can't re-use a leaf (tpc)!
> can't re-use a leaf (TurboEnable)!
> can't re-use a leaf (beaconInterval)!
> can't re-use a leaf (bssType)!
> can't re-use a leaf (privacyInvoked)!
> can't re-use a leaf (sleepMode)!
> can't re-use a leaf (FragThreshold)!
> can't re-use a leaf (RTSThreshold)!
> can't re-use a leaf (rateCtrlEnable)!
> can't re-use a leaf (SmeEnable)!
> can't re-use a leaf (TransmitRate)!
> can't re-use a leaf (bkScanEnable)!
> ndis0: NDIS API version: 5.0
(Continue reading)

Permalink | Reply | 0 comments |
headers
Christian S.J. Peron | 1 Jun 2004 02:30
Picon
Favicon

raw socket+prison warning

For those of you not subscribed to src-committers <at> FreeBSD.org,
cvs-src <at> FreeBSD.org or cvs-all <at> FreeBSD.org, I just committed
a warning note in jail(8) for the security.jail.allow_raw_sockets
sysctl MIB about the risks of enabling raw sockets in prisons.

Because raw sockets can be used to configure and interact
with various network subsystems, extra caution should be
used where privileged access to jails is given out to
untrusted parties. As such, by default this option is disabled.

A few others and I are currently auditing the kernel
source code to ensure that the use of raw sockets by
privledged prison users is safe.

--
Christian S.J. Peron
csjp <at> FreeBSD.org
FreeBSD committer
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Doug Ambrisko | 1 Jun 2004 05:51

Re: Lockups with Intel ICH5 SATA

Tony Byrne writes:
| In recent weeks my FreeBSD current box has been experiencing frequent
| hard lockups.  Seldom a day goes by without the machine freezing
| solid.  My hunch is that this is somehow related to the onboard Intel
| ICH5 controller and SATA HD, because during reboot after a lockup,
| the machine often complain of a DMA timeout that hangs the box
| while reading from the SATA drive.

FYI, if the drive has a media error or does a spin down/spin up sequence
things will hang since the ata driver currently doesn't deal with the
SATA PHY registers.  After a while of ignoring various issues flagged
in these bits your system will lock up solid on a inb/outb to the controller.

Doug A.
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 2 comments |
headers
Drew Broadley | 1 Jun 2004 06:06
Picon

Re: ACPI event testing needed

Kevin Oberman wrote:

>>Date: Fri, 28 May 2004 00:38:32 -0700 (PDT)
>>From: Nate Lawson <nate <at> root.org>
>>Sender: owner-freebsd-current <at> freebsd.org
>>
>>I've just finished a lot of work on acpi events (GPEs).  These drive
>>things like the lid switch and device wake capabilities.  If your system
>>works for suspend/resume, please make sure it still behaves correctly over
>>multiple suspend/resume cycles.  If you're feeling adventurous, try the
>>new wake sysctls:
>>
>>sysctl dev | grep wake
>>
>>By setting them to 0 or 1, you can enable/disable a device waking the
>>system.  Note that non-ACPI devices are still not properly hooked in here
>>so they won't work (i.e. sio or modems).  But you can change the lid
>>independently of the sleep button, for example.
>>
>>Also, please be sure that your system still powers off correctly when
>>shutdown.  I may have fixed some systems that didn't power off correctly
>>as well.
>>    
>>
I did a cvsup and buildworld earlier today and I cannot shutdown -p  my 
machine anymore. It just hangs on "Uptime: xh xm xs". (I used to be able 
to shutdown -p)

I also cannot go into standby, nor suspend/resume. But these were not 
working prior
(Continue reading)

Permalink | Reply | 3 comments |
headers
Mark Johnston | 1 Jun 2004 06:42
Picon

Yet another late src summary

It seems like I'm on a bad trend these days of having nothing to offer on 
summary day except delays and apologies.  Here's another of each.  I've got 
some FreeBSD time set aside tomorrow evening, and after that, I hope to be 
back on track.  Thanks for bearing with me.

Mark
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Scott Long | 1 Jun 2004 07:19
Picon
Favicon

Re: Lockups with Intel ICH5 SATA

Doug Ambrisko wrote:
> Tony Byrne writes:
> | In recent weeks my FreeBSD current box has been experiencing frequent
> | hard lockups.  Seldom a day goes by without the machine freezing
> | solid.  My hunch is that this is somehow related to the onboard Intel
> | ICH5 controller and SATA HD, because during reboot after a lockup,
> | the machine often complain of a DMA timeout that hangs the box
> | while reading from the SATA drive.
> 
> FYI, if the drive has a media error or does a spin down/spin up sequence
> things will hang since the ata driver currently doesn't deal with the
> SATA PHY registers.  After a while of ignoring various issues flagged
> in these bits your system will lock up solid on a inb/outb to the controller.
> 
> Doug A.

Can you explain this a bit more?  Is the driver ignoring the interrupt
and thus allowing an interrupt storm?  Or is it ACK'ing the interrupt,
but the ICH5 controller is expecting a certain further response that
it's not getting?  Or is it masking the interrupt entirely which in turn
exposes a flaw in the ICH5 hardware?

Scott
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Gleb Smirnoff | 1 Jun 2004 08:36
Picon

Re: [HEADS-UP] mbuma is in the tree

  Bosko,

On Mon, May 31, 2004 at 02:51:01PM -0700, Bosko Milekic wrote:
B>   In order to avoid having to type everything again, I'll refer
B>   to the commit log.  PLEASE READ IT IN FULL:
B> 
B> Bring in mbuma to replace mballoc.
B> 
B> mbuma is an Mbuf & Cluster allocator built on top of a number of
B> extensions to the UMA framework, all included herein.

Have you done any performance tests? How this new allocator affects
network performance?

How stable is it? :) Yesterday I was planning to upgrade CURRENT on
my production router. Should I do it?

--

-- 
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 3 comments |
headers
Wilkinson, Alex | 1 Jun 2004 08:59
Picon

Re: SCHED_BSD vs SCHED_ULE ...

	On Sat, May 29, 2004 at 08:41:53PM -0300, Marc G. Fournier wrote:
	
	Is there a circumstance where the older SCHED is better then ULE?
	
	Or is the older one something that will eventually just be removed 
	altogether?
	
	If the older does have areas in which it is the better, are there any docs 
	comparing the two?

An article was written here:

"Scheduler Performance: ULE vs. 4BSD"

http://www.thejemreport.com/modules.php?op=modload&name=News&file=article&sid=116&mode=thread&order=0&thold=0

 - aW	
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Doug Rabson | 1 Jun 2004 10:16

Re: Project Evil APs

On Tuesday 01 June 2004 00:17, Brian Feldman wrote:
> On Mon, May 31, 2004 at 09:48:55AM +0100, Doug Rabson wrote:
> > On Sunday 30 May 2004 20:06, Bill Paul wrote:
> > > > > <jedi mind trick>
> > > > > You want to use ad-hoc mode. You don't want to bother me with
> > > > > silly questions about hostap mode because it doesn't really
> > > > > let you do anything you can't do with ad-hoc mode anyway. Use
> > > > > IPSec with ad-hoc mode and you'll probably get better
> > > > > security than any access point can give you in the first
> > > > > place.
> > > > > </jedi mind trick>
> > > >
> > > > Probably. Only if I can get this silly little WinME laptop to
> > > > do ad-hoc as well though. The main reason for doing this is
> > > > that my AP died and my gf wants to use the laptop in the garden
> > > > :-).
> > >
> > > Did you... read the little booklet that came with the card in
> > > your gf's computer? Sometimes there's a special control panel
> > > snap-in or custom utility to configure the card. If not, go to
> > > the control panel, click "system" and look for the device
> > > manager. Select the wireless device and check for driver
> > > settings. You might be able to set ad-hoc mode there.
> >
> > I managed to find new drivers for the laptop's card and it works
> > fine now. Now I just have to put some kind of tunnelling thing
> > together (I guess pptp is the only option for WinMe) so that the
> > neighbours can't 'borrow' our service.
>
> Doing a Windows-style VPN is pretty darn easy on FreeBSD:
(Continue reading)

Permalink | Reply | 0 comments |

Gmane