Pfsense-router doesn't show up in traceroute
-
I've set up a pfsense 2.0 router (IP 10.0.0.1) with 2 WAN's :
- VDSL-line (ISP Belgacom) and IP 10.1.0.1 on the modem
- VDSL-line (ISP Schedom) and IP 10.2.0.1 on the modem
The wifi.office.it2go.eu is my ddwrt-router for my wireless connections.
That one does come up like it should be on a tracert, but my pfsense router should be on line 2 as rtr-fw01.office.it2go.eu [10.0.0.1].Does someone know how to enable that? :)
Kris
1 1 ms 3 ms <1 ms wifi.office.it2go.eu [192.168.100.1]
2 3 ms 2 ms 2 ms 10.1.0.1
3 23 ms 23 ms 22 ms 1.87-182-91.adsl-dyn.isp.belgacom.be [91.182.87.1]
4 2528 ms 3788 ms * 8.241-183-91.adsl-static.isp.belgacom.be [91.183.241.8]
5 27 ms 24 ms 24 ms 18.247-183-91.adsl-static.isp.belgacom.be [91.183.247.18]
6 33 ms 32 ms 31 ms bru-22-r7-t7-2.car.belbone.be [80.84.21.166]
7 194 ms 229 ms 311 ms bru-11-r6-t2-2.car.belbone.be [80.84.18.140]
8 32 ms 32 ms 34 ms 94.102.162.204
9 32 ms 32 ms 32 ms 74.125.50.21
10 * 43 ms 46 ms 209.85.252.76
11 40 ms 38 ms 38 ms 216.239.43.123
12 41 ms 40 ms 39 ms 72.14.239.197
13 51 ms 39 ms * 209.85.255.106
14 40 ms 40 ms 40 ms ew-in-f104.1e100.net [74.125.77.104]1 1 ms <1 ms <1 ms wifi.office.it2go.eu [192.168.100.1]
2 4 ms 1 ms 1 ms 10.2.0.1
3 19 ms 21 ms 18 ms gateway.dyn1.namur.schedom-europe.net [83.101.6.1]
4 22 ms 21 ms 21 ms atm-26-32.largo-matisse.bru.schedom-europe.net [83.101.0.26]
5 22 ms 22 ms 22 ms 4-5.r1.br.hwng.net [209.197.1.105]
6 30 ms 29 ms 29 ms 3-4.r1.am.hwng.net [69.16.191.85]
7 31 ms 30 ms 36 ms 1-1.r3.am.hwng.net [69.16.191.26]
8 30 ms 31 ms 31 ms core1.ams.net.google.com [195.69.144.247]
9 31 ms 31 ms 36 ms 209.85.248.93
10 83 ms 58 ms 33 ms 64.233.175.246
11 35 ms 38 ms 34 ms 72.14.239.199
12 * * * Time-out bij opdracht.
13 35 ms 35 ms 38 ms ew-in-f104.1e100.net [74.125.77.104]De trace is voltooid.
-
If you use policy routing, pf takes the traffic and sends it out the WAN selected for that connection - it does not stop on the pfSense box as a hop.
-
If you use policy routing, pf takes the traffic and sends it out the WAN selected for that connection - it does not stop on the pfSense box as a hop.
Strange, because before pfsense did show up at the traceroute?
-
Hi Krisken,
you would need to add a reverse record (PTR) in your local DNS server for 10.2.0.1 which is resolvable from the PC you are running traceroute on, in order for having the pfsense hop appear as rtr-fw01.office.it2go.eu [10.0.0.1]. Since the 192.168.100.1 hop appears as wifi.office.it2go.eu [192.168.100.1], it seems you already created a PTR record for this address.
Andreas
-
Hi Krisken,
you would need to add a reverse record (PTR) in your local DNS server for 10.2.0.1 which is resolvable from the PC you are running traceroute on, in order for having the pfsense hop appear as rtr-fw01.office.it2go.eu [10.0.0.1]. Since the 192.168.100.1 hop appears as wifi.office.it2go.eu [192.168.100.1], it seems you already created a PTR record for this address.
Andreas
It should still show as an ip address even if the RDNS doesn't resolve.
Mine shows up, but then i'm not presently using multi-wan for anything.
-
All,
Any idea what option i did checked/non-checked so that my pfsense router don't show up?
I think that's the first part of the problem :)Kris
-
All,
Any idea what option i did checked/non-checked so that my pfsense router don't show up?
I think that's the first part of the problem :)Kris
Jimp seems to be suggesting it's because of policy based routing, which may explain things as mine isn't setup to do any policy based routing and is showing up.
-
Hi Krisken,
you would need to add a reverse record (PTR) in your local DNS server for 10.2.0.1 which is resolvable from the PC you are running traceroute on, in order for having the pfsense hop appear as rtr-fw01.office.it2go.eu [10.0.0.1]. Since the 192.168.100.1 hop appears as wifi.office.it2go.eu [192.168.100.1], it seems you already created a PTR record for this address.
Andreas
It should still show as an ip address even if the RDNS doesn't resolve.
Mine shows up, but then i'm not presently using multi-wan for anything.
In that case I misunderstood, I thought the problem was that 10.1.0.1 was showing up without hostname, but I see now that he is expecting 10.0.0.1 to show up, while it isn't.
A
-
It is correct that pfSense will not show up when used with PBR.
Not sure a fix should be done for this or not! -
An FAQ entry should be enough. I'll add one. I don't think it's worth coding a fix to make it show up.
EDIT: FAQ added: http://doc.pfsense.org/index.php/Router_is_Missing_from_traceroute_Output
-
An FAQ entry should be enough. I'll add one. I don't think it's worth coding a fix to make it show up.
EDIT: FAQ added: http://doc.pfsense.org/index.php/Router_is_Missing_from_traceroute_Output
So if i do understand it all well, that's quite normal and there isn't a solution for it?
I tought that my pfsense router did show up in the beginning that i use pfsense.Kris
-
If you use normal routing, it does show up.
If you use policy routing (e.g. selected a gateway in a rule, typically for multi-wan) then it does not show up.
-
If you use normal routing, it does show up.
If you use policy routing (e.g. selected a gateway in a rule, typically for multi-wan) then it does not show up.
http://krisken.dommel.be/pfsense/rules.jpg
So like that…isn't possible? -
If you always had gateways set on every rule like that, then pfSense shouldn't have ever shown up as a hop when tracing outbound.
-
If you always had gateways set on every rule like that, then pfSense shouldn't have ever shown up as a hop when tracing outbound.
It has always been like that indeed. So probably i'm wrong :)
Thanks for the great help!
