Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - frakkin64

#1
Quote from: L on December 19, 2024, 06:55:37 PMI am having an issue where if my AT&T BGW320-500 modem reboots sometimes my router WAN will be given a private IP.

I assume this is happening before the WAN IP is assigned, have you tried dropping the lease on the DHCP server in the modem to 10 minutes (same as IP passthrough lease time)?  I haven't encountered this yet, but only 1 month on AT&T Fiber so far.  I'm happy to be back on AT&T, I went to cable after being frustrated with the high-price & low bandwidth of AT&T DSL (still no fiber).  I got the speed from cable but the provider was awful (they had a lot of outages).

I haven't changed the DHCP server lease, but maybe I will preemptively.
#2
General Discussion / Re: website update looks great!
December 13, 2024, 10:55:13 AM
Quote from: meyergru on December 13, 2024, 01:31:42 AMAlas, I must say that I am less than impressed by the new layout. I can hardly read it, partly because of the low contrast, partly because of the small font size of 83%. Instead of readable text, many layout elements take up much space, thus nearly half of the page is full before content starts even on my 38" monitor. Thus, scaling up to 120% is no option.

...

Sad to say that, but this is the first website I had to resort to something like this just to be able to use it decently.

Agree on all points, I was in the middle of using Stylus as well for the first time to fix the stylesheet issues.  Unfortunately there are some issues that require the template to be fixed, such as why unread/updated topics is out there with it's own bar and not part of another navigation bar.  But the excessive padding & margins and massive logos/headers are the biggest problem, on my laptop I had to scroll down a full page just to see the first post.
#3
Quote from: franco on August 08, 2023, 09:40:51 PM
Perhaps reloading the config is heavier than expected, but it would also depend on the the size of the config.xml. Additional pairs of eyes are appreciated.

Not really seeing the same problem here (CPU-usage wise, but it is the one with the most CPU time racked up), but I profiled it with xdebug and other than sleep the top two calls are:
- return_gateways_status, with most of the time spent in legacy_interfaces_details/php::exec
- parse_config, with almost all of the time spent in OPNsense\Core\Config->toArray (lots of recursive calls for this one, sounds like it is serializing XML into a PHP array?)

Perhaps a caching option, checking mtime to decide whether to reload?