connorm
Senior Member
here is the issue im having
Running in Router mode but as an AP
once i setup the script to run at every boot i can connect to the router over the internet
initially i noticed NTP wasnt working, but i figured once the default gateway was entered the issue would be fixed, however it is not...
im using ca.pool.ntp.org as my ntp server
this message keeps popping up in my logs
notice how the time on the logs is wrong haha, almost every reboot the router just picks a random time to start from lol
Aug 4 09:25:12 hour monitor: ntp is not syn
Aug 4 09:25:42 hour monitor: daemon is starting
Aug 4 09:25:42 hour monitor: ntp is not syn
Aug 4 09:26:12 hour monitor: daemon is starting
Aug 4 09:26:12 hour monitor: ntp is not syn
Aug 4 09:26:42 hour monitor: daemon is starting
Aug 4 09:26:42 hour monitor: ntp is not syn
Aug 4 09:27:13 hour monitor: daemon is starting
Aug 4 09:27:13 hour monitor: ntp is not syn
Aug 4 09:27:42 hour monitor: daemon is starting
Aug 4 09:27:42 hour monitor: ntp is not syn
Aug 4 09:28:12 hour monitor: daemon is starting
Aug 4 09:28:12 hour monitor: ntp is not syn
Aug 4 09:28:42 hour monitor: daemon is starting
Aug 4 09:28:42 hour monitor: ntp is not syn
Aug 4 09:29:12 hour monitor: daemon is starting
Aug 4 09:29:12 hour monitor: ntp is not syn
Aug 4 09:29:42 hour monitor: daemon is starting
Aug 4 09:29:42 hour monitor: ntp is not syn
this was also appearing in the logs around the time of boot
Jul 31 17:04:42 kernel: TCP: time wait bucket table overflow
Jul 31 17:04:42 kernel: TCP: time wait bucket table overflow
Jul 31 17:04:42 kernel: TCP: time wait bucket table overflow
Jul 31 17:04:42 kernel: TCP: time wait bucket table overflow
Jul 31 17:04:42 kernel: TCP: time wait bucket table overflow
Jul 31 17:04:42 kernel: TCP: time wait bucket table overflow
would be nice to get NTP going
Running in Router mode but as an AP
once i setup the script to run at every boot i can connect to the router over the internet
initially i noticed NTP wasnt working, but i figured once the default gateway was entered the issue would be fixed, however it is not...
im using ca.pool.ntp.org as my ntp server
this message keeps popping up in my logs
notice how the time on the logs is wrong haha, almost every reboot the router just picks a random time to start from lol
Aug 4 09:25:12 hour monitor: ntp is not syn
Aug 4 09:25:42 hour monitor: daemon is starting
Aug 4 09:25:42 hour monitor: ntp is not syn
Aug 4 09:26:12 hour monitor: daemon is starting
Aug 4 09:26:12 hour monitor: ntp is not syn
Aug 4 09:26:42 hour monitor: daemon is starting
Aug 4 09:26:42 hour monitor: ntp is not syn
Aug 4 09:27:13 hour monitor: daemon is starting
Aug 4 09:27:13 hour monitor: ntp is not syn
Aug 4 09:27:42 hour monitor: daemon is starting
Aug 4 09:27:42 hour monitor: ntp is not syn
Aug 4 09:28:12 hour monitor: daemon is starting
Aug 4 09:28:12 hour monitor: ntp is not syn
Aug 4 09:28:42 hour monitor: daemon is starting
Aug 4 09:28:42 hour monitor: ntp is not syn
Aug 4 09:29:12 hour monitor: daemon is starting
Aug 4 09:29:12 hour monitor: ntp is not syn
Aug 4 09:29:42 hour monitor: daemon is starting
Aug 4 09:29:42 hour monitor: ntp is not syn
this was also appearing in the logs around the time of boot
Jul 31 17:04:42 kernel: TCP: time wait bucket table overflow
Jul 31 17:04:42 kernel: TCP: time wait bucket table overflow
Jul 31 17:04:42 kernel: TCP: time wait bucket table overflow
Jul 31 17:04:42 kernel: TCP: time wait bucket table overflow
Jul 31 17:04:42 kernel: TCP: time wait bucket table overflow
Jul 31 17:04:42 kernel: TCP: time wait bucket table overflow
would be nice to get NTP going