Greetings, I'm just a bit confused, I have two network interfaces and I was wondering about the gateways, currently I have two default gateways, which is right? chadlap:~ # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0 * 255.255.255.0 U 0 0 0 eth1 196.25.100.0 * 255.255.255.0 U 0 0 0 eth0 link-local * 255.255.0.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default preload.teq.pin 0.0.0.0 UG 0 0 0 eth1 default techno.za.tisca 0.0.0.0 UG 0 0 0 eth0 chadlap:~ # My laptop is situated between two networks, on the one side I have teq.pinteq (wireless) and on the other I have .za.tiscali. Surely you can't ( as I currently do!) have two defualt gateways, but there are two gateways to pass to the internet. My correct path to the internet would be first to preload, and then techno, but since I am on both networks, suse has decided it be best if I have both, What would you suggest? TIA Chad
On Wednesday 20 April 2005 12:44 pm, Chadley Wilson wrote:
Greetings,
I'm just a bit confused, I have two network interfaces and I was wondering about the gateways, currently I have two default gateways, which is right?
chadlap:~ # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.2.0 * 255.255.255.0 U 0 0 0 eth1 196.25.100.0 * 255.255.255.0 U 0 0 0 eth0 link-local * 255.255.0.0 U 0 0 0 eth0 loopback * 255.0.0.0 U 0 0 0 lo default preload.teq.pin 0.0.0.0 UG 0 0 0 eth1 default techno.za.tisca 0.0.0.0 UG 0 0 0 eth0 chadlap:~ #
My laptop is situated between two networks, on the one side I have teq.pinteq (wireless) and on the other I have .za.tiscali. Surely you can't ( as I currently do!) have two defualt gateways, but there are two gateways to pass to the internet.
My correct path to the internet would be first to preload, and then techno, but since I am on both networks, suse has decided it be best if I have both, What would you suggest? No. You can only have 1 default interface. Your static routing table may have as many different networks coded, but only 1 default. Think of the routing table as a traffic intersection. There may always be many ways to get to the same place, but the road signs must be designed to point in a specific way: for instance, the intersection of the Mass. Pike and route 9 in Framingham, Ma. The signs on route 9, say to take the Mass. Pike to Boston or to New York, eventhough route 9 goes directly into Boston, and route 9 west used to be the main road to New York. In your case: eth0: is the main way to get to the Internet and to subnet 192.168.2. while eth1 is the main way to subnet 196.25.100., eventhough you can get to the Internet via eth1 also.
--
Jerry Feldman
On Wednesday 20 April 2005 19:42, Jerry Feldman wrote:
On Wednesday 20 April 2005 12:44 pm, Chadley Wilson wrote:
0 0 lo default preload.teq.pin 0.0.0.0 UG 0 0 0 eth1 default techno.za.tisca 0.0.0.0 UG 0 0 0 eth0 chadlap:~ #
No. You can only have 1 default interface. Your static routing table may have as many different networks coded, but only 1 default. Think of the routing table as a traffic intersection. There may always be many ways to get to the same place, but the road signs must be designed to point in a specific way: for instance, the intersection of the Mass. Pike and route 9 in Framingham, Ma. The signs on route 9, say to take the Mass. Pike to Boston or to New York, eventhough route 9 goes directly into Boston, and route 9 west used to be the main road to New York. In your case: eth0: is the main way to get to the Internet and to subnet 192.168.2. while eth1 is the main way to subnet 196.25.100., eventhough you can get to the Internet via eth1 also.
Thanks Jerry I will remove the one default GW, but do I leave it out or put it somewhere else, such as a normal gateway? TIA Chad
On Wednesday 20 April 2005 2:45 pm, Chadley Wilson wrote:
Thanks Jerry I will remove the one default GW, but do I leave it out or put it somewhere else, such as a normal gateway? You would leave eth1 in there but associate it with a specific subnet. Let's say that one interface is connected to let's say, Comcast and the other one to Verizon. (Directly or indirectly). Since Comcast is directly attached, this is the default, but you might want to hard code some verizon sites to eth1.
This is why we have a routing daemon, routed. it builds a dynamic routing
table. But in your case, a static routing table is best.
--
Jerry Feldman
participants (2)
-
Chadley Wilson
-
Jerry Feldman