Re: Compiling netmap in Ubuntu 1.04 in VMWare
Hi Mahnaz, This is my kernel: 3.13.0-29-generic I don't know if this path contains the drivers that supported by my kernel: /lib/modules/3.13.0-29-generic/kernel/drivers/net/ethernet/intel/ These are what in side that path: e1000 e1000e e100.c e100.ko i40e i40evf igb igbvf ixgb ixgbe ixgbevf Kconfig Makefile In the patches directory, I found these: e1000 e1000e igb ixgbe So I guess my kernel has the drivers supported by netmap. Also, I forgot to include the error when I run the make command. Here it is: make -C /lib/modules/3.13.0-29-generic/build M=/home/kl/Workspaces/netmap/LINUX CONFIG_NETMAP=m CONFIG_E1000=m CONFIG_E1000E=m CONFIG_IXGBE=m CONFIG_IGB=m CONFIG_BNX2X=m CONFIG_MLX4=m CONFIG_VIRTIO_NET=m \ EXTRA_CFLAGS='-I/home/kl/Workspaces/netmap/LINUX -I/home/kl/Workspaces/netmap/LINUX/../sys -I/home/kl/Workspaces/netmap/LINUX/../sys/dev -DCONFIG_NETMAP -Wno-unused-but-set-variable' \ O_DRIVERS=e1000/ e1000e/ igb/ ixgbe/ modules make[1]: Entering directory `/usr/src/linux-headers-3.13.0-29-generic' *make[3]: *** No rule to make target `/home/kl/Workspaces/netmap/LINUX/e1000/e1000_main.o', needed by `/home/kl/Workspaces/netmap/LINUX/e1000/e1000.o'. Stop.make[2]: *** [/home/kl/Workspaces/netmap/LINUX/e1000] Error 2make[1]: *** [_module_/home/kl/Workspaces/netmap/LINUX] Error 2make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-29-generic'make: *** [build] Error 2* The thing is my laptop has intel card, but I don't know if my VM (I am using VMWare) has that card. Right now, I create four NICs for my VM: host only, bridge to my host's ethernet, bridge to my wireless card, and two other private NICs that connect privately within different VMs. Do you think that is the problem VM, not netmap itself? Thank you, *Long Tran* Research Assistant MS in Network Communications and Technology Project Management University of Houston On Mon, Sep 29, 2014 at 12:07 AM, Mahnaz Talebi mhnz.tal...@gmail.com wrote: What is your kernel? Are you check list of supported drivers to see if your kernel's drivers are supported whit the your version of netmap? Supported drivers are in folder patch and their name show their supported kernels. On Sun, Sep 28, 2014 at 10:02 PM, Long Tran kyle.longt...@gmail.com wrote: Hi Mahnaz, I installed the headers and sources using these commands: sudo apt-get install linux-headers-3.13.0-29 sudo apt-get install linux-source-3.13.0 Thanks, -- *Long Tran* Research Assistant MS in Network Communications and Technology Project Management University of Houston ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
[FreeBSD Bugzilla] Commit Needs MFC
Hi, You have a bug in the Needs MFC state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by ead...@freebsd.org. (1 bugs) Bug 183659: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183659 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-net@FreeBSD.org Status: Needs MFC Resolution: Summary: [tcp] TCP stack lock contention with short-lived connections ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967 Jeroen van Heugten vanheug...@gmail.com changed: What|Removed |Added CC||vanheug...@gmail.com --- Comment #12 from Jeroen van Heugten vanheug...@gmail.com --- Created attachment 147795 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147795action=edit Output of ifconfig -a -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967
--- Comment #13 from Jeroen van Heugten vanheug...@gmail.com ---
We are facing the same problem, running FreeBSD 10.0-p9, connected with LACP to
two Juniper EX4550 switches (virtual-chassis/stacked). In our case the Junipers
are already in active mode, but we still have issues with the connection. We
are experiencing lots of outages (every few mins).
dmesg shows (on -multiple- FreeBSD servers:
ix1: Interface stopped DISTRIBUTING, possible flapping
ix1: Interface stopped DISTRIBUTING, possible flapping
ix1: Interface stopped DISTRIBUTING, possible flapping
Juniper configuration:
ae21 {
description serverX (xe-0/0/17 en xe-1/0/17);
aggregated-ether-options {
link-speed 10g;
lacp {
active;
periodic fast;
}
}
unit 0 {
family ethernet-switching {
port-mode access;
vlan {
members S1_SERVERS;
}
}
}
}
- attached output of ifconfig -a
- attached output of /etc/rc.conf
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
[Bug 185967] [lagg] [patch] Link Aggregation LAGG: LACP not working in 10.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967 --- Comment #14 from Jeroen van Heugten vanheug...@gmail.com --- Created attachment 147796 -- https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147796action=edit LACP settings in /etc/rc.conf -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Choice of private ioctl approach
Hello, we need to add private ioctl to the driver sfxge(4) to make FW update, do internal diagnostics commands etc. We see at least two approaches in other drivers: 1. SIOCGPRIVATE_0/ SIOCGPRIVATE_1 on net device 2. dedicated char device with its own ioctl's Is there any recommendations on which way is preferred? Thanks, Andrew. The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error, please notify the sender immediately and delete the message. Unless you are an addressee (or authorized to receive for an addressee), you may not use, copy or disclose to anyone this message or any information contained in this message. The unauthorized use, disclosure, copying or alteration of this message is strictly prohibited. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
pf stuck
Hello. Today a box of mine (8.4p16/amd64) stopped working as a router; I don't have a clear picture, but the internal nets were working perfectly, while the external interfaces lagged, dropped connections or stopped packets from passing. The box is running pf (for handling multiple Internet lines) + ipfw (for firewalling). I tried a simple telnet xxx:80 and this is what I observed: _ tcpdump would see packets going out and replies coming in; _ an early ipfw allow rule with setup keep-state would see no packet going out and would not create any dinamic rule. This lead me to look into pf... /etc/rc.d/pf restart did not solve. /etc/rc.d/pf stop ; /etc/rc.d/pf start did! These are my pf rules: pass out quick inet from 192.168.x.0/24 to 192.168.y.0/24 no state pass out quick inet from 192.168.x.0/24 to 192.168.z.0/24 no state pass out log quick route-to (vlan3 192.168.x.x) inet from 192.168.x.0/24 to ! 192.168.x.0/24 no state pass out quick inet from a.b.c.d/29 to 192.168.y.0/24 no state pass out quick inet from a.b.c.d/29 to 192.168.z.0/24 no state pass out log quick route-to (vlan1 a.b.c.e) inet from a.b.c.d/29 to ! a.b.c.d/29 no state pass out quick inet from i.j.k.l/29 to 192.168.z.0/24 no state pass out quick inet from i.j.k.l/29 to 192.168.z.0/24 no state pass out log quick route-to (vlan2 i.j.k.m) inet from i.j.k.l/29 to ! i.j.k.l/29 no state These rules are working fine, but have hanged already twice in two weeks (once on this box, once on an almost identical one). Is there any known problem wrt running pf? pf+ipfw? pf on 8.4? Any hint on how to search for what's wrong? bye Thanks av. P.S. Please, forgive me, but I'm quite noob with pf. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
igb update - 2.4.0 - 2.4.2
Jack/ Eric, When do you guys plan to bring this in the tree? https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=15815 cheers, Hiren ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: pf stuck
Probably is better you ask this on freebsd-pf@. Though this sounds like state limit reached. On Mon, Sep 29, 2014 at 7:32 PM, Andrea Venturoli m...@netfence.it wrote: Hello. Today a box of mine (8.4p16/amd64) stopped working as a router; I don't have a clear picture, but the internal nets were working perfectly, while the external interfaces lagged, dropped connections or stopped packets from passing. The box is running pf (for handling multiple Internet lines) + ipfw (for firewalling). I tried a simple telnet xxx:80 and this is what I observed: _ tcpdump would see packets going out and replies coming in; _ an early ipfw allow rule with setup keep-state would see no packet going out and would not create any dinamic rule. This lead me to look into pf... /etc/rc.d/pf restart did not solve. /etc/rc.d/pf stop ; /etc/rc.d/pf start did! These are my pf rules: pass out quick inet from 192.168.x.0/24 to 192.168.y.0/24 no state pass out quick inet from 192.168.x.0/24 to 192.168.z.0/24 no state pass out log quick route-to (vlan3 192.168.x.x) inet from 192.168.x.0/24 to ! 192.168.x.0/24 no state pass out quick inet from a.b.c.d/29 to 192.168.y.0/24 no state pass out quick inet from a.b.c.d/29 to 192.168.z.0/24 no state pass out log quick route-to (vlan1 a.b.c.e) inet from a.b.c.d/29 to ! a.b.c.d/29 no state pass out quick inet from i.j.k.l/29 to 192.168.z.0/24 no state pass out quick inet from i.j.k.l/29 to 192.168.z.0/24 no state pass out log quick route-to (vlan2 i.j.k.m) inet from i.j.k.l/29 to ! i.j.k.l/29 no state These rules are working fine, but have hanged already twice in two weeks (once on this box, once on an almost identical one). Is there any known problem wrt running pf? pf+ipfw? pf on 8.4? Any hint on how to search for what's wrong? bye Thanks av. P.S. Please, forgive me, but I'm quite noob with pf. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org -- Ermal ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: pf stuck
On 09/29/14 20:21, Ermal Luçi wrote: Probably is better you ask this on freebsd-pf@. Thanks, I see you have already cc:ed it. Though this sounds like state limit reached. Can this happen even if all my pf rules have no state? bye Thanks av. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: vlan id 0
Ok.. Can someone please submit a PR with a patch that addresses this? I'll try to make sure it gets into freebsd-head. -a On 27 September 2014 18:24, Danny J. Mitzel mit...@acm.org wrote: On Sat, Sep 27, 2014 at 4:44 PM, Adrian Chadd wrote: .. the spec allows vlan id=0? 0 is not a valid VLAN ID but the specs do allow it in a tagged packet, it's called Priority tagged. The priority bits should be interpreted when making any queuing / scheduling decisions during forwarding. The VLAN ID bits are ignored and packet is to be treated as untagged during forwarding / flooding decisions. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: Success with Qualcomm Atheros QCA8171
On Thu, Sep 25, 2014 at 11:44:24AM +0200, Nils Beyer wrote: Hi Gulyaev, Gulyaev Ghosh wrote: Since I ask on the FreeBSD forums, there is a proposition to check alx-freebsd and have initialized interface. So if someone have similar hardware, you can got your experience with that project and share info. I've got an onboard AR8161 Gigabit Ethernet adapter. With your proposed GIT- repository and using its branch master I'm able to rudimentarily use the NIC. But only if the network cable is short ( 2m). Using longer cables gives me a no carrier status. When it is connected, speed is abysmal and functio- nality ceases as soon as I perform an iperf benchmark until I reboot. FYI: I've completed adding AR816x/AR817x support . You can find diff at the following URLs. http://people.freebsd.org/~yongari/alc/pci.quirk.diff http://people.freebsd.org/~yongari/alc/alc.diff.20140930 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
Re: Compiling netmap in Ubuntu 1.04 in VMWare
Hi Mahnaz, Thank you. I just got it worked without drivers. Could you please explain how netmap can be used without drivers? I thought it required the NIC's driver to run. Thanks, Long. *Long Tran* Research Assistant MS in Network Communications and Technology Project Management University of Houston On Mon, Sep 29, 2014 at 2:04 AM, Mahnaz Talebi mhnz.tal...@gmail.com wrote: I guess that all of your NICs use e1000 driver. You can check out this by 'lsmod | grep e1000'. I have been faced this problem that arising from incompatibility between netmap and your kernel. I guess that netmap doesn't support your kernel. About patches: for example, diff--e1000e--20620--20623 support kernel 2.6.20 to 2.6.23. I use ubunto 12.4 and upgrade its kernel to 3.8.7 and can install and use netmap successfully. You can install netmap without drivers by 'make NODRIVERS=1'. On Mon, Sep 29, 2014 at 10:13 AM, Long Tran kyle.longt...@gmail.com wrote: Hi Mahnaz, This is my kernel: 3.13.0-29-generic I don't know if this path contains the drivers that supported by my kernel: /lib/modules/3.13.0-29-generic/kernel/drivers/net/ethernet/intel/ These are what in side that path: e1000 e1000e e100.c e100.ko i40e i40evf igb igbvf ixgb ixgbe ixgbevf Kconfig Makefile In the patches directory, I found these: e1000 e1000e igb ixgbe So I guess my kernel has the drivers supported by netmap. Also, I forgot to include the error when I run the make command. Here it is: make -C /lib/modules/3.13.0-29-generic/build M=/home/kl/Workspaces/netmap/LINUX CONFIG_NETMAP=m CONFIG_E1000=m CONFIG_E1000E=m CONFIG_IXGBE=m CONFIG_IGB=m CONFIG_BNX2X=m CONFIG_MLX4=m CONFIG_VIRTIO_NET=m \ EXTRA_CFLAGS='-I/home/kl/Workspaces/netmap/LINUX -I/home/kl/Workspaces/netmap/LINUX/../sys -I/home/kl/Workspaces/netmap/LINUX/../sys/dev -DCONFIG_NETMAP -Wno-unused-but-set-variable' \ O_DRIVERS=e1000/ e1000e/ igb/ ixgbe/ modules make[1]: Entering directory `/usr/src/linux-headers-3.13.0-29-generic' *make[3]: *** No rule to make target `/home/kl/Workspaces/netmap/LINUX/e1000/e1000_main.o', needed by `/home/kl/Workspaces/netmap/LINUX/e1000/e1000.o'. Stop.make[2]: *** [/home/kl/Workspaces/netmap/LINUX/e1000] Error 2make[1]: *** [_module_/home/kl/Workspaces/netmap/LINUX] Error 2make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-29-generic'make: *** [build] Error 2* The thing is my laptop has intel card, but I don't know if my VM (I am using VMWare) has that card. Right now, I create four NICs for my VM: host only, bridge to my host's ethernet, bridge to my wireless card, and two other private NICs that connect privately within different VMs. Do you think that is the problem VM, not netmap itself? Thank you, *Long Tran* Research Assistant MS in Network Communications and Technology Project Management University of Houston On Mon, Sep 29, 2014 at 12:07 AM, Mahnaz Talebi mhnz.tal...@gmail.com wrote: What is your kernel? Are you check list of supported drivers to see if your kernel's drivers are supported whit the your version of netmap? Supported drivers are in folder patch and their name show their supported kernels. On Sun, Sep 28, 2014 at 10:02 PM, Long Tran kyle.longt...@gmail.com wrote: Hi Mahnaz, I installed the headers and sources using these commands: sudo apt-get install linux-headers-3.13.0-29 sudo apt-get install linux-source-3.13.0 Thanks, -- *Long Tran* Research Assistant MS in Network Communications and Technology Project Management University of Houston ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org
