So yeah, multiple layer 3s are normal with IPv6.

That might be pertinent had OP mentioned IPv6.

Hello,

I'm just wondering if anyone has experienced the same issue or if anyone has some insights that could point me in the right direction (i.e. what/where I should be looking). As far as I know, there is no setting (at least in the pfSense GUI) to disable EAP.

Any hints would be greatly appreciated.

Cheers

Hi,

Yeah it looks very normal indeed, and the traffic came in thru one door & exited thru another just right as expected … until I realized that I should count how many left by counting those who exited ... not by counting those who came in. In other words, for me those marked as OUT in the graph should be labeled OUT in the list. This screen is traffic statistics for the LAN interface only, not combined WAN/LAN.

It's just labelling anyway. Thanks.

Edwin

@JKnott:

Works fine for me.

Check if your default gateway is setup correctly in System->Routing.

was looking at this one  LINKSYS SWITCH LGS318P 18-Port Smart Gigabit PoE+ Switch

System->Advanced->Misc

Disable PowerD

Script works for 2.4 also!

my ISP is not dchp, we using static ip.
then, i set my pfsense wan to static ip

@joelones:

Any suggestion on how I could troubleshoot this?

Better to ask at Asterisk forum as there is no evidence that pfSense is guilty.
General advise - forget about generic Asterisk log and check your SIP signalling.

Does pfSense support a CNAME alias?  If so, he could create an alias for the Android-* name.  I do that with my firewall WAN address.  It's host name is dependent on the computer & modem MAC addresses.  So, I created an alias for it on my public DNS.

@fredfox_uk:

Tried pfSense and VMWare ?

No.
I have no experience with VMWare.

And it isn't the Virtualization in any case.

well you could look in the dhcp leases if pfsense is your dhcp server.. You could look in the arp table, or you could look for states on the firewall for IPs that have states open, etc.

If your feeling lucky you might try perhaps?: pkg add http://pkg.freebsd.org/FreeBSD:10:i386/release_4/All/freeradius-2.2.9.txz might need several dependencies that need dependencies which can probably be found on that same site..

Squid & squidguard can do that.  In squidguard, you create Group ACLs and then apply policies to the group.

Yeah. dpinger can't ping the IP address you have set as the monitor IP address. Change it to something that interface can ping.

I've had this problem for over a year and didn't find a solution until now, when I did a dive into the code and put debugging around routing commands.

I'm sharing my findings in case it helps you and others who Google this error.

Symptoms:
Reset a WAN interface and the routing dies.

In the logs:

Dec  6 06:46:35 fw kernel: arpresolve: can't allocate llinfo for 192.168.21.1 on lagg0_vlan21

In the routing table:

Destination        Gateway            Flags      Netif Expire 192.168.21.0/24    link#14            U      lagg0_vl 192.168.21.1      192.168.21.1      UGHS  lagg0_vl 192.168.21.10      link#14            UHS        lo0

Root cause:
The DNS server and gateway are the same.

Fix:
Either change DNS servers, or patch the code (pfSense 2.2 and 2.3.5):

/etc/inc/system.inc, near line 257:

Change

                            mwexec("/sbin/route {$cmd} -host {$inet6}{$dnsserver} {$gatewayip}"); ```To

if( $dnsserver != $gatewayip )
                            mwexec("/sbin/route {$cmd} -host {$inet6}{$dnsserver} {$gatewayip}");