FreeBSD 11.1 with Intel(R) PRO/1000 unresponsive to all network interfaces from outside (seems, during idle), but immediately up when ping anything from inside the server
Hello guys, Need help with issues I never met before for my long experience with FreeBSD. A new server in remote DC based of Intel S1200RP with FreeBSD 11.1 uses igb driver for Intel(R) PRO/1000. There is no any load or traffic yet, I'm just configuring it, so I believe that my Kitty (Putty) session is the only one that makes traffic. I lost connection to the server dozens times during last week. I never lost connection when I was doing something on the server via remote Kitty terminal, but it was always when I return back to Kitty after some idle. Then, I kicked out of terminal and server doesn't response to pings or 'telnet port' from anywhere. The server has IPMI (and so KVM) and I now can see that the server is live and network interface is up. No messages in dmesg when this happens. The network goes up (i.e. pings go trough from outside) immediately after I ping something from inside the server (via IPMI's KVM access) or immediately after I execute netstat -r. I now run GENERIC to exclude any issue with my own kernel. The problem is 100% repeatable right now while I'm writing this: 1) leave Kitty terminal for a period of time (about 10 minutes enough) 2) come back to terminal, start typing, got kicked off, ping - no response 3) login to server via KVM (I'm already logged in) and ping any URL from there 4) server is responsive again I run continuous ping to this server last nigh and it never dropped. It looks to me like Intel card goes to some sleep mode during idle (when no traffic comes to the server at all, except Kitty's keep-alive perhaps). This is my first experience with FreeBSD 11.1 and ZFS (include root from ZFS). All my previous servers are on FreeBSD 9 and UFS, but not the first with Intel cards. Not sure if filesystem matter in this issue. I tried some things described here https://forums.freebsd.org/threads/workaround-freebsd-10-1-sudden-network-down.49264/ - it doesn't help. What else information do you need to debug this? ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FreeBSD 11.1 with Intel(R) PRO/1000 unresponsive to all network interfaces from outside (seems, during idle), but immediately up when ping anything from inside the server
25.03.2018 17:38, supportsobaka--- via freebsd-net wrote: > Hello guys, > Need help with issues I never met before for my long experience with FreeBSD. > > A new server in remote DC based of Intel S1200RP with FreeBSD 11.1 uses igb > driver for Intel(R) PRO/1000. There is no any load or traffic yet, I'm just > configuring it, so I believe that my Kitty (Putty) session is the only one > that makes traffic. I lost connection to the server dozens times during last > week. > > I never lost connection when I was doing something on the server via remote > Kitty terminal, but it was always when I return back to Kitty after some > idle. Then, I kicked out of terminal and server doesn't response to pings or > 'telnet port' from anywhere. > > The server has IPMI (and so KVM) and I now can see that the server is live > and network interface is up. No messages in dmesg when this happens. The > network goes up (i.e. pings go trough from outside) immediately after I ping > something from inside the server (via IPMI's KVM access) or immediately after > I execute netstat -r. > > I now run GENERIC to exclude any issue with my own kernel. > > The problem is 100% repeatable right now while I'm writing this: > > 1) leave Kitty terminal for a period of time (about 10 minutes enough) > 2) come back to terminal, start typing, got kicked off, ping - no response > 3) login to server via KVM (I'm already logged in) and ping any URL from there > 4) server is responsive again > > I run continuous ping to this server last nigh and it never dropped. It looks > to me like Intel card goes to some sleep mode during idle (when no traffic > comes to the server at all, except Kitty's keep-alive perhaps). > > This is my first experience with FreeBSD 11.1 and ZFS (include root from > ZFS). All my previous servers are on FreeBSD 9 and UFS, but not the first > with Intel cards. Not sure if filesystem matter in this issue. > > I tried some things described here > https://forums.freebsd.org/threads/workaround-freebsd-10-1-sudden-network-down.49264/ >- it doesn't help. > > What else information do you need to debug this? It might be that network of your DC provider has famous bug: sometimes its MAC/ARP cache expires MAC address of your machine and does not re-ask it using ARP protocol nor delivers a packet to the server. When you run ping or netstat -r you make some outgoing traffic (ICMP for ping and DNS for netstat) so you forcibly re-fill MAC/ARP caches of DC provider and now things come to normal for some time. There is an easy way to check if this is the case. You can change sysctl net.link.ether.inet.max_age parameter to some low value like 60 (seconds), so your own ARP cache for gateway's MAC address would expire often producing outgoing ARP request that re-fills caches of DC provider too, before it expires. If this helps - use it as workaround and bug DC provider. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Calling nxge(4) users
The nxge(4) driver for the Neterion Xframe-I and Xframe-II 10GbE adapters has obvious bugs (by inspection) and it doesn't appear the company exists any more. We'd like to see if there are any significant users of this device and plan to remove it from FreeBSD-12 if not. -- Brooks signature.asc Description: PGP signature
Re: Calling nxge(4) users
On Sun, Mar 25, 2018 at 11:40 AM, Brooks Davis wrote: > The nxge(4) driver for the Neterion Xframe-I and Xframe-II 10GbE > adapters has obvious bugs (by inspection) and it doesn't appear the > company exists any more. We'd like to see if there are any significant > users of this device and plan to remove it from FreeBSD-12 if not. > > -- Brooks > Just for the record, Neterion was acquired by Exar, an old-line hybrid IC company in 2010 and Exar was acquired last year by MaxLinear. Looks like Exar bought them for some of their tech and killed off the Ethernet products. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Calling nxge(4) users
> The nxge(4) driver for the Neterion Xframe-I and Xframe-II 10GbE > adapters has obvious bugs (by inspection) and it doesn't appear the > company exists any more. We'd like to see if there are any significant > users of this device and plan to remove it from FreeBSD-12 if not. > > -- Brooks Neterion has been acquired by exar. https://www.eetimes.com/document.asp?doc_id=1173009 They have the datasheet for the Xframe-I here: https://www.exar.com/ds/xframedatasheet.pdf The cards appear to be readily avaliable on ebay. -- Rod Grimes rgri...@freebsd.org ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Problem reports for freebsd-net@FreeBSD.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- In Progress |165622 | [ndis][panic][patch] Unregistered use of FPU in k In Progress |206581 | bxe_ioctl_nvram handler is faulty In Progress |221146 | [ixgbe] Problem with second laggport New |204438 | setsockopt() handling of kern.ipc.maxsockbuf limi New |205592 | TCP processing in IPSec causes kernel panic New |206053 | kqueue support code of netmap causes panic New |209682 | [panic] [netinet] arptimer race New |213410 | [carp] service netif restart causes hang only whe New |217748 | sys/dev/ixgbe/if_ix.c: PVS-Studio: Assignment to Open|193452 | Dell PowerEdge 210 II -- Kernel panic bce (broadc Open|194485 | Userland cannot add IPv6 prefix routes Open|194515 | Fatal Trap 12 Kernel with vimage Open|202510 | [CARP] advertisements sourced from CARP IP cause Open|206544 | sendmsg(2) (sendto(2) too?) can fail with EINVAL; Open|211962 | bxe driver queue soft hangs and flooding tx_soft_ Open|213814 | AWS/EC2: no egress traffic stats on ixv(4) Open|73 | igb(4): Kernel panic (fatal trap 12) due to netwo 17 problems total for which you should take action. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: FreeBSD 11.1 with Intel(R) PRO/1000 unresponsive to all network interfaces from outside (seems, during idle), but immediately up when ping anything from inside the server
26.03.2018 4:37, supportsob...@mail.ru wrote: > It doesn't help, unfortunately. The DC provides rescue system, both Linux and > FreeBSD 11.1. I booted to both today > and keep it idle for several hours and never get lost connection to the > server (never kicked out from terminal). > They also run GENERIC on FreeBSD 11.1. That's just fine. > They have sysctl net.link.ether.inet.max_age = 1200, so even higher than > default 600. No, default is 1200. > So the confuse now is what's the difference between their and mine FreeBSD > 11.1 that I didn't tune much yet. Firewalls disabled. > > Any idea? That's obviously your tuning then :-) Post it. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re[2]: FreeBSD 11.1 with Intel(R) PRO/1000 unresponsive to all network interfaces from outside (seems, during idle), but immediately up when ping anything from inside the server
I think so. I use a set of sysctl from my previous servers that work 5+ years flawlessly, I will set all to defaults to see if it helps and will be including one by one to see where it fails. >That's obviously your tuning then :-) Post it. > > ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
accf_http question
In my application I set SO_RECVTIMEO to 1.5 seconds, then enable SO_ACCEPTFILTER (httpready). accf_http module is loaded in the kernel. The problem is that if I connect to the socket but don’t send any data, the connection remains open indefinitely. The application of course won’t see a connection since the accept filter don’t see a complete http request. Why is this the case? Why doesn’t SO_RECVTIMEO affect the socket? How to close such connections early? Also, the documentation says: “The optional argument af_arg can be passed to the accept filter specified by af_name to provide additional configuration options at attach time.” I checked the code of accf_http.c, but from what I see – the “arg” value is not used anywhere, nor is there any indication as to what that value might be. Does anyone have any ideas? ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
