Making my Znyx ZX346Q nic to work
-
i do not know the history of the card, i got it of ebay, but i currently have 2 of the same cards and i'm having the same issue with both of them, i do not think i have bad cables, since i made them and tested them (i am a sound n com tech/low volt electrician, so at the very least i know how to make a patch cord or a crossover cable) also i did try different ports on the card.
as for the error messages, the only thing i can see that happens is this:acd0: FAILURE - READ_BIG ILLEGAL REQUEST ASC=0X64 ASCQ = 0X00
that error shows up multiple times in a row
there is also a ZFS WARNING about a recommended minimum kmem size.
as for doing anything manually, i do not even know where to begin. I only know how to set the interfaces manually but not how to set them up.
I appreciate the help.
-
Neither of those warnings are a problem. acd0 is the cd-rom drive which I presume is empty and you are booting from hard disk? ZFS is not used unless you have specially chosen to use it in a custom install (you haven't!).
Ok. So first off you need to prove the hardware. Start by proving your cables especially if you've just made them up for this. If you don't have a cable tester I usually use two devices such as a switch and an access point or two switches.
You should probably also prove the network card operates OK under a different OS. Stick it in a Windows box or boot the pfSense box from a live Linux CD.Once both of those are proved try setting both ends of the connection to 100Mbps full duplex. Importantly you MUST set BOTH ends. If you leave one end set to auto-negotiation it will fail (because the other end is set to manual) and then fall back to default setting, usually 10Mbps half duplex.
Steve
-
i can go ahead n prove that both the cables and the card works in a few min, my concern will be is how do i set both ends to 100mbps full duplex. I would not know how to do so manually
also would this affect my other machine (mac pro) and another thing, at this point im at a loss, do i have to use a crossover cable, or straight through would work? pfsense nic is a 10/100 base and my workstation is 1gbit port.
ill get back in a bit after i see if i can get the 4 port nic to work on my workstation.
EDIT: additional information.
I threw the network card in to my widows machine, as I suspected, it recognizes that it is there but can not find drivers for it, i looked around on the webs, i seem to can not find anything suitable.
-
Maybe try a live Linux CD then to prove the card.
The gigabit NIC in your workstation should take care of the cross-over/straight through selection for you, all gigabit NICs are auto-MDX.
Assume you have dc0 assigned as the LAN interface in pfSense. Go to Interfaces: LAN: in the webgui and next to 'speed and duplex' hit the advanced button. Now from the drop down select '100baseTX full duplex'. Save and apply.
In the Windows workstation the setting is in the network card properties.
Steve
-
Live Linux CD? never done that before, will have to look it up, never used linux before either. as for web gui, well i cant access that, unless i can do so through pfsense box… will have to look at that as well.
This is turning out pretty interesting though, a crush course on different OS'
Also... any particular linux build i should look for? or would any work? and then, if i do use live linux cd, what am i looking for? how do i check the NIC basically.
its seems at this point that it might be easier for me to shell out $100 and get an inter card instead, i might as well do so, i kinda want to see if i can make it work, if only to replace is as soon as i get a new card. or that way ill be able to have 8 ports (not that i would ever need that many).
-
Hmm, that card is older than I thought, Windows drivers are only available for Windows 2000 or NT4. However there is this patch tool which might be a clue:
http://docs.znyx.com/support/drivers/driverdocs/dc012501.pdf
The Win 2K driver might run in WinXP if you still have that.For a live Linux CD just download the latest Ubuntu iso and write it. Boot it and choose 'try Ubuntu' and it will boot to a complete desktop. From there you can test the card and view the logs etc.
Steve
-
Assuming that the card and the cables are fine, how would i make a manual selection on pfsense box to choose 100base full duplex speed? its easy on the windows machine but i have no idea how to do so on pfsense machine.
-
It's possible to do it from the command line:
ifconfig dc0 media 100baseTX mediaopt full-duplexThat setting will be overwritten whenever the box renews it's interfaces for whatever reason though so I suggest you set it via the webgui as I outlined above. If your LAN interface is assigned to fxp0 you should have no problems accessing the webgui.
Steve
-
Ok, I followed the directions on making my fxp0 a LAN connection and was able to acces web gui. There I was able to assign interfaces and was able to change the speed to 100base Base TX full duplex, which seemed to "work", at least now when i plug in to the nic it shows a sign of life, link light turns on and activity light blinks for few seconds. But I can not pass traffic through it and i can not access web gui (invalid IP address, i dont know what i am doing i assigned a 192.168.1.2 for dc0 interface and tried using that), im not sure how to assign my interfaces back or how to configure the rest of the ports to act as LAN interface. I kind of tried to copy the info from the interface that was automatically set, but I am facing an issue where my 192.168.1.1 address is taken and i can not assign it to other interfaces (im not sure what i am supposed to do though)
Basically i have a jumbled mess of interfaces my fxp0 is now LAN1 (mobo nic) and my dc3 is WAN, and I want WAN to be fxp0 and LAN1-4 to be dc0-3 (for simplicity sake) i'm just not sure how to work around the problem and configure interfaces properly. I am not even sure how to explain this. I am sorry if this sounds like nonsense, hopefully I can clear it up.
-
Aha! ;D
Ok well that's a huge step forward, everything else is standard configuration.
When you add a new interface in pfSense, like LAN2, it must be in a different subnet to any existing interfaces. So you could use 192.168.2.1/24. You can't use 192.168.1.2 because it's in the subnet used by LAN.
Secondly when you add new interfaces all traffic to it will be blocked by the firewall by default. The LAN interface comes with a default rule to allow traffic to make things easier but that is an exception.
Go to Firewall: Rules: LAN: in the webgui and look at the default LAN rule. Now go to Firewall: Rules: LAN2: and add similar rule there. If you want to allow all traffic it would be something like:
Protocol: IPv4 any
Source: LAN2 NET
Source port: any
Destination: any
Destination port: anyOnce you are familiar with setting the rules on the interfaces you can reassign the NICs in the order you wish either from the webgui or at the console.
Steve
-
hrmm… i was able to set up and copy the rules and assign the interfaces as i wanted, i do not get the connection or i cant get traffic to pass through the the lan ports, im not sure if im missing something in the rules, or somewhere else. frustrating. I been trying to see if anyone has any instructions on youtube, but all i get are advance settings for the stuff that already works and they are just showing how to finetune or implement other stufff...
i configured it as follows,
fxp - wan - it gets its own IPs from the modem.
dc0 - Lan1 - 192.168.1.1 its automatically set up (rulles and everything) - unable to connect to either internets or the webgui
dc1 - Lan2 - 192.168.2.20 tried to copy rules from Lan1 - no connection (it does have IPV6 assigned to it and so are others)
dc2 - etc.
dc3 - etc.so im not sure, and again i do get a link up lights on all 4 ports on the card...
-
Hmm. OK. So possibly the card is now talking correctly at the hardware level but the driver is not indicating a connection in some way. Can you get back to the webgui via the WAN? You can disable the firewall entirely to allow that using 'pfctl -d' at the console. Check the Status: Interfaces: page. Does it show a load of errors? Does it show a conection?
Are you using DHCP for the client machine on LAN1? Is it working?
Steve
-
i am able to access webgui if i assign fxp0 to lan.
Checking Status:Interfaces window shows 0/0 errors on all ports, all show 0/0 in out packets except dc0 (lan4) it shows in/out packets 112/133 (pass) no errors nothing. all show status 'no carrier', im not sure how to see if it show a connection.as for the DHCP, in the Interfaces:DHCP Leases it shows the IP 192.168.1.130 as online and active and it shows my workstations name. Keep in mind Lan1 is fxp0 port which is my mobo port that was originally known to work (machine was in working order when i started messing with pfsense)
I did run pfctl -d it shows pf disabled, ill try seeing if that changed anything.
I hope this gives you any ideas.
-
all show status 'no carrier', im not sure how to see if it show a connection.
Hmm, well that's not good. Did they have a physical connection when you were looking a this?
If you ssh in and run ifconfig at a the command line you can copy and paste that output here.What did you have connected to dc0 (lan4) that manged to send/receive some traffic?
I forgot earlier that none of the additional interfaces will have DHCP enabled unless you manually set it in Services: DHCP Server: so you would have to use static IP addresses.
Steve
-
well, ya, they had nothing pluged in, and dc0 (lan4) i have no idea i honestly dont think anything was. i believe i use statick IPs on all but Wan. If I remember right if i assign wan to any dc interfaces it wont work either, basically the only interface that does everything it should is fxp0 the one that is currently on a mobo. and would i run ssh from webgui? ill look at it in a bit and see if i can figure it out on my own.
and again i greatly appreciate all the help.
i am kind-off glad that i am running in to so many problems with it, i at least will know what to do in a future if it ever starts working.
-
well, ya, they had nothing pluged in
Ok, well connect a client and make sure they're both configured manually at 10/100. Check the output of ifconfig at the console for a change in the status. We already talked about cross-over cables.
To connect via SSH you have to enable it first in the webgui in System: Advanced: Admin access: then connect to it using an SSH client like putty.
Steve
-
ok so i realized that i never configured WAN port for a manual speed, i did change that. Sadly nothing changed, also i did run ifconfig and have an image of it maybe it can tell you anything.
another thing i do notice is that if i configure wan port to any of the dc0-3 interfaces the interface does not get an IP assigned to it (tried resetting the pfsense box and the modem, no result, or same result to be exact) and again, the physical RJ45 ports show link lights and activity lights when i plug in to them.
Would be nice if everything just worked.
-
O.k. so two things:
1. You have set the fxp port to 100MbpsFD manually and tht should really be left as autoselect unless you have a good reason not to.
2. The dc3 interface shows that the connection is 'active', it can see that a cable is attached. Since it doesn't have an IP assigned to it I assume you had that assigned as WAN when the screenshot was taken? Have you been able to set the modem interface to 100Mb-FD? If you check the Status: Interfaces: page does it show and packets or errors on dc3?If you plug other clients in the dc0-2 NICs do they receive IP addresses from pfSense?
Ultimately if you can't set the modem interface you will have to use the fxp NIC as WAN but obviously you can only do that once you can talk to one of the dc NICs.
Steve
-
the first part was done just to see if that would change anything, I will change the
fxp0 port to auto, since it works finethe second part, yes dc3 was set up as WAN I just picked the last port on the card, I did set all the interfaces for manual 100baseTX fd. In the status, interface window, there are some packets shown 221/33 (23kb/3kb) so minimal and no errors 0/0, that's after about 30 min of looking around.
as for plugin in to other interfaces, the webgui shows status as "up" but again, no real traffic through, minimal packets in and out…
(i plugged in my laptop to check that out)
as to weather or not they receive IPs, im not sure how to even check, i know that if i assign dc0 to 192.168.1.1 i cant get on to webgui through it, and in the end i do want fxp0 to be my WAN port, that is as soon as i can get the other 4 running -
If the NIC were in fact still completely inactive I would expect to see some packets going out but not any received.
If you have setup a dhcp server on dc0 at 192.168.4.20 and when you connect a client to it it receives an address then the NIC is working and the problem lies elsewhere.You definitely proved your cross-over cables with some thing else?
Steve
