Re: WiFi hotspot keeps dropping

2020-06-20 Thread D'Arcy Cain
On 2020-06-19 12:13, Adrian Chadd wrote:
> If I can't keep it running can someone suggest a system test I can do to
> decide that hostapd needs to be restarted?
> 
> So, you shouldn't need to restart hostapd after a stuck beacon. It
> should recover.

That was my understanding.

> One thing I found was lots of log entries like this:
> 
> ath0: stuck beacon; resetting (bmiss count 4)
> 
> So there's plenty of reasons for a stuck beacon. I've mostly fixed the
> programming problems and now it's typically really busy air. 
>
> From reading up on that it seems that it is just a cosmetic warning.
> Could this be an indication of something that is killing the hotspot?
>
> It's possible but it shouldn't be killing the interface.
> 
> What you could try is forcing a full reset every time the NIC needs to
> reset.
> 
> sysctl dev.ath.0.hal.force_full_reset=1

I have done this.  It still happened.  Note that hostapd is still
running when I restart it.

> What I suggest you do is recompile your kernel/modules with the
> following options:
> 
> IEEE80211_DEBUG
> ATH_DEBUG
> AH_DEBUG
> ATH_DIAGAPI
> 
> Then you'll get access to a lot more debugging tools (ie, the stuff in
> tools/tools/ath/) which we can use to diagnose what's going on.
I like to run a generic kernel and use loadable modules so I don't
compile my own kernel yet.  I will try that if I can't fix it any other way.

-- 
D'Arcy J.M. Cain  |  Democracy is three wolves
http://www.druid.net/darcy/|  and a sheep voting on
+1 416 788 2246 (DoD#0082)(eNTP)   |  what's for dinner.
IM: da...@vybenetworks.com, VoIP: sip:da...@druid.net



signature.asc
Description: OpenPGP digital signature


[Bug 247439] ue(4): Rename to match it's driver (cdce or uether)

2020-06-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247439

Kubilay Kocak  changed:

   What|Removed |Added

 CC||n...@freebsd.org
   Keywords||needs-patch, needs-qa
Summary|network interface "ue"'s|ue(4): Rename to match it's
   |name should be same as it's |driver (cdce or uether)
   |driver (cdce or uether) |
 Status|New |Open

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 247439] ue(4): Rename to match it's driver (cdce or uether)

2020-06-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247439

Hans Petter Selasky  changed:

   What|Removed |Added

 CC||hsela...@freebsd.org

--- Comment #1 from Hans Petter Selasky  ---
Hi,

The line you are looking for is:

if_initname(ifp, "ue", ue->ue_unit);

I'm not sure if it will solve anything to have different names for the USB
ethernet adapters. They are currently named the same because these are USB
devices, and so it is easy to recognize them.

If you want to map ueX to a given USB port, you need to look at the "sysctl -a"
output. There is something called %parent and %location which will help you. 

Check this out:

net.ue.0.%parent: axge0

--HPS

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 174087] [tcp] Problems with ephemeral port selection

2020-06-20 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=174087

Mark Linimon  changed:

   What|Removed |Added

 Status|Open|In Progress
 CC||lini...@freebsd.org
URL||https://reviews.freebsd.org
   ||/D24781
   Assignee|n...@freebsd.org |kar...@freebsd.org

--- Comment #7 from Mark Linimon  ---
Mike believes that the following commits should fix the issue:

  https://svnweb.freebsd.org/base?view=revision&revision=361228
  https://svnweb.freebsd.org/base?view=revision&revision=361231

which were as a result of https://reviews.freebsd.org/D24781 (which Mike had
seen before noticing this PR).

To submitter: I know that this is a very old bug, but, just in case, are you in
a position to be able to test and verify?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"