Thibor's 191005 fw and logging - w/ our w/o firewall script?

Discussion in 'HyperWRT Firmware' started by mquandt, Oct 30, 2005.

  1. mquandt

    mquandt Network Guru Member

    Hi all,

    I am new to third party fw's, so bear with me...

    Started with the 'beta' HyperWrt 2.0something for my WRT54GS 1.1 from and enabled logging to wallwatcher via the startup and firewall scripts.

    Found that this fw version has no WPA2 support and thus installed Thibor's latest version based on 4.70.6. (Which also works great, thanks Thibor!)

    By chance, I discovered that this fw has an enhanced logging option on the Administration->Log page. Putting the IP of my client here and removing the Startup script has logging still working. (Before I removed the Startup script I noticed in WW that klogd would be started multiple times, by the way, which was confirmed by 'ps' in the command shell).

    Ok, now I still have two questions:

    1. what does the 'Log Level' selectionwith 'Low', 'Medium', 'High' on the Log page do? Is it process priority of the syslogd, or detail level of the logs, or what?

    2. What with the firewall script I used with the old fw? Is this still required, or will it even by in the way like the old Startup script apparently was?

    And more generally: Is there a summary documentation of all these brilliant new features somewhere? :)

  2. Thibor

    Thibor Super Moderator Staff Member Member

    log level is this:
    Low: Messages only
    Med: Denied or rejected plus messages
    High: All traffic

    your old script is no longer necessary.
  3. cliffi

    cliffi Network Guru Member

    do i still ned the :

    echo 4096 > /proc/sys/net/ipv4/ip_conntrack_max
    echo 1 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
    echo 1 > /proc/sys/net/ipv4/icmp_ignore_bogus_error_responses
    echo 512 > /proc/sys/net/ipv4/neigh/default/gc_thresh1
    echo 2048 > /proc/sys/net/ipv4/neigh/default/gc_thresh2
    echo 4096 > /proc/sys/net/ipv4/neigh/default/gc_thresh3
    echo "600 1800 120 60 120 120 10 60 30 120" > /proc/sys/net/ipv4/ip_conntrack_tcp_timeouts

    or is it optimized already?
  4. Thibor

    Thibor Super Moderator Staff Member Member

    ip_conntrack_max is set by default to 2048
    ip_conntrack_tcp_timeouts is set to "600 14400(4 hours) 120 60 120 120 10 60 30 120"
    i have seen mention that the other values in your startup script can actually make the performance worse. fwiw, i don't use a startup script of this nature, and i do use bt software(purely to test of course :) ) and i don't have a problem
  5. mquandt

    mquandt Network Guru Member


    Thibor, thanks, this saves a little config work when updating the fw...

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice