(IPTables) old dog needs some help with a dual-homed debian (woody) system

(IPTables) old dog needs some help with a dual-homed debian (woody) system

Post by U. Sarma Seetamra » Sat, 18 Oct 2003 06:44:58



(N)          WIRELESS            (H)           ETHERNET     (x)
Notebook         <---->        linux-dev        <----->   linux-fs
w/ wireless              w/ wireless IP 10.0.2.1          ethernet
card IP: 10.0.2.2        &  ethernet IP 10.0.1.12         IP 10.0.1.9

NOTE: THERE ARE NO wireless HUBS (that stuff that we can buy at
stores).

The last machine (x) is ONE sample machine on the ethernet hub, I
picked it to explain my problem better.

(N) can ping (H) and vice versa.  ANd ofcourse, the ethernet network
has been working for a while now.

But (N) cannot PING anything other than (H) and (N)'s IP is assigned
manually.
(N) is a windows PC with netmask set to 255.255.0.0  and the gateway
to 10.0.1.1
And yes, the OTHER machines can ping each other quite well over
othernet (10.0.1.x).

I tried all possible combinations of netmasks, but no luck.
In my youth :-) I used to tell IPCHAINS to ' -j FORWARD ' and that
would (I think) have done the job...

Please let me know what I neeed to do.

Thanks in advance...

Sarma


Linux linuxdev.localdomain 2.4.16-k6 #1 Wed Nov 28 10:34:08 EST 2001
i586 unknown


Chain INPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere


Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref  
Use Iface
10.0.2.1        0.0.0.0         255.255.255.255 UH    0      0      
0 eth1
10.0.2.0        0.0.0.0         255.255.255.0   U     0      0      
0 eth1
10.0.1.0        0.0.0.0         255.255.255.0   U     0      0      
0 eth0
0.0.0.0         10.0.1.1        0.0.0.0         UG    0      0      
0 eth0


eth0      Link encap:Ethernet  HWaddr 00:48:54:1C:30:CF
          inet addr:10.0.1.12  Bcast:10.0.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:155489 errors:0 dropped:0 overruns:0 frame:0
          TX packets:127575 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:16425790 (15.6 MiB)  TX bytes:15916255 (15.1 MiB)
          Interrupt:11 Base address:0xa000

eth1      Link encap:Ethernet  HWaddr 00:00:F1:11:73:8D
          inet addr:10.0.2.1  Bcast:10.0.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1400  Metric:1
          RX packets:3863 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2274 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:332766 (324.9 KiB)  TX bytes:272377 (265.9 KiB)
          Interrupt:3

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:693 errors:0 dropped:0 overruns:0 frame:0
          TX packets:693 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:46335 (45.2 KiB)  TX bytes:46335 (45.2 KiB)

=====================================
Below is the IFCONFIG on the machine (x), just in case the cause of
the problem is here ....
=====================================


eth0      Link encap:Ethernet  HWaddr 00:0A:E6:16:CD:3C
          inet addr:10.0.1.9  Bcast:10.0.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5200126 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22054147 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:559561516 (533.6 MiB)  TX bytes:3671206402 (3.4
GiB)
          Interrupt:5 Base address:0xcc00

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:9613 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9613 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1482431 (1.4 MiB)  TX bytes:1482431 (1.4 MiB)


Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref  
Use Iface
10.0.0.0        0.0.0.0         255.255.0.0     U     0      0      
0 eth0
0.0.0.0         10.0.1.1        0.0.0.0         UG    0      0      
0 eth0

[End]

 
 
 

1. NEED HELP IN DUAL-HOMED LINUX

    I will greatly appreaciate any little help on setting up a Red-Hat
5.0 using 2 network adapters connecting 2 different networks. I've
exhausted all my howtos and other documents but still cannot get to ping

across the 2 networks through the 2 network adapters. I'm doing this to
set up a dual-homed firewall.

    LAN -------- 192.90.1.23  +  202.186.246.39 --------- To the
Internet
                          1st card             2nd card

I can ping both networks from the Linux server but I can't ping from any

other node from one network to the other and vice-versa.

Do I need a router to sit between the LAN and 192.90.1.23 and another
router between the Internet and 202.186.246.39? Will 'routed' do the job

of routing between the 2 networks without the need for routers?

Thanks a lot!

2. RS6000/AIX4.2 Mouse problem

3. simple dual-homed iptables script

4. Do I even need a nameserver?

5. Probleme mit debian woody, iptables, masquerading

6. Printing Problem

7. debian woody uses old mawk instead of gawk

8. IlogBuilder library replacement

9. Benefits of dual-homed firewall for home network?

10. 3.4-R: natd problems on dual-homed system

11. g++ 2.95 and g++ 3.0 on same debian woody system ???

12. Spamassassin and razor system-wide on Debian Woody

13. How I upgraded to debian-stable (potato) to debian-testing (woody)