OK thanks Bald Eagle - I am happy to use a GUI-enabled build to reconfig the LAN, but was under the impression (based on its location) that the GUI version is still 'experimental'. So, for the record, which is considered the recommended working firmware? I installed Howlingwolf's 30SP06_unlocked, but assume you're suggesting 30SP06_unlockedgui?
Yep, that's the one I would recommend & that quite a few users have been using since it was created without any issue whatsoever.
It may be stored in the Experimental area, but I can't see that it needs any amendments at all after this amount of time.
Also, I'd still be interested to hear if anyone is aware of a telnet command for reconfiguring the LAN2 IP. I have no real need for the GUI - I will be using my own shell scripts to grab the stats I'm interested in via xdslcmd. All I want to end up with is a modem which I can telnet to on the 192.168.0.x LAN and which doesn't need reflashing until there's a fantastic new firmware available.
Once in BusyBox, you could try typing this command:-
ifconfig --help
# ifconfig --help
BusyBox v1.9.1 (2013-06-01 18:30:08 CST) multi-call binary
Usage: ifconfig [-a] interface [address]
Configure a network interface
Options:
[[-]broadcast [ADDRESS]] [[-]pointopoint [ADDRESS]]
[netmask ADDRESS] [dstaddr ADDRESS]
[outfill NN] [keepalive NN]
[hw ether ADDRESS] [metric NN] [mtu NN]
[[-]trailers] [[-]arp] [[-]allmulti]
[multicast] [[-]promisc] [txqueuelen NN] [[-]dynamic]
[mem_start NN] [io_addr NN] [irq NN]
[up|down] ...
You can apparently change ip address using ifconfig command itself. To set IP address 192.168.1.20, enter command:
# ifconfig br0 192.168.1.20 netmask 255.255.255.0 up
# ifconfig br0
typing ifconfig on its own will give you all the relevant current settings details:-
# ifconfig
br0 Link encap:Ethernet HWaddr 5C:7D:5E:EE:CC:63
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:506844 errors:0 dropped:0 overruns:0 frame:0
TX packets:158253 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:30130876 (28.7 MiB) TX bytes:53776056 (51.2 MiB)
& so on.......................
I haven't tested it out myself so I don't know if it actually works or not.
However, from what I have read, I believe it doesn't survive a resync, so would have to be reset at each resync (using the default IP address to initially connect via Telnet).