On 28/08/2010, at 12:19 AM, Christiano F. Haesbaert wrote:
Hi there,
I'm willing to buy a SATA controller (PCI) with at least 4 ports.
I'll put it on an Alpha 500au or a Sun Ultra 5, if it doesn't work
out, on an old intel.
Any recommendations ?
sili(4). you might have more success with
Hi,
according to several sources [1,2,3] 802.1x (WPA enterprise) is not
supported with native tools.
The wpa_supplicant package doesn't help either, since it doesn't
support WPA.
Is there *any* other solution how I could get this to work on a laptop?
I'm even considering a qemu session with
On 2010-08-29, Robert info...@die-optimisten.net wrote:
according to several sources [1,2,3] 802.1x (WPA enterprise) is not
supported with native tools.
The wpa_supplicant package doesn't help either, since it doesn't
support WPA.
Is there *any* other solution how I could get this to work on
If you can explain what you're actually trying to do, rather
than talk about how you're thinking of accomplishing it, maybe
someone can suggest a way.
On 2010-08-28, Jean-Francois jfsimon1...@gmail.com wrote:
Good evening,
Is it possible to redirect to an IF or at least an IP range such as
On Sun, 29 Aug 2010 10:02:33 + (UTC)
Stuart Henderson s...@spacehopper.org wrote:
this last option seems the most straightforward, but you would
specifically need something that can act as a client bridge (sometimes
also called STA mode) and can authenticate with 802.1x in that mode
Si no es este tu correo o si deseas cancelar la suscripcisn haz clic aqum
Si no puedes visualizar este correo, haz clic aqum
[IMAGE]
[IMAGE]
[IMAGE]
[IMAGE]
Cuarto Informe de Gobierno
Hola:
www.informe.gob.mx
[IMAGE]
Mensaje del Presidente
[IMAGE]
[IMAGE]
[IMAGE]
[IMAGE]
Si no es
A panic occurred to one of our servers. I never experienced this panic
before, but I have to say that we recently upgraded that server from
OpenBSD 4.4 to 4.7.
The error was:
/var: bad dir ino 3 at offset 81920: mangled entry
panic: bad dir
I have done two photos of the panic and of the
Hello,
I would like to redirect particular ports on the sub-network, not only on one
ip adress of the subnetwork.
Taking an example, I would like some software that listen to ports on different
machines with different ip adress without having to change the pf.conf rules
each time it is
Hi,
One question, I run gnome on openbsd 4.7 and apparently there is no reason to
keep the following rule since nothing listens to those ports on my machine.
block in on ! lo0 proto tcp to port 6000:6010
I verified with netstat that there is nothing listening to any of tcp ports in
the range
On Sun, 29 Aug 2010 11:12:34 +0200
Robert info...@die-optimisten.net wrote:
Hi,
according to several sources [1,2,3] 802.1x (WPA enterprise) is not
supported with native tools.
The wpa_supplicant package doesn't help either, since it doesn't
support WPA.
Other suggestions?
One of the
On Sun, Aug 29, 2010 at 02:05:40PM +0200, Jean-Francois wrote:
Hello,
I would like to redirect particular ports on the sub-network, not only on one
ip adress of the subnetwork.
Taking an example, I would like some software that listen to ports on
different
machines with different ip
Jean-Francois jfsimon1...@gmail.com writes:
I would like to redirect particular ports on the sub-network, not only on one
ip adress of the subnetwork.
'on the sub-network' is a little too fuzzy, but if you can populate a
table with your probable target addresses something like
On Sun, 29 Aug 2010 14:07:15 +0100
Kevin Chadwick ma1l1i...@yahoo.co.uk wrote:
One of the mags on bsdmag.org has an interview with Damien Bergamini
(shown on it's contents page) who did the/some of the wpa for OpenBSD.
I believe he describes why WPA enterprise is problematic and not so
On August 28, 2010 11:35 PM Bret S. Lambert wrote:
39: pass out quick log from 172.16.0.1 route-to (em0 192.168.0.1)
$ traceroute -s 172.16.0.1 -n google.com
Tcpdump pflog0 output:
Aug 28 21:41:11.225656 rule 39/(match) pass out on em1: 172.16.0.1.48096
74.125.45.147.33449: udp 12
I don't understand. Why are you not running a default deny setup?
On 29 August 2010 14:45, Jean-Francois jfsimon1...@gmail.com wrote:
Hi,
One question, I run gnome on openbsd 4.7 and apparently there is no reason to
keep the following rule since nothing listens to those ports on my machine.
ropers rop...@gmail.com writes:
I don't understand. Why are you not running a default deny setup?
Maybe because this pf.conf is the default one.
On 29 August 2010 14:45, Jean-Francois jfsimon1...@gmail.com wrote:
Hi,
One question, I run gnome on openbsd 4.7 and apparently there is
no
Hello misc@,
I have a problem with uplcom(4). Whenever I connect to a remote terminal
with cu -l /dev/ttyU0, it hangs after a few seconds (usually under 2
minutes).
I tried various settings and still have the same issue :
- using /dev/cuaU0
- setting speed 9600 or 19200
- connecting to a
I made a mistake, in fact I deny access by default even to those ports that
are normally available from localhost.
I did this because I see nothing listening to those ports, and gnome is
running through sockets.
I just don't understand why the range tcp 6000:6010 shall be available from
2010/8/29, Denis Fondras open...@ledeuns.net:
I have a problem with uplcom(4). Whenever I connect to a remote terminal
with cu -l /dev/ttyU0, it hangs after a few seconds (usually under 2
minutes).
I've seen way too many faulty/misbehaving uplcom's. Have you tried
different piece of hardware?
Jean-Francois jfsimon1...@gmail.com writes:
I just don't understand why the range tcp 6000:6010 shall be available from
localhost.
To speak with X using tcp. If you launch X with the option -nolisten
tcp, you can block it.
If you have set skip on lo in your pf.conf, every ports will be open
we'll happily take diffs though.
On 29/08/2010, at 4:14 AM, Jonathan Gray wrote:
There is currently no support for native sata hotplug in OpenBSD,
so this is expected.
On Sat, Aug 28, 2010 at 07:31:26PM +0200, Gerald Holl wrote:
Hello,
I'm using OpenBSD 4.7 on an IBX 530 Intel Atom[1]. If
Congreso Nacional de Negociacisn y Rentabilidad en COMPRAS
Guadalajara 27 y 28 de Septiembre
Monterrey 23 y 24 de Septiembre
Mexico DF 30 de Septiembre y 01 de Octubre
Este congreso le ofrece los principios, criterios y directrices mas
efectivos para establecer
alianzas poderosas que incrementen
22 matches
Mail list logo
