Wifi 2.4ghz mode, only G+N or N, c2600 and r7800

[ActionHenk]

By the way, is there a list of characters i can't use in newer firmwares?

I had some trouble when for the first time in 1. 14 i set everything up and the dhcp server was very buggy in 1.14 because i used a = in a static hostname. It took me a day to realise i couldn't use a = in 1. 14 where as in 1.10 i could.

Like, do system>identification "hostname" and "domain" entrys have any negative effect on the network? I always used spaces or a - in 1.10.
Maybe i shouldn't?

[Lantis]

Don’t use symbols or spaces at all, that is safest.
I don’t have an audit of where symbols are safe or not. The community could compile one

[ActionHenk]

ok well did a new test with 1.15 beta, here are the results:

------------------------------------

In this try i'm gonna setup the r7800 as basic as possible.


01 connect r7800 lan to pc, nothing more connected

02 sysupgrade to gargoyle 1.15 beta

03 login and restore default settings

04 login and set password & timezone

05 set country code

06 set router ip & disable allow namecoin

07 disable all 3 ipv6 options

08 set dhcp range 1-100, 24h

09 set the first static dhcp ip by hand

10 export (copy/past) all static entry's with winscp to config/dhcp

11 set a custom dns server with pi-hole ip

12 add "dhcp-option=6,piholeIP" to etc/dnsmasq.conf

13 reboot and shutdown r7800

14 shutdown all wifi and utp clients still connected to the c7 router

15 shutdown and disconnect c7 router

16 connect utp's from wan, pihole, domoticz and pc and boot r7800 router

17 boot pihole

18 enable and set wifi in gargoyle

19 boot domoticz

20 boot 3 x esp lights

21 boot 1 x esp light

22 boot 1 x esp relay (mqtt) + 1 x nodemcu with 5 x http switched relays (cooker hood)

23 the http relays (no mqqt) on nodemcu response very strange, for the 5 relays i have setted a time delay in automation, because they need to switch in a timed sequence.
When i start the automation in domoticz, the http commands for each relay are transmitted, it looks like the http commands are lagged, and when they arive at the nodemcu, they almost all switch at the same time.

24 reboot r7800

25 boot broadlink rm mini IR transmitter

26 Again strange behaviour, some esp's constantly show up and dissapeare at the "Connected Wireless Hosts", cant reach them anymore

27 shutdown broadlink rm mini ir transmnitter

28 reboot r7800

29 problem stays, some esp's can't connect, and delays between command and light on

30 shutdown nodemcu

31 reboot r7800

32 problem stays, some esp's can't connect and sometimes when the esp's are connected, there is a huge delay between the domoticz command and lights.

33 Connected all 3 switches, NAS, pc's and camera's to the r7800, still no other wifi clients connected other then esp's and ir transmitter

34 strange enough after the previous step all esp's are now responding as they should, probably because something has changed in the network? i didn't reboot the r7800 after previous 2 steps.

35 reboot r7800

36 problem is back, some esp's dont response and looks like they can't connect to wifi untill i reboot, and then only with luck.


It looks like always the same esp's are affected, while they all have the same firmware (tasmota 13.4.0)
I could "clean wipe" and flash all the esp's with serial programmers on the headers like when i installed them, there is only one (or actually many) problem(s), i build all esp boards in lights, equipment, dryers, junctionboxes, walls, etc it would take me weeks to get them all out and flash them all in my spare time.

So if i revert back to the archer c7 with gargoyle v1.10 i have a stable network but it means i got 160mbit up and 160 mbit down max.

I think my best option for now is use the r7800 as my main router so i have 400mbit/400mbit at the wan port and 5 ghz wifi, and use a old tp link wr1043nd v2 with gargoyle v1.10 as 2.4 ghz accesspoint so i keep my stability for domotica.

[ActionHenk]

The community could compile one

Sorry, you mean compile a v1.10 gargoyle for the r7800 or c2600? Is that possible?

[Lantis]

Compile a list of allowed symbols.

Your DHCP settings sound odd to me, what IP is the router? It is weird that your DHCP range starts at 1.

[ActionHenk]

Yes, router is 101, 102 till 254 are reserved for static. So 1 till 100 are for dynamic releases.

[ActionHenk]

I think my best option for now is use the r7800 as my main router so i have 400mbit/400mbit at the wan port and 5 ghz wifi, and use a old tp link wr1043nd v2 with gargoyle v1.10 as 2.4 ghz accesspoint so i keep my stability for domotica.

Ok this is what i did, netgear r7800 with gargoyle 1.14 is running as router with all the bells and whistles, i kept both 5ghz and 2.4 ghz bands online and gave them new SSIDS, so no wireless domotica will connect on this router.

I hooked up my good old tp link wr1043n v2 with gargoyle v1.10 as "dumb" accesspoint with the "old" 2.4ghz SSID name for all domotica.
This way i don't have to change the wifi ssid settings individually in all IOT devices.

It looks like all domotica is stable for now, and i have finally 400mbit up/400mbit down. I'm happy.

I could try gargoyle 1.14 on the tp link wr1043n v2 to see if i get those problems again. If no problems ocure, then i also have the new 1.14 "shared client information" instead of a bunch of unknown devices.

Anyway, thanks all for so far! At least ive got a workable situation right now. From here i can always try other methods to get support for esp back on the r7800, without swapping routers back and forth.

----------------

A question, does the tp link wdr4300 as dumb actionpoint have any advantage over the wr1043n v2? Would it make a better dumb accesspoint? It does have external dualband antennas, the c7 has the 2.4ghz antennas internal so i think i'm better of with either the wr1043n or the wdr4300?


Thanks all!

[ActionHenk]

I could try gargoyle 1.14 on the tp link wr1043n v2 to see if i get those problems again. If no problems ocure, then i also have the new 1.14 "shared client information" instead of a bunch of unknown devices.

Well i tested this now, gargoyle 1.14 is running on the wr1043n v2 instead of 1.10 and again the same problems start.

Client information sharing is nice by the way, but it works different then i expected. I thought all accesspoint connected clients would be visible in the accespoint itself, but instead their visible in the router, nice touch!

So gonna roll back, thanks!

[ActionHenk]

Well here is something strange,

I'm running 1.13 experimental on wr1043n v2 now, and it is pretty stable! Sometimes a ESP that doesn't response, but 95% of the commands are coming thruw, also no ESP wifi disconnects, or trouble with esp's connecting to the accesspoint after a accesspoint reboot. I did 3 accesspoint reboots now and it kinda keeps working. Still 5% miss commands.

Wich is strange because 1.13 experimental on the r7800 had as much problems as 1.14 or 1.15 beta did. Is there something to hook on now?

Edit, After i was typing this and hitting forum>Submit, going back to firing mqqt commands at the esp's and more problems now. All ESP's are still connected, and i can command them from their own web interfaces, but sending mqtt commands are a hit and miss. Like when i give it a little rest, it has to be awaken. Anyway, never had this good results on any other router. Going to try 1.12 on the wr1043n v2 now.

Edit> 1.12 is 100% stable, ill stay on 1.12, no need to go back to 1.10 i guess.

[Lantis]

I don’t really have any further suggestions. Except to try vanilla OpenWrt 23.05 and see if you have the same issue. If not then a comparison between config with 1.15 might reveal something.