System log routing error



  • i just updated to the latest nanobsd snap and im seeing endless entries of the below, i have 2 pppoe conenctions from same isp so the gateway is same for both but the monitor ip is different for both in routing

    Sep 30 15:41:18 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:20 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:22 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:24 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:26 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:28 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:30 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:32 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:34 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:36 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:38 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:40 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:42 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:44 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:46 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:48 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:50 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:52 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:54 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:56 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:41:58 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:00 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:03 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:05 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:07 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:09 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:11 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:13 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:15 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:17 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:19 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:21 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:23 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:25 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:27 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:29 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:31 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:33 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:35 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:37 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:39 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:41 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    Sep 30 15:42:43 	routed[25240]: pppoe1 (219.91.x.x/32-->203.187.196.1) is duplicated by pppoe0 (203.187.x.x/32-->203.187.196.1)
    


  • it seems enabling RIP on the LAN interface causes that to appear



  • actually its happening to old snaps as well and enabling RIP causes it



  • any1 on this issue?



  • @xbipin:

    any1 on this issue?

    I have the barest knowledge of RIP and routed but I will have a go.

    routed is complaining that you have itwo nterfaces with 203.187.196.1 as the next hop. Perhaps you could:

    • Use multilink PPP

    • Tell routed to ignore one of the PPP interfaces

    • Tell routed to ignore both PPP interfaces and configure to routed a "combined" route (systems on your LAN side don't need to know there are two PPP links to your ISP)

    • Tell routed to ignore duplicate routes

    • not enable RIP on the LAN interface



    • cant use multilink
    • how?
    • how?
    • how?
    • can do this but wont be able to use RIP then


  • can we use multilink ppp and also be able to route different for each client (policy based routing) as i use one link for voip and the second link for the rest



  • @xbipin:

    • how?

    See the FreeBSD man page for routed at http://www.freebsd.org/cgi/man.cgi?query=routed&apropos=0&sektion=0&manpath=FreeBSD+9.0-RELEASE&arch=default&format=html

    It looks to me that command line options

    • -h

    • -P

    might be of interest.



  • yes but i think some way to specify those in the pfsense gui need to be present as well for more control


Log in to reply