MLPPP WAN Gateway Issues

chpalmer

Gateways on Dashboard Widget shows "unknown"

Status_Gateways shows only "pending"

2_1_1WanGateway.jpg_thumb

jimp

Anything in the Gateways log at all?

Can you post your /var/etc/apinger.conf here?

chpalmer

This also happened when I gitsync'd this box late last year. I since reloaded the box from a fresh 2.1 release and have run it from that since. It had not been gitsync'd this time around.

This upgrade to 2.1.1 was done via "automatic firmware update".

| Jan 19 15:46:37 | apinger: Starting Alarm Pinger, apinger(23037) |
| Jan 19 15:48:32 | apinger: ALARM: WAN1(64.146.240.1) *** delay *** |
| Jan 19 15:48:42 | apinger: Error while starting command form alarm(delay) on target(64.146.240.1-WAN1) |
| Jan 19 15:48:42 | apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns WAN1' -c 'service reload ipsecdns' -c 'service reload openvpn WAN1' -c 'filter reload' ) exited with status: 255 |
| Jan 19 15:49:07 | apinger: alarm canceled: WAN1(64.146.240.1) *** delay *** |
| Jan 19 15:49:17 | apinger: Error while starting command form alarm(delay) on target(64.146.240.1-WAN1) |
| Jan 19 15:49:17 | apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns WAN1' -c 'service reload ipsecdns' -c 'service reload openvpn WAN1' -c 'filter reload' ) exited with status: 255 |
| Jan 19 23:14:43 | apinger: ALARM: WAN1(64.146.240.1) *** delay *** |
| Jan 19 23:14:53 | apinger: Error while starting command form alarm(delay) on target(64.146.240.1-WAN1) |
| Jan 19 23:14:53 | apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns WAN1' -c 'service reload ipsecdns' -c 'service reload openvpn WAN1' -c 'filter reload' ) exited with status: 255 |
| Jan 19 23:15:52 | apinger: alarm canceled: WAN1(64.146.240.1) *** delay *** |
| Jan 19 23:16:02 | apinger: Error while starting command form alarm(delay) on target(64.146.240.1-WAN1) |
| Jan 19 23:16:02 | apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns WAN1' -c 'service reload ipsecdns' -c 'service reload openvpn WAN1' -c 'filter reload' ) exited with status: 255 |
| Jan 19 23:17:42 | apinger: Starting Alarm Pinger, apinger(22740) |
| Jan 19 23:17:42 | apinger: No usable targets found, exiting |
| Jan 19 23:28:07 | apinger: Starting Alarm Pinger, apinger(23377) |
| Jan 19 23:28:07 | apinger: No usable targets found, exiting |


# pfSense apinger configuration file. Automatically Generated!

## User and group the pinger should run as
user "root"
group "wheel"

## Mailer to use (default: "/usr/lib/sendmail -t")
#mailer "/var/qmail/bin/qmail-inject"

## Location of the pid-file (default: "/var/run/apinger.pid")
pid_file "/var/run/apinger.pid"

## Format of timestamp (%s macro) (default: "%b %d %H:%M:%S")
#timestamp_format "%Y%m%d%H%M%S"

status {
    ## File where the status information should be written to
    file "/var/run/apinger.status"
    ## Interval between file updates
    ## when 0 or not set, file is written only when SIGUSR1 is received
    interval 5s
}

########################################
# RRDTool status gathering configuration
# Interval between RRD updates
rrd interval 60s;

## These parameters can be overridden in a specific alarm configuration
alarm default {
    command on "/usr/local/sbin/pfSctl -c 'service reload dyndns %T' -c 'service reload ipsecdns' -c 'service reload openvpn %T' -c 'filter reload' "
    command off "/usr/local/sbin/pfSctl -c 'service reload dyndns %T' -c 'service reload ipsecdns' -c 'service reload openvpn %T' -c 'filter reload' "
    combine 10s
}

## "Down" alarm definition.
## This alarm will be fired when target doesn't respond for 30 seconds.
alarm down "down" {
    time 10s
}

## "Delay" alarm definition.
## This alarm will be fired when responses are delayed more than 200ms
## it will be canceled, when the delay drops below 100ms
alarm delay "delay" {
    delay_low 200ms
    delay_high 500ms
}

## "Loss" alarm definition.
## This alarm will be fired when packet loss goes over 20%
## it will be canceled, when the loss drops below 10%
alarm loss "loss" {
    percent_low 10
    percent_high 20
}

target default {
    ## How often the probe should be sent
    interval 1s

    ## How many replies should be used to compute average delay
    ## for controlling "delay" alarms
    avg_delay_samples 10

    ## How many probes should be used to compute average loss
    avg_loss_samples 50

    ## The delay (in samples) after which loss is computed
    ## without this delays larger than interval would be treated as loss
    avg_loss_delay_samples 20

    ## Names of the alarms that may be generated for the target
    alarms "down","delay","loss"

    ## Location of the RRD
    #rrd file "/var/db/rrd/apinger-%t.rrd"
}

chpalmer

Just did a firmware update to latest (built on Mon Jan 20 06:37:26 EST 2014 ) and the gateway is now showing up. :)

Possible config.xml past entry issue?

chpalmer

Last time this happened…

https://forum.pfsense.org/index.php/topic,70540.msg384975.html#msg384975

chpalmer

This is still an issue.

2.1.1-PRERELEASE (i386)
built on Wed Jan 22 03:09:38 EST 2014
FreeBSD 8.3-RELEASE-p14

| Jan 22 19:58:17 | php: rc.bootup: Could not find IPv4 gateway for interface (wan). |
| Jan 22 19:58:17 | php: rc.bootup: Could not find IPv4 gateway for interface (wan). |
| Jan 22 19:58:17 | php: rc.bootup: Could not find IPv4 gateway for interface (wan). |
| Jan 22 19:58:17 | php: rc.bootup: Could not find IPv4 gateway for interface (wan). |
| Jan 22 19:58:17 | kernel: vr0: link state changed to UP |
| Jan 22 19:58:17 | php: rc.bootup: Could not find IPv4 gateway for interface (wan). |
| Jan 22 19:58:17 | php: rc.bootup: Could not find IPv4 gateway for interface (wan). |
| Jan 22 19:58:17 | php: rc.bootup: Could not find IPv4 gateway for interface (wan). |
| Jan 22 19:58:17 | php: rc.bootup: Could not find IPv4 gateway for interface (wan). |
| Jan 22 19:58:17 | php: rc.bootup: Could not find IPv6 gateway for interface(wan). |

|

| Pending |
|
|

|

| Interface WAN1 Dynamic Gateway |

| Jan 19 23:14:53 | apinger: Error while starting command form alarm(delay) on target(64.146.240.1-WAN1) |
| Jan 19 23:14:53 | apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns WAN1' -c 'service reload ipsecdns' -c 'service reload openvpn WAN1' -c 'filter reload' ) exited with status: 255 |
| Jan 19 23:15:52 | apinger: alarm canceled: WAN1(64.146.240.1) *** delay *** |
| Jan 19 23:16:02 | apinger: Error while starting command form alarm(delay) on target(64.146.240.1-WAN1) |
| Jan 19 23:16:02 | apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns WAN1' -c 'service reload ipsecdns' -c 'service reload openvpn WAN1' -c 'filter reload' ) exited with status: 255 |
| Jan 19 23:17:42 | apinger: Starting Alarm Pinger, apinger(22740) |
| Jan 19 23:17:42 | apinger: No usable targets found, exiting |
| Jan 19 23:28:07 | apinger: Starting Alarm Pinger, apinger(23377) |
| Jan 19 23:28:07 | apinger: No usable targets found, exiting |
| Jan 20 12:53:51 | apinger: Starting Alarm Pinger, apinger(23573) |
| Jan 22 19:58:18 | apinger: Starting Alarm Pinger, apinger(24767) |
| Jan 22 19:58:18 | apinger: No usable targets found, exiting |
| | |

Guest

I have to restart the apinger service to make it work on mine, I have had to do that on the last few builds.
I'm not using MLPPP, just a single PPPoE connection.
Also all firewall NAT port forwarding doesn't work on this build until I edit one which causes a reload.

2.1.1-PRERELEASE (amd64)
built on Wed Jan 22 04:46:20 EST 2014
FreeBSD .com 8.3-RELEASE-p14 FreeBSD 8.3-RELEASE-p14 #1: Wed Jan 22 05:23:40 EST 2014 root@snapshots-8_3-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64

chpalmer

@JoeMcJoe:

I have to restart the apinger service to make it work on mine, I have had to do that on the last few builds.

That worked for me as well. This was the only box I had running that didn't have the "services status" widget on the dashboard so I missed that it wasn't running.

added this to the general log-

| Jan 22 23:47:14 | syslogd: kernel boot file is /boot/kernel/kernel |
| Jan 22 23:47:14 | kernel: pid 78831 (syslogd), uid 0: exited on signal 11 (core dumped) |
| | |