Pfs v2 - WAN: PPTP – no InternetAccess



  • Maybe I'am a complete moron but I don't get InternetAccess to work on pfSense v2

    Version: pfSense v2.0 RELEASE x64
    Host: xenServer v6 beta

    What I've done:

    • fresh install of pfSense v2.0

    • assigned interfaces in shell after startup

    • assigned IP for LAN (192.168.23.254) in shell after startup

    • auto-launch of wizard in webbrowser

    Wizard-Config:

    • DNS servers

    • hostname

    • domainname

    • WAN

      • type: PPtP

      • MTU: 1492

      • intIP 10.0.0.140/24

      • extIP 10.0.0.138

      • no DialOnDemand

      • no IdleTimeout

      • block private/bogon

    When the wizard is finished the PPTP connection is sucessfully established and I can ping (Diagnostics->Ping) a domain (www.google.at) from WAN interface. Ping from LAN interface isn't possible.
    Firewall Rules are the standard ones after installation (LAN allow all).
    The same configuration works just fine with pfSense v1.2.3



  • Can you ping IP without using the name?



  • @podilarius:

    Can you ping IP without using the name?

    Yes and No^^

    Update:
    pinging google doesn't seem to work on LAN interface, pinging other sites (www.orf.at) does work.
    pinging IP's from LAN do work for 195.3.96.67 and 213.33.98.136 (ISP DNS), but doesn't work for 8.8.8.8 and 8.8.4.4 (google DNS)

    Pings were done on a client on LAN interface and within pfSense PING from WAN and LAN interface.
    all Pings from WAN interface do work.
    pfSense diagnostic->traceroute - everythings fine (except I use additional google DNS, they don't respond, but that's another story)
    WebSurfing (aka any filetransfer from / to web) doesn't work

    and the best - played around too much and accidently deletet the v1 snapshot (in this case you can call me a moron :( )

    XenServer, Modem, …. - I don't think there's a problem, till today pfSense v1 worked like charm - also ipFire which I use now for fallback works just fine



  • Update 2:
    Thank's to VM I can play around a bit more….
    Added a IPFire between pfSense WAN and modem and configurated pfSense's WAN to DHCP - everything's working (also google-dns 8.8.8.8/8.8.4.4)

    The problem can be pinned to PPTP / communication between modem and pfSense

    BTW - this is not a fix, I don't wanna use a additional system between modem and pfSense



  • Update 3:
    If it's useful - installed a m0n0wall (v1.33) with same Sources as pfSense and it also work's just fine….



  • Scenario x86:


    Version: pfSense v2.0 RELEASE x86
    Host: xenServer v6 beta

    Config:

    • fresh install of pfSense v2.0

    • assigned interfaces in shell

    • assigned IP for LAN (192.168.23.254) and enabled DHCP in shell

    • hostname (katan)

    • domainname (araboth)

    • WAN

      • type: PPTP

      • MTU: 1492

      • intIP 10.0.0.137/30

      • extIP 10.0.0.138

      • no DialOnDemand

      • no IdleTimeout

      • block private/bogon

    Attempts:

    • WAN

      • MTU: 1492, 1500
    • LAN

      • MTU: 1492, 1500

      • all network speed and duplex settings

    • Hardware

      • complete reboot of all devices (XenServer, modem, switches;)

      • changed network cable

    Status:

    • I can ping everything from everywhere (IP, domain, LAN, WAN) which didn't work before

    • I can tracert everything from everywhere (IP, domain, LAN, WAN) which too didn't work before

    • I can't open Webpages

    • I can do a FirmwareCheck

    • I can't open install packages tab in pfsense - returns the error that no communication is possible


    If anyone has idea's, need additional informations, etc. let me know, I'm going to freak out about this problem.



  • I've given up - after a few fresh-installs, new creation of new VM and "pain in the head" log file reading I'll wait till  pfSense gets an update - maybe then it will work.
    Actual FW is m0n0 which indeed is very good, but I'm missing pfSense features ;-)


Log in to reply