v_lestat
The Blood Is The Life
join:2002-11-09
1 edit | reply to v_lestat
Re: why cant i make wall watcher work
you dont enter your pc ip into anything with wallwatcher or hyperwrt.
if it dont work with hyperWRT someone speakup now.. i have said i been using this from the begining..
and the bv runtimes are only for systems where the program wont even open at all... and those are VB 5 rntimes older stuff i might add
this opens says its starting.. and never reports anything and infact just sits there saying starting......
not sure what the deal is...
hyperWRT doesnt give any options for external log watching.
is that the issue ?
--
System Specs
AMD64 3200+ Venice @2.9ghz Water Cooled
DFI SLI-DR 1gig OCZ PC4800 Elite -Modded Audigy2 ZS w/ 3 AD8620 OPAMPS chips -2x 36gig Raptors + 120gig
eVGA 6800GT WaterCooled
Logitech Z5300 THX 5.1 spk |
|
will792
join:2003-11-18
Stamford, CT
| You have to explain your problem so other people can understand. If WW is running but does not have any entries in the log it is very different from WW program shutting down.
The version of HyperWRT (old) that I used required the following entries in the startup/firewall scripts:
Startup script:
sleep 2
/sbin/klogd
/sbin/syslogd -R
echo "#!/bin/sh" > /tmp/loggit.sh
echo "while true" >> /tmp/loggit.sh
echo "/usr/bin/killall -9 klogd" >> /tmp/loggit.sh
echo "sleep 1" >> /tmp/loggit.sh
echo "/sbin/klogd" >> /tmp/loggit.sh
echo "sleep 960" >> /tmp/loggit.sh
echo "done" >> /tmp/loggit.sh
chmod 700 /tmp/loggit.sh
/tmp/loggit.sh &
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
Firewall script:
/usr/sbin/iptables -R INPUT 7 -j logdrop
/usr/sbin/iptables -R INPUT 1 -j logdrop -m state --state INVALID
You have to configure syslogd process on the router in order to see anything in the log. This process sends UDP traffic with the events that WW listens to. WW is a passive program, it just sits and listens on a particular socket.
I thought that the most recent version of HyperWRT has user interface for syslogd configuration (just destination IP and enable/disable) but I might be wrong. |
|
