Intel NIC Failing weirdly[SOLVED]



  • Hi there,

    One of interface is acting weirdly. When i installed system nic was detected and it worked when used auto assign.
    In console i gaved ip address and in webgui take same settings as two another same kind of nics, and the another ones is working.

    The problem: when pc is connected to interface straight or via switch, pc gets ip address, mask and gateway, anything is right. but pc cannot connect to internet.
    And why i'm concerned of interface: lights aren't all green, but it looks like green+orange lid up same time.

    And before you're telling that i misconfigured trafic shaper that wasn't applied before testing.
    I took sysctl -a | grep dev.em.2 and here is output

    
    $ sysctl -a | grep dev.em.2
    dev.em.2.%desc: Intel(R) PRO/1000 Legacy Network Connection 1.0.3
    dev.em.2.%driver: em
    dev.em.2.%location: slot=6 function=0
    dev.em.2.%pnpinfo: vendor=0x8086 device=0x107c subvendor=0x8086 subdevice=0x1376 class=0x020000
    dev.em.2.%parent: pci4
    dev.em.2.nvm: -1
    dev.em.2.rx_int_delay: 0
    dev.em.2.tx_int_delay: 66
    dev.em.2.rx_abs_int_delay: 66
    dev.em.2.tx_abs_int_delay: 66
    dev.em.2.rx_processing_limit: 100
    dev.em.2.flow_control: 3
    dev.em.2.mbuf_alloc_fail: 0
    dev.em.2.cluster_alloc_fail: 0
    dev.em.2.dropped: 0
    dev.em.2.tx_dma_fail: 0
    dev.em.2.tx_desc_fail1: 0
    dev.em.2.tx_desc_fail2: 0
    dev.em.2.rx_overruns: 0
    dev.em.2.watchdog_timeouts: 0
    dev.em.2.device_control: 1480327745
    dev.em.2.rx_control: 32770
    dev.em.2.fc_high_water: 47104
    dev.em.2.fc_low_water: 45604
    dev.em.2.fifo_workaround: 0
    dev.em.2.fifo_reset: 0
    dev.em.2.txd_head: 129
    dev.em.2.txd_tail: 129
    dev.em.2.rxd_head: 39
    dev.em.2.rxd_tail: 38
    dev.em.2.mac_stats.excess_coll: 0
    dev.em.2.mac_stats.single_coll: 0
    dev.em.2.mac_stats.multiple_coll: 0
    dev.em.2.mac_stats.late_coll: 0
    dev.em.2.mac_stats.collision_count: 0
    dev.em.2.mac_stats.symbol_errors: 0
    dev.em.2.mac_stats.sequence_errors: 0
    dev.em.2.mac_stats.defer_count: 0
    dev.em.2.mac_stats.missed_packets: 0
    dev.em.2.mac_stats.recv_no_buff: 0
    dev.em.2.mac_stats.recv_undersize: 0
    dev.em.2.mac_stats.recv_fragmented: 0
    dev.em.2.mac_stats.recv_oversize: 0
    dev.em.2.mac_stats.recv_jabber: 0
    dev.em.2.mac_stats.recv_errs: 0
    dev.em.2.mac_stats.crc_errs: 0
    dev.em.2.mac_stats.alignment_errs: 0
    dev.em.2.mac_stats.coll_ext_errs: 0
    dev.em.2.mac_stats.xon_recvd: 0
    dev.em.2.mac_stats.xon_txd: 0
    dev.em.2.mac_stats.xoff_recvd: 0
    dev.em.2.mac_stats.xoff_txd: 0
    dev.em.2.mac_stats.total_pkts_recvd: 429606
    dev.em.2.mac_stats.good_pkts_recvd: 429606
    dev.em.2.mac_stats.bcast_pkts_recvd: 283
    dev.em.2.mac_stats.mcast_pkts_recvd: 0
    dev.em.2.mac_stats.rx_frames_64: 410919
    dev.em.2.mac_stats.rx_frames_65_127: 16258
    dev.em.2.mac_stats.rx_frames_128_255: 168
    dev.em.2.mac_stats.rx_frames_256_511: 641
    dev.em.2.mac_stats.rx_frames_512_1023: 1362
    dev.em.2.mac_stats.rx_frames_1024_1522: 258
    dev.em.2.mac_stats.good_octets_recvd: 28967674
    dev.em.2.mac_stats.good_octets_txd: 1257245145
    dev.em.2.mac_stats.total_pkts_txd: 838388
    dev.em.2.mac_stats.good_pkts_txd: 838388
    dev.em.2.mac_stats.bcast_pkts_txd: 11
    dev.em.2.mac_stats.mcast_pkts_txd: 0
    dev.em.2.mac_stats.tx_frames_64: 2225
    dev.em.2.mac_stats.tx_frames_65_127: 1337
    dev.em.2.mac_stats.tx_frames_128_255: 5657
    dev.em.2.mac_stats.tx_frames_256_511: 1151
    dev.em.2.mac_stats.tx_frames_512_1023: 1222
    dev.em.2.mac_stats.tx_frames_1024_1522: 826796
    dev.em.2.mac_stats.tso_txd: 0
    dev.em.2.mac_stats.tso_ctx_fail: 0
    
    

    EDIT: Problem was modem settings



  • I'm not clear what your problem is. Are you concerned that the LEDs on a NIC are not what you expect?

    What is the significance of the sysctl information on em2? I had a quick glance through that and didn't see anything that would suggest a malfunction - plenty of data exchanged and no errors reported.



  • Problem is that i have no internet connection from that interface. While visiting that interface's dhcp server page it announce that gateway is wrong(empty field like lan and opt2 also, and those work well)

    when checked from client machine ip-address information it has right ip,mask and gateway. but no internet access.

    And why i showed sysctl info, i don't know what you want to see so i gave some extra info.

    EDIT:
    Rules for that interface is currently allow anything from subnet to anything as attach shows




  • @Metu69salemi:

    Problem is that i have no internet connection from that interface.

    You have internet access from other interfaces on the same pfSense box?

    @Metu69salemi:

    While visiting that interface's dhcp server page it announce that gateway is wrong(empty field like lan and opt2 also, and those work well)

    Please post a screenshot of that page.

    Does the DHCP log (pfSense web GUI Status -> System logs, clck on the DHCP tab) show DHCP requests received and responses on em2? (If your client is really getting DHCP service from pfSense then its strange its not able to access the internet through pfSense.)

    When you ping the em2 IP address from a client on the em2 network what response do you get?



  • @wallabybob:

    You have internet access from other interfaces on the same pfSense box?

    Yes i do have, using it currently

    @wallabybob:

    Does the DHCP log (pfSense web GUI Status -> System logs, clck on the DHCP tab) show DHCP requests received and responses on em2? (If your client is really getting DHCP service from pfSense then its strange its not able to access the internet through pfSense.)

    I'll have to check that. it'll take some while

    @wallabybob:

    When you ping the em2 IP address from a client on the em2 network what response do you get?

    Normal response, i can ping that interface from another subnet, like you can see from screen shot #2

    Oh, there seems to be somekind brainfart from my side. dhcp log showed that it was em0 and not em2. Sorry for providing wrong info






  • @Metu69salemi:

    @wallabybob:

    When you ping the em2 IP address from a client on the em2 network what response do you get?

    Normal response, i can ping that interface from another subnet, like you can see from screen shot #2

    I don't care (for now) whether you can ping that interface from another subnet. What you have told me doesn't help diagnose why you can't access the internet from the em2 (or em0?) subnet.

    @Metu69salemi:

    Oh, there seems to be somekind brainfart from my side. dhcp log showed that it was em0 and not em2. Sorry for providing wrong info

    Showed what was em0? and does this discovery relate to your previous statement that the clients on the troublesome interface were getting DHCP service?

    The screenshot of the DHCP server page doesn't show a gateway so I guess you have a gateway for the relevant interface in System -> Routing, click on the Gateways tab and you should delete that gateway.



    1. I can ping from right subnet to 192.168.4.1 (pfsense address)
      1.1) Diagnose didn't change, what i stated to be em2 was em0
      1.2) Same kind of working still with dhcp, client get right ip,mask and gateway

    And removing gateway is something what i don't prefer to do right away. Because to other networks use that gateway with success



  • @Metu69salemi:

    And removing gateway is something what i don't prefer to do right away. Because to other networks use that gateway with success

    Well then you had better explain why that gateway is there. pfSense is telling you that DHCP is going to tell those clients that when they want to send something to a system that isn't on their subnet they should send it to a system that isn't on their subnet. They won't know how to do that unless you provide them with additional information.

    For ease of configuration DHCP clients should use a system on their own subnet as their default gateway. Why don't you want the DHCP clients to use the IP address of the relevant pfSense interface as their default gateway? It would probably help to provide a network diagram including interface IP addresses and network masks.



  • Yes i know how should dhcp and ip-addressing work, trust me(ccnp + ccna security).

    But problem is that another networks has same setup where gw info is empty and wangw is like name says wan side gateway.
    clients from 192.168.2.0/23 and 192.168.5.0/24 can access internet normally as i'm typing this message through sensebox.

    Internet - pfsensebox - LAN1 192.168.2.0 /23
                                    - LAN2 192.168.4.0 /24
                                    - LAN3 192.168.5.0 /24

    I'm having also 5 static ip-addresses with outbound nat for each of these networks. All of those ip's are in same subnet and that is the reason i use CARP-vips
    LAN1 - 83.#.#.153 <– this is also wan interface address
    LAN2 - 83.#.#.55
    LAN3 - 83.#.#.56
    OpenVPN - 83.#.#.61
    not in use currently - 83.#.#.75






  • I gitsynced pfsense, because it repaired dhcp error previously mentioned. thats ok but internet connectivity problem stays. I did some tests as previously asked todo. take a look of screenshots

    DHCP log says that computer has ip-address from dhcp server
    ping shows that ip-address is right one and it can ping pfsense box, not to outer world
    rule shows that there is nothing to block this action
    gateway shows that ip-address, subnet, gateway and dhcp server is all like it should be

    Is there something what i can do?










  • Its a puzzling problem.

    I suggest you start a ping (with a large count) from same client to 8.8.8.8 and do a packet capture on the pfSense interface (to verify the ping is actually getting to pfSense). If you see the ping coming in to pfSense then do a packet capture on the "output" interface to verify the pfSense routing. If you see the pings going out the correct interface then the problem is probably outside pfSense. Is there a ping response coming in from 8.8.8.8?

    Yesterday I discovered something I hadn't seen before and hadn't expected. I haven't had a chance to look into it yet. I have a  windows client on wired LAN which is bridged with wireless LAN. SCP attempts from Windows to Wireless LAN client timed out UNLESS I had a concurrent ping from the WLAN client to the windows system. I'm running 2.0-RC3-IPv6 (i386) built on Tue Jun 21 17:40:54 EDT 2011



  • I'll do this after my working hours. But i like to remind you that any part of this machine is brand new and thus i have warranty for every single piece of hardware. I just want to make sure that this interface is failing and nothing else.



  • @wallabybob:

    Its a puzzling problem.

    I suggest you start a ping (with a large count) from same client to 8.8.8.8 and do a packet capture on the pfSense interface (to verify the ping is actually getting to pfSense). If you see the ping coming in to pfSense then do a packet capture on the "output" interface to verify the pfSense routing. If you see the pings going out the correct interface then the problem is probably outside pfSense. Is there a ping response coming in from 8.8.8.8?

    This did the trick

    Packetcapture showed some details, every single ping left from the pfsense, but none returned. Intel nic is all ok. 8)
    I'm having telewell EA501 as modem and it was as default settings, ports 1&2 routing and ports 3&4 bridging. Modem had ip-address of .55 which was outbound nat of this verstas verkko which didn't work.

    Now this demonish modem is all bridging and not generating problems.
    @Wallabybob, thank you very much, needed your help and time.

    So in the end i can only say, my bad not hardware. And i never thought to this be pfsense's problem.


Log in to reply