On 5 Jan 2015 22:21, Stefan Sperling wrote:
> Hmm, that makes a driver bug more likely.
>
> Can you try with FreeBSD? Their driver has essentially become the upstream
> version of run(4). If their driver works better we might be able to fix ours.
Yes I will, but on Satuarday the earliest. I wil
On Mon, Jan 05, 2015 at 08:20:28PM +0100, Clemens Goessnitzer wrote:
> driver to try getting a connection for a longer time? The following shows
> that run0 gets a connection/handshake, but after the "no link...
> sleeping". And why would it try getting and successing getting a connection
>
On 01/05/15 19:43, Stefan Sperling wrote:
This shows a scan.
I don't see an association in there. You should also see WPA handshake
on a successfull connect messages since your network uses WPA.
In any case this should allow you to see exactly when the driver gets
and drops link. These messages
On Mon, Jan 05, 2015 at 07:11:07PM +0100, Clemens Goessnitzer wrote:
> On 01/05/15 18:25, Stefan Sperling wrote:
> >Not sure. Perhaps check if deactivating power-saving on the AP is possible.
> >I don't believe the run(4) driver has support for it.
>
> Should be deactivated now.
>
> >Can you shar
On 01/05/15 18:25, Stefan Sperling wrote:
Not sure. Perhaps check if deactivating power-saving on the AP is possible.
I don't believe the run(4) driver has support for it.
Should be deactivated now.
Can you share information shown in dmesg after 'ifconfig run0 debug' while
you're using the ne
On Mon, Jan 05, 2015 at 12:07:05PM +0100, Clemens Goessnitzer wrote:
> On 01/05/15 11:39, Stefan Sperling wrote:
> >Try setting the AP to a 2.4 Ghz channel (1-13) and see if that improves
> >things. 11a (5Ghz) has a shorter range than 11b/g.
> >
>
> Still the same behavior. Could this be the APs f
Is your SSID hidden? I had the same problem on 5.6-stable when the SSID was
hidden. Thankfully I could change the AP behaviour. No more problems since. hth
No, not hidden, since this is absolutely useless.
Is your SSID hidden? I had the same problem on 5.6-stable when the SSID
was hidden. Thankfully I could change the AP behaviour. No more problems
since. hth
Am 05.01.2015 um 11:30 schrieb Clemens Goessnitzer:
Hello everyone,
I am running -current as of end-Decemberish. I am using a Ralink c
On 01/05/15 11:39, Stefan Sperling wrote:
Try setting the AP to a 2.4 Ghz channel (1-13) and see if that improves
things. 11a (5Ghz) has a shorter range than 11b/g.
Still the same behavior. Could this be the APs fault? I am getting an
Intel NUC soon and will set it up as an OpenBSD wireless A
On Mon, Jan 05, 2015 at 11:30:30AM +0100, Clemens Goessnitzer wrote:
> Hello everyone,
>
> I am running -current as of end-Decemberish. I am using a Ralink chip
> powered wireless adapter (chip: Ralink RT3052), which should be supported by
> the run driver. However, I get
>
> # sh /etc/netstart
Hello everyone,
I am running -current as of end-Decemberish. I am using a Ralink chip
powered wireless adapter (chip: Ralink RT3052), which should be
supported by the run driver. However, I get
# sh /etc/netstart run0
run0: no link ... sleeping
when I try to start the network (also
11 matches
Mail list logo
