what might be causing
this? (e.g. misconfiguration of some sort)
--
Bill Moffitt
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
My understanding is that UBNT has an ASIC in their devices to help with
the timing of the TDMA mode. My suspicion is that, without that ASIC,
"software only" TDMA would probably not be precise enough to bring benefit.
Does anyone have a better understanding of this?
-Bill
_
has a MAC address starting with
68:72, which is not new (in the past, UBNT has "signaled" a change by
changing the MAC address prefix). It is still an "XM" device (only the
M5 seems to have moved to "XW").
Has anyone else seen this? Is there a fix at hand?
--
B
I wasn't able to download the trunk nightlies. It looks like there's a
nice, slick, new web interface, but no builds in some areas
(particularly the AR7xx generic platform). Is it just a failed build or
a problem in the webpage?
--
Bi
any new ones at the moment, and probably won't for a
few weeks. And I don't recall what the new ones I was testing came with.
--
Ticket URL: <https://dev.openwrt.org/ticket/20982#comment:32>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
--
Bill Moffitt
I just downloaded CC for the Rocket M2
(openwrt-15.05-ar71xx-generic-ubnt-rocket-m-squashfs-factory.bin) and
could not get it to work.
Specifically, the lights worked, but I could not obtain any response
(ping, ssh - I even tried telnet) at 192.168.1.1 from the Ethernet port.
I saw Ben West'
I have been busy with other things, but I finally got a shipment of
brand-new PicoStations (XM, identical to Bullet) here and tried to flash
both the trunk builds of OpenWRT and LEDE on them.
I'm getting the same error I did some months back:
sent DATA
received ERROR
Error code 2: Firmware c
m.lede-project.org/t/new-ubiquiti-loco-m2-xw/5760/5> or
reply to this email to respond.
In Reply To
[bmoffitt] bmoffitt <http://forum.lede-project.org/users/bmoffitt>
Bill Moffitt <http://forum.
t; in one action. At
some point we would probably change the default behavior from "all
closed" to "all open."
However, for the moment, I would argue that the "rightness" of following
expected behavior is greater than the "rightness" of delivering the
t.org>
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
--
Bill Moffitt
Ayrstone Productivity
http://ayrstone.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>Message: 1
>Date: Tue, 07 Oct 2014 12:35:25 +0200
>From: Felix Fietkau
>To: mailinglist
>Subject: Re: [OpenWrt-Devel] Q: mac80211: defailt distance-settings 0
>Message-ID: <5433c1ed.5050...@openwrt.org>
>Content-Type: text/plain; charset=windows-1252
>
>On 2014-10-07 08:15, Bastian Bittorf w
e at bmoff...@ayrstone.com.
As a side note, I tried selling them on ebay using "running OpenWRT,
not Ubiquiti's firmware" as a differentiation point. I did not even
get a bid, even setting the starting price at $20.
On Fri, Apr 28, 2023 at 2:19 PM Bill Moffitt wrote:
>
> I ha
I have been using an older version of OpenWRT on my E110N; I loaded up
the latest release to see if it would fix some "LOST BEACON" problems.
Unfortunately, it didn't even boot, so I broke out the serial cable,
busted open the radio, and connected it. Here's what I captured:
U-Boot 1.1.4-ge619c1
I have been using an older version of OpenWRT on my E110Ns; I loaded up
the latest release to see if it would fix some "LOST BEACON" problems.
Unfortunately, it didn't even boot (went into a bootloop), so I broke
out the serial cable,
busted open the radio, and connected it. Here's what I captured
hich one was it? CF-E110N is supported since
> 19.07...), then upgrade one major release at a time (first 21.02, then
> 22.03, until 23.05). When does this issue appear, if it does?
>
> Best,
>
> Roger
>
> El 23/10/23 a les 23:54, Bill Moffitt ha escrit:
> > I have been usi
Trying to set up meshing on Comfast EW-72 v2 - my first time working
with the Mediatek chipset. I have played around with meshing quite a
bit on Atheros chips.
The interesting problem is that it seems to work in v23.05.2 and
v23.05.3 with wpad-basic-mbedtls, but, when I swap it out for
wpad-mesh (
wpa_supplicant[1211]: Set new
config for phy phy0
So it definitely looks like a problem with wpa_supplicant.
root@OpenWrt:~# wpa_supplicant -v
wpa_supplicant v2.11-devel
Again, any suggestions appreciated.
-Bill
On Fri, Jun 21, 2024 at 8:42 AM Bill Moffitt wrote:
>
> Trying to set up m
wpa-supplicant, but I'm not sure even where to look for more information
at this point.
All help gratefully accepted...
--
Bill Moffitt
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
On March 26, 2014 11:29:59 AM PDT, Sergey Ryazanov
wrote:
>2014-03-26 9:13 GMT+04:00 Bill Moffitt :
>> It's clear that SOMETHING is getting time-limited, but I have
>distance=0 and
>> dissassoc_low_ack=0 on both the AP and the station, and I'm not sure
>what
>
Confirming that the patch seems to work - ports correct, all lights work
correctly.
--
Bill Moffitt
Ayrstone Productivity
http://www.ayrstone.com
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman
dmesg) says,
"wifi%d ath_attach failed: -22"
I don't know enough about MadWifi and the HAL to even debug this.
Any help will be appreciated!
--
Bill Moffitt
Ayrstone Productivity
http://www.ayrstone.com
___
openwrt-devel mailing lis
our speedy reply. I agree the best short-term workaround
is to do a runtime patch of the regdomain, but how, practically, to do it?
I'm very open to suggestions - I'm currently dead in the water.
-Bill
--
Bill Moffitt
Ayrstone Productivity
htt
products in OpenWRT.
If you're qualified and interested (or know someone who might be),
please contact me at bmoff...@ayrstone.com.
Thanks,
Bill
--
Bill Moffitt
Ayrstone Productivity
http://www.ayrstone.com
___
openwrt-devel mailing list
openwrt-
workaround I can think of is to runtime-patch
the in-memory copy of the radio-data in the board setup code.
~ Jow
Here's how I did it is this; first, I put the following script in /etc/
and called it regdoman-script.sh:
*Code:*
#!/bin/sh
# By Bill Moffitt - this script puts a
as OpenWRT developers, need to
be very diligent in ensuring OpenWRT "plays well" on V6 in anticipation
of this event, should it come to pass. It may be a nice opportunity for
OpenWRT to get some nice publicity by "saving the day" when the "crisis"
occurs.
--
Bill M
25 matches
Mail list logo
