CN100568852C - The router of operation IS-ISv6 is set up the method for single topology syntople - Google Patents
The router of operation IS-ISv6 is set up the method for single topology syntople Download PDFInfo
- Publication number
- CN100568852C CN100568852C CNB2006100600345A CN200610060034A CN100568852C CN 100568852 C CN100568852 C CN 100568852C CN B2006100600345 A CNB2006100600345 A CN B2006100600345A CN 200610060034 A CN200610060034 A CN 200610060034A CN 100568852 C CN100568852 C CN 100568852C
- Authority
- CN
- China
- Prior art keywords
- interface
- supported
- support
- agreement
- route entity
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
A kind of method of setting up Intermediate System to Intermediate System single topology syntople, router in prior art passes through to make up hello packet according to the IS-IS configuration of oneself, and support interface transmissions/the receptions hello packet of IS-IS to set up on the basis of syntople having disposed, proposition at this interface in the remote interface support and only support to accept under the situation of IP agreement of route entity support under this interface the neighbours' of remote interface conduct oneself scheme.Adopt the present invention, the syntople that the IS-ISv6 single topology is set up has guaranteed that IPv4 and IPv6 advertising of route are reliable and stable, path black hole can not occur.
Description
Technical field
The present invention relates to IPv6 Data Communication in Computer Networks field, be to use the ip router of Intermediate System to Intermediate System IS-IS to set up the technology of IS-ISv6 single topology syntople.
Background technology
Along with the application of IPv6, Intermediate System to Intermediate System IS-IS will expand and support the IPv6 agreement, becomes IS-ISv6.IS-ISv6 divides single topology and two kinds of patterns of many topologys.About the scheme of IS-ISv6 single topology, see and organize IETF (The Internet Engineering Task Force) by Internet document " Routing IPv6with IS-IS " (draft-ietf-isis-ipv6-06.txt).How topological about IS-ISv6, see IETF document " M-ISIS:Multi Topology (MT) Routing in IS-IS " (draft-ietf-isis-wg-multi-topology-11.txt).
The user wants a certain router operation Intermediate System-Intermediate System, and wants to support IS-IS on certain interface on the router, and do two work: (1) disposes the Intermediate System-Intermediate System entity; (2) interface will dispose IS-IS and support any IP topology, promptly disposes IS-ISv4 or/and IS-ISv6.If configuration IS-ISv4 illustrates this interface support of customer requirements IPv4, IPv4 routes all on this interface will be announced by IS-IS; If configuration IS-ISv6 illustrates this interface support of customer requirements IPv6, IPv6 routes all on this interface will be announced by IS-IS.More than these 2 be the basic configuration requirement of all products of present industry operation Intermediate System-Intermediate System.
Two IS-IS routers that directly link to each other will be set up syntople by the IS-IS hello packet before the intercommunication route.If it is incorrect to set up the method for syntople, can cause the appearance of path black hole.
According to the standard (RFC1142, RFC1195 and RFC3373) that Internet organizes IETF to announce, the process of setting up syntople is as follows:
(1) router makes up hello packet according to the IS-IS configuration of oneself, and is disposing the interface transmission/reception hello packet of supporting IS-IS.
(2) the original state of the interface of router is down.Received the hello packet that remote interface (with the interface of the own router that directly links to each other) is sent by interface,, judged whether to accept the neighbours of far-end as oneself according to the configuration of self.If of course, the state of this interface changes init into from down so.The hello packet that sends has again afterwards just shown that this node accepts far-end as own neighbours.If can not accept remote interface, receive that hello packet will be dropped, Interface status is constant.
(3) if remote interface is also accepted this interface (being that the remote interface state changes init into from down), the hello packet that it sends has shown that also remote interface acceptance oneself (this interface) is as neighbours.After this interface was received such hello packet, the state of this interface became up from init so.Similarly, the state of remote interface also can become up from init.Syntople is set up like this.
The direct interconnection router of operation IS-ISv6 Routing Protocol needed to form the IS-IS syntople before the announcement route.Intermediate System to Intermediate System is set up syntople by transmission/reception hello packet.But document " Routing IPv6with IS-IS " does not illustrate the router interface of operation IS-ISv6 single topology and how to remove to judge whether to accept to send the remote interface (interface of direct-connected router) of hello packet according to the information on the hello packet of receiving, thereby sets up the method for IS-ISv6 single topology syntople.In other words, document " RoutingIPv6with IS-IS " does not illustrate how the router interface of operation IS-ISv6 single topology is accepted and the neighbours of the own router interface that directly links to each other as oneself.
Summary of the invention
Technical problem to be solved by this invention is, the router that proposes a kind of IS-ISv6 of operation is set up the method for single topology syntople, has solved the interface that does not have in the prior art to solve and how to have accepted and the problem of the own router interface that directly links to each other as IS-ISv6 single topology neighbours.
The present invention is by the following technical solutions:
The original state of the interface of step 2, router is down, receive the hello packet that remote interface sends after, according to the configuration of self, judge whether to accept the neighbours of remote interface as oneself; If of course, the state of this interface changes init into from down so; The hello packet that sends afterwards shows that this interface accepts far-end as own neighbours; If can not accept remote interface, receive that hello packet will be dropped, Interface status is constant;
If the step 3 remote interface is also accepted this interface, the remote interface state changes init into from down, and the hello packet that it sends shows that also remote interface accepts this interface as neighbours; After this interface was received such hello packet, state became up from init; Similarly, the state of remote interface also can become up from init; Syntople is set up;
In step 2, at this interface in the remote interface support and only support to accept the neighbours of remote interface under the situation of IP agreement of route entity support under this interface as oneself, similarly, remote interface is in the support of this interface and only support to accept the neighbours of this interface as oneself under the situation of IP agreement of route entity support under the remote interface; Wherein, the IP agreement comprises IPv4 and IPv6.
In the solution of the present invention, remote interface support and only support that the IP agreement of route entity support is meant under this interface:
(a) remote interface is supported all IP agreements that the affiliated route entity of this interface is supported;
(b) remote interface is only supported the IP agreement that the affiliated route entity of this interface is supported;
(a) herein and (b) order can put upside down, promptly also can judge (b) earlier and then judge (a).
In the solution of the present invention, this interface support and only support the IP agreement that route entity is supported under the remote interface is meant:
(a) this interface is supported all IP agreements that the affiliated route entity of remote interface is supported;
(b) this interface is only supported the IP agreement that the affiliated route entity of remote interface is supported.
(a) herein and (b) order can put upside down, promptly also can judge (b) earlier and then judge (a).
Adopt the method for the invention, the syntople that the IS-ISv6 single topology is set up has guaranteed that IPv4 and IPv6 advertising of route are reliable and stable, path black hole can not occur.
If the method that the router R1 of an operation IS-ISv6 single topology has used the present invention to propose, started how topology of IS-ISv6 with router R2 that it directly links to each other, router R1 can set up or not set up syntople suitably, can not cause the IS-IS calculating route of R1 or R2 unusual, for example, path black hole can not appear.
If the method that the router R1 of an operation IS-ISv6 single topology has used the present invention to propose, started the IS-IS that makes up support IPv6 with the router R2 that it directly links to each other, for example, do not support the IS-IS of IS-ISv6, router R1 also can set up or not set up syntople suitably, can not cause the IS-IS calculating route of R1 or R2 unusual, for example, path black hole can not occur.
Description of drawings
Fig. 1 is that this interface judges whether remote interface can set up one of the mode of syntople flow chart;
Fig. 2 is that this interface judges whether remote interface can set up two flow charts of the mode of syntople;
Fig. 3 is one of a networking example schematic diagram;
Fig. 4 is two schematic diagrames of networking example;
Fig. 5 is three schematic diagrames of networking example.
Embodiment
On a router, can move a plurality of IS-IS route entities.For simplicity, in the following description, on a router, just move an IS-IS route entity, and the interface of any support IS-IS, this entity all belonged to.
When any one interface configuration of router IPv4 address and IS-ISv4 the time, we think that the IS-IS route entity of this router operation supports IPv4, the hello packet that any one interface of router is sent all has the mark 0xCC that entity is supported IPv4, i.e. NLPID 0xCC; When any one interface configuration of router when starting IPv6 and IS-ISv6, we think that the IS-IS route entity of this router operation supports IPv6, the hello packet that any one interface of router is sent all has the mark that entity is supported IPv6, i.e. NLPID 0x8E.NLPID carries (seeing ietf standard RFC1195) by TLV129.
When the interface configuration of router IS-ISv4 the time, the hello packet that it sends has the address of this interface IPv4.This interface IP address carries (seeing ietf standard RFC1195) by TLV132; When the interface configuration of router IS-ISv6 the time, the hello packet that it sends has the IPv6linklocal address of this interface.(seeing ietf draft " Routing IPv6with IS-IS ", i.e. draft-ietf-isis-ipv6-06.txt) carried by TLV232 in this linklocal address.
More than be our standard RFC1142 to IETF, RFC1195 and draft " Routing IPv6withIS-IS " understanding (draft-ietf-isis-ipv6-06.txt).
If we receive certain hello packet, find that this message has NLPID 0xCC, and have the address of at least one IPv4 that we say the interface support IPv4 that sends this hello packet.If we receive certain hello packet, find that this message has NLPID 0x8E, and have the linklocal address of at least one IPv6 that we say the interface support IPv6 that sends this hello packet.
After receiving hello packet, how does this interface accept remote interface, allows the state of oneself become init from down? the present invention proposes this interface and accepts the condition of remote interface and be: remote interface support and only support the IP agreement (the IP agreement comprises IPv4 and IPv6) that route entity is supported under this interface.This condition is meant:
(a) remote interface is supported all IP agreements that the affiliated route entity of this interface is supported
(b) remote interface is only supported the IP agreement that the affiliated route entity of this interface is supported.
When as (a) and (b) all setting up, this interface is just accepted remote interface, and the state of this interface becomes init from down.As long as (a) or (b) one of them is false, the hello packet of receiving can abandon, and processing can finish, and this interface is not accepted remote interface, and the state of this interface remains unchanged.
Certainly, in above-mentioned condition, if our hypothesis is supported IPv4, the IPv4 network segment of remote interface has at least one of them the IPv4 network segment with this interface to belong to the same network segment so.In this piece of writing explanation, unless additional description, our this hypothesis is all set up.
In our this method of realization, (a) with the sequencing that (b) does not have to realize.That is, receive hello packet after, can judge (b) earlier, (a) judged in the back, perhaps judges (a) earlier, (b) judged in the back.
Fig. 1 is that this interface judges whether remote interface can set up one of the mode of syntople flow chart.This interface is according to configuration, known what IP agreement own affiliated IS-IS route entity supports, to receiving the hello packet of remote interface, judge earlier whether remote interface supports all IP agreements that the affiliated route entity of this interface is supported, judge then whether remote interface only supports the IP agreement that the affiliated route entity of this interface is supported.
Fig. 2 is that this interface judges whether remote interface can set up one of the mode of syntople flow chart.Different with Fig. 1 is that the sequencing of judging is different.
With three examples this Rule of judgment is described below.In the realization of example, our first Rule of judgment (a), (b) judged in the back.In all examples, interface all is up below.
Example 1 is as Fig. 3: router Router1 and Router2 operation IS-IS, and interface A and B have disposed IPv4 address and A, and B belongs to the same network segment.In addition, A and B have started IPv6.
To the networking of Fig. 3, we dispose like this:
Interface A:is-is v4, is-is v6
Interface B:is-is v4, is-is v6
Because interface A has started is-is v4, the IP agreement that the IS-IS route entity of router Router1 (route entity under the A) is supported comprises IPv4.Because A has also started is-is v6, the IP agreement of the IS-IS route entity support of Router1 also comprises IPv6.Similarly, the agreement that the IS-IS route entity of Router2 (route entity under the B) is supported had both comprised IPv4, also comprised IPv6.That is:
Router?1：ip，ipv6
Router?2：ip，ipv6
After interface B received the hello packet that A sends, according to the method that we propose, B judged:
Does (a) remote interface A support all IP agreements that the affiliated route entity of this interface B is supported? we know IS-IS route entity support IPv4 and the IPv6 that moves on Router2, whether support IPv4 and IPv6 so B will judge A.Because A has disposed is-is v4, the hello packet that A sends has the mark 0xCC that supports IPv4, and has the interface IPv4 address of A, so B thinks that A supports IPv4.Because A has disposed is-is v6, the hello packet that A sends has the mark 0x8E that supports IPv6, and has the interface IPv6linklocal address of A, so B thinks that A also supports IPv6.And the route entity under the B is supported IPv4 and IPv6.Like this, B thinks that A supports all IP agreements that own affiliated route entity is supported.
Does (b) remote interface A only support the IP agreement that the affiliated route entity of B is supported? by above-mentioned processing to (a), B thinks that A supports IPv4 and IPv6, and A does not have the IP agreement of support except IPv4 and IPv6.So B thinks that remote interface A only supports the IP agreement that the affiliated route entity of B is supported.
Like this, B accepts A, and the state of oneself is become init from down.Use same Rule of judgment, A also accepts B, and the state of A becomes init from down.Afterwards, use traditional processing procedure (seeing RFC1142, RFC1195 and RFC3373), A and B set up syntople at last, and state all can become up.
Example 2 is as Fig. 4: router Router1 and Router2 operation IS-IS, and interface A, C and B have disposed IPv4 address and A, and B belongs to the same network segment.In addition, A and B have started IPv6.
To the networking of Fig. 4, we dispose like this:
Interface A:is-is v6
Interface B:is-is v4, is-is v6
Interface C:is-is v4
Because interface C has started is-is v4, the IP agreement that the IS-IS route entity of router Router1 (route entity under A and the C) is supported comprises IPv4.Because interface A has started is-is v6, the IP agreement of the IS-IS route entity support of Router1 also comprises IPv6.
Interface B has started is-is v4 and is-is v6, so the agreement that the IS-IS route entity of Router2 (route entity under the B) is supported had both comprised IPv4, also comprises IPv6.That is:
Router?1：ip，ipv6
Router?2：ip，ipv6
After interface B received the hello packet that A sends, according to the method that we propose, B judged:
Does (a) remote interface A support all IP agreements that the affiliated route entity of this interface B is supported? we know IS-IS route entity support IPv4 and the IPv6 that moves on Router2, whether support IPv4 and IPv6 so B will judge A.Because A has disposed IS-ISv6, the hello packet of A has the mark 0x8E that supports IPv6, and has the interface IPv6linklocal address of A, so B thinks that A supports IPv6.B finds that the hello packet of A has the mark 0xCC (interface C configuration IS-ISv4 causes hello packet to have 0xCC) that supports IPv4, but do not have interface IPv4 address (because A is not activated IS-ISv4), be that the hello packet that A sends does not have interface IPv4 address, so B does not think that A supports IPv4.Like this, B does not think that A supports all IP agreements that own affiliated route entity is supported.
Does (b) remote interface A only support the IP agreement that the affiliated route entity of B is supported? by above-mentioned processing to (a), B thinks that A supports IPv4, and A does not have the IP agreement of support except IPv4 and IPv6.So B thinks that remote interface A only supports the IP agreement that the affiliated route entity of B is supported.
Condition (b) is set up, but because condition (a) is false, B does not accept A, the state of oneself is not become init from down.
After interface A received the hello packet that B sends, according to the method that we propose, A judged:
Does (a) remote interface B support all IP agreements that the affiliated route entity of this interface A is supported? we know IS-IS route entity support IPv4 and the IPv6 that moves on Router1, whether support IPv4 and IPv6 so A will judge B.B has disposed IS-ISv6, and the hello packet that B sends has the mark 0x8E that supports IPv6, and has the interface IPv6linklocal address of B, so A thinks that B supports IPv6.B has disposed IS-ISv4, and the hello packet that B sends has the mark 0xCC that supports IPv4, and has the IPv4 address of interface, so A thinks that B supports IPv4.Like this, A thinks that B supports all IP agreements that own affiliated route entity is supported.
Does (b) remote interface B only support the IP agreement that the affiliated route entity of A is supported? by above-mentioned processing to (a), A thinks that B supports IPv6 and IPv4, and B does not have the IP agreement of support except IPv4 and IPv6.So A thinks that remote interface B only supports the IP agreement that the affiliated route entity of A is supported.
Like this, A accepts B, and the state of oneself is become init from down.
But because B does not accept A, the state of two interfaces does not finally have up, does not set up syntople.
Example 3 is as Fig. 5: router Router1 and Router2 operation IS-IS, and interface A and B have disposed IPv4 address and A, and B belongs to the same network segment.In addition, A and B have started IPv6.
To the networking of Fig. 5, we dispose like this:
Interface A:is-is v6
Interface B:is-is v4, is-is v6
Because interface A has started is-is v6, the IP agreement that the IS-IS route entity of Router1 (route entity under the A) is supported comprises IPv6, and has only IPv6.
Interface B has started is-is v4 and is-is v6, so the agreement that the IS-IS route entity of Router2 (route entity under the B) is supported had both comprised IPv4, also comprises IPv6.That is:
Router?1：ipv6
Router?2：ip，ipv6
After interface B received the hello packet that A sends, according to the method that we propose, B judged:
Does (a) remote interface A support all IP agreements that the affiliated route entity of this interface B is supported? we know IS-IS route entity support IPv4 and the IPv6 that moves on Router2, whether support IPv4 and IPv6 so B will judge A.Because A has disposed IS-ISv6, the hello packet of A has the mark 0x8E that supports IPv6, and has the interface IPv6linklocal address of A, so B thinks that A supports IPv6.B finds not support the mark 0xCC of IPv4 by the hello packet of A, and (Router1 is without any an interface configuration IS-IS v4, cause hello packet not have 0xCC), do not have interface IPv4 address (because A is not activated IS-ISv4), so B does not think that A supports IPv4 yet.Like this, B does not think that A supports all IP agreements that own affiliated route entity is supported.
Does (b) remote interface A only support the IP agreement that the affiliated route entity of B is supported? by above-mentioned processing to (a), B thinks that A supports IPv6, and A does not have the IP agreement of support except IPv4 and IPv6.So B thinks that remote interface A only supports the IP agreement that the affiliated route entity of B is supported.
Because condition (a) is false, B does not accept A, the state of oneself is not become init from down.
After interface A received the hello packet that B sends, according to the method that we propose, A judged:
Does (a) remote interface B support all IP agreements that the affiliated route entity of this interface A is supported? we know the IS-IS route entity support IPv6 that moves on Router1, whether support IPv6 so A will judge B.Because B has disposed IS-ISv6, the hello packet that B sends has the mark 0x8E that supports IPv6, and has the interface IPv6linklocal address of B, so A thinks that B supports IPv6.Because B has disposed IS-ISv4, the hello packet that B sends has the mark 0xCC that supports IPv4, and has the IPv4 address of interface, so A thinks that B supports IPv4.Because A just supports IPv6, like this, A thinks that B supports all IP agreements that own affiliated route entity is supported.
Does (b) remote interface B only support the IP agreement that the affiliated route entity of A is supported? by above-mentioned processing to (a), A thinks that B also supports IPv4 except supporting IPv6.So A thinks that remote interface B is not an IP agreement of only supporting that the affiliated route entity of A is supported.
Because condition (b) is false, A does not accept B, the state of oneself is not become init from down.
The state of two interfaces does not all become init from down, does not more have up, does not finally set up syntople.
In example 3, if interface A has just disposed is-is v4, as long as but the Intermediate System to Intermediate System that operates on the router Router1 is supported the IS-ISv6 single topology, and the method for using the present invention to propose, the process of Chu Liing is similar with example 3 so.Just, start IS-ISv6 even without any interface, having made up the IS-IS that supports the IS-ISv6 single topology uses the method for the present invention's proposition that the hello packet of receiving is judged, still can set up or not set up syntople suitably, and can not cause the IS-IS calculating route of Router1 or Router2 unusual, for example, path black hole can not appear.
Claims (5)
1, the router of a kind of IS-ISv6 of operation is set up the method for single topology syntople, may further comprise the steps:
Step 1, router dispose according to the IS-IS of oneself, make up hello packet, and are disposing the interface transmission/reception hello packet of supporting IS-IS;
The original state of the interface of step 2, router is down, receive the hello packet that remote interface sends after, according to the configuration of self, judge whether to accept the neighbours of remote interface as oneself; If of course, the state of this interface changes init into from down so; The hello packet that sends afterwards shows that this interface accepts far-end as own neighbours; If can not accept remote interface, receive that hello packet will be dropped, Interface status is constant;
If the step 3 remote interface is also accepted this interface, the remote interface state changes init into from down, and the hello packet that it sends shows that also remote interface accepts this interface as neighbours; After this interface was received such hello packet, state became up from init; Similarly, the state of remote interface also can become up from init; Syntople is set up;
It is characterized in that this interface is in the remote interface support and only support to accept the neighbours of remote interface as oneself under the situation of IP agreement of route entity support under this interface; Remote interface is in the support of this interface and only support to accept the neighbours of this interface as oneself under the situation of IP agreement of route entity support under the remote interface; Wherein, the IP agreement comprises IPv4 and IPv6.
2, the router of the described operation of claim 1 IS-ISv6 is set up the method for single topology syntople, it is characterized in that remote interface support and only support the IP agreement that route entity is supported under this interface is meant:
(a) remote interface is supported all IP agreements that the affiliated route entity of this interface is supported;
(b) remote interface is only supported the IP agreement that the affiliated route entity of this interface is supported.
3, the router of the described operation of claim 1 IS-ISv6 is set up the method for single topology syntople, it is characterized in that remote interface support and only support the IP agreement that route entity is supported under this interface is meant:
(a) remote interface is only supported the IP agreement that the affiliated route entity of this interface is supported;
(b) remote interface is supported all IP agreements that the affiliated route entity of this interface is supported.
4, the router of the described operation of claim 1 IS-ISv6 is set up the method for single topology syntople, it is characterized in that this interface support and only support the IP agreement that route entity is supported under the remote interface is meant:
(a) this interface is supported all IP agreements that the affiliated route entity of remote interface is supported;
(b) this interface is only supported the IP agreement that the affiliated route entity of remote interface is supported.
5, the router of the described operation of claim 1 IS-ISv6 is set up the method for single topology syntople, it is characterized in that this interface support and only support the IP agreement that route entity is supported under the remote interface is meant:
(a) this interface is only supported the IP agreement that the affiliated route entity of far-end is supported;
(b) this interface is supported all IP agreements that the affiliated route entity of remote interface is supported.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100600345A CN100568852C (en) | 2006-03-22 | 2006-03-22 | The router of operation IS-ISv6 is set up the method for single topology syntople |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2006100600345A CN100568852C (en) | 2006-03-22 | 2006-03-22 | The router of operation IS-ISv6 is set up the method for single topology syntople |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101043425A CN101043425A (en) | 2007-09-26 |
| CN100568852C true CN100568852C (en) | 2009-12-09 |
Family
ID=38808642
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2006100600345A Active CN100568852C (en) | 2006-03-22 | 2006-03-22 | The router of operation IS-ISv6 is set up the method for single topology syntople |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100568852C (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102420739A (en) * | 2010-09-28 | 2012-04-18 | 杭州华三通信技术有限公司 | ISIS (Intermediate System to Intermediate System) neighbor maintaining method and ISIS device |
| CN103685012B (en) * | 2012-09-26 | 2017-06-16 | 中国电信股份有限公司 | The determination method and apparatus of forward-path in multiple topology |
| CN103780487B (en) * | 2014-01-29 | 2017-07-14 | 新华三技术有限公司 | Set up the method and device of Intermediate System-to-Intermediate System neighbours |
| CN105812168B (en) * | 2014-12-31 | 2019-02-15 | 北京神州泰岳软件股份有限公司 | A kind of method and apparatus for drawing network topological diagram |
| CN105591798B (en) * | 2015-07-24 | 2019-04-09 | 新华三技术有限公司 | The method, apparatus of OAM Information is transmitted in DCN |
| CN109309616B (en) * | 2017-07-27 | 2022-03-01 | 中兴通讯股份有限公司 | Notification method and device based on ISIS protocol |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1309135A1 (en) * | 2001-10-30 | 2003-05-07 | Alcatel | Forwarding of IP packets for routing protocols |
| CN1464704A (en) * | 2002-06-06 | 2003-12-31 | 深圳市中兴通讯股份有限公司 | Routing method based on link status |
| CN1571423A (en) * | 2003-07-19 | 2005-01-26 | 华为技术有限公司 | Method for implementing neighbor discovery of different link layer separated domain |
-
2006
- 2006-03-22 CN CNB2006100600345A patent/CN100568852C/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1309135A1 (en) * | 2001-10-30 | 2003-05-07 | Alcatel | Forwarding of IP packets for routing protocols |
| CN1464704A (en) * | 2002-06-06 | 2003-12-31 | 深圳市中兴通讯股份有限公司 | Routing method based on link status |
| CN1571423A (en) * | 2003-07-19 | 2005-01-26 | 华为技术有限公司 | Method for implementing neighbor discovery of different link layer separated domain |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101043425A (en) | 2007-09-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1677464B1 (en) | Packet distribution control method | |
| Clausen et al. | Mobile ad hoc network (manet) neighborhood discovery protocol (nhdp) | |
| US7720010B2 (en) | Tree based wireless mesh for an OSPF network with intra-tree communication optimization | |
| CN100568852C (en) | The router of operation IS-ISv6 is set up the method for single topology syntople | |
| US20160044145A1 (en) | Learning a mac address | |
| KR20070081733A (en) | Apparatus for setting multipath and method thereof | |
| CN109600293B (en) | GRE tunnel establishment method and system | |
| Harrison et al. | IPv6 Traffic Engineering in IS-IS | |
| WO2004036831B1 (en) | Determining a path through a managed network | |
| WO2008021686A3 (en) | System and method for routing and domain name system support of a mobile node | |
| CN102185766A (en) | Unicast forwarding method and forwarding equipment for responding messages by DHCP (Dynamic host configuration protocol) server | |
| US6947392B2 (en) | Methods and arrangements for building a subsource address multicast distribution tree using traced routes | |
| CN102546407A (en) | Message sending method and device | |
| CN102664811B (en) | Message forwarding method and device | |
| CN102932255B (en) | Method and device for selecting tunnel path | |
| EP2337275B1 (en) | Method of automatically discovering an adjacent network node | |
| US7263087B2 (en) | Method and system for adding IP routes to a routing mobile terminal with 3G messages | |
| JP6378121B2 (en) | Gateway apparatus and communication method | |
| EP4152701A1 (en) | Routing processing method and related device | |
| CN101674245A (en) | Exit port route filtering method and device | |
| US7562148B2 (en) | Distributed domain name service | |
| EP1835666B1 (en) | Communication device, routing method, and program | |
| CN101626341B (en) | Method and device for synchronizing information under link-state protocol | |
| JP7273125B2 (en) | Method and first network device for transmitting BIERv6 packets | |
| Cisco | Configuring OSPF |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |