Hi,
I think that you have to do:
Box #1
route add -net 216.192.10.0 netmask 255.255.255.0 gw 215.192.10.15
Box #2
ipfwadm -F -a m -S 215.192.10.0/24 -D 0.0.0.0/0
Please inform me if this solves your problem
Agim Cami
[EMAIL PROTECTED]
At 09:49 PM 11/22/99 -0200, Jose Luis Saraiva Hime wrote:
>Hello, everybody:
>
>I am experiencing a problem with network routing, I hope some of you can
>help me... Let me explain my problem to you:
>
>I have two lan segments: LAN "A" (215.192.10.0/255.255.255.0) and
> LAN "B" (216.192.10.0/255.255.255.0)
>
>I have three Linux boxes: all of them with Red Hat Linux 5.2,
>Kernel 2.0.36.
>
>The box #1 has one ethernet adapter and participates on LAN "A";
>The box #2 has TWO ethernet adapters and participates on both LANs: "A" and
>"B";
>The box #3 has one ethernet adapter and participates on LAN "B";
>So, box #2 is the router between LANs "A" and "B".
>
>I have configured (properly ???) all routing tables and firewall policies
(see
>the outputs below); box #1 can successfully ping box #2 at its LAN "B"
>address;
>box #3 can successfully ping box #2 at its LAN "A" address but BOX #1 CAN NOT
>PING BOX #3 AT ALL.
>
>+------------------------+
>| Box #1 |
>| eth0: LAN A |--+
>| IP 215.192.10.1 | |
>+------------------------+ |
> | LAN segment "A"
>+------------------------+ |
>| Box #2 | |
>| eth0: LAN A |--+
>| IP 215.192.10.15 |
>| eth1: LAN B |--+
>| IP 216.192.10.15 | |
>+------------------------+ |
> | LAN segment "B"
>+------------------------+ |
>| Box #3 | |
>| eth0: LAN B |--+
>| IP 216.192.10.1 |
>+------------------------+
>
>Am I doing something wrong? I have made EXACTLY this same configuration on
>IBM/AIX boxes, and everything worked fine.
>
>
>Thanks in advance,
>Hime
>
>
>============ Routing table at box #1 ============
>[root@mor7 /root]# route -n
>Kernel IP routing table
>Destination Gateway
> Genmask Flags Metric Ref Use Iface
>215.192.10.0
>0.0.0.0 255.255.255.0 U 0 0 11449 eth0
>216.192.10.0
> 215.192.10.15 255.255.255.0 UG 0 0 2 eth0
>127.0.0.0
> 0.0.0.0 255.0.0.0 U 0 0 14 lo
>
>============ Routing table at box #3 ============
>[root@treinamento /root]# route -n
>Kernel IP routing table
>Destination
>Gateway Genmask Flags Metric Ref Use Iface
>216.192.10.0
> 0.0.0.0 255.255.255.0 U 0 0 4 eth0
>215.192.10.0
> 216.192.10.15 255.255.255.0 UG 0 0 9 eth0
>127.0.0.0
> 0.0.0.0 255.0.0.0 U 0 0 1 lo
>
>============ Routing table and firewall policies at box #1 ============
>[root@per1 /root]# route
>Kernel IP routing table
>Destination Gateway
> Genmask Flags Metric Ref Use Iface
>215.192.10.0 *
> 255.255.255.0 U 0 0 7 eth0
>216.192.10.0 *
> 255.255.255.0 U 0 0 6 eth1
>127.0.0.0 *
> 255.0.0.0 U 0 0 2 lo
>
>[root@per1 /root]# ipfwadm -F -l
>IP firewall forward rules, default policy:
>accept
>
>[root@per1 /root]# ipfwadm -O -l
>IP firewall output rules, default policy:
>accept
>
>[root@per1 /root]# ipfwadm -I -l
>IP firewall input rules, default policy:
>accept
>
>I had also tried with the following firewall policies
>
>[root@per1 /root]# ipfwadm -F -l
>IP firewall forward rules, default policy:
>accept
>type prot source destination ports
>acc all
> anywhere anywhere n/a
>
>[root@per1 /root]# ipfwadm -I -l
>IP firewall input rules, default policy:
>accept
>type prot source destination ports
>acc all
> anywhere anywhere n/a
>
>[root@per1 /root]# ipfwadm -O -l
>IP firewall output rules, default policy:
>accept
>type prot source destination ports
>acc all
> anywhere anywhere n/a
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-net" in
>the body of a message to [EMAIL PROTECTED]
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
