Project

General

Profile

Actions

Bug #1737

closed

ospfd - Route deleted after reboot and reload of the ospfd process

Added by Jean Aumont about 14 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
08/02/2011
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

I have installed PfSense2.0-RC3.
The wan interface is em0 with ip 2.2.2.2/24

The lan interface is em1 with ip 10.90.10.2/30
This interface is directly connected to a Cisco routing switch with ip interface 10.90.10.1/30
The netmask of 30 bits (255.255.255.252) is used to create a local network segment with
the 2 devices (the pfsense computer and the switch).

This network segment will be propagating route by ospf from the switch to the pfsence computer.

#========================================================================================
  1. While Booting ... the boot is stopped trying to get to the NTP Server ...
  2. this give me time to access the PfSense router ...
  3. the important point is that the route on the em1 interface
  4. 10.90.10.0/30 link#3 U 0 0 em1
  5. =======================================================================================

[2.0-RC3][]/root(1): netstat -rn
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
2.2.2.0/24 link#2 U 0 372 em0
2.2.2.2 link#2 UHS 0 0 lo0
10.90.10.0/30 link#3 U 0 0 em1
10.90.10.2 link#3 UHS 0 0 lo0
127.0.0.1 link#5 UH 0 139 lo0

Internet6:
Destination Gateway Flags Netif Expire
::1 ::1 UH lo0
fe80::%em0/64 link#2 U em0
fe80::21b:21ff:fe09:3626%em0 link#2 UHS lo0
fe80::%em1/64 link#3 U em1
fe80::21b:21ff:fe09:3627%em1 link#3 UHS lo0
fe80::%lo0/64 link#5 U lo0
fe80::1%lo0 link#5 UHS lo0
ff01:2::/32 fe80::21b:21ff:fe09:3626%em0 U em0
ff01:3::/32 fe80::21b:21ff:fe09:3627%em1 U em1
ff01:5::/32 ::1 U lo0
ff02::%em0/32 fe80::21b:21ff:fe09:3626%em0 U em0
ff02::%em1/32 fe80::21b:21ff:fe09:3627%em1 U em1
ff02::%lo0/32 ::1 U lo0
[2.0-RC3][]/root(2):

  1. ==============================================================================
  2. I can ping the other end of the network 10.90.10.1/30
  3. ==============================================================================
    [2.0-RC3][]/root(2): ping 10.90.10.1
    PING 10.90.10.1 (10.90.10.1): 56 data bytes
    64 bytes from 10.90.10.1: icmp_seq=0 ttl=255 time=7.108 ms
    64 bytes from 10.90.10.1: icmp_seq=1 ttl=255 time=2.253 ms
    ^C
    --- 10.90.10.1 ping statistics ---
    2 packets transmitted, 2 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 2.253/4.681/7.108/2.427 ms
  1. ==============================================================================
  2. The Boot finished (the NTP server deamon finally give up)
  3. The OSPF deamon is started ...
  4. The ping does not work any more ... the route to network 10.90.10.0/30
  5. has been deleted .... THIS IS ONE BUG !!!
  6. ==============================================================================

[2.0-RC3][]/root(3): ping 10.90.10.1
PING 10.90.10.1 (10.90.10.1): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
^C
--- 10.90.10.1 ping statistics ---
2 packets transmitted, 0 packets received, 100.0% packet loss
[2.0-RC3][]/root(4): netstat -rn
Routing tables

Internet:
Destination Gateway Flags Refs Use Netif Expire
2.2.2.0/24 link#2 U 0 514 em0
2.2.2.2 link#2 UHS 0 0 lo0
10.90.10.2 link#3 UHS 0 0 lo0
127.0.0.1 link#5 UH 0 148 lo0

Internet6:
Destination Gateway Flags Netif Expire
::1 ::1 UH lo0
fe80::%em0/64 link#2 U em0
fe80::21b:21ff:fe09:3626%em0 link#2 UHS lo0
fe80::%em1/64 link#3 U em1
fe80::21b:21ff:fe09:3627%em1 link#3 UHS lo0
fe80::%lo0/64 link#5 U lo0
fe80::1%lo0 link#5 UHS lo0
ff01:2::/32 fe80::21b:21ff:fe09:3626%em0 U em0
ff01:3::/32 fe80::21b:21ff:fe09:3627%em1 U em1
ff01:5::/32 ::1 U lo0
ff02::%em0/32 fe80::21b:21ff:fe09:3626%em0 U em0
ff02::%em1/32 fe80::21b:21ff:fe09:3627%em1 U em1
ff02::%lo0/32 ::1 U lo0
[2.0-RC3][]/root(5):

#========================================================================================
  1. Adding the missing route will not completely solve the issue ...
  2. After the addition of the route, the ping still will not work ...
  3. Putting the interface down and up, with the commands:
  4. ifconfig em1 down
  5. ifconfig em1 up
  6. will bring back everything to a working state ...
  7. all the OSPF route will be learned correctly ...
  8. THIS IS A SECOND BUG ... OR PART OF THE FIRST ONE ??? (not sure) #========================================================================================

I consider this bug priority quite high since it destroy the hole routing functionnality
of pfsense.

Do not hesitsate to contact me by email or phone 514-913-7275

Jean Aumont

#

Actions #1

Updated by Jim Pingle over 13 years ago

Just to keep this ticket in the loop, the quagga package for FreeBSD seems to behave much better for OSPF than openospfd does. A quagga package is in the works to take its place.

Actions #2

Updated by Chris Buechler over 13 years ago

  • Status changed from New to Closed

closing since openospfd is being ditched in favor of quagga

Actions

Also available in: Atom PDF