Smoothwall routing

[tesseract]

Does any one know how to get smoothwall 2.0 to do some routing?

I have 2 servers connected to the internet, one of them is running smoothwall express 2.0 and the other is running windows server 2003.
I am using a ethernet ADSL modem and the modem and the 2 servers are connected on the same switch.
Windows 2003 is using "routing and remote access" service, but only the NAT part is activated. This server's IP address is 192.168.0.1
A lot of my internet traffic is local, so I want all local traffic to go through 1 adsl account, and the windows server is always connected to this account, and the smoothwall server is always connected to the other "international" adsl account.

All the client computers are configured to use 192.168.0.2 (smoothwall server) as the default gateway. I want the smoothwall server to route the local traffic to the windows server, but without much sucess. (using a list of local traffic networks, so it is static not dynamic)

I tried this:
root@smoothwall: route add -net 196.25.0.0 netmask 255.255.0.0 gw 192.168.0.1 dev eth0 (eth0 is connected to local network)
After this command, the smoothwall server seems to route 196.25.0.0/24 to 192.168.0.1, if the traffic originates from localhost (smoothwall). When I tried to tracert any host on the 196.25.0.0/24 network from a client computer, I simply get "timed outs".

It seems that the smoothwall program is not doing routing for the network I have added if the traffic comes from client computers. If I remove the additional route, 196.25.0.0/24 becomes accessible to client computers.(but using precious "international" adsl account)

Does anyone solve this problem? (I got a similar network to work using only microsoft systems, but I want to try Linux based systems)

Any assistance is appreciated, I am quite frustrated...

 

[neobyte]

Check to make sure forwarding is enabled on the smoothwall box. I think it is /etc/???/ipv4/ip_forward. Make sure that the ip_forward file contains a 1 in it... Can't remember the exact dir it is in though....

 

[tesseract]

Check to make sure forwarding is enabled on the smoothwall box. I think it is /etc/???/ipv4/ip_forward. Make sure that the ip_forward file contains a 1 in it... Can't remember the exact dir it is in though....

I tried this: "echo 1 > /proc/sys/net/ipv4/ip_forward"
But it still does not route.

This is my first time using Linux, so not too sure about the whole thing. But I have read up on the internet that smoothwall 2.0 uses iptables, and chains are split up into INPUT, OUTPUT, and FORWARD. From the symptoms, maybe the system is allowing OUTPUT through that route and not forwarding to that route when other clients connect.

Any ideas?

 

[tesseract]

I eventually solved this problem.
Edit /etc/rc.d/rc.firewall.up

After the section on "# Allow packets that we know about through ..."

Add:
# Allow packets from green to green
/sbin/iptables -A FORWARD -i $GREEN_DEV -o $GREEN_DEV -j ACCEPT