Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Some Advice Please - WAN 0.0.0.0

    Scheduled Pinned Locked Moved
    Problems Installing or Upgrading pfSense Software
    4
    9
    12.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      dciso
      last edited by

      Im trying to set up pfsense but I cannot seem to get an ip address on the WAN. Ive tried cloning the old routers mac address and done the usual reset on the cable modem just to be sure. I would just like to check that i've connected everything correctly.

      So this is how ive done it:

      WAN:
      (ISP)Virgin Media -> Cable Modem -> WAN (pfsense)

      LAN:
      LAN(pfsense) -> Router (DD-WRT) - Using WAN Port

      Cheers, Jason.

      1 Reply Last reply Reply Quote 0
      • Cry HavokC
        Cry Havok
        last edited by

        Before my motherboard gave up the ghost I had my pfSense 1.2.3 box hooked up to the VirginMedia cable modem without problems.

        What version of pfSense are you running?  Is it set to use DHCP for the LAN?  Did you power down both the cable modem and the pfSense host before powering up first the cable modem and then the pfSense host?  Is the cable modem synchronised - does it work if you hook up another device with the same network cable?

        1 Reply Last reply Reply Quote 0
        • D
          dciso
          last edited by

          Its wierd I've got it working now. Im running 1.2.3 and all I did was switch the LAN & WAN round.

          I was orginally using Broadcom 440x for the WAN and D-Link DFE-690TXD for LAN. So I changed it to:
          WAN: D-Link, LAN: Broadcom and restarted pfsense and everythings working.

          Cheers for your reply  :)

          1 Reply Last reply Reply Quote 0
          • E
            e
            last edited by

            I am also running in the same problem and I have tried reassigning the LAN and WAN but it still doesn't work.

            I have Realtek and 3com 3c920 NIC in my setup and pfsense recognizes both NIC's.

            Currently I have:

            LAN: Realtek -> crossover cable -> switch -> PC  [this works and I can connect to pfsense via www]
            WAN: 3com -> crossover cable & patch cable -> cable modem [set for DHCP but doesn't pick up an IP]

            I have tried spoofing the mac address of the WAN NIC to the mac address of my old dlink router and that did not work. I can connect my PC directly to the cable modem and it automatically picks up an IP and connects.

            I have also powered down the cable modem and pfsense and rebooted the cable modem and then pfsense. That didn't work either.

            Anyone have any tips?

            1 Reply Last reply Reply Quote 0
            • W
              wallabybob
              last edited by

              Your WAN interface should be UP else it won't send the DHCP request to get an IP adress. Check in web GUI:  Status -> Interfaces, scroll to the appropriate interface and status line.

              dhclient process should be running. If not, did it leave any clues in the system log? (Check from console or ssh session by command  clog /var/log/system.log or web GUI: Status -> System logs )

              1 Reply Last reply Reply Quote 0
              • E
                e
                last edited by

                Thanks for the reply.

                Here is how it looks currently. I have tried connecting the WAN to the cable modem with both a crossover and a patch cable but neither works. The cable modem does light up when I do connect the either of the cables to the pfsense server and the wan nic lights up too when it is connected. I have also swapped the LAN and WAN interfaces and that didn't work. I enabled bridging the LAN and WAN too and that didn't work. The mac addresses for the LAN and WAN are the same spoof for a home router that did connect to the cable modem before I tried pfsense. I removed the spoof for the interfaces and that didn't fix it either. Here is the output that you recommended that I post:

                WAN interface (ed0)
                Status     up
                DHCP     up
                MAC address     00:11:95:0c:6b:8d
                IP address     0.0.0.0
                Subnet mask     255.0.0.0
                ISP DNS servers    
                Media     10baseT/UTP
                In/out packets     84839/11288 (5.29 MB/3.85 MB)
                In/out errors     0/2
                Collisions     429
                LAN interface (xl0)
                Status     up
                MAC address     00:11:95:0c:6b:8d
                IP address     192.168.1.1
                Subnet mask     255.255.255.0
                Media     100baseTX <full-duplex>In/out packets     451427/35990 (27.07 MB/11.75 MB)
                In/out errors     0/0
                Collisions     0

                I tried enabling "Bridge (bridge0)     learning " but release->renew ip didn't change anything

                Dec 23 22:08:57     dhclient[1536]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 7
                Dec 23 22:09:04     dhclient[1536]: No DHCPOFFERS received.
                Dec 23 22:09:04     dhclient[1536]: No working leases in persistent database - sleeping.
                Dec 23 22:09:05     dhclient[1655]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 1
                Dec 23 22:09:06     check_reload_status: reloading filter
                Dec 23 22:09:06     dhclient[1655]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 2
                Dec 23 22:09:06     dnsmasq[1218]: exiting on receipt of SIGTERM
                Dec 23 22:09:08     dnsmasq[1767]: started, version 2.45 cachesize 150
                Dec 23 22:09:08     dnsmasq[1767]: compile time options: IPv6 GNU-getopt BSD-bridge ISC-leasefile no-DBus no-I18N TFTP
                Dec 23 22:09:08     dnsmasq[1767]: no servers found in /etc/resolv.conf, will retry
                Dec 23 22:09:08     dnsmasq[1767]: no servers found in /etc/resolv.conf, will retry
                Dec 23 22:09:08     dnsmasq[1767]: read /etc/hosts - 2 addresses
                Dec 23 22:09:08     dhclient[1655]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 5
                Dec 23 22:09:09     php: /interfaces_wan.php: NOTE: DHCP Server on LAN is enabled.
                Dec 23 22:09:09     dhcpd: Internet Systems Consortium DHCP Server V3.0.7
                Dec 23 22:09:09     dhcpd: Copyright 2004-2008 Internet Systems Consortium.
                Dec 23 22:09:09     dhcpd: All rights reserved.
                Dec 23 22:09:09     dhcpd: For info, please visit http://www.isc.org/sw/dhcp/
                Dec 23 22:09:12     check_reload_status: reloading filter
                Dec 23 21:58:43     dhclient[38862]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 12
                Dec 23 21:58:55     dhclient[38862]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 18
                Dec 23 21:59:13     dhclient[38862]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 2
                Dec 23 21:59:15     dhclient[38862]: No DHCPOFFERS received.
                Dec 23 21:59:15     dhclient[38862]: No working leases in persistent database - sleeping.
                Dec 23 21:59:16     dhclient[38862]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 1
                Dec 23 21:59:17     dhclient[38862]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 2
                Dec 23 21:59:19     dhclient[38862]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 2
                Dec 23 21:59:21     dhclient[38862]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 3
                Dec 23 21:59:24     dhclient[38862]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 8
                Dec 23 21:59:32     dhclient[38862]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 13
                Dec 23 21:59:45     dhclient[38862]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 21
                Dec 23 22:00:06     dhclient[38862]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 11
                Dec 23 22:00:17     dhclient[38862]: No DHCPOFFERS received.
                Dec 23 22:00:17     dhclient[38862]: No working leases in persistent database - sleeping.
                Dec 23 22:00:18     dhclient[38862]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 2</full-duplex>

                1 Reply Last reply Reply Quote 0
                • W
                  wallabybob
                  last edited by

                  The log suggests no dhcp response. Could it have been blocked by the firewall?
                  I would check the firewall log and take a packet trace on your wan interface to get more information.

                  1 Reply Last reply Reply Quote 0
                  • E
                    e
                    last edited by

                    I appreciate your help. The firewall was blocking traffic and I added the following rules but still no go:

                    WAN

                    Proto Source Port Destination Port Gateway Schedule Description
                    [add new rule]
                    [click to toggle enabled/disabled status] * * * * * *   Net -> WAN any  
                      LAN

                    Proto Source Port Destination Port Gateway Schedule Description
                    [add new rule]
                    [click to toggle enabled/disabled status] * LAN net * * * *   Default LAN

                    Disabled Block private networks & Block bogon networks

                    WAN interface (ed0)
                    Status up
                    DHCP up 
                    MAC address 00:11:95:0c:6b:8d
                    IP address 0.0.0.0 
                    Subnet mask 255.0.0.0
                    ISP DNS servers

                    Last 50 system log entries
                    Dec 25 01:39:28 dhclient[52789]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 11
                    Dec 25 01:39:09 dhclient[52789]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 19
                    Dec 25 01:38:59 dhclient[52789]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 10
                    Dec 25 01:38:52 dhclient[52789]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 7
                    Dec 25 01:38:47 dhclient[52789]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 5
                    Dec 25 01:38:43 dhclient[52789]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 4
                    Dec 25 01:38:41 dhclient[52789]: DHCPDISCOVER on ed0 to 255.255.255.255 port 67 interval 2
                    Dec 25 01:38:40 dhclient[52789]: No working leases in persistent database - sleeping.
                    Dec 25 01:38:40 dhclient[52789]: No DHCPOFFERS received.

                    Last 50 firewall log entries
                    Dec 25 01:38:27 pf: Client-Ethernet-Address 00:18:39:69:35:dc [|bootp]
                    Dec 25 01:38:27 pf: Gateway-IP 10.20.184.1
                    Dec 25 01:38:27 pf: Your-IP 24.XXX.XXX.XXX
                    Dec 25 01:38:27 pf: 47. 355595 rule 40/0(match): pass in on ed0: (tos 0x0, ttl 255, id 60784, offset 0, flags [none], proto UDP (17), length 367) 10.20.184.1.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length 339, xid 0x27c6, Flags [Broadcast]
                    Dec 25 01:37:39 pf: 35. 867439 rule 41/0(match): pass in on ed0: (tos 0xc0, ttl 1, id 50768, offset 0, flags [none], proto IGMP (2), length 28) 192.168.100.1 > 224.0.0.1: igmp query v1
                    Dec 25 01:37:03 pf: file "d;kf" [|bootp]

                    I have the WAN set to DHCP. I cannot ping the Gateway-IP. The LAN is bridged to WAN.

                    1 Reply Last reply Reply Quote 0
                    • W
                      wallabybob
                      last edited by

                      @e:

                      I have also powered down the cable modem and pfsense

                      Others have reported that the power needs to be off for some seconds, at least long enough for the power supply capacitors to drain.

                      Have you done the suggested packet trace on the wan interface?

                      Might be time to talk with your ISP's technical support.

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post