DynDNS Problems with 1.0 Beta 1



  • Hi  & a happy new year

    after installing or updating to 1.0 beta 1, I´ve got a problem with DynDNS !
    After Install ( or Update ) DynDNS works fine and then after a reboot, DynDNS got this IP form me

    "192.0.2.112"

    its not my IP, I think its come from pfsense

    best wishes
    Udo



  • If that ip is not assigned to pfSense then I don't see how…



  • if he is beheind a extra router then the pfsense ip is not the ip that dyndns needs



  • In that case the router in front would have to do the dyndnsupgrade as only this one sees the real public IP. Don't understand why that should have worked before the upgrade though. More details on his setup needed.



  • @MainFrame:

    Hi  & a happy new year

    after installing or updating to 1.0 beta 1, I´ve got a problem with DynDNS !
    After Install ( or Update ) DynDNS works fine and then after a reboot, DynDNS got this IP form me

    "192.0.2.112"

    its not my IP, I think its come from pfsense

    best wishes
    Udo

    Yup, that came from pfSense

    billm@workstation$ grep -n 192.0.2 *
    interfaces.inc:1106:    set iface addrs 192.0.2.112 192.0.2.113

    Odd though, that address is only used during PPPOE link-up, as soon as the link is up the interface has it's real address then the DynDNS script is supposed to run.  Unfortunately, w/out PPPOE here I won't be able to replicate this and it's unlikely to get fixed unless someone with PPPOE can replicate and troubleshoot it.

    –Bill



  • Hello,
    always the same problems DynDNs, last testet ver 28.01, here is the last log :

    Jan 31 15:50:10 php: : Resyncing configuration for all packages.
    Jan 31 15:50:09 php: : phpDynDNS: (Success) IP Address Changed Successfully! (192.0.2.112)
    Jan 31 15:50:09 php: : phpDynDNS: updating cache file /cf/conf/dyndns.cache: 82.83.52.25
    Jan 31 15:50:09 php: : DynDns: Current Service: dyndns
    Jan 31 15:50:09 php: : DynDns: DynDns _checkStatus() starting.
    Jan 31 15:50:03 mpd: [pppoe] IFACE: Up event
    Jan 31 15:50:03 mpd: [pppoe] exec: /usr/local/sbin/ppp-linkup ng0 inet 82.83.52.25 82.83.32.1 xxxxxxxxxxxxx dns1 195.50.140.114
    Jan 31 15:50:03 mpd: [pppoe] exec: /sbin/route add 0.0.0.0 82.83.32.1
    Jan 31 15:50:03 mpd: [pppoe] exec: /sbin/route add 82.83.52.25 -iface lo0
    Jan 31 15:50:03 mpd: [pppoe] exec: /sbin/ifconfig ng0 82.83.52.25 82.83.32.1 netmask 0xffffffff -link0
    Jan 31 15:50:03 mpd: [pppoe] setting interface ng0 MTU to 1492 bytes
    Jan 31 15:50:03 mpd: [pppoe] exec: /sbin/ifconfig ng0 down delete -link0
    Jan 31 15:50:03 mpd: [pppoe] exec: /sbin/route delete 192.0.2.112 -iface lo0
    Jan 31 15:50:03 mpd: [pppoe] exec: /sbin/route delete 0.0.0.0 192.0.2.113
    Jan 31 15:50:03 mpd: [pppoe] IFACE: Up event
    Jan 31 15:50:03 mpd: 82.83.52.25 -> 82.83.32.1
    Jan 31 15:50:03 mpd: [pppoe] IPCP: LayerUp
    Jan 31 15:50:03 mpd: [pppoe] IPCP: state change Ack-Sent –> Opened
    Jan 31 15:50:03 mpd: PRIDNS 195.50.140.114
    Jan 31 15:50:03 mpd: IPADDR 82.83.52.25
    Jan 31 15:50:03 mpd: [pppoe] IPCP: rec'd Configure Ack #3 link 0 (Ack-Sent)
    Jan 31 15:50:03 mpd: PRIDNS 195.50.140.114
    Jan 31 15:50:03 mpd: IPADDR 82.83.52.25
    Jan 31 15:50:03 mpd: [pppoe] IPCP: SendConfigReq #3
    Jan 31 15:50:03 mpd: PRIDNS 195.50.140.114
    Jan 31 15:50:03 mpd: 82.83.52.25 is OK
    Jan 31 15:50:03 mpd: IPADDR 82.83.52.25
    Jan 31 15:50:03 mpd: [pppoe] IPCP: rec'd Configure Nak #2 link 0 (Ack-Sent)
    Jan 31 15:50:03 mpd: PRIDNS 0.0.0.0
    Jan 31 15:50:03 mpd: IPADDR 0.0.0.0
    Jan 31 15:50:03 mpd: [pppoe] IPCP: SendConfigReq #2
    Jan 31 15:50:03 mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Jan 31 15:50:03 mpd: [pppoe] IPCP: rec'd Configure Reject #1 link 0 (Ack-Sent)
    Jan 31 15:50:03 mpd: [pppoe] IPCP: state change Req-Sent –> Ack-Sent
    Jan 31 15:50:03 mpd: IPADDR 82.83.32.1
    Jan 31 15:50:03 mpd: [pppoe] IPCP: SendConfigAck #70
    Jan 31 15:50:03 mpd: 82.83.32.1 is OK
    Jan 31 15:50:03 mpd: IPADDR 82.83.32.1
    Jan 31 15:50:03 mpd: [pppoe] IPCP: rec'd Configure Request #70 link 0 (Req-Sent)
    Jan 31 15:50:03 mpd: PRIDNS 0.0.0.0
    Jan 31 15:50:03 mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Jan 31 15:50:03 mpd: IPADDR 0.0.0.0
    Jan 31 15:50:03 mpd: [pppoe] IPCP: SendConfigReq #1
    Jan 31 15:50:03 mpd: [pppoe] IPCP: state change Starting –> Req-Sent
    Jan 31 15:50:03 mpd: [pppoe] IPCP: Up event
    Jan 31 15:50:03 mpd: [pppoe] up: 1 link, total bandwidth 64000 bps
    Jan 31 15:50:03 mpd: [pppoe] setting interface ng0 MTU to 1492 bytes
    Jan 31 15:50:03 mpd: [pppoe] LCP: phase shift AUTHENTICATE –> NETWORK
    Jan 31 15:50:03 mpd: [pppoe] LCP: authorization successful
    Jan 31 15:50:03 mpd: MESG: CHAP authentication success, unit 11282
    Jan 31 15:50:03 mpd: [pppoe] CHAP: rec'd SUCCESS #1
    Jan 31 15:50:03 mpd: [pppoe] CHAP: sending RESPONSE
    Jan 31 15:50:03 mpd: Using authname "xxxxxxxxxxxxx"
    Jan 31 15:50:03 mpd: Name: "hanbr4"
    Jan 31 15:50:03 mpd: [pppoe] CHAP: rec'd CHALLENGE #1
    Jan 31 15:50:03 mpd: [pppoe] LCP: LayerUp
    Jan 31 15:50:03 mpd: [pppoe] LCP: auth: peer wants CHAP, I want nothing
    Jan 31 15:50:03 mpd: [pppoe] LCP: phase shift ESTABLISH –> AUTHENTICATE
    Jan 31 15:50:03 mpd: [pppoe] LCP: state change Ack-Sent –> Opened
    Jan 31 15:50:03 mpd: MAGICNUM ccab5381
    Jan 31 15:50:03 mpd: MRU 1492
    Jan 31 15:50:03 mpd: [pppoe] LCP: rec'd Configure Ack #1 link 0 (Ack-Sent)
    Jan 31 15:50:03 mpd: [pppoe] LCP: state change Req-Sent –> Ack-Sent
    Jan 31 15:50:03 mpd: MAGICNUM 3c93fcb9
    Jan 31 15:50:03 mpd: AUTHPROTO CHAP MD5
    Jan 31 15:50:03 mpd: MRU 1492
    Jan 31 15:50:03 mpd: [pppoe] LCP: SendConfigAck #127
    Jan 31 15:50:03 mpd: MAGICNUM 3c93fcb9
    Jan 31 15:50:03 mpd: AUTHPROTO CHAP MD5
    Jan 31 15:50:03 mpd: MRU 1492
    Jan 31 15:50:03 mpd: [pppoe] LCP: rec'd Configure Request #127 link 0 (Req-Sent)
    Jan 31 15:50:03 mpd: MAGICNUM ccab5381
    Jan 31 15:50:03 mpd: MRU 1492
    Jan 31 15:50:03 mpd: [pppoe] LCP: SendConfigReq #1
    Jan 31 15:50:03 mpd: [pppoe] LCP: phase shift DEAD –> ESTABLISH
    Jan 31 15:50:03 mpd: [pppoe] LCP: state change Starting –> Req-Sent
    Jan 31 15:50:03 mpd: [pppoe] LCP: Up event
    Jan 31 15:50:03 mpd: [pppoe] link: origination is local
    Jan 31 15:50:03 mpd: [pppoe] link: UP event
    Jan 31 15:50:03 mpd: [pppoe] device is now in state UP
    Jan 31 15:50:03 mpd: [pppoe] device: UP event in state OPENING
    Jan 31 15:50:03 mpd: [pppoe] PPPoE connection successful
    Jan 31 15:50:03 mpd: [pppoe] rec'd ACNAME "hanbr004"
    Jan 31 15:50:03 mpd: [pppoe] device is now in state OPENING
    Jan 31 15:50:03 mpd: [pppoe] device: OPEN event in state DOWN
    Jan 31 15:50:03 mpd: [pppoe] LCP: LayerStart
    Jan 31 15:50:03 mpd: [pppoe] LCP: state change Initial –> Starting
    Jan 31 15:50:03 mpd: [pppoe] LCP: Open event
    Jan 31 15:50:03 mpd: [pppoe] link: OPEN event
    Jan 31 15:50:03 mpd: [pppoe] opening link "pppoe"…
    Jan 31 15:50:03 mpd: [pppoe] bundle: OPEN event in state CLOSED
    Jan 31 15:50:03 mpd: [pppoe] IPCP: LayerStart
    Jan 31 15:50:03 mpd: [pppoe] IPCP: state change Initial –> Starting
    Jan 31 15:50:03 mpd: [pppoe] IPCP: Open event
    Jan 31 15:50:03 mpd: [pppoe] outgoing packet is demand
    Jan 31 15:50:03 php: : DynDns: DynDns _update() starting.
    Jan 31 15:50:03 php: : DynDns: More than 25 days. Updating.
    Jan 31 15:50:03 php: : DynDns: cacheIP != wan_ip. Updating.
    Jan 31 15:50:03 php: : DynDns: Cached IP:
    Jan 31 15:50:03 php: : DynDns: Current WAN IP: 192.0.2.112
    Jan 31 15:50:03 php: : DynDns: _detectChange() starting.
    Jan 31 15:50:03 php: : DynDns: updatedns() starting
    Jan 31 15:50:03 php: : DynDns: Running updatedns()
    Jan 31 15:50:03 dnsmasq[461]: using nameserver 195.50.140.114#53
    Jan 31 15:50:03 dnsmasq[461]: using nameserver 213.148.130.10#53
    Jan 31 15:50:03 dnsmasq[461]: reading /etc/resolv.conf
    Jan 31 15:50:03 dnsmasq[461]: read /etc/hosts - 6 addresses
    Jan 31 15:50:03 dnsmasq[461]: started, version 2.22 cachesize 150
    Jan 31 15:49:59 kernel: pflog0: promiscuous mode enabled
    Jan 31 15:49:30 php: : DEVD Ethernet attached event for sis3
    Jan 31 15:49:29 php: : Hotplug event detected for sis2 but ignoring since interface is not set for DHCP
    Jan 31 15:49:28 php: : Hotplug event detected for sis1 but ignoring since interface is not set for DHCP
    Jan 31 15:49:28 mpd: [pppoe] exec: /usr/local/sbin/ppp-linkup ng0 inet 192.0.2.112 192.0.2.113 xxxxxxxxxxxxx
    Jan 31 15:49:28 mpd: [pppoe] exec: /sbin/route add 0.0.0.0 192.0.2.113
    Jan 31 15:49:27 mpd: [pppoe] exec: /sbin/route add 192.0.2.112 -iface lo0
    Jan 31 15:49:27 mpd: [pppoe] exec: /sbin/ifconfig ng0 192.0.2.112 192.0.2.113 netmask 0xffffffff link0
    Jan 31 15:49:27 mpd: [pppoe] setting interface ng0 MTU to 1500 bytes
    Jan 31 15:49:27 mpd: [pppoe] IFACE: Open event
    Jan 31 15:49:27 mpd: [pppoe] IPCP: peer address cannot be zero
    Jan 31 15:49:27 mpd: [pppoe] using interface ng0
    Jan 31 15:49:27 mpd: [pppoe] exec: /sbin/ifconfig sis3 up
    Jan 31 15:49:27 mpd: [pppoe] ppp node is "mpd209-pppoe"
    Jan 31 15:49:27 mpd: mpd: pid 209, version 3.18 (root@builder.livebsd.com 21:37 23-Dec-2005)
    Jan 31 15:49:27 php: : Hotplug event detected for sis0 but ignoring since interface is not set for DHCP

    At first DynDNS get the right IP, but this RIGHT IP, would be overwritten with 192.0.2.112
    What can I do ?? :-[

    The last working Version is 0.95.8



  • I find it very strange that nobody else is having problems.  Whenever there are problems with DynDNS people come out in droves with pitchforks making my life a living hell.

    With that said, it thinks you're ip is phpDynDNS: (Success) IP Address Changed Successfully! (192.0.2.112)  so where is this ip coming from.

    Do a ifconfig and post the results.



  • Ok, here the log from ifconfig:

    $ ifconfig
    sis0: flags=8843 <up,broadcast,running,simplex,multicast>mtu 1500
    options=8 <vlan_mtu>inet 192.168.123.254 netmask 0xffffff00 broadcast 192.168.123.255
    inet6 fe80::200:24ff:fec4:5d54%sis0 prefixlen 64 scopeid 0x1
    ether 00:00:24:c4:5d:54
    media: Ethernet autoselect (100baseTX <full-duplex>)
    status: active
    sis1: flags=8842 <broadcast,running,simplex,multicast>mtu 1500
    options=8 <vlan_mtu>ether 00:00:24:c4:5d:55
    media: Ethernet autoselect (none)
    status: no carrier
    sis2: flags=8842 <broadcast,running,simplex,multicast>mtu 1500
    options=8 <vlan_mtu>ether 00:00:24:c4:5d:56
    media: Ethernet autoselect (none)
    status: no carrier
    sis3: flags=8843 <up,broadcast,running,simplex,multicast>mtu 1500
    options=8 <vlan_mtu>inet6 fe80::200:24ff:fec4:5d57%sis3 prefixlen 64 scopeid 0x4
    ether 00:00:24:c4:5d:57
    media: Ethernet autoselect (100baseTX <full-duplex>)
    status: active
    lo0: flags=8049 <up,loopback,running,multicast>mtu 16384
    inet 127.0.0.1 netmask 0xff000000
    inet6 ::1 prefixlen 128
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
    pflog0: flags=100 <promisc>mtu 33208
    pfsync0: flags=41 <up,running>mtu 2020
    pfsync: syncdev: lo0 maxupd: 128
    ng0: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>mtu 1492
    inet6 fe80::200:24ff:fec4:5d54%ng0 prefixlen 64 scopeid 0x8
    inet 82.83.39.180 –> 82.83.32.1 netmask 0xffffffff</up,pointopoint,running,noarp,simplex,multicast></up,running></promisc></up,loopback,running,multicast></full-duplex></vlan_mtu></up,broadcast,running,simplex,multicast></vlan_mtu></broadcast,running,simplex,multicast></vlan_mtu></broadcast,running,simplex,multicast></full-duplex></vlan_mtu></up,broadcast,running,simplex,multicast>



  • That IP is not even in you're list.  So I stand by my earlier statement of I dont see how this is happening.



  • Hi,
    ok - this IP is not in the list - BUT this IP was transfered to DynDNS. In which file was the IP saved - that I can check it and delete it by myself.

    It´s a problem and I don´t no why this problem is ONLY in my system ? ???

    Have a nice WE



  • Hi, I ´ve found the Problem  :)

    "General Setup" DNS servers: If there is an entry with the original DNS server from Arcor (195.50.140.114) DynDNS don´t work, if this entry is empty and pfsense get the DNS server (195.50.140.114) automatically from the ISP (a bit later) all works fine  :)

    Bye



  • These problems where just fixed.


Locked