Hi Angelo, > thank you for the reply. The good news is that the problem seems to be > disappeared when I performed the upgrade to last available firmware (even > if I didn't find anything related to this problem in the changelog). > Unfortunately I have no idea about what the problem was. Weird, but good to hear it's working for you know. Frankly, I didn't have good hopes for being able to diagnose and solve this problem...
> Regarding the ping to my modem, it wasn't possible with default settings, > but I managed to get ping and to be able to connect to the modem from lan > (useful to check adsl signal quality) by assigning an IP address to eth0.2 > in the subnet of the modem and then configuring the firewall (so I can also > connect from hosts different from the Fonera): > > ifconfig eth0.2 192.168.1.2 netmask 255.255.255.0 > > iptables -A forwarding_rule -d 192.168.1.1 -j ACCEPT > > iptables -t nat -A POSTROUTING -d 192.168.1.1 -j MASQUERADE > > of course 192.168.1.1 is my modem's ip and I use a different subnet for the > lan. Ok, apparently the modem has its own IP while also doing PPPoE, didn't know they did that :-) > Regarding issuing "top" command while fonera is dropping packets, I tried > to do that, but I didn't notice any process that is particularly cpu > consuming, but in case it will happen again I'll try to do some more > testing. Ok! Thanks for reporting back, Matthijs
signature.asc
Description: Digital signature
_______________________________________________ Development mailing list [email protected] http://fonosfera.org/mailman/listinfo/development
