[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: IP Masq troubles

David P James was roused into action on 2003-01-04 00:29 and wrote:
Here's the box: 3.0r1, Kernel 2.2.20 (gave up on trying to compile/install a 2.4.x kernel). eth1 is the external, eth0 internal. 





ISP
-->
- 24.x.y.z (external, by DHCP)
RH7.3 Gateway
-192.168.1.1 (internal)
-->hub-->
- 192.168.1.14 (external, by DHCP - eth1)
Debian 3.0r1 gateway-to-be
- 192.168.0.1 (internal - eth0)
-->hub-->
- 192.168.0.10 (eth0, by DHCP)
My Debian 3.0 machine


When this gets moved to my university city, it will look like:

ISP
-->
- 24.x.y.z (external, by DHCP - eth1)
Debian 3.0r1 gateway-to-be
- 192.168.0.1 (internal - eth0)
-->hub-->
- 192.168.0.10 (eth0, by DHCP)
My Debian 3.0 machine
So the fact that the gateway-to-be is behind another firewall shouldn't matter, right?
Right now, the gateway-to-be can connect to the internet. My box in this set up behind it can't, but it can connect to the gateway-to-be and get its IP from there through DHCP (eg I can ping 192.168.0.1 but not 192.168.1.1 or 192.168.1.14 or anything else - the network is unreachable). I've installed the ipmasq package, which, the last time I did this a year and a half ago set up everything fine. 

The relevant bits of interfaces are:

      auto eth1
      iface eth1 inet dhcp

      auto eth0
      iface eth0 inet static
      address 192.168.0.1
      network 192.168.0.0
      netmask 255.255.255.0
      broadcast 192.168.0.255
The problem, amazingly, was that the modules ipip and/or ip_gre weren't loaded into the kernel (I don't know which is the problem yet as both are now loaded and forwarding is working). Last time when I installed Debian 2.2 I loaded every ipv4 module there was in a shotgun type of approach. This time I didn't... 


--
David P. James
Ottawa, Ontario
http://members.rogers.com/dpjames/

The bureaucratic mentality is the only constant in the universe.
-Dr. Leonard McCoy, Star Trek IV
Reply to: