search for: default_routes

Hi all, I''ve been trying to set up a shorewall box with 2 ISPs. After a shorewall start/restart, shorewall correctly configures and balances the default main route via both ISPs: [...] default nexthop via 200.173.215.94 dev eth0 weight 10 nexthop via 200.157.40.129 dev eth2 weight 20 but after a boot, that route is not configured. Inspecting the code, I solved

Hi Is there a way for puppet to create cron job on each of my node based on my gateway''s IP ? bala@bala-desktop:~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.2.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0 0.0.0.0

dumb question but what''s the view format in trunk? I have a simple router: Merb::Router.prepare do |r| # default route, usually you don''t want to change this r.default_routes # change this for your home page to be avaiable at / r.add ''/'', :controller => ''upload'', :action =>''new'' end I have a simple controller which should render the view: def new @photo = Photo.new respond_to do |format|...

I put together a sample app to help people learn Merb: http://svn.depixelate.com/applications/invoice_tracker/ I also blogged about it here: http://depixelate.com/2007/5/31/taking-merb-for-a-spin -- Zack Chandler http://depixelate.com

I''m following the example provided in the type reference under ''zone'', i.e.: zone{myzone: autoboot=>true, create_args=>"-b", ip=>"nge0:10:130.55.201", path=>"/zoneds/%s", realhostname=>"myzone.example.com",

hi all, I want to move some routing tasks out of the router and into the controller. The goal is to make Merb feel less like mod_rewrite and give the user more control at the controller. The new Router is simple: it takes the path_info (not the whole request) then outputs a controller class and some parameters from the path matching. The rest of the routing would be done at the controller level.

Beta 1 is now availablew for testing. Problems Corrected: 1) Previously, the Shorewall and Shorewall6 install.sh scripts did two things wrong with respect to the /etc/shorewall[6]/routes file: - The existing file was unconditionally removed. - A skeleton file was not installed when SPARSE was not set in the shorewallrc file. Additionally, the installer would remove

Beta 1 is now availablew for testing. Problems Corrected: 1) Previously, the Shorewall and Shorewall6 install.sh scripts did two things wrong with respect to the /etc/shorewall[6]/routes file: - The existing file was unconditionally removed. - A skeleton file was not installed when SPARSE was not set in the shorewallrc file. Additionally, the installer would remove

Hi all, I was trying to test ROUTE specific code with a multi-isp serviced box. There is a bug somewhere, but I''m not able to understand what the real problem is: when I issue a "shorewall show capabilities" I get: Loading /usr/share/shorewall/functions... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... Loading Modules... Shorewall has