Issues with the GA-C1007UN-D Intel NM70



  • so i think this is just a hardware issue, but i thought i would check here for thoughts. I had pfSense 2.1 up and working on a test box of spare parts and after that i decided to move it to smaller/faster hardware. to that end i bought and installed  http://www.newegg.com/Product/Product.aspx?Item=N82E16813128598
    it does not pick up the lan ports on 2.0.3 which is fine, i knew going in i would have to use 2.1.

    I installed 2.1 noted it did not pull a wan ip but the lan seemed to work and recovered the last profile. had to correct the wan/lan port assignments, could not get the wan to configure. it would either show no ip or 0.0.0.0 from checking the router with another device it had an IP right away. I thought must be the config rolled back to factory defualts. no IP for wan both web and console.

    at this point i did a reinstall from the cd, pulled a wan connected to the lan, was able to connect and update the image. started configuring, installing packages. backed up settings…. at this point i lost power my ups's kicked in and i ran it till the ups had 5 min left shut it down. when it came back up after power restore no wan ip listed, tried form console ifconfig xxx down then up did not help. rebooted same. checked with another device was on right away.

    thought it might be the lan ports both being on the mobo, added a spare old netgear 10/100 pci card i had laying around, reinstalled made it the wan, same issue. no wan ip. swapped cables. rebooted no wan ip. shutdown removed the netgear nic

    swapped ports made the re1 the wan and not the re0, pulled an IP could get on, recovered  by section this time not all of it. rebooted as had too, no ip for the wan. reset to factory again. no ip,

    look at the wan look at the gateway shows pending, check the wan out from the web gui was going to swap ports from the gui, noted that the interface status showed an IP for the wan but console and the web gui dashboard do not, and the gateway shows pending, renew IP from web gui, shows it pulls an IP but the gateway stays pending and the console does not show the ip, cannot ping out from the console or from web gui.

    reboot same thing. think i must have screwed up a config so revert to factory one more time. now pulls an ip for wan and gives out ip addresses on the lan can ping from console on the box the web, but cannot connect to the web gui or browse the web from the lan side, cannot ping out from lan side. take the lan port up and down. does not help, set dns and IP on the computer connected to lan, does not help. set gateway for computer on lan does not help. set the interface for the lan again on the router, says its set, gives my device an IP cannot connect to router from lan try to ssh to device from lan cannot. reboot, same.

    reinstall from CD again, same issue as above now pulls IP and can ping from router, but lan despite handing out IP addresses does not seem to work....

    any ideas?

    im going to take a bit of a break and roll back to a spare netgear router for a bit and take my mind off it.... if its the hardware, its a shame

    edit... i would have already taken it as a  write off if it had not worked ever so briefly twice both times unconfigured... the older test hardware works. its an lga 775 board using two intel nics, did a clean test on it, had no issues setting it back up



  • What is your WAN interface type - PPPoE or DHCP?

    What is the WAN interface connected to?

    The appropriate pfSense system log entries could give some clues about what is going on. A packet capture on the wan interface would also help.

    Some cable modems need a cold reset if the MAC address of the downstream system changes.



  • DHCP, i also tried setting as static after pulling the info from the cable modem. normally comcast leaves me with the same IP for a few months

    WAN is connected to a Motorola SB6120 surfboard.

    I had tried rebooting the modem leaving it unplugged for about 10 min from everything, i also tried spoofing known good MACs

    Ill work on getting the log providing i can get the lan working again, in the short term, i am moving the wan off of a switch  and will try to turn on access to the web gui through the wan from the console then get the logs

    edit

    I was able to login to the webgui by setting the ip for the network to 192.168.2.1, but after logging in as defualt any page i went to outside the dashboard would not load, tried re-laoding the webconfigurator, but after that reloaded wan and lan dropped their IP… frustration



  • @hansrotec:

    I was able to login to the webgui by setting the ip for the network to 192.168.2.1,

    I presume you mean you set the IP address for an INTERFACE. Which interface?

    @hansrotec:

    but after logging in as defualt any page i went to outside the dashboard would not load,

    which page? what did the browser report (if anything)? There is a known problem with a page related to PPP - the web server stalls before downloading the page.

    @hansrotec:

    tried re-laoding the webconfigurator, but after that reloaded wan and lan dropped their IP… frustration

    What do you mean by "reloaded WAN" … ? Do you mean you rebooted and both pfSense LAN and WAN interfaces were reported by the console startup without an IP address?



  • @wallabybob:

    @hansrotec:

    I was able to login to the webgui by setting the ip for the network to 192.168.2.1,

    I presume you mean you set the IP address for an INTERFACE. Which interface?

    @hansrotec:

    but after logging in as defualt any page i went to outside the dashboard would not load,

    which page? what did the browser report (if anything)? There is a known problem with a page related to PPP - the web server stalls before downloading the page.

    @hansrotec:

    tried re-laoding the webconfigurator, but after that reloaded wan and lan dropped their IP… frustration

    What do you mean by "reloaded WAN" … ? Do you mean you rebooted and both pfSense LAN and WAN interfaces were reported by the console startup without an IP address?

    set the ip for the local network and interface, or at lest im pretty sure thats what i did.

    any page other than the login page and the dashboard, would not load 404 or 500 errors -

    to clarify on the wan, used ifconfig down and up,

    i worked on it for about another 3 hours trying vairous things, could never get both wan and lan to work at the same time, the macs for the integrated nics are different but only by one number  a 2 vs a 6.

    for now i have rolled back to the test tower, which following the same steps was set up and working in under 5 min … its got to be something about either the lan ports or the chipset. ill repurpose the board for something else its just a bit of a pain, new rule for myself intel NICs only and make sure they are in BSD  thinking of trying a http://www.amazon.com/computers-accessories/dp/B00840BAIE  .... it seems to have gone up in price since i last looked.

    I would stay on the test hardware if i could but the MB has issues on reboots about 1/3 the time. thats why it was laying around for me to test with.

    edit - i really think the NM70 chipset is the issue, seems to have  caused problems for people using atom upon looking into it further

    thanks for the help these forums are always quite helpful I hope to be the one helping someday.



  • Nice!

    Thanks for your post, I hope you find this information. I also have a GA-C1007UN-D board. Using yours, and another's post (http://forum.pfsense.org/index.php?topic=49445.0)  I have been able to make it work. It turns out what is screwing this board up is IPV6.
    In order to get a WAN, I had to ifdown and then ifup the WAN interface. After that, under general settings, completely disable IPV6, and everything should be dandy! Cheers!



  • Nope. I still have to manuall bring the WAN IF down then back up to reset it. This board is garbage.



  • I currently have this board working:

    In /etc/rc.conf add

    ipv6_enable="NO"



  • I have this board as well.  I initially had this issue with the 64bit version, but when I reinstalled with the 32bit version I got a dhcp address on my wan link right away.  I did not have to change any ip v6 settings.