Recent content by jamestx10

Is there a way to install updates via SSH? Being hard wired through another switch was not ok. I had to directly hard wire to the router before the upgrade would install.

I have been using a script provided here to keep my DHCP registrations in order by IP. #!/bin/sh # Refresh a sorted list of the DHCP STATIC table logger -t "($(basename $0))" DHCP static table reset # Add lines in the order / grouping as desired to be displayed in the GUI nvram set...

It took 75 min on the LAN AP and did the same thing. The SSIDs are configured the same other then the VLAN tag. WPA2, AES/CCMP

Not sure of a way to show the whole config. Anything you are looking for specifically?

So that works from the script point of view and the client shows the lease good until the year 2153 BUT it still hangs and sends the dnsmasq-dhcp request to the router around 20 min later.

There was a driver update and it was looking promising but alas no change. Nothing in the client config is static.

It is a cheap Win10 tablet. It has a Realtek RTL8723BS wireless chip in it. I just found a driver update for it so will see if that helps but like I said it works fine on the non-guest WiFi.

Here is what I am using: # Add DHCP custom range for VLAN 4 being a private network # interface=vlan4 dhcp-range=vlan4,10.10.11.10,10.10.11.250,24h dhcp-option=vlan4,15,NULEAFGUEST dhcp-option=vlan4,3,10.10.11.1 dhcp-option=vlan4,6,10.10.11.1,0.0.0.0 My LAN subnet is 10.10.10.1

The good news is it seems to work fine on another client. The first client with the issue did not have that problem though when it was not on this restricted guest network. Is there anything in the config that could be changed to maybe improve this?

No change in behavior. The client loses connectivity for a min or two and then the DHCP requests are seen in the log. The DHCP lease on the client shows that it was obtained yesterday but the expiration date move out 24 hours.

I have put in that change and rebooted. iptables -S still fails. It will probably be tomorrow before I can test and see if that change helped.

Same 86400. It is more often then an hour May 4 09:56:56 dnsmasq-dhcp[246]: DHCPREQUEST(vlan4) 10.10.11.20 MAC May 4 09:56:56 dnsmasq-dhcp[246]: DHCPACK(vlan4) 10.10.11.20 MAC May 4 10:16:58 dnsmasq-dhcp[246]: DHCPREQUEST(vlan4) 10.10.11.20 MAC May 4 10:16:58 dnsmasq-dhcp[246]...

The DHCP request seems to be the key now. Same thing happened again. Client lost internet for a while and when it came back the syslog shows the DHCP request. May 4 10:16:58 dnsmasq-dhcp[246]: DHCPREQUEST(vlan4) 10.10.11.20 May 4 10:16:58 dnsmasq-dhcp[246]: DHCPACK(vlan4) 10.10.11.20 May 4...

That works. Here is the output with internet working on the guest network: RT-N66U:/tmp/home/root# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere...

iptables v1.3.8: Unknown arg `-S' Try `iptables -h' or 'iptables --help' for more information. Did not like that command. Internet dropped again and this time I did not do anything and it started working again. Syslog shows the same DHCP action when the internet came back up. So it seems...