Danger!
Note that the smb.conf places the file-serving on 'eth3'. This is the *public interface*. There seems to be no way to disable this absent modifying the smb.conf file via telnet (and I don't believe this file persists across reboots).
In fact, all of the services on this router are exposed to the internet by default and there is no functional firewall through the GUI. You can configure much of this through the command-line, but it isn't clear how to set these settings persistent across reboots.
One relatively easy option to get security on this router is to set a DMZ host. Then, all incoming packets are forwarded. One option is to set that DMZ host to the broadcast address (i.e. 192.168.1.255) which will have the side-effect of allowing external WOL packets to come in. However, that might also open other security holes (such as smurf attacks).
Note that the smb.conf places the file-serving on 'eth3'. This is the *public interface*. There seems to be no way to disable this absent modifying the smb.conf file via telnet (and I don't believe this file persists across reboots).
In fact, all of the services on this router are exposed to the internet by default and there is no functional firewall through the GUI. You can configure much of this through the command-line, but it isn't clear how to set these settings persistent across reboots.
One relatively easy option to get security on this router is to set a DMZ host. Then, all incoming packets are forwarded. One option is to set that DMZ host to the broadcast address (i.e. 192.168.1.255) which will have the side-effect of allowing external WOL packets to come in. However, that might also open other security holes (such as smurf attacks).
Last edited: