comment added; resolution set; status changed
status changed from new to closedresolution set to wontfix
View Articleowner deleted; comment added; status changed
ownernobody deleted status changed from reopened to new
View Articleresolution deleted; comment added; status changed
status changed from closed to reopenedresolutionwontfix deleted
View Articlecomment added; resolution, milestone set; status changed
status changed from reopened to closedresolution set to wontfixmilestone set to Gateway 1.1.3 I'll close this bug as I'll be adding the info to fix the problem to the wiki: If you are running the...
View Articlecomment added
Removing following line from forward chain works for me iptables -A FORWARD -i br0 -o br0 -j ACCEPT iptables -A FORWARD -i $LAN -o $WAN -j ACCEPT I am using openwrt experimental
View Articleversion, milestone deleted; comment added; priority, description changed
priority changed from 2 to normalversionFor 1.0 deleted description modified (diff) milestoneWifiDog Auth Server 1.0 deleted
View Articleresolution deleted; comment added; milestone set; priority, status, version...
priority changed from 5 to 2status changed from closed to reopenedversion changed from v1.0 (example) to For 1.0resolutionNone deleted milestone set to WifiDog Auth Server 1.0 I repeat - this problem...
View Articlecomment added
Logged In: YES user_id=1245118 It's been working fine on Whiterussian for 2 months. I'm closing this one
View Articlecomment added
Logged In: YES user_id=1359416 I can confirm that applying ludocornut's patch to S45firewall fixes the problem. I think we should add this information to the README or the installation instructions -...
View Articlecomment added
Logged In: YES user_id=793839 I dindt try the fix by ludocornut, i guess it is ok. I confirm itand maybe it will be fixed :]
View Articlecomment added
Logged In: YES user_id=1273191 Another way to workaround this problem is to comment (in S45firewall) the line iptables -A FORWARD -i br0 -o br0 -j ACCEPT iptables -A FORWARD -i $LAN -o $WAN -j ACCEPT...
View Articlecomment added
Logged In: YES user_id=793839 I finally find a way to fix this problem : just put wifidog before S45firewall in booting process (for example rename it S43wifidog) And add a sleep 10 at the beginnig of...
View Article
