Hi, adding the route fails, but apparently it is a misconfiguration since using the gateway option of 'stabridge' solves the routing problems for attached clients.
Thanks > Christian Huldt <[email protected]> hat am 9. März 2016 um 13:20 > geschrieben: > > > Den 2016-03-09 kl. 09:37, skrev Thomas Roehr: > > Hi, > > > > I am using OpenWrt Chaos Calmer on an OM2P access point and > > fail embed to setup of a default route into the configuration. > > Adding the route manually does the job: > > > > $route add default gw 10.250.247.1 dev eth0 > > > > Adding the following configuration block (as suggested on > > https://wiki.openwrt.org/doc/uci/network) > > > > config route > > option interface 'lan' > > option target '0.0.0.0' > > option netmask '0.0.0.0' > > option gateway '10.250.247.1' > > > > does not seem to have any effect -- already tried with or without the > > gateway option for interface 'lan'. (Full config is attached) > > What am I missing here - any suggestions on how to set it up correctly? > > > Wouldn't that be because interface 'lan' cannot have a gateway it cannot > reach? > From the command line you never specify an interface... > > config interface 'lan' > option ifname 'eth0' > option force_link '1' > option proto 'static' > option ip6assign '60' > option ipaddr '192.168.10.125' > option netmask '255.255.240.0' > option gateway '10.250.247.1' > > > > _______________________________________________ > openwrt-users mailing list > [email protected] > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users _______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
