Are you sure you didn't mean for the netmask on your wireless interface to be 255.255.255.128? As it is now, it thinks that IP addresses on eth0 are on the same subnet and tries to send to them directly, but eth0 doesn't think that IPs on ath0 are on the same subnet. Generally it's Very Bad(tm) to put two different interfaces on the same subnet.
The wireless adapter is part of a completely seperate network on the otherside of the building I am in. They have their own router and their own network of pc's. I enable my wireless adapter when they need support and I can remote into their windows boxes, etc...
My eth0 interface is part of my own network. I have my own router and my own internet connection.
--Motorola Canopy Equipment--
--Renter Rtr WAN-- --My Router WAN-- --My Router SWITCH--
192.168.110.0 192.168.120.0 169.254.0.0
That is a rough diagram...
The renters have their own PPPoE account
I have my own PPPoE account
We share the same Canopy equipment
The reason I have two cat5's from my switch to my router is so that I can sit on the 169.254 network (the Canopy network) AND my network 192.168.120.0. I wanted to eliminate that CAT5 drop from the switch to my routers switch and use the second nic and go straigh to the 5-port router.
The way I have it setup now works, but it less than desireable. I'm not running DHCP on my router so that is the main reason why this setup works OK, but I really don't want the CAT5 going between the two switches.
Anyway, I do not have IP Forwarding in my kernel. Is that a requirement if I want two NIC's?
Thanks for the help so far