Why am I having trouble signing in/signing up to the forums?

[psherman]

@le_berger_des_photon

by reading your propaganda that it's a substitute good for tomato

Calling the documentation "propaganda" is not really necessary here, and will quickly turn off people who would otherwise be willing to help. Maybe this firmware is not for you if you really believe that this is propaganda.

There are reasons that Tomato is good for some scenarios and not for others... and there are reasons that OpenWrt is better for some and not for others. Static routes are not going to be a make-or-break situation here, so feel free to use Tomato or DD-WRT or whatever else you fancy if you have somethign against OpenWrt. And if it is simply an issue of your issues logging into the forum, that's quite a strange reason to have a chip on your shoulder about the whole firmware platform.

[psherman]

@le_berger_des_photon

I want the route to apply to every device which has that machine as its gateway.

Then the source should be removed.... it should be just the three lines. In fact, you can even reduce it to just these 2 lines:

@psherman

config route
        option target '192.168.68.0/22'
        option gateway '192.168.50.68'

[berger.des.photons]

ok, but that doesn't answer the question of why this can't be done in the gui? It doesn't answer the question of why a command in the startup script doesn't function the same as at the putty command line. thanks.

[psherman]

@berger.des.photons

but that doesn't answer the question of why this can't be done in the gui?

It absolutely can be done in the GUI. Maybe you can show us what you did... screenshot?

@berger.des.photons

It doesn't answer the question of why a command in the startup script doesn't function the same as at the putty command

Maybe it is because your command (the target network and gateway) don't match??

@le_berger_des_photon

ip route add 192.168.24.0/24 dev br-lan via 192.168.20.58

vs

@le_berger_des_photon

config route
        option target '192.168.68.0/22'
        option gateway '192.168.50.68'
        option type 'anycast'
        option interface 'lan'
        option table 'main'
        option source '192.168.50.150'

Different targets and gateways...
in fact... now that I look closer... the route in the config file won't work because the gateway is not part of your lan.

@le_berger_des_photon

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option ipaddr '192.168.20.1'

Maybe you can draw a diagram of your network complete with IP addresses. Seems like there are some significant inconsistencies.

[berger.des.photons]

[berger.des.photons]

if my target was wrong why would my route work when I add it via putty with the route command?

[berger.des.photons]

[psherman]

@berger.des.photons

if my target was wrong

let's look again at what your target is with the command you put into your startup script...

@le_berger_des_photon

ip route add 192.168.24.0/24 dev br-lan via 192.168.20.58

This has a target of 192.168.24.0/24 via 192.168.20.58

When we compare that with what you entered into the GUI...

@le_berger_des_photon

config route
        option target '192.168.68.0/22'
        option gateway '192.168.50.68'

The target is 192.168.68.0/22 via 192.168.50.68

The latter (entered via the GUI) is a different network entirely, and the gateway is unreachable from your lan.

[le_berger_des_photon]

the gui routes are now working, using unicast and lan. I guess I was being hasty. Still curious about why the startup script didn't work though the meme characters worked in putty. thanks.

[dave14305]

Is this router getting the 192.168.50.150 IP on the WAN interface via DHCP from another router? (Saw the URL in the LuCI screenshot).

[le_berger_des_photon]

my error was in the screen shot I showed you, not in my command, the proof is that it worked in putty.

[psherman]

@le_berger_des_photon

my error was in the screen shot I showed you

But this would clearly explain why the route entered in the GUI didn't work... it was both the wrong target and the wrong gateay.

[le_berger_des_photon]

[le_berger_des_photon]

startup script still not working, but the route works when I copy my line out of the startup script into a putty session.

[psherman]

@le_berger_des_photon

startup script still not working

I'll state again that this is not the preferred method of adding a static route.
It should simply be in the network config file.

[le_berger_des_photon]

ok, not sure why you'd want the startup script to function differently than a putty session, but I don't need to do that now that I'm able to add static routes in the gui. Thanks for your effort, forgive me for being a d**k at first, but the thing with the passwords, the fact that the gui accepted my routes without creating any routes anywhere or complaining. it was a bit frustrating.

[le_berger_des_photon]

I guess I've had these r6220s for 3 years. good I"ll finally get to use them.

I did notice that openwrt with the relatively weaker r6220 gets faster throughput than rt-n18u with tomato.

[psherman]

@le_berger_des_photon

Thanks for your effort, forgive me for being a d**k at first,

Yeah... maybe in the future it'll be better not to come out swinging your fists...

@le_berger_des_photon

but the thing with the passwords

I get that it's frustrating... but we have a forum section for "site feedback" where you could have raised this (ideally in a less confrontational tone)...

@le_berger_des_photon

the fact that the gui accepted my routes without creating any routes anywhere or complaining

It appears it did make the route that you asked it to... it was just not right.
"stupid computers... they keep doing what I tell them to do and not what I want them to do!"

[psherman]

meanwhile...

If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.
Thanks!

[le_berger_des_photon]

it would still be nice to know why a startup script doesn't function the same as entering in putty. Maybe it was after boot but before something else which wipes it out?