Configuring a client to use a server as a gateway

I want to hook my network to two internet providers, and set it up so that if one internet service goes down, internet requests will automatically be routed to the one still up.

I’ve setup an IBM ThinkCntr with a USB wireless card. I’ve got the networking set up so I have access to the internet from the ThinkCntr

I’ve also enabled ip forwarding and masquerading in the firewall.

On my second machine I added a default route to my IBM server.
route add default gw 10.7.1.10

But I still can’t access the internet from the second machine.

Any ideas?

I’m actually getting pretty desperate here because I think my ISP, Speakeasy, went under. Their DSL is down and they aren’t responding to trouble tickets.

My idea is that you should provide more technical information instead of this story. Give systems a name. Show how systems are configured with statements like

ifconfig -a

and

route -n

Try to post a schematic diagram of the network. It is to easy to understand you wrong or not at all as it is now.

And do not forget to post computer text between CODE tags: Posting in Code Tags - A Guide

So, you’re advising me to post detailed configuration information concerning my firewall, directly hooked to the internet, on a public forum? Planning on doing a bit of hacking, are we? :slight_smile:

I’m learning about iptables, but there doesn’t seem to be much on how to use YAST to control them. I like GUI.

Here’s the route -n from the client machine. The 10.7.1.10 is the gateway computer, why aren’t requests being routed there?

route -n

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.7.1.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
0.0.0.0 10.7.1.10 0.0.0.0 UG 0 0 0 eth0

ping google.com

ping: unknown host google.com

On 10/23/2011 06:36 PM, dougnc wrote:

> So, you’re advising me to post detailed configuration information
> concerning my firewall, directly hooked to the internet, on a public
> forum? Planning on doing a bit of hacking, are we? :slight_smile:

well…one sure way to not get the help you need here is to refuse to
provide the info needed to help you…

so, here Henk, @dougnc and all the crackers out there have a lot of fun
hacking me:


linux-os114:~ # ifconfig -a
eth0      Link encap:Ethernet  HWaddr 1C:75:08:06:BA:9A
inet addr:192.168.1.101  Bcast:192.168.1.255  Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:3186757 errors:0 dropped:0 overruns:0 frame:0
TX packets:1770443 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:433765367 (413.6 Mb)  TX bytes:124723257 (118.9 Mb)
Interrupt:46

lo        Link encap:Local Loopback
inet addr:127.0.0.1  Mask:255.0.0.0
UP LOOPBACK RUNNING  MTU:16436  Metric:1
RX packets:689 errors:0 dropped:0 overruns:0 frame:0
TX packets:689 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:42608 (41.6 Kb)  TX bytes:42608 (41.6 Kb)

wlan0     Link encap:Ethernet  HWaddr 00:26:C7:AF:4B:16
BROADCAST MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

linux-os114:~ # route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     1      0        0 eth0
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0

btw, Henk is a volunteer moderator here with a real day job of herding
enterprise class servers/software around the net, safely… :slight_smile:


DD
openSUSE®, the “German Automobiles” of operating systems

  1. I did not ask anything about your firewall configuration.

  2. I asked you to post computer text between CODE tags. As you seem not to take the effort to do that, why should I take the effort to try to read it?

  3. From reading what I got (not half of what I asked for) I can see that 10.7.1.10 is the default gateway in a system (which one). But it does not prove that you can not reach another system, e.g. on the internet, from that system through that gateway.

  4. I also see your system can not resolve the hostname google.com to an IP address. That points to a broken DNS environment. And that MAY BE because you can not reach your DNS server, but first we should find out if you can reach the internet. And that is done by using IP addresses, not hostnames. Do that using

ping 74.125.79.104
  1. I asked for more information about your setup because you talk about client sytem, server system, second system. Most of those terms have no connection whatever with the problem. You have a system (please give it a name, it should have one allready), that you want to use as your default gateway by another system (please give it a name). And you assume that the system that acts as default gateway routes packets to/from the internet Is that gateway system indeed correct configured as router, did you prove that by using it from another system as gateway?

Please reread my other post and rethink if you want to provide the missing information. It is up to you. With much more joy I will spend my time trying to help others.

dougnc wrote:
> Any ideas?

As others have said, you have provided precious little information, and
then been coy about answering direct questions.

In particular, you haven’t said what operating system is running on the
various systems.

> Here’s the route -n from the client machine. The 10.7.1.10 is the
> gateway computer, why aren’t requests being routed there?

But at a guess, you have opensuse on your gateway and you haven’t
enabled routing on it. Routing is disabled by default on suse boxes for
security reasons.