Not quite sure if this is the appropriate area for this, but since this is my second device & this happens once the VFX VoIP config script is loaded, as per instructions, I'm wondering if anyone else here is experiencing similar issues.
Previously I had a WAG54PG2v2 device, and now I've "upgraded" to a WAG310G, but the issue remains the same.
Do a factory-reset (paper-clip @ the the back) & going through the motions of setting the device up from scratch, again.
Keeping the default IP/class of 192.168.1.1/255.255.255.0, & disabled the WiFi completely (setting up a secondary firewall & services behind it, like WiFi, VoIP, etc).
Check connection & see that everything's OK, and then load the config: http://58.28.20.69/configs/default/default$MA.cfg
Reboot for good measure
Make calls via analogue phone & everything goes swimmingly for a wile, so there's no need to continually jump into the device & muck around, so I assume that everything *stays* OK
The rub is: when I try to get into the device at a later stage, I'm am unable to log in at a later stage.
With the WAG54GP2v2 unit, it seems to have set the login values to something I have no access to.
With the WAG300G device, I'm not even able to get the login dialogue. Only sockets available are 21 (FTP) & 8080 (proxy/voip interface), event though I *distinctly* set 443 (HTTPS) & pretty-much noting else, to lock the device down solid
Will now have to go through the motions of setting the device up, again, to make sure settings are cool (not too happy with nodes on my network that I don't have full control over)
Anyone experience similar issues, or know what's up with this?



