Hello, I've been trying to get my Linux IP masquerading gateway going, but
I've run into a few problems. Initially, I could not get any connections 
with my 
ethernet cards, but Linux (Red Hat 5) did detect one of them. I have two 
Realtek
NE2000 compatible cards. One is PCI, the other is ISA. After struggling 
with them 
for awhile, I read in some of the docs that I have that you had to 
re-compile the
kernel to enable linux to detect more than one adapter card.

Ok, no prob. I re-compiled the kernel and said yes to all the IP 
masquerading
options (might as well compile that in if I'm re-compiling...) and sure 
enough on 
the next boot, Linux detected *both* cards. However, I can't ping any of 
the
computers on the LAN (192.168.0.*) but I can ping the ADSL providers 
gateway.
So the card connected to the ADSL line must at least be working, but that's 
all
I can do with it is ping the gateway, I cannot ping any other internet 
address, and
I can't reach the DNS servers provided by my ISP.

My route table looks something like this:


Dest.                   Gateway                                                        
 
Interface
206.37.47.0                     *                                                      
         eth0
192.168.0       .0                      *                                              
                 
eth1

I'm not at my linux box so I don't know what the rest of the values in the 
table
were. The address of the gateway would be 206.37.47.1 (These are not the 
exact IP addresses I use, different numbers for privacy, same format).

The interface IP addresses should be 
eth0            206.37.47.55            ====> connected to the ADSL modem
eth1            192.168.0.4             ====> connected to the LAN

I'm wondering about the gateway entries in the route table. Shouldn't there 
be 
a gateway assigned to eth0? When I installed it and oit asked me to 
configure
the network I entered the correct gateway in the gateway section, but it 
does not 
turn up in the route table. I also saw somewhere that you need to provide a
route to the gateway, before you can use that as a gateway for a different 
route.
Shouldn't the table route all info other than 192.168.0.* to eth0? The way 
it seems
now is that it is only routing 206.37.47.* to eth0. Any help in 
explaining/clarifying
this mess would be appreciated. Thanks.

-----------------------------------------------
        Joe Duncan
        Systems
        Human Resources Development Canada
        (613)997-7986
        [EMAIL PROTECTED]
-----------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]

Reply via email to