[ previous ] [ next ] [ threads ]
 
 From:  "Joey Morin" <joeymorin at gmail dot com>
 To:  "Lee Sharp" <leesharp at hal dash pc dot org>
 Cc:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] more ez-ipupdate woes
 Date:  Wed, 18 Apr 2007 16:53:44 -0400
hi lee,

well, i just found an ugly workaround, but i haven't exactly solved the
problem.  two problems, actually:

the workaround is to impose a slight delay in the boot script before running
ez-ipupdate.  i modified /etc/rc.bootup in /cf/mfsroot.gz.  the dyndns
service usually starts after the dnsmasq service (with 15 boot tasks
starting after dyndns).  i move the dyndns service function call to the end
of the list, and put sleep(10); before it.

that had a positive effect.  ez-ipupdate now succeeds, but still not on the
first try!  below is a sanitized log excerpt:

Apr 18 16:13:12     mpd: [pppoe] PAP: rec'd ACK #1
Apr 18 16:13:12     mpd: [pppoe] LCP: authorization successful
Apr 18 16:13:12     mpd: [pppoe] LCP: phase shift AUTHENTICATE --> NETWORK
Apr 18 16:13:12     mpd: [pppoe] setting interface ng0 MTU to 1492 bytes
Apr 18 16:13:12     mpd: [pppoe] up: 1 link, total bandwidth 64000 bps
Apr 18 16:13:12     mpd: [pppoe] IPCP: Up event
Apr 18 16:13:12     mpd: [pppoe] IPCP: state change Starting --> Req-Sent
Apr 18 16:13:12     dnsmasq[96]: started, version 2.35 cachesize 150
Apr 18 16:13:12     mpd: [pppoe] IPCP: SendConfigReq #1
Apr 18 16:13:12     dnsmasq[96]: compile time options: no-IPv6 GNU-getopt
ISC-leasefile no-DBus no-I18N
Apr 18 16:13:12     mpd: IPADDR 0.0.0.0
Apr 18 16:13:12     dnsmasq[96]: setting --bind-interfaces option because of
OS limitations
Apr 18 16:13:12     dnsmasq[96]: setting --bind-interfaces option because of
OS limitations
Apr 18 16:13:12     dhcpd: Internet Systems Consortium DHCP Server V3.0.5
Apr 18 16:13:12     mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Apr 18 16:13:12     dnsmasq[96]: no servers found in /etc/resolv.conf, will
retry
Apr 18 16:13:12     dnsmasq[96]: no servers found in /etc/resolv.conf, will
retry
Apr 18 16:13:12     dhcpd: Copyright 2004-2006 Internet Systems Consortium.
Apr 18 16:13:12     mpd: PRIDNS 0.0.0.0
Apr 18 16:13:12     dnsmasq[96]: read /etc/hosts - 3 addresses
Apr 18 16:13:12     dhcpd: All rights reserved.
Apr 18 16:13:12     mpd: SECDNS 0.0.0.0
Apr 18 16:13:12     dhcpd: For info, please visit
http://www.isc.org/sw/dhcp/
Apr 18 16:13:12     mpd: [pppoe] IPCP: rec'd Configure Request #77 link 0
(Req-Sent)
Apr 18 16:13:12     mpd: IPADDR xx.xx.xx.xx
Apr 18 16:13:12     mpd: xx.xx.xx.xx is OK
Apr 18 16:13:12     mpd: [pppoe] IPCP: SendConfigAck #77
Apr 18 16:13:12     mpd: IPADDR xx.xx.xx.xx
Apr 18 16:13:12     mpd: [pppoe] IPCP: state change Req-Sent --> Ack-Sent
Apr 18 16:13:12     mpd: [pppoe] IPCP: rec'd Configure Reject #1 link 0
(Ack-Sent)
Apr 18 16:13:12     mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Apr 18 16:13:13     mpd: [pppoe] IPCP: SendConfigReq #2
Apr 18 16:13:13     mpd: IPADDR 0.0.0.0
Apr 18 16:13:13     mpd: PRIDNS 0.0.0.0
Apr 18 16:13:13     mpd: SECDNS 0.0.0.0
Apr 18 16:13:13     mpd: [pppoe] IPCP: rec'd Configure Nak #2 link 0
(Ack-Sent)
Apr 18 16:13:13     mpd: IPADDR xx.xx.xx.xx
Apr 18 16:13:13     mpd: xx.xx.xx.xx is OK
Apr 18 16:13:13     mpd: PRIDNS xx.xx.xx.xx
Apr 18 16:13:13     mpd: SECDNS xx.xx.xx.xx
Apr 18 16:13:13     mpd: [pppoe] IPCP: SendConfigReq #3
Apr 18 16:13:13     mpd: IPADDR xx.xx.xx.xx
Apr 18 16:13:13     mpd: PRIDNS xx.xx.xx.xx
Apr 18 16:13:13     mpd: SECDNS xx.xx.xx.xx
Apr 18 16:13:13     mpd: [pppoe] IPCP: rec'd Configure Ack #3 link 0
(Ack-Sent)
Apr 18 16:13:13     mpd: IPADDR xx.xx.xx.xx
Apr 18 16:13:13     mpd: PRIDNS xx.xx.xx.xx
Apr 18 16:13:13     mpd: SECDNS xx.xx.xx.xx
Apr 18 16:13:13     mpd: [pppoe] IPCP: state change Ack-Sent --> Opened
Apr 18 16:13:13     mpd: [pppoe] IPCP: LayerUp
Apr 18 16:13:13     mpd: mpd: pid 109, version 3.18
(root at fb411 dot neon1 dot net10:49 7-Apr-2007)
Apr 18 16:13:13     mpd: xx.xx.xx.xx -> xx.xx.xx.xx
Apr 18 16:13:13     mpd: [pt0] ppp node is "mpd109-pt0"
Apr 18 16:13:13     mpd: [pppoe] IFACE: Up event
Apr 18 16:13:13     mpd: mpd: local IP address for PPTP is 0.0.0.0
Apr 18 16:13:13     mpd: [pppoe] setting interface ng0 MTU to 1492 bytes
Apr 18 16:13:13     mpd: [pt0] using interface ng1
Apr 18 16:13:13     mpd: [pppoe] exec: /sbin/ifconfig ng0 xx.xx.xx.xx
xx.xx.xx.xx netmask 0xffffffff -link0
Apr 18 16:13:13     mpd: [pt1] ppp node is "mpd109-pt1"
Apr 18 16:13:13     mpd: [pt1] using interface ng2
Apr 18 16:13:13     mpd: [pt2] ppp node is "mpd109-pt2"
Apr 18 16:13:13     mpd: [pppoe] exec: /sbin/route add xx.xx.xx.xx -iface
lo0
Apr 18 16:13:13     mpd: [pt2] using interface ng3
Apr 18 16:13:13     mpd: [pt3] ppp node is "mpd109-pt3"
Apr 18 16:13:13     mpd: [pt3] using interface ng4
Apr 18 16:13:13     mpd: [pt4] ppp node is "mpd109-pt4"
Apr 18 16:13:13     mpd: [pppoe] exec: /sbin/route add 0.0.0.0 xx.xx.xx.xx
Apr 18 16:13:13     mpd: [pt4] using interface ng5
Apr 18 16:13:13     mpd: [pt5] ppp node is "mpd109-pt5"
Apr 18 16:13:13     mpd: [pt5] using interface ng6
Apr 18 16:13:13     mpd: [pppoe] exec: /usr/local/sbin/ppp-linkup ng0 inet
xx.xx.xx.xx xx.xx.xx.xx XXXXXXXX dns1 xx.xx.xx.xx dns2 xx.xx.xx.xx
Apr 18 16:13:13     mpd: [pt6] ppp node is "mpd109-pt6"
Apr 18 16:13:14     mpd: [pt6] using interface ng7
Apr 18 16:13:14     mpd: [pppoe] IFACE: Up event
Apr 18 16:13:14     mpd: [pt7] ppp node is "mpd109-pt7"
Apr 18 16:13:14     mpd: [pt7] using interface ng8
Apr 18 16:13:14     mpd: [pt8] ppp node is "mpd109-pt8"
Apr 18 16:13:14     mpd: [pt8] using interface ng9
Apr 18 16:13:14     mpd: [pt9] ppp node is "mpd109-pt9"
Apr 18 16:13:14     mpd: [pt9] using interface ng10
Apr 18 16:13:14     mpd: [pt10] ppp node is "mpd109-pt10"
Apr 18 16:13:14     mpd: [pt10] using interface ng11
Apr 18 16:13:14     mpd: [pt11] ppp node is "mpd109-pt11"
Apr 18 16:13:14     mpd: [pt11] using interface ng12
Apr 18 16:13:14     mpd: [pt12] ppp node is "mpd109-pt12"
Apr 18 16:13:14     mpd: [pt12] using interface ng13
Apr 18 16:13:14     mpd: [pt13] ppp node is "mpd109-pt13"
Apr 18 16:13:14     mpd: [pt13] using interface ng14
Apr 18 16:13:14     mpd: [pt14] ppp node is "mpd109-pt14"
Apr 18 16:13:14     mpd: [pt14] using interface ng15
Apr 18 16:13:14     mpd: [pt15] ppp node is "mpd109-pt15"
Apr 18 16:13:14     mpd: [pt15] using interface ng16
Apr 18 16:13:28     /usr/local/bin/ez-ipupdate[175]: ez-ipupdate Version
3.0.11b8, Copyright (C) 1998-2001 Angus Mackay.
Apr 18 16:13:28     /usr/local/bin/ez-ipupdate[175]:
/usr/local/bin/ez-ipupdate started for interface ng0 host
xxxxxxxx.dyndns.org using server members.dyndns.org and service dyndns
Apr 18 16:13:28     /usr/local/bin/ez-ipupdate[175]: got last update
xx.xx.xx.xx on 2007/04/18 16:10 from cache file
Apr 18 16:13:28     /usr/local/bin/ez-ipupdate[175]: failure to update ng0->
xx.xx.xx.xx (xxxxxxxx.dyndns.org)
Apr 18 16:13:30     /usr/local/bin/ez-ipupdate[175]: SIGHUP recieved,
re-reading config file
Apr 18 16:13:30     /usr/local/bin/ez-ipupdate[175]: failure to update ng0->
xx.xx.xx.xx (xxxxxxxx.dyndns.org)
Apr 18 16:23:31     dnsmasq[96]: reading /etc/resolv.conf
Apr 18 16:23:31     dnsmasq[96]: using nameserver xx.xx.xx.xx#53
Apr 18 16:23:31     dnsmasq[96]: using nameserver xx.xx.xx.xx#53
Apr 18 16:23:31     /usr/local/bin/ez-ipupdate[175]: successful update for
ng0->xx.xx.xx.xx (xxxxxxxx.dyndns.org)

note that ez-ipudate no longer complains 'unable to resolve interface ng0'
(which didn't seem to matter for my 2nd m0n0wall: see previous post), but it
still fails on the first attempt, despite the fact that all other boot tasks
have already completed.

note also, an unusual number of log entries from mpd while bringing up the
pppoe link.  i don't speak mpd, so i can't tell if this indicates a problem
or not, but it differs from the mpd log entries for my other m0n0wall
deployments.

i'll post a sanitized config next.  it's worth noting that this problem
didn't manifest itself right away.  i re-tasked this box from another
m0n0wall deployment, where it had no troubles running 1.22.  a few days ago
i re-tasked it and cleared the config of many things.  i'll be using it as a
'single-port vpn' and need only a minimal config.  previously it had a much
more sophisticated config and dyndns worked just fine.  at some point in my
re-config process i noticed that dyndns wasn't working any more, although i
know for certain that it was when i started.  don't know if the problems
began with 1.231, or with some other change.

so the first problem is "why does it fail until a manual update?" and the
second problem is "why does adding a delay fix the first problem, but still
fails on the first attempt?"

out of curiosity, have you checked your logs after a reboot to see if
ez-ipupdate fails the first (few) times?

cheers,
jj

On 4/18/07, Lee Sharp <leesharp at hal dash pc dot org> wrote:
>
> Odd... I have Dyndns on everything (over 30 boxes) and do not have this
> problem.  Can you post a sanitized config?
>
>                         Lee
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>
>