ASROCK D2700B ITX + D-Link DFE-580TX (4 ports NIC) : ethernet port locks
-
Hello
I try to setup pfSense 2.01 but i meet some hardware problem (i think).
My hardware is :
ASROCK D2700B ITX bios rev 1.20 (Asrock page)
DLINK DFE-580TX rev 0x12. PCI 4 ports NIC. (Dlink page). This card is in the hw compatibility list.The main problem:
It seems there is inter action problem between NIC ports. Each time a port goes up others ports became locked.I setup LAN port ste1, address to 192.168.1.1/24
I setup WAN to port ste0 and pppoe
If ppoe is down i can reach webConfigurator on 192.168.1.1 address (pc have static address 192.168.1.120)
If i set WAN pppoe up using Status/Interface menu. I can not reach webConfigurator anymore.
I try change port (ie WAN ste3, LAN ste1) it is the same.I saw this topic about DFE-580TX problem but it's not the same (each port have an different address).
I have no idea of how solve that problem so i would like some help.
Many thanks by advance
and happy new year to the community :) !
-
Can you use the onboard Realtek NIC as the LAN interface? You might have to use 2.1Beta in order to have new enough drivers for it.
That way you may be able to access the box after the problem happens to look at the logs etc.
When the webGUI becomes unavailable are you still able to ping the box? SSH? Are you running it headless? Do you have console access?Steve
-
Hi Steve and thanks for your help.
Can you use the onboard Realtek NIC as the LAN interface? You might have to use 2.1Beta in order to have new enough drivers for it.
That way you may be able to access the box after the problem happens to look at the logs etc.Currently, i can access to the box using console but i am a newbie with BSD system, so it doesn't help.
Unfortunately internal NIC is not recognized by pfSense.
Ok i will try pfSense 2.1BetaWhen the webGUI becomes unavailable are you still able to ping the box? SSH? Are you running it headless? Do you have console access?
System seems to be Ok => console is running ok (i did not try ssh) and i can reset interfaces assignation/IP (no reboot). Then I can have access to webGUI.
-
@m3z:
System seems to be Ok => console is running ok (i did not try ssh) and i can reset interfaces assignation/IP (no reboot). Then I can have access to webGUI.
Ah that's interesting, it implies that assigning the new interface is causing the other interface to lose it's address settings.
Do you have some sort of subnet overlap perhaps? I.e. you have given the new interface an address that lies within the subnet of the original?Is it possible your WAN interface is coming up with a 192.168.1.* address via PPPoE? It would be very unusual.
You can access the system log from the console by using option 8 from the menu (shell) and then typing:
clog /var/log/system.logIf you need to see more of the log you can pipe the output to 'less' by typing:
clog /var/log/system.log | lessThen you can scroll through it with the cursor keys, press q to quit.
Though if you can just re-assign an interface to get access you can just look in the webgui at the log.
If there is some address conflict happening it should show in the logs.
Steve
-
Hello Steve,
I and thanks a lot. I fix the problem (well you do in fact ;).
The problem was that i setup LAN in 2 step because pfSense will replace and old ipcop router.1)First i have prepared new router. Lan interface is setup to a fix 192.168.0.28 ip without DHCP server (to avoid problem with old router).
2) Then new router took place of the old one. i halted the old router, setup lan interface to 192.168.0.1 and enable DHCP. and reboot.I don't know but the second setup failed (probably a mistake from myself) . The addess for LAN was 192.168.1.1.
Shame on me !
Thanks for your help again
Marc
-
Glad you got it fixed and thanks for following up. I came from IPCop myself. :)
Steve
