On 2016-12-15, Patrick Dohman <patrick_doh...@centurylink.net> wrote:
> Stuart
>
> Please see below for more info:
>
> Please note the 5.7 dmesg is subsequent to a reboot.
Thanks. I was wondering about a bug with LCP echoes I accidentally
introduced that made it into 5.9 (fixed for 6.0).
Nothing stands out from what you've sent. Some possibilities:
- connection somewhere between the APU and the ISP really is dropping out
(are you using the same cable for the different locations you placed the APU
in? could a cable be bad? check for errors on the ethernet interface)
- machine too busy to handle traffic - maybe tail -f /var/log/messages in the
background while "vmstat -w 10" or something is running (maybe under "script"),
look for the timeouts in the output and see what cpu is doing at the time
> pass out quick on egress inet6 proto { tcp, udp } from { (pppoe0:network),
> (athn0:network), (re2:network) } modulate state
btw using (...) causes an extra address lookup to be done when the rule
is evaluated (i.e. when a packet doesn't match existing state) - you may need
this for pppoe0 but you can save a bit of cpu with
pass out quick on egress inet6 proto { tcp, udp } from { (pppoe0:network),
athn0:network, re2:network } modulate state
(and same for the v4 rule)
> ### --- Optional Runtime Options --- ###
> set optimization conservative
not likely to be the problem, but you're pretty unlikely to need that.
