> Good question. Hey, did you know our Actiontec modem runs busybox? > Telnet into it and login with admin, password admin. (Not sure if you can > do anything because everything is owned by a user id 501.) No I didn't know that. Maybe there is hope for this modem after all. At least now I can see exactly what the thing is doing - to an incredible degree. dhcp-fwd is a binary, but this line in the usage statement is promising:
Report bugs to Enrico Scholz <[EMAIL PROTECTED]> Indeed it looks like an open source project itself[1], so let's get cracking with the bug reports. The file ownerships aren't an issue, since you're root when you log in, but the root filesystem is read-only. /var is not, though, and most of what's in /etc is symlinked to /var/etc. > The other thing you and I should probably do is look at firmware > updates. This is a real problem (although Windows TCP/IP stack seems to > handle it gracefully) that you'd think would be addressed by now. I don't see any on Qwest's site. This modem appears to be quite new. There was something somewhere about not using the firmware update from Actiontec's site because it would break DSL with Qwest, so be careful. ;-) In the meantime I think I'll work on a good bug report and set up my network statically with bind running on a machine that can answer ipv6 queries and hopefully they will pay attention to /etc/resolv.conf then. -- .O. Hans Fugal | De gustibus non disputandum est. ..O http://hans.fugal.net | Debian, vim, mutt, ruby, text, gpg OOO | WindowMaker, gaim, UTF-8, RISC, JS Bach --------------------------------------------------------------------- GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460
signature.asc
Description: Digital signature
____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
