Routing Issue?



  • Hi,

    While investigating why devices in LAN_1G (OPT1) will occasionally get pings of 400ms+,  I noticed that when I do a traceroute that pfsense will show up twice.  The second time will have a latency of 30ms.  I was wondering where this is coming from.  Disabling the OPT1 interface did not make this extra hop go away.  I tried searching the forums for "routing loop and extra hop" without much success.

    I'm running three interfaces, WAN, LAN, LAN_1G.  I just did a factory reset, but it didn't make a difference.
    LAN - 10.20.1.0/24
    LAN_1G - 10.20.5.0/28

    Auto outbound NAT rules
    Firewall rule for LAN_1G: Identical rule to default LAN rule
    Config file is attached to this post.

    Running 1.2RC4

    Tracert from LAN:

    
    dreamnid@dreamnid-desktop:~$ tracepath zackfasel.com
     1:  dreamnid-desktop.local (10.20.1.199)                   0.171ms pmtu 1500
     1:  pfsense.bond007.local (10.20.1.4)                      0.583ms 
     2:  pfsense.bond007.local (10.20.1.4)                     40.252ms 
     3:  gig1-3.rochnybtn-rtr01.nyroc.rr.com (24.93.0.221)     31.757ms 
     4:  srp7-0.rochnymth-rtr03.nyroc.rr.com (24.93.3.119)     34.077ms 
     5:  srp3-0.rochnymth-rtr01.nyroc.rr.com (24.93.3.177)     35.347ms 
     6:  so-0-2-2.syrcnycsr-rtr03.nyroc.rr.com (24.92.224.173) asymm  7  37.074ms 
     7:  te-3-1.car2.Cleveland1.Level3.net (4.78.59.45)       asymm 16  53.647ms 
     8:  ae-11-11.car1.Cleveland1.Level3.net (4.69.132.197)   asymm 15  57.414ms 
     9:  ae-4-4.ebr1.Washington1.Level3.net (4.69.132.194)    asymm 14  64.003ms 
    10:  ae-2.ebr3.Atlanta2.Level3.net (4.69.132.85)          asymm 15  69.531ms 
    11:  ae-7.ebr3.Dallas1.Level3.net (4.69.134.21)           asymm 16  88.508ms 
    12:  ae-73-73.csw2.Dallas1.Level3.net (4.69.136.158)      asymm 17  93.047ms 
    13:  ae-1-69.edge3.Dallas1.Level3.net (4.68.19.8)         asymm 19  84.526ms 
    14:  te7-2.cer01.dal01.dallas-border.com (4.71.198.18)    asymm 22  87.294ms 
    15:  po55.fcr03.dal01.dallas-datacenter.com (66.228.118.182) asymm 22  87.016ms 
    
    

    Routing Table from Pfsense
    Weird thing is that the ips defined were from before I reseted to the defaults… Not sure why they're still in there since all the NAT port forward/WAN firewalls rules are gone.

    
    IPv4
    Destination 	Gateway 	Flags 	Refs 	Use 	Mtu 	Netif 	Expire
    default 	74.65.28.1 	UGS 	0 	2191 	1500 	xl0 	 
    10.20.1/24 	link#2 	UC 	0 	1 	1500 	dc0 	 
    10.20.1.161 	00:17:31:8f:da:3b 	UHLW 	1 	520 	1500 	dc0 	874
    10.20.1.172 	00:0b:6a:92:6e:48 	UHLW 	1 	231 	1500 	dc0 	873
    10.20.1.180 	00:19:21:70:b5:f4 	UHLW 	1 	46 	1500 	dc0 	1083
    10.20.1.199 	00:50:8d:9f:99:ec 	UHLW 	1 	9062 	1500 	dc0 	259
    10.20.5/28 	link#1 	UC 	0 	3 	1500 	em0 	 
    10.20.5.2 	link#1 	UHLW 	1 	0 	1500 	em0 	 
    10.20.5.3 	00:0f:1f:c1:9a:06 	UHLW 	1 	880 	1500 	em0 	506
    10.20.5.5 	00:07:e9:5e:b9:8a 	UHLW 	1 	7 	1500 	em0 	890
    74.65.28/22 	link#3 	UC 	0 	0 	1500 	xl0 	 
    74.65.28.1 	00:1b:54:ca:e9:05 	UHLW 	2 	80 	1500 	xl0 	1200
    74.65.31.22 	127.0.0.1 	UGHS 	0 	0 	16384 	lo0 	 
    127.0.0.1 	127.0.0.1 	UH 	1 	0 	16384 	lo0 	 
    
    ```[config-pfsense.bond007.local-20080125065245.txt](/public/_imported_attachments_/1/config-pfsense.bond007.local-20080125065245.txt)


  • Traceroute from LAN_1G (OPT1)
    Note that it appears three times

    
    dreamnid@agentx:~$ tracepath zackfasel.com     
     1:  agentx.local (10.20.5.3)                               0.171ms pmtu 1500
     1:  10.20.5.1 (10.20.5.1)                                  0.524ms 
     1:  10.20.5.1 (10.20.5.1)                                  0.475ms 
     2:  10.20.5.1 (10.20.5.1)                                 33.050ms 
     3:  gig1-3.rochnybtn-rtr01.nyroc.rr.com (24.93.0.221)     33.259ms 
     4:  srp7-0.rochnymth-rtr03.nyroc.rr.com (24.93.3.119)     33.714ms 
     5:  srp3-0.rochnymth-rtr01.nyroc.rr.com (24.93.3.177)     32.491ms 
     6:  so-0-2-2.syrcnycsr-rtr03.nyroc.rr.com (24.92.224.173)  35.512ms asymm  7 
     7:  te-3-2.car2.Cleveland1.Level3.net (64.156.66.41)      54.347ms asymm 16 
     8:  ae-11-11.car1.Cleveland1.Level3.net (4.69.132.197)    54.681ms asymm 15 
     9:  ae-4-4.ebr1.Washington1.Level3.net (4.69.132.194)     55.968ms asymm 14 
    10:  ae-2.ebr3.Atlanta2.Level3.net (4.69.132.85)           73.618ms asymm 15 
    11:  ae-7.ebr3.Dallas1.Level3.net (4.69.134.21)            93.455ms asymm 16 
    12:  ae-83-83.csw3.Dallas1.Level3.net (4.69.136.162)       85.446ms asymm 17 
    13:  ae-4-99.edge3.Dallas1.Level3.net (4.68.19.200)        86.994ms asymm 19 
    14:  te7-2.cer01.dal01.dallas-border.com (4.71.198.18)     87.819ms asymm 22 
    15:  po55.fcr03.dal01.dallas-datacenter.com (66.228.118.182)  87.324ms asymm 22
    
    

    Let me know if you need anything else.

    Thanks!


Log in to reply