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

    No WAN and Webgui after adding second Intel Quad NIC

    Hardware
    2
    3
    617
    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.
    • N
      newbie1975
      last edited by newbie1975

      Using pfSense 2.5.1. with Intel PRO/1000 VT PCI-E Quad Port Server Adapter. Everything works.

      Today installed second NIC (now ET version): Intel Pro/1000 ET PCI-E Quad Port Server Adapter.

      pfSense seems to fully boot and new NIC seems to be recognized as igb4 - igb7, but WAN is not coming up and also no webgui. Also all connected laptops disconnect.

      Only relevant item in log I can find:

      Apr 17 17:51:18 	kernel 		done.
      Apr 17 17:51:18 	php 	397 	rc.bootup: NTPD is starting up.
      Apr 17 17:51:18 	ppp 	9611 	[wan_link0] PPPoE: Connecting to ''
      Apr 17 17:51:18 	ppp 	9611 	[wan_link0] Link: reconnection attempt 1
      Apr 17 17:51:18 	kernel 		done.
      Apr 17 17:51:18 	kernel 		failed!
      Apr 17 17:51:18 	php 	397 	rc.bootup: The command '/usr/local/sbin/nginx -c /var/etc/nginx-webConfigurator.conf' returned exit code '1', the output was 'nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use) nginx: [emerg] still could not bind()'
      Apr 17 17:51:16 	nginx 		2021/04/17 17:51:16 [emerg] 6745#100117: still could not bind()
      Apr 17 17:51:16 	nginx 		2021/04/17 17:51:16 [emerg] 6745#100117: bind() to 0.0.0.0:443 failed (48: Address already in use)
      Apr 17 17:51:17 	ppp 	9611 	[wan_link0] Link: reconnection attempt 1 in 1 seconds
      Apr 17 17:51:17 	ppp 	9611 	[wan_link0] LCP: Down event
      Apr 17 17:51:17 	ppp 	9611 	[wan_link0] Link: DOWN event
      Apr 17 17:51:17 	ppp 	9611 	[wan_link0] PPPoE connection timeout after 9 seconds
      Apr 17 17:51:16 	nginx 		2021/04/17 17:51:16 [emerg] 6745#100117: bind() to 0.0.0.0:443 failed (48: Address already in use)
      Apr 17 17:51:16 	nginx 		2021/04/17 17:51:16 [emerg] 6745#100117: bind() to 0.0.0.0:443 failed (48: Address already in use)
      Apr 17 17:51:16 	nginx 		2021/04/17 17:51:16 [emerg] 6745#100117: bind() to 0.0.0.0:443 failed (48: Address already in use)
      Apr 17 17:51:16 	nginx 		2021/04/17 17:51:16 [emerg] 6745#100117: bind() to 0.0.0.0:443 failed (48: Address already in use)
      Apr 17 17:51:15 	kernel 		done.
      Apr 17 17:51:14 	kernel 		done. 
      

      I do not think it is a faulty NIC, as I already tried another with same results.

      Would the error "emerg] 6745#100117: bind() to 0.0.0.0:443 failed (48: Address already in use)" be related to the new NIC and no WAN / WebGui?

      stephenw10S 1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator @newbie1975
        last edited by

        That might prevent accessing the webgui, though it's probably showing that because it's already running, but it wouldn't stop the WAN connecting.

        More likely the ports have been re-ordered because you added more igb NICs. You will have you will have to do some testing to find out which port is now igb0 etc.

        Steve

        N 1 Reply Last reply Reply Quote 0
        • N
          newbie1975 @stephenw10
          last edited by

          @stephenw10 Thanks for your reply, but I am not sure if this was the case, as I can see in the log that igb0 - igb3 is still same (original) mac address.

          I also switched the two Quad NICs in the PCI-E ports. After switching the WebGui and WAN were available again and I was also able to enable to new interfaces. Everything now works.

          Still do not understand why just adding new NIC in empty PCI-E didn't work immediately. Adding a new NIC shouldn't require any adjustments or analysis (imo).

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.