RE: urgent TEQL problem

Linux Advanced Routing and Traffic Control

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

 



One more thing to add is that when I "ping 16.119.144.66" from Node1
(16.119.144.66 is the teql0 of Node2), all messages I saw from
Node1.eth1 are ARP messages "Who has 16.119.144.66? Tell 16.119.144.33".

Thanks,
-Ji

-----Original Message-----
From: lartc-bounces@xxxxxxxxxxxxxxx
[mailto:lartc-bounces@xxxxxxxxxxxxxxx] On Behalf Of Li, Ji
Sent: Thursday, June 23, 2005 3:45 PM
To: Pan'ko Alexander; lartc@xxxxxxxxxxxxxxx
Cc: jli@xxxxxxx
Subject: RE:  urgent TEQL problem

Thanks for your advice. The routing tables are shown below. Your help is
highly appreciated!


Topology: Node1.eth0 and Node2.eth0 are directly connected. Node1.eth1
is connected to Gateway.eth0, and Node2.eth1 is connected to
Gateway.eth1.
The problem is: When I "ping 16.119.144.66" from Node1, all ping request
go to Node1.eth0, no packet goes to Node1.eth1.

Node 1:
- eth0:  16.119.144.21
- eth1:  16.119.144.33
- teql0: 16.119.144.34

Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
16.119.144.66   0.0.0.0         255.255.255.255 UH    0      0        0
teql0
16.119.144.27   0.0.0.0         255.255.255.255 UH    0      0        0
eth0
16.119.144.32   0.0.0.0         255.255.255.224 U     0      0        0
eth1
16.119.144.64   16.119.144.35   255.255.255.224 UG    0      0        0
eth1
0.0.0.0         16.119.144.35   0.0.0.0         UG    0      0        0
eth1


Node 2:
- eth0:  16.119.144.27
- eth1:  16.119.144.65
- teql0: 16.119.144.66

Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
16.119.144.21   0.0.0.0         255.255.255.255 UH    0      0        0
eth0
16.119.144.34   0.0.0.0         255.255.255.255 UH    0      0        0
teql0
16.119.144.32   16.119.144.67   255.255.255.224 UG    0      0        0
eth1
16.119.144.64   0.0.0.0         255.255.255.224 U     0      0        0
eth1
0.0.0.0         16.119.144.67   0.0.0.0         UG    0      0        0
eth1


Gateway:
- eth0: 16.119.144.35
- eth1: 16.119.144.67

Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
16.119.144.32   0.0.0.0         255.255.255.224 U     0      0        0
eth0
16.119.144.64   0.0.0.0         255.255.255.224 U     0      0        0
eth1
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0
lo 


Best regards,
-Ji

-----Original Message-----
From: lartc-bounces@xxxxxxxxxxxxxxx
[mailto:lartc-bounces@xxxxxxxxxxxxxxx] On Behalf Of Pan'ko Alexander
Sent: Thursday, June 23, 2005 2:51 PM
To: lartc@xxxxxxxxxxxxxxx
Subject: Re:  urgent TEQL problem


I advice you to do not discribe your problem, but give your routing
rules on both sides. I think here is your problem.

--
With best regards, Pan'ko Alexander.
pankoAA@xxxxxxxxx
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
_______________________________________________
LARTC mailing list
LARTC@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc


[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux