Router gets no Gateway-IP!



  • Hi All!

    First of all, sorry for my English it's not perfect…

    Problem:

    Main target: we would like to simulate a real ISP (with the DSLAM and a PPPoE auth.), but we are still in a private network!

    I'm running a PPPoE-Sever on pfSense via DSLAM to a Router:

    pfSense (PPPoE)

    WAN:

    • IP-address: 192.168.3.3 / 24
    • Gateway: 192.168.3.4

    LAN:

    • 172.16.0.1 / 16

    DNS:

    • 192.168.3.4 (last pfSense behind the "real" router)
    • 195.186.1.111 (DNS from the ISP)

    The PPPoE-conf looks like this:

    • Interface: LAN
    • Subnetmask: 16
    • Server address: 172.16.0.16
    • Remote address range: 172.16.0.32

    Services:

    • DNS forwarder

    The authentification runs now on the PPPoE Sever and not on the freeRADIUS, but it works fine (the log say…)!
    So finally the Router gets an ip-address (i.e. 172.16.0.97) and the subnetmask 255.255.255.255, but no gateway!
    I have no idea whats wrong or which config is missing, so please help me... thx!

    cu



  • 
    Jul 18 14:54:14 	syslogd: kernel boot file is /boot/kernel/kernel
    Jul 18 14:55:07 	mpd: Incoming PPPoE connection request via xl0: for service "*" from 00:02:cf:4b:7b:a4
    Jul 18 14:55:07 	mpd: PROTOCOMP
    Jul 18 14:55:07 	mpd: MRU 1492
    Jul 18 14:55:07 	mpd: MAGICNUM 1beee7da
    Jul 18 14:55:07 	mpd: AUTHPROTO CHAP MD5
    Jul 18 14:55:07 	mpd: MRU 1492
    Jul 18 14:55:07 	mpd: MAGICNUM 00000cdf
    Jul 18 14:55:07 	mpd: MRU 1492
    Jul 18 14:55:07 	mpd: MAGICNUM 00000cdf
    Jul 18 14:55:07 	mpd: PROTOCOMP
    Jul 18 14:55:07 	mpd: MRU 1492
    Jul 18 14:55:07 	mpd: MAGICNUM 1beee7da
    Jul 18 14:55:07 	mpd: AUTHPROTO CHAP MD5
    Jul 18 14:55:07 	mpd: MRU 1492
    Jul 18 14:55:07 	mpd: MAGICNUM 1beee7da
    Jul 18 14:55:07 	mpd: AUTHPROTO CHAP MD5
    Jul 18 14:55:07 	mpd: Name: "virDSL"
    Jul 18 14:55:07 	mpd: Peer name: "virDSL"
    Jul 18 14:55:07 	mpd: Response is valid
    Jul 18 14:55:07 	mpd: IPADDR 172.16.0.16
    Jul 18 14:55:07 	mpd: IPADDR 0.0.0.0
    Jul 18 14:55:07 	mpd: NAKing with 172.16.0.32
    Jul 18 14:55:07 	mpd: PRIDNS 0.0.0.0
    Jul 18 14:55:07 	mpd: NAKing with 172.16.0.1
    Jul 18 14:55:07 	mpd: SECDNS 0.0.0.0
    Jul 18 14:55:07 	mpd: NAKing with 192.168.3.4
    Jul 18 14:55:07 	mpd: IPADDR 172.16.0.32
    Jul 18 14:55:07 	mpd: PRIDNS 172.16.0.1
    Jul 18 14:55:07 	mpd: SECDNS 192.168.3.4
    Jul 18 14:55:07 	mpd: IPADDR 172.16.0.16
    Jul 18 14:55:07 	mpd: IPADDR 172.16.0.32
    Jul 18 14:55:07 	mpd: 172.16.0.32 is OK
    Jul 18 14:55:07 	mpd: PRIDNS 172.16.0.1
    Jul 18 14:55:07 	mpd: SECDNS 192.168.3.4
    Jul 18 14:55:07 	mpd: IPADDR 172.16.0.32
    Jul 18 14:55:07 	mpd: PRIDNS 172.16.0.1
    Jul 18 14:55:07 	mpd: SECDNS 192.168.3.4
    Jul 18 14:55:07 	mpd: 172.16.0.16 -> 172.16.0.32
    
    


  • Search forum for secondary dns.  Your ISP is not giving you a second DNS server so pfSense rejects it.  There is a hidden knob to disable this.



  • Nice, I would try this…



  • Hmm… I don't get it! Probably my description was not the best, take a look at the network-plan it might helps.

    /first post -> update
    /system log -> update


Log in to reply