Hi Aaron, OSPFv2 in 8.3R2 still has it, I don't know why you don't see this option
[EMAIL PROTECTED] show protocols ospf area 0.0.0.0 { interface ge-0/0/0.0 { interface-type p2p; } } For IPv6 ... take a look at RFC 2740. 2.11. Identifying neighbors by Router ID In OSPF for IPv6, neighboring routers on a given link are always identified by their OSPF Router ID. This contrasts with the IPv4 behavior where neighbors on point-to-point networks and virtual links are identified by their Router IDs, and neighbors on broadcast, NBMA and Point-to-MultiPoint links are identified by their IPv4 interface addresses. This may explain why it's not really needed. Cheers Sean -- not so long ago , you wrote: > Greetings, > I'm wondering what the equivalent of this is for ospf3: > http://www.juniper.net/techpubs/software/junos/junos81/swconfig81-routing/html/ospf-summary24.html > I'm looking to force ospf3 running on a GigE interface to function as > if it were a point-to-point interface. > e.g. > # edit protocols ospf3 area 0.0.0.0 interface ge-0/0/0 > # set interface-type p2p > I noticed that somewhere between 7.2 and 8.1 the p2p statement was > removed for ospf (and never showed up for ospf3) even though it is > still mentioned in the first link for 8.1... > http://www.juniper.net/techpubs/software/junos/junos72/swconfig72-routing/html/ospf-config.html > http://www.juniper.net/techpubs/software/junos/junos81/swconfig81-routing/html/ospf-config.html > Is there a reason this was removed, and is there some other way to > force this behavior? > The IOS equivalent would be the interface-level command: > (config-if)#ipv6 ospf network point-to-point > Thanks, > ~Aaron > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp