Re: kern/144572: [carp] CARP preemption mode traffic partially goes to backup node
Synopsis: [carp] CARP preemption mode traffic partially goes to backup node State-Changed-From-To: open->closed State-Changed-By: glebius State-Changed-When: Mon Dec 19 08:28:54 UTC 2011 State-Changed-Why: Closed per submitters request. http://www.freebsd.org/cgi/query-pr.cgi?pr=144572 ___ 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: ng_mppc_decompress: too many (4094) packets dropped, disabling node
On 12/19/2011 8:59 AM, Sami Halabi wrote: i wonder how how other MPD users deal with problems like these since i don't think I'm the only only that facing this problem, i wonder if people actually use 8.2-R or maybe these stuck in 7-R Probably most people don't use MPPC. Perhaps you can turn off compression? as I understand the error is related to compression. Nikos ___ 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"
Current problem reports assigned to freebsd-net@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o kern/162927 net[tun] Modem-PPP error ppp[1538]: tun0: Phase: Clearing o kern/162926 net[ipfilter] Infinite loop in ipfilter with fragmented I o kern/162558 net[dummynet] [panic] seldom dummynet panics o kern/162509 net[re] [panic] Kernel panic may be related to if_re.c (r o kern/162352 net[patch] Enhancement: add SO_PROTO to socket.h o kern/162153 net[em] intel em driver 7.2.4 don't compile o kern/162110 net[igb] [panic] RELENG_9 panics on boot in IGB driver - o kern/162028 net[ixgbe] [patch] misplaced #endif in ixgbe.c o kern/161899 net[route] ntpd(8): Repeating RTM_MISS packets causing hi o kern/161381 net[re] RTL8169SC - re0: PHY write failed o kern/161277 net[em] [patch] BMC cannot receive IPMI traffic after loa o kern/160873 net[igb] igb(4) from HEAD fails to build on 7-STABLE o kern/160750 netIntel PRO/1000 connection breaks under load until rebo o kern/160693 net[gif] [em] Multicast packet are not passed from GIF0 t o kern/160420 net[msk] phy write timeout on HP 5310m o kern/160293 net[ieee80211] ppanic] kernel panic during network setup o kern/160206 net[gif] gifX stops working after a while (IPv6 tunnel) o kern/159817 net[udp] write UDPv4: No buffer space available (code=55) o kern/159795 net[tcp] excessive duplicate ACKs and TCP session freezes o kern/159629 net[ipsec] [panic] kernel panic with IPsec in transport m o kern/159621 net[tcp] [panic] panic: soabort: so_count o kern/159603 net[netinet] [patch] in_ifscrubprefix() - network route c o kern/159601 net[netinet] [patch] in_scrubprefix() - loopback route re o kern/159294 net[em] em watchdog timeouts o kern/159203 net[wpi] Intel 3945ABG Wireless LAN not support IBSS o kern/158930 net[bpf] BPF element leak in ifp->bpf_if->bif_dlist o kern/158726 net[ip6] [patch] ICMPv6 Router Announcement flooding limi o kern/158694 net[ix] [lagg] ix0 is not working within lagg(4) o kern/158665 net[ip6] [panic] kernel pagefault in in6_setscope() o kern/158635 net[em] TSO breaks BPF packet captures with em driver f kern/157802 net[dummynet] [panic] kernel panic in dummynet o kern/157785 netamd64 + jail + ipfw + natd = very slow outbound traffi o kern/157429 net[re] Realtek RTL8169 doesn't work with re(4) o kern/157418 net[em] em driver lockup during boot on Supermicro X9SCM- o kern/157410 net[ip6] IPv6 Router Advertisements Cause Excessive CPU U o kern/157287 net[re] [panic] INVARIANTS panic (Memory modified after f o kern/157209 net[ip6] [patch] locking error in rip6_input() (sys/netin o kern/157200 net[network.subr] [patch] stf(4) can not communicate betw o kern/157182 net[lagg] lagg interface not working together with epair o kern/156877 net[dummynet] [panic] dummynet move_pkt() null ptr derefe o kern/156667 net[em] em0 fails to init on CURRENT after March 17 o kern/156408 net[vlan] Routing failure when using VLANs vs. Physical e o kern/156328 net[icmp]: host can ping other subnet but no have IP from o kern/156317 net[ip6] Wrong order of IPv6 NS DAD/MLD Report o kern/156283 net[ip6] [patch] nd6_ns_input - rtalloc_mpath does not re o kern/156279 net[if_bridge][divert][ipfw] unable to correctly re-injec o kern/156226 net[lagg]: failover does not announce the failover to swi o kern/156030 net[ip6] [panic] Crash in nd6_dad_start() due to null ptr o kern/155772 netifconfig(8): ioctl (SIOCAIFADDR): File exists on direc o kern/155680 net[multicast] problems with multicast s kern/155642 net[request] Add driver for Realtek RTL8191SE/RTL8192SE W o kern/155604 net[flowtable] Flowtable excessively caches dest MAC addr o kern/155597 net[panic] Kernel panics with "sbdrop" message o kern/155420 net[vlan] adding vlan break existent vlan o kern/155177 net[route] [panic] Panic when inject routes in kernel o kern/155030 net[igb] igb(4) DEVICE_POLLING does not work with carp(4) o kern/155010 net[msk] ntfs-3g via iscsi using msk driver cause kernel o kern/154943 net[gif] ifconfig gifX create on existing gifX clears IP s kern/154851 net[request]: Port brcm80211 driver from Linux to FreeBSD o kern/154850 net[netgraph] [patch] ng_ether fails to name
Re: What is the relationship between Intel and FreeBSD in regards to igb(4)?
Kevin and Jack, thank you both for your replies. As you might have guessed, I was asking because I'm looking into buying a whole bunch of NIC's and I feel much more reassured now. Yet, there is one additional question, as I mentioned, I couldn't find much in src/sys/dev/igb, is the source for igb to be found elsewhere in the src? Happy Holidays! Tanel ___ 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: What is the relationship between Intel and FreeBSD in regards to igb(4)?
On Dec 19, 2011, at 12:01 PM, Tanel Rebane wrote: > Kevin and Jack, thank you both for your replies. As you might have guessed, > I was asking because I'm looking into buying a whole bunch of NIC's and I > feel much more reassured now. Yet, there is one additional question, as I > mentioned, I couldn't find much in src/sys/dev/igb, is the source for igb > to be found elsewhere in the src? They are in src/sys/dev/e1000/ Best regards Michael > > Happy Holidays! > Tanel > ___ > 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-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: What is the relationship between Intel and FreeBSD in regards to igb(4)?
On Dec 19, 2011, at 7:03 AM, Michael Tuexen wrote: > On Dec 19, 2011, at 12:01 PM, Tanel Rebane wrote: > >> Kevin and Jack, thank you both for your replies. As you might have guessed, >> I was asking because I'm looking into buying a whole bunch of NIC's and I >> feel much more reassured now. Yet, there is one additional question, as I >> mentioned, I couldn't find much in src/sys/dev/igb, is the source for igb >> to be found elsewhere in the src? > They are in > src/sys/dev/e1000/ > In case this is not clear, the sys/dev/e1000 folder contains three drivers: if_lem.c : legacy 1G cards if_em.c: older 1G cards if_igb.c: newer 1G cards The rest of the files are common code shared among the three drivers. -Andrew -- Andrew Boyerabo...@averesystems.com ___ 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 without ip address
On Dec 19, 2011, at 12:52 AM, saeedeh motlagh wrote: > you're right but we can't assign tow parent interface to one vlan in > freebsd therefore i define two vlans with the one vlan id. > although we can do it by blow command but it's not work too: > ifconfig gbeth0.10 create > ifconfig msk0.10 create > ifconfig > gbeth0.10: flags=8842 metric 0 mtu 1500 >options=3 >ether 00:27:0e:03:4b:2f >media: Ethernet autoselect (1000baseT ) >status: active >vlan: 10 parent interface: gbeth0 > msk0.10: flags=8842 metric 0 mtu 1500 >options=100 >ether 00:30:4f:63:5a:bc >media: Ethernet autoselect (none) >status: active >vlan: 10 parent interface: msk0 > > you know when i define vlans with ip addressess they work as i expected but > i want to know if i can define vlan without ip address as the switch > beacuse i wanna configure a freebsd box as a real switch in my network. > maybe it's impossible to do that :( Take a few minutes to think out (and describe to us in detail if you really want useful input) your network topology. What interfaces do you have on the FreeBSD machine and what are they connected to? Which interfaces should carry tagged traffic? Which interfaces should carry untagged traffic? How many VLAN's exist? Which ones does the FreeBSD machine care about? (i.e. which ones will it be tagging/untagging for?) Traffic for other VLAN's can pass through the box but you don't need to create VLAN interfaces for them. You need VLAN interfaces only for those VLAN's where: The FreeBSD box itself should communicate on one or more specific VLAN's (and/or provide services, etc) -OR- The FreeBSD box is sending/receiving untagged traffic on one or more interfaces and should untag/tag it as needed for other hosts. Once you've got that figured out, configure your bridges and VLANs as follows: Any physical interface that carries traffic for multiple VLAN's should be considered a "trunk" port. Traffic on trunk ports is tagged. If you only have one trunk port, it shouldn't be in a bridge at all. If you have more than one, all of your trunk ports should be members of a single bridge (the "real" parent interfaces). If you don't want the FreeBSD box to do any tagging/untagging then you're done. However it sounds like that is not the case.. Now create VLAN interfaces off of the trunk bridge (or interface if just one) for only those VLAN's this machine cares about. For each VLAN that should do tagging/untagging for a physical interface, create a NEW bridge device. Add to the bridge the untagged physical interface(s) and the appropriate VLAN interface from the trunk. If the FreeBSD box itself needs to communicate on one or more specific VLAN's, configure it to do so using the bridge device created for that VLAN (if any) or the appropriate VLAN sub-interface of the trunk bridge (if not shared with any untagged physical interfaces). In short, you should only have ONE trunk device, whether it's a bridge or a single interface. You don't need to create a VLAN interface for VLAN's this machine doesn't care about. ALL of the VLAN sub-interfaces you do create should be children of the trunk device. VLAN's that have untagged interfaces should be in their own bridges with those interfaces. HTH, JN > On Sun, Dec 18, 2011 at 10:52 PM, Alexander Lunev wrote: > >> first of all, you should name and number you vlan same, if it's clan10 >> on the one side, then it's vlan10 on the other side and in betweeen. >> then (though you have to do it first of all), you should understand >> how vlan's work, and after that connect ports to each other according >> to your scheme. >> >> >> -- >> your sweet isn't ready yet >> >> >> >> On Sun, Dec 18, 2011 at 10:01 AM, saeedeh motlagh >> wrote: >>> i have 3 freebsd system: 0.28 , 0.25 and 0.12 which 28 is assumed to be >>> switch here. one interface of 28 is connected to 25 and the other >> interface >>> of 28 is connected to 12. as mentioned below, i've defined two vlan10 and >>> 11 with the same vlan id on the 28 and bridge them. >>> now i can't ping 0.25 from 0.12. what's wrong here? should i define >> vlan10 >>> on 12 and 25? >>> please tell me if i'm misunderstanding. >>> this is the ifconfig for 0.28: >>> vlan10: flags=8943 >> metric 0 >>> mtu 1500 >>> options=3 >>> ether 00:27:0e:03:4b:2f >>> media: Ethernet autoselect (1000baseT ) >>> status: active >>> vlan: 10 parent interface: gbeth0 >>> vlan11: flags=8943 >> metric 0 >>> mtu 1500 >>> options=100 >>> ether 00:30:4f:63:5a:bc >>> media: Ethernet autoselect (none) >>> status: active >>> vlan: 10 parent interface: msk0 >>> bridge0: flags=8843 metric 0 mtu >>> 1500 >>> ether d6:c4:f6:0f:5e:4f >>> id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 >>> maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 >>> root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 >>> member: vlan11 flags=143 >>> ifmaxaddr 0 port 6 p
Re: vlan without ip address
i made a little lab, all on 8.2-R: freebsd1-le0.10 (192.168.2.1) <=> bridge0( le0.10 - freebsd2 - le1.10 ) <=> le0.10(192.168.2.1) - freebsd3 freebsd2 is a "switch" it has no ip addresses assigned to interfaces (except localhost of course), "switch" is made by bridge0 interface which contain vlan interfaces le0.10 and le1.10. Ethernet segments freebsd1-freebsd2 and freebsd2-freebsd3 are different and not visible to each other. In this scheme i can ping 192.168.2.2 from 192.168.2.1 just fine, so if your question was "will bridge work without ip addresses", then answer is "yes". -- your sweet isn't ready yet On Mon, Dec 19, 2011 at 8:52 AM, saeedeh motlagh wrote: > you're right but we can't assign tow parent interface to one vlan in freebsd > therefore i define two vlans with the one vlan id. > although we can do it by blow command but it's not work too: > ifconfig gbeth0.10 create > ifconfig msk0.10 create > ifconfig > gbeth0.10: flags=8842 metric 0 mtu 1500 > > options=3 > ether 00:27:0e:03:4b:2f > media: Ethernet autoselect (1000baseT ) > status: active > vlan: 10 parent interface: gbeth0 > msk0.10: flags=8842 metric 0 mtu 1500 > > options=100 > ether 00:30:4f:63:5a:bc > media: Ethernet autoselect (none) > status: active > vlan: 10 parent interface: msk0 > > you know when i define vlans with ip addressess they work as i expected but > i want to know if i can define vlan without ip address as the switch beacuse > i wanna configure a freebsd box as a real switch in my network. maybe it's > impossible to do that :( > > > On Sun, Dec 18, 2011 at 10:52 PM, Alexander Lunev wrote: >> >> first of all, you should name and number you vlan same, if it's clan10 >> on the one side, then it's vlan10 on the other side and in betweeen. >> then (though you have to do it first of all), you should understand >> how vlan's work, and after that connect ports to each other according >> to your scheme. >> >> >> -- >> your sweet isn't ready yet >> >> >> >> On Sun, Dec 18, 2011 at 10:01 AM, saeedeh motlagh >> wrote: >> > i have 3 freebsd system: 0.28 , 0.25 and 0.12 which 28 is assumed to be >> > switch here. one interface of 28 is connected to 25 and the other >> > interface >> > of 28 is connected to 12. as mentioned below, i've defined two vlan10 >> > and >> > 11 with the same vlan id on the 28 and bridge them. >> > now i can't ping 0.25 from 0.12. what's wrong here? should i define >> > vlan10 >> > on 12 and 25? >> > please tell me if i'm misunderstanding. >> > this is the ifconfig for 0.28: >> > vlan10: flags=8943 >> > metric 0 >> > mtu 1500 >> > options=3 >> > ether 00:27:0e:03:4b:2f >> > media: Ethernet autoselect (1000baseT ) >> > status: active >> > vlan: 10 parent interface: gbeth0 >> > vlan11: flags=8943 >> > metric 0 >> > mtu 1500 >> > options=100 >> > ether 00:30:4f:63:5a:bc >> > media: Ethernet autoselect (none) >> > status: active >> > vlan: 10 parent interface: msk0 >> > bridge0: flags=8843 metric 0 mtu >> > 1500 >> > ether d6:c4:f6:0f:5e:4f >> > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 >> > maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 >> > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 >> > member: vlan11 flags=143 >> > ifmaxaddr 0 port 6 priority 128 path cost 55 >> > member: vlan10 flags=143 >> > ifmaxaddr 0 port 5 priority 128 path cost 2 >> > >> > >> > On Sat, Dec 17, 2011 at 8:47 PM, Alireza Torabi >> > wrote: >> > >> >> َAlso it's a good idea to to attach a ifconfig output. >> >> >> >> On 12/17/11, saeedeh motlagh wrote: >> >> > when i do that, the vlan is defined but from a system in a vlan, i >> >> > can't >> >> > ping the other one which is in the same vlan. so i think that the >> >> > vlan is >> >> > not working. am i right? >> >> > >> >> > On Sat, Dec 17, 2011 at 1:15 PM, Juli Mallett >> >> wrote: >> >> > >> >> >> You probably just need to do ifconfig vlanxxx up instead of >> >> >> assigning an >> >> >> IP. >> >> >> >> >> >> On Sat, Dec 17, 2011 at 00:08, saeedeh motlagh >> >> >> wrote: >> >> >> > hi every body >> >> >> > >> >> >> > i wanna configure a freebsd box as a switch. in order to do that, >> >> >> > i >> >> >> bridged >> >> >> > all my interfaces to have switching and it works fine. after that >> >> >> > i >> >> want >> >> >> to >> >> >> > have vlans on it. as you know, in a real switch, a vlan is >> >> >> > configured >> >> >> just >> >> >> > by assigning a port to it without any additional configuration and >> >> vlans >> >> >> > are submitted just by name. but in freebsd a vlan just works when >> >> >> > it >> >> has >> >> >> an >> >> >> > ip address (i think). when i define vlan121 on two freebsd systems >> >> with >> >> >> ip >> >> >> > address it works fine but without ip address i don't know how it >> >> should >> >> >> be >> >> >> > worked. >> >> >> > >> >> >> > can sombody tell me if it is possible to simulate vl
Re: vlan without ip address
There are reports that hw assisted VLANs caused problems in bridging senarios. Users have reported that -vlanhwtag and/or promisc on the physical interface helped. Using -vlanhwtag helped in a case of mine. On 12/20/2011 8:13 AM, Alexander Lunev wrote: i made a little lab, all on 8.2-R: freebsd1-le0.10 (192.168.2.1)<=> bridge0( le0.10 - freebsd2 - le1.10 )<=> le0.10(192.168.2.1) - freebsd3 freebsd2 is a "switch" it has no ip addresses assigned to interfaces (except localhost of course), "switch" is made by bridge0 interface which contain vlan interfaces le0.10 and le1.10. Ethernet segments freebsd1-freebsd2 and freebsd2-freebsd3 are different and not visible to each other. In this scheme i can ping 192.168.2.2 from 192.168.2.1 just fine, so if your question was "will bridge work without ip addresses", then answer is "yes". -- your sweet isn't ready yet On Mon, Dec 19, 2011 at 8:52 AM, saeedeh motlagh wrote: you're right but we can't assign tow parent interface to one vlan in freebsd therefore i define two vlans with the one vlan id. although we can do it by blow command but it's not work too: ifconfig gbeth0.10 create ifconfig msk0.10 create ifconfig gbeth0.10: flags=8842 metric 0 mtu 1500 options=3 ether 00:27:0e:03:4b:2f media: Ethernet autoselect (1000baseT) status: active vlan: 10 parent interface: gbeth0 msk0.10: flags=8842 metric 0 mtu 1500 options=100 ether 00:30:4f:63:5a:bc media: Ethernet autoselect (none) status: active vlan: 10 parent interface: msk0 you know when i define vlans with ip addressess they work as i expected but i want to know if i can define vlan without ip address as the switch beacuse i wanna configure a freebsd box as a real switch in my network. maybe it's impossible to do that :( On Sun, Dec 18, 2011 at 10:52 PM, Alexander Lunev wrote: first of all, you should name and number you vlan same, if it's clan10 on the one side, then it's vlan10 on the other side and in betweeen. then (though you have to do it first of all), you should understand how vlan's work, and after that connect ports to each other according to your scheme. -- your sweet isn't ready yet On Sun, Dec 18, 2011 at 10:01 AM, saeedeh motlagh wrote: i have 3 freebsd system: 0.28 , 0.25 and 0.12 which 28 is assumed to be switch here. one interface of 28 is connected to 25 and the other interface of 28 is connected to 12. as mentioned below, i've defined two vlan10 and 11 with the same vlan id on the 28 and bridge them. now i can't ping 0.25 from 0.12. what's wrong here? should i define vlan10 on 12 and 25? please tell me if i'm misunderstanding. this is the ifconfig for 0.28: vlan10: flags=8943 metric 0 mtu 1500 options=3 ether 00:27:0e:03:4b:2f media: Ethernet autoselect (1000baseT) status: active vlan: 10 parent interface: gbeth0 vlan11: flags=8943 metric 0 mtu 1500 options=100 ether 00:30:4f:63:5a:bc media: Ethernet autoselect (none) status: active vlan: 10 parent interface: msk0 bridge0: flags=8843 metric 0 mtu 1500 ether d6:c4:f6:0f:5e:4f id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: vlan11 flags=143 ifmaxaddr 0 port 6 priority 128 path cost 55 member: vlan10 flags=143 ifmaxaddr 0 port 5 priority 128 path cost 2 On Sat, Dec 17, 2011 at 8:47 PM, Alireza Torabi wrote: َAlso it's a good idea to to attach a ifconfig output. On 12/17/11, saeedeh motlagh wrote: when i do that, the vlan is defined but from a system in a vlan, i can't ping the other one which is in the same vlan. so i think that the vlan is not working. am i right? On Sat, Dec 17, 2011 at 1:15 PM, Juli Mallett wrote: You probably just need to do ifconfig vlanxxx up instead of assigning an IP. On Sat, Dec 17, 2011 at 00:08, saeedeh motlagh wrote: hi every body i wanna configure a freebsd box as a switch. in order to do that, i bridged all my interfaces to have switching and it works fine. after that i want to have vlans on it. as you know, in a real switch, a vlan is configured just by assigning a port to it without any additional configuration and vlans are submitted just by name. but in freebsd a vlan just works when it has an ip address (i think). when i define vlan121 on two freebsd systems with ip address it works fine but without ip address i don't know how it should be worked. can sombody tell me if it is possible to simulate vlans in freebsd as they are in a real switch? i mean can we have vlans without ip addresses which works fine? maybe some kind of vlan which works by MAc address. is it possible? it's so necessary for me to do that:( yours, motlagh ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsu
