vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I have a router that is connected to an ospf cloud using ospfd. For redundancy reasons, the router has several physical links into the ospf cloud. The goal is to have the router doing NAT for a set of public addresses (there is also a physical interface connected to a LAN with private adresses). However, I do not want to assign these public addresses to any physical interface (hence, "distribute connected" does not work for me). Since I am using successfully a software loopback interface (lo1) to distribute the router's looback address into the ospf cloud, I thought that this might also work for networks. I simply assigned a network to lo2 and set the link1 flag. No, it did not work =) Probably because ospfd handles the lo interfaces as point-to-point links. A quick and dirty method to "inject" a route into the ospf cloud seems to be to add a static route to lo1. # ifconfig lo1 1.2.3.4 # the lookback adress # route add 1.2.5.0/24 1.2.3.4 Ugly, but both the loopback address and the 1.2.5.0/24 network are then known in the ospf cloud (as long as one uses ("redistribute static"). This method has also some nasty sideffects (e.g., ICMP does not seem to work, since the loopback interface is for some reason not able to send back ICMP replies). Does anybody have a better idea? Thanks, Christian |