Two different Default Gateways on same Network?

Can anyone assist me on how to make two different gateways interact on the same network?

ISP is Frontier (they suck I know). One is 192.168.254.254 default modem/router from Frontier, other is a netgear with 192.168.1.1.

From what I understand and my knowledge on the subject, I need to turn off DHCP on my 192.168.1.1 and add a static route on 192.168.254.254 for my 192.168.1.1 router.

Is this correct?

My goal is to subnet my home network on a 255.255.255.128 /25
Having servers and computer on on network & xbox, iphone, etc. On another.

I believe you are way off track.

A "default gateway" is simply the router that the computer "sees" from its perspective.

If you want to do subnetting, and thereby have two separate networks in your house, I think you can do that with one router, and not complicate it by trying to use two.

Read this and see if it helps:

http://www.techrepublic.com/article/ip-subnetting-made-easy/6089187

if your router's firmware (menus) does not allow subnetting, you might look into DD-WRT.

You can only have one "default" gateway, where anything goes if not specifically routed elsewhere. Typically the (only) default route is to whatever gateway leads to the internet.

If you want to route to a different subnet, that needs to have a network specific route (gateway to to reach a specific subnet) through a real router (or PC that can act as a router), not your average broadband router (where everything behind it would be NAT'd as its WAN IP).

Some broadband routers might be able to set up to do actual network routing without NAT, but that would be the exception rather than the rule. In most cases anything connected to your modem/router would not even see or reach IPs on the LAN of your Netgear router, since they would all appear to be its WAN IP from their view.

Many years ago before I had a wireless/router/modem I used Linux with 3 nics as my router. One nic did pppoe (masquerading anything to internet as its IP), one was wired LAN, and other was wireless AP (WAP11). But the /28 (255.255.255.248) wireless subnet was within my /24 main LAN subnet and proxy_arp was enabled to answer LAN arp requests for wireless IPs.

In that case the default gateway for the LAN was Linux ethernet connected to the LAN. Gateway for wireless was ethernet IP connected to WAP11. Linux knew whether to route /28 wireless traffic to LAN or internet, and whether to answer arp requests from main LAN for wireless subsubnet.

Use /24 NAT won't care one way or another.