Jeff Liebermann <(E-Mail Removed)> wrote:
>
>The problem I was faced with (different issue) is that routing
>wouldn't do anything for non-IP wireless traffic. I was dealing with
>a bunch of gamers running NETBEUI over IP that the IP router didn't
That doesn't make sense to me. Is NETBEUI over IP an example of
non-IP traffic? I would have thought that would be routed...
Or do you mean NETBEUI over Ethernet? (I've never messed with
any of the non-IP protocols.)
I haven't looked at either the switch or the bridge in the
WRT54G to see what can be done as far as protocol restrictions.
>>Or at least for somebody who is comfortable doing Unix systems
>>admin, and can figure out how to make such routing persistent
>>across restarts and power failures on the WRT54G, neither of
>>which are necessarily easy skills to acquire over a weekend.
>
>Chuckle. Be nice. Do a search on the web and usenet for my name and
>SCO Unix, especially in comp.unix.sco.misc.
You need not preen Jeff... I was *not* talking about you.
The average reader in this newsgroup, to whom my comments are
addressed, is almost certainly using MS Windows, and probably
has *no* background in systems admin for even that environment,
much less something as different as Linux is from Windows.
You obviously have the background and won't find it difficult to
come up with the various conceptual models needed to implement
just about anything that strikes your fancy. (And I'd be silly
to think that I'm going to educate you... even if I did find
something you don't know. ;-)
>You're correct about one item. I didn't or couldn't figure out how to
>make the routes persistent. Probably by editing rc_startup.
Yep. Two ways to do it that I know of.
The first one is to make an appropriate file on another system,
and then go to the "Administration->Diagnostics" web page of the
WRT54G, and insert it into the command input window. Instead of
clicking on the "run" box next to it, go down to the bottom of
the window and click on the "startup file" box. (I'm not
looking at the web page, and the quoted titles may be a bit
different than what I'm listing here from memory.)
What that actually does is write to the nvram "rc_startup"
variable, and sets the entire text of the file equal to that
variable. When the system boots it dumps the value of that
variable into a file named /tmp/.rc_startup (/tmp is a ramdisk).
The second way is to create a working file in /tmp, using vi or
any other suitable means (e.g., tftp it from another system).
then do "nvram set rc_startup=$(cat /tmp/foo)", where the
working file is /tmp/foo. On the next boot, that will be found
in /tmp/.rc_startup.
Another trick that is really nice is to put things into the
startup file that create /tmp/.profile, /tmp/host, and
/tmp/resolv.conf files. The last two are symlinked to the /etc
directory, so whatever is in them will be useful.
(I need to try diddling with nvram, or download the source code,
and see if there is an appropriate nvram variable name for those
files, the same as with .rc_startup. That would be easier.)
My WRT54G's boot up with a handy ~/.profile for the root user
that even uses color in the prompt, and provides a few useful
aliases to do complex commands with simple names. It also sets
the current date and time when the system boots. And having
canonical host names in /etc/hosts certainly makes a number
of things much easier to do.
>I wanted
>to tinker and didn't want to deal with undoing my mistakes. It's the
>same way with Cisco. I don't run:
> copy running_config to startup_config
>until I've tested the hell out of my running configuration and am sure
>it's worth saving. If I completely mangle the running config it's
>very easy to recover.
With the WRT54G's you can of course just set everything to
whatever you like, using manual commands from the shell command
line, and if it gets hosed... just reseat the power plug, let
it reboot, and it's back to where it started.
>Thanks to Google, the proper incantation is probably something like:
> nvram set rc_startup="/sbin/route add..."
>or something similar. Am I close? Do I get a prize?
Close enough for government work!
Are you aware that you can add *any* variable to nvram that you
like? You can then use your own nvram variable names to change
what the init script does, or whatever...
Of course playing with nvram is kinda dangerous, because dead
WRT54G's aren't shaped well to be useful as either a door stop
or a boat anchor.
--
Floyd L. Davidson <http://web.newsguy.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska)
(E-Mail Removed)
Similar Threads
Linear Mode
