ispyisail wrote:The real work is done by others, I just push a script.
The people doing the real work I suspect would get a little annoyed at me getting praise for their work.
Well, then I simply extend my gratitude to everybody involved, making those 'unofficial' updates happen
Unfortunately though, I am still having quite a few weird WiFi problems, I can't really make sense of and therefore am asking for help from people, much more knowledgeable in that area, than I currently still am.
Netgear WNR2000v3 (F/W upgraded from V220.127.116.11 to V18.104.22.168, just to make sure) is the AP/WAN Gateway (IP: 192.168.1.1), connected to a cable modem.
Buffalo WZR-HP-G300NH (1.5.X (Built 20131030-1936 git@8a56193); WAN IP Address: 192.168.1.11) connects to Netgear in Wireless Mode: AP+Client (LAN IP Address: 192.168.11.1).
Connect Via: Wireless (DHCP | Static IP)
Access Point SSID: Gargoyle (broadcasting SSID: disabled)
SSID Joined By Client: NETGEAR
1.): multiple times per day, traffic between the Buffalo and the Netgear gets interrupted, even though doing a Connection->Basic: Re-Scan shows, that the Netgear SSID is still around with a signal strength usually between some 47...56% and still using the same channel as before.
AFAIKT, there is no difference in using DHCP or connecting via Static WiFi IP to the Netgear.
I also can't notice any difference of the setting: "Wan Ethernet Port: En-|Disabled"
I can ping from WiFi-LAN both sides of the Buffalo (168.1.11 & 168.11.1), while the Netgear (168.1.1) remains silent.
Q1.1): [x] Drop Ping From WAN Side: Why do I still get a WiFi response from 168.1.11? Or does this setting only relate to the Ethernet WAN port?
A "Save Changes" from the Connection->Basic or ->Routing screen, usually re-establishes the link, if not, I have to Reboot.
Q1.2): Why doesn't Gargoyle reconnect automatically, when the IP connection breaks?
Q1.3): Is there another way to kickstart the apparent broken WiFi link between the Netgear and Buffalo through the WiFi LAN side, other than as described above?
2.): After doing a "Save Changes" as described for Q1.2) it occasionally happens, that the Buffalo's radio seems to remain silent, since it doesn't show up in any iwlist scans from 2 laptops or in any available-WiFi scans of 3 Android smart phones.
Q2): shouldn't the Buffalo's radio work all the time as AP for LAN WiFi clients, no matter what is going on with the WAN WiFi link between it and the Netgear, or is there a dependency?
3.) During the last 2 nights the temp dropped slightly below freezing and the Buffalo is mounted to an outside wall inside a wooden garage.
Q3): Is there anything known about special temperature sensitivity of the WZR-HP-G300NH, causing it to have its radio silenced, when "Save Changes" as described for Q1.2) was necessary?
With last night having been the colder one (-6C), the whole thing must have 'frozen up', when I additionally made an actual change in the static WAN IP from 168.1.9 to 168.1.11 @ around 1:30h, when the IP flow got stuck once again, since neither a scheduled Reboot @ 5h this morning was performed, nor was I able to connect to it via Ethernet.
I had to pull the power plug on it, to force a hard reset. Really strange. Just a coincidence?
Now it is up to you, smart readers, to flood me with your expert suggestions and explanations