Passive Neighbor
A routing daemon can declare that it passively accepts connections from its neighbor, but does not actively initiate the connection itself.
Consider these example situations:
| • | Unidirectional firewall. |
Routing daemon abc.homeNet.myDom.com is located behind a firewall that allows connection requests in only one direction—outward. Active connection attempts by its neighbor, mno.lyonNet.myDom.com, would invariably fail, marking each attempt as a potential security violation at the firewall. When mno.lyonNet.myDom.com declares abc.homeNet.myDom.com as a neighbor, it can specify passive connect, reflecting its inability to initiate a connection to abc.homeNet.myDom.com. To become actual neighbors, abc.homeNet.myDom.com must initiate the connection to mno.lyonNet.myDom.com.
| • | Modem restriction. |
Routing daemon fgh.oshkoshNet.myDom.com is located on a host that depends on a modem for network access; the modem settings permit fgh.oshkoshNet.myDom.com to dial out, but the modem does not accept incoming calls. Active connection attempts by its neighbor, klm.chicagoNet.myDom.com, would invariably fail, while wasting resources. When klm.chicagoNet.myDom.com declares fgh.oshkoshNet.myDom.com as a neighbor, it can specify passive connect, reflecting its inability to initiate a connection to fgh.oshkoshNet.myDom.com. To become actual neighbors, fgh.oshkoshNet.myDom.com must initiate the connection to klm.chicagoNet.myDom.com.
Specifying Passive Neighbors
To specify a passive neighbor, you must supply this information:
| • | Remote Router Name |
| • | Local Connect Port |