I have finally gotten my FC5 firewall running, however here is the problem that I am having.

Current route -n output

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth1

Here is how the routing is supposed to be, and if the above mentioned routing is wrong, let me know please!

LAN -> WAN packet transversal:

LAN -> eth0 -> IPTables & Squid -> eth1 -> WAN

WAN -> LAN packet transversal:

WAN -> eth1 -> IPTables & Squid -> eth0 -> LAN

Now, here is where my problem is, **IF** I go back and check the routing later tonight or tomorrow, this is how it looks:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0

So far I have had to change the routing what seems like every time.

If there is something I can do, I'd like to know please!

Thanks!!

Does this happen on its own or does a change or network restart did this ?

Well, it appears to change on it's own... Has not changed today though

check ps -AH for dhcpcd or dhclient and please confirm there is no seperate dhcp server running on your lan side

Well the only other device that could run DHCP, the router, is disabled. DHCP is running on this linux box, but eth0 / eth1 are configured for static at this time. If I put eth1 on WAN then it will be switched over.

i assume it is dhcp3-server that you are using - you can tell a dhcp server which device to we working on - force it to run on eth0
or better yet - dissable the dhcp server for some time and see if that makes a diff - then you at least know if it is dhcp server at all that is causing the issue - though if the local routing table is alterd without your influence it either is a script locally or dhcp
even with statically assigned ip's it is still possible to retreive routing and dns info from a running dhcp server
you may want to check your /etc/dhclient /etc/dhclient-script or dhcpcd config (i do not know the files relevant for dhcpcd)

Well, it appears as though the routing has fixed it's self, It's now gone 2 days without dumping the routing or disabling packet forwarding.

If I have any more problems, I will re-check my logs and see what could be causing it.

I will also try what you suggested Nathanael!

Thanks