>From your traceroute results, this looks like it might be related to your switch(es).
You said that the first traceroute was from 192.168.10.15 to 192.168.10.250. Both of those are in the same subnet, which means they should be on the same physical portion of the network. That traceroute should only have a single hop - directly from .15 to .250. It will never hit the pfSense. What type of switches do you have? How are they configured? Moshe -- Moshe Katz -- [email protected] -- +1(301)867-3732 On Fri, Sep 9, 2016 at 12:31 PM, Pol Hallen <[email protected]> wrote: > Does the traceroute fail on the first hop, or does it get to the pfSense? >> Can you share with us the actual terminal output of the traceroute? >> > > Sure! :) > > from 192.168.10.15 IP > > traceroute 192.168.10.250 (250 is IP of LAN1) > traceroute to 192.168.10.250 (192.168.10.250), 30 hops max, 60 byte packets > 1 * * * > 2 * * * > 3 * * * > 4 * * * > 5 * * * > 6 * * * > 7 * * * > 8 * * * > 9 * * * > 10 * * * > 11 * * * > 12 * * * > 13 * * * > 14 * * * > 15 * * * > 16 * * * > 17 * * * > 18 * * * > 19 * * * > 20 * * * > 21 * * * > 22 * * * > 23 * * * > 24 * * * > 25 * * * > 26 * * * > 27 * * * > 28 * * * > 29 * * * > 30 * * * > > and always from LAN1: > > traceroute 192.168.1.212 > traceroute to 192.168.1.212 (192.168.1.212), 30 hops max, 60 byte packets > 1 pfSense.localdomain (192.168.10.250) 4.080 ms 4.462 ms 4.653 ms > 2 * * * > 3 * * * > 4 * * * > 5 * * * > 6 * * * > 7 * * * > 8 * * * > 9 * * * > 10 * * * > 11 * * * > 12 * * * > 13 * * * > 14 * * * > 15 * * * > 16 * * * > 17 * * * > 18 * * * > 19 * * * > 20 * * * > 21 * * * > 22 * * * > 23 * * * > 24 * * * > 25 * * * > 26 * * * > 27 * * * > 28 * * * > 29 * * * > 30 * * * > > > > > Pol > _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
