RE: Default route destination changing without warning follow-up
Hi, The server that actually has the problem is: - FreeBSD 9.0-RELEASE-p3 - Uses IPFW & dummynet for traffic shaping - Uses PF for firewalling and NAT - Uses MPD 5.6 for PPPoE server - Uses freeradius and PostgreSQL for authentication. I wrote a script some weeks ago that does the following: = #!/bin/sh RIGHT_GATEWAY='1.1.1.1' NOC_EMAIL='b...@test.com' i=5 while [ $i -gt 0 ] do if [ `/usr/bin/netstat -rn |grep default |grep $RIGHT_GATEWAY |wc -l` -ne 1 ] then /sbin/route del -net default /sbin/route add -net default $RIGHT_GATEWAY tail -n 100 /tmp/route_monitor.log | mail -s "Default route bug happened" $NOC_EMAIL fi i=`expr $i - 1` sleep 10 done = I've changed the variables for privacy purposes. This script is executed each minutes in crontab. So if the gateway changes, it is fixed within 10 seconds (a mean of 5 seconds). I have seen multiple days where it doesn't happen at all... Today was a record!! 43 times between 22:43 and 23:56. It means, 43 times the script detected the gateway wasn't the good one and had to change it. It looks like it happens when network usage is higher than usual.. there's obviously a link with usage...The server isn't using all its resources. I usually see 25% CPU usage at higher loads... All loads value are almost always under 0.4 and are mostly around 0.35 for past 15 minutes. I'm running a route monitor in a screen and I'm sending the output to a textfile. As you see in the script, I'm sending me the last 100 lines of it and I only see my script changing the gateway... nothing before is changing it. The other people experiencing that bug seems to have the same behaviour. -Message d'origine- De : Alexander V. Chernikov [mailto:melif...@freebsd.org] Envoyé : 30 septembre 2012 17:07 À : Dominic Blais Cc : freebsd-net@freebsd.org Objet : Re: Default route destination changing without warning follow-up On 01.10.2012 00:59, Dominic Blais wrote: > It's all about IPv4 in my case. It will be great to supply some more details (e.g. like FreeBSD version, interfaces configuration, netstat -rn output). How often does this happen ? (e.g. while true; do echo -n `date` ; route -n get default | grep gate; sleep 1; done can help) If this is reproducible, what actions precedes this change? Maybe some ARP traffic on that interface, or interface creation/deletion, or.. ? Is route monitor completely silent when the change happens? > > > -- > > > > -Message d'origine- > De : Alexander V. Chernikov [mailto:melif...@freebsd.org] Envoyé : 30 > septembre 2012 16:39 À : Dominic Blais Cc : freebsd-net@freebsd.org > Objet : Re: Default route destination changing without warning > follow-up > > On 01.10.2012 00:33, Dominic Blais wrote: >> Yes, I'm very sure of it! A "route monitor" show no changes when it happens. >> I've heard of another person with the same bug that has no traces in "route >> monitor" either... We have in common that we're using IPFW and PF. > So, are we talking about IPv4 or IPv6? >> >> >> >> -- >> >> >> >> -Message d'origine- >> De : Alexander V. Chernikov [mailto:melif...@freebsd.org] Envoyé : 30 >> septembre 2012 16:31 À : Dominic Blais Cc : freebsd-net@freebsd.org >> Objet : Re: Default route destination changing without warning >> follow-up >> >> On 01.10.2012 00:00, Dominic Blais wrote: >>> Hi, >> Hello! >>> >>> I was just wondering if there was anything new about the bug of default >>> route changing without warning... Is there any test I can do to help >>> fixing it? >> Can you be a bit more precise and specify FreeBSD version and address family? >> >> Are you sure that it is not changed by some other userland process (e.g. >> did you do some `route monitor` checks) ? >>> >>> -- >>> [cid:image001.gif@01CD9F24.B366CBF0] >>> >>> >>> >>> >>> >>> ___ >>> 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: Default route destination changing without warning follow-up
W dniu 2012-10-04 15:41, Dominic Blais pisze: Hi, The server that actually has the problem is: - FreeBSD 9.0-RELEASE-p3 - Uses IPFW & dummynet for traffic shaping - Uses PF for firewalling and NAT - Uses MPD 5.6 for PPPoE server - Uses freeradius and PostgreSQL for authentication. I have similar issues, it can happen many times a day, or there are few days without a problem. There is no "route monitor" output when it happens. "fstat | grep route" periodically gives just ntpd and bsnmpd. I turned it off, no change. I tried to turn TSO on all em interfaces - no change. Three routers with similar setup and problem of changing default gateway or static routes: - 9.0-RELEASE-p1 FreeBSD (amd64) - IPFW & dumynet for shaping - PF for NAT and filtering I do not use MPD. However I do use PPPoE in my network, terminated at Mikrotik Routerboard and then routed to FBSD. Sorry for my poor english. Best regards! Krzysiek ___ 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: Default route destination changing without warning follow-up
About hardware, the my server is a HP Proliant ML115. It has a Broadcom BCM5722 as network controller. In my network configuration, I'm using a single NIC (bge0). This interface has an IP address in the default gateway subnet. I also have a vlan interface on the same NIC for pppoe traffic. -- -Message d'origine- De : Dominic Blais Envoyé : 4 octobre 2012 09:41 À : 'Alexander V. Chernikov' Cc : freebsd-net@freebsd.org Objet : RE: Default route destination changing without warning follow-up Hi, The server that actually has the problem is: - FreeBSD 9.0-RELEASE-p3 - Uses IPFW & dummynet for traffic shaping - Uses PF for firewalling and NAT - Uses MPD 5.6 for PPPoE server - Uses freeradius and PostgreSQL for authentication. I wrote a script some weeks ago that does the following: = #!/bin/sh RIGHT_GATEWAY='1.1.1.1' NOC_EMAIL='b...@test.com' i=5 while [ $i -gt 0 ] do if [ `/usr/bin/netstat -rn |grep default |grep $RIGHT_GATEWAY |wc -l` -ne 1 ] then /sbin/route del -net default /sbin/route add -net default $RIGHT_GATEWAY tail -n 100 /tmp/route_monitor.log | mail -s "Default route bug happened" $NOC_EMAIL fi i=`expr $i - 1` sleep 10 done = I've changed the variables for privacy purposes. This script is executed each minutes in crontab. So if the gateway changes, it is fixed within 10 seconds (a mean of 5 seconds). I have seen multiple days where it doesn't happen at all... Today was a record!! 43 times between 22:43 and 23:56. It means, 43 times the script detected the gateway wasn't the good one and had to change it. It looks like it happens when network usage is higher than usual.. there's obviously a link with usage...The server isn't using all its resources. I usually see 25% CPU usage at higher loads... All loads value are almost always under 0.4 and are mostly around 0.35 for past 15 minutes. I'm running a route monitor in a screen and I'm sending the output to a textfile. As you see in the script, I'm sending me the last 100 lines of it and I only see my script changing the gateway... nothing before is changing it. The other people experiencing that bug seems to have the same behaviour. -Message d'origine- De : Alexander V. Chernikov [mailto:melif...@freebsd.org] Envoyé : 30 septembre 2012 17:07 À : Dominic Blais Cc : freebsd-net@freebsd.org Objet : Re: Default route destination changing without warning follow-up On 01.10.2012 00:59, Dominic Blais wrote: > It's all about IPv4 in my case. It will be great to supply some more details (e.g. like FreeBSD version, interfaces configuration, netstat -rn output). How often does this happen ? (e.g. while true; do echo -n `date` ; route -n get default | grep gate; sleep 1; done can help) If this is reproducible, what actions precedes this change? Maybe some ARP traffic on that interface, or interface creation/deletion, or.. ? Is route monitor completely silent when the change happens? > > > -- > > > > -Message d'origine- > De : Alexander V. Chernikov [mailto:melif...@freebsd.org] Envoyé : 30 > septembre 2012 16:39 À : Dominic Blais Cc : freebsd-net@freebsd.org > Objet : Re: Default route destination changing without warning > follow-up > > On 01.10.2012 00:33, Dominic Blais wrote: >> Yes, I'm very sure of it! A "route monitor" show no changes when it happens. >> I've heard of another person with the same bug that has no traces in "route >> monitor" either... We have in common that we're using IPFW and PF. > So, are we talking about IPv4 or IPv6? >> >> >> >> -- >> >> >> >> -Message d'origine- >> De : Alexander V. Chernikov [mailto:melif...@freebsd.org] Envoyé : 30 >> septembre 2012 16:31 À : Dominic Blais Cc : freebsd-net@freebsd.org >> Objet : Re: Default route destination changing without warning >> follow-up >> >> On 01.10.2012 00:00, Dominic Blais wrote: >>> Hi, >> Hello! >>> >>> I was just wondering if there was anything new about the bug of default >>> route changing without warning... Is there any test I can do to help >>> fixing it? >> Can you be a bit more precise and specify FreeBSD version and address family? >> >> Are you sure that it is not changed by some other userland process (e.g. >> did you do some `route monitor` checks) ? >>> >>> -- >>> [cid:image001.gif@01CD9F24.B366CBF0] >>> >>> >>> >>> >>> >>> ___ >>> 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: Default route destination changing without warning follow-up
Alexander V. Chernikov wrote this message on Mon, Oct 01, 2012 at 01:07 +0400: > On 01.10.2012 00:59, Dominic Blais wrote: > >It's all about IPv4 in my case. > > It will be great to supply some more details (e.g. like FreeBSD version, > interfaces configuration, netstat -rn output). > > How often does this happen ? > (e.g. while true; do echo -n `date` ; route -n get default | grep gate; > sleep 1; done can help) > > If this is reproducible, what actions precedes this change? > Maybe some ARP traffic on that interface, or interface > creation/deletion, or.. ? > > Is route monitor completely silent when the change happens? Just for refernece, Dominic brought this up in an earlier thread: http://www.freebsd.org/cgi/mid.cgi?2de61b0869b7484997bca012845482c7ebe62dd...@win2008.domnt.abi.ca and at least on other person seems to have the same issue... quick question for you Dominic, do you see the correct number of routes, but a new wrong one appear? or does the route just simply disapear? or does a new one seem to replace the old one? The reason I ask is that if a new wrong one appears, it could be memory corruption, but if a new one replaces the old one, for some reason when allocating a new route, it could accidentatlly be replacing the default route... Just some thoughts... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ 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: Default route destination changing without warning follow-up
There's never 2 default route... it's always a single default route. Since route monitor shows nothing, I guess it's the same route that gets its gateway changed for some reason... I guess the effective and appearing change could be due to a pointer changing somewhere or the memory space where is located the default gateway is replaced with new stuff... I don't know how it's coded but it looks like that kind of stuff since nothing is triggered on the route monitor radar... The default route always exists and there's no trace of it deleted prior to what my script does so we may be quite sure it's the same route that's brutalized ;) Since mpd creates new interfaces for each new connection I see some route being added/replaced from time to time. I first thought it was mpd's fault because it was the only thing playing with routes but Krzysztof Barcikowski doesn't use MPD and shares the use of IPFW and PF like me and has the same default route gateway changing behaviour... -- -Message d'origine- De : John-Mark Gurney [mailto:j...@funkthat.com] Envoyé : 4 octobre 2012 12:03 À : Alexander V. Chernikov Cc : Dominic Blais; freebsd-net@freebsd.org Objet : Re: Default route destination changing without warning follow-up Alexander V. Chernikov wrote this message on Mon, Oct 01, 2012 at 01:07 +0400: > On 01.10.2012 00:59, Dominic Blais wrote: > >It's all about IPv4 in my case. > > It will be great to supply some more details (e.g. like FreeBSD > version, interfaces configuration, netstat -rn output). > > How often does this happen ? > (e.g. while true; do echo -n `date` ; route -n get default | grep > gate; sleep 1; done can help) > > If this is reproducible, what actions precedes this change? > Maybe some ARP traffic on that interface, or interface > creation/deletion, or.. ? > > Is route monitor completely silent when the change happens? Just for refernece, Dominic brought this up in an earlier thread: http://www.freebsd.org/cgi/mid.cgi?2de61b0869b7484997bca012845482c7ebe62dd...@win2008.domnt.abi.ca and at least on other person seems to have the same issue... quick question for you Dominic, do you see the correct number of routes, but a new wrong one appear? or does the route just simply disapear? or does a new one seem to replace the old one? The reason I ask is that if a new wrong one appears, it could be memory corruption, but if a new one replaces the old one, for some reason when allocating a new route, it could accidentatlly be replacing the default route... Just some thoughts... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ 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: Default route destination changing without warning follow-up
W dniu 2012-10-04 18:02, John-Mark Gurney pisze: Alexander V. Chernikov wrote this message on Mon, Oct 01, 2012 at 01:07 +0400: On 01.10.2012 00:59, Dominic Blais wrote: It's all about IPv4 in my case. It will be great to supply some more details (e.g. like FreeBSD version, interfaces configuration, netstat -rn output). How often does this happen ? (e.g. while true; do echo -n `date` ; route -n get default | grep gate; sleep 1; done can help) If this is reproducible, what actions precedes this change? Maybe some ARP traffic on that interface, or interface creation/deletion, or.. ? Is route monitor completely silent when the change happens? Just for refernece, Dominic brought this up in an earlier thread: http://www.freebsd.org/cgi/mid.cgi?2de61b0869b7484997bca012845482c7ebe62dd...@win2008.domnt.abi.ca and at least on other person seems to have the same issue... quick question for you Dominic, do you see the correct number of routes, but a new wrong one appear? or does the route just simply disapear? or does a new one seem to replace the old one? The reason I ask is that if a new wrong one appears, it could be memory corruption, but if a new one replaces the old one, for some reason when allocating a new route, it could accidentatlly be replacing the default route... Just some thoughts... Hi, I don't see a second new route appearing in my case, just the default or static route is replaced. I'm not conviced of memory corruption, as it happens on 3 different physical machines. Best regards! Krzysiek Barcikowski ___ 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: Default route destination changing without warning follow-up
Dominic Blais wrote this message on Thu, Oct 04, 2012 at 12:12 -0400: > There's never 2 default route... it's always a single default route. Since > route monitor shows nothing, I guess it's the same route that gets its > gateway changed for some reason... I guess the effective and appearing change > could be due to a pointer changing somewhere or the memory space where is > located the default gateway is replaced with new stuff... I don't know how > it's coded but it looks like that kind of stuff since nothing is triggered on > the route monitor radar... > > The default route always exists and there's no trace of it deleted prior to > what my script does so we may be quite sure it's the same route that's > brutalized ;) It looks like ddb does support breaking on a hardware address, so we might be able to track it down this way... If you can use ddb or gdb to track down the memory address of the ip of the default route, you can set an hwatch (see ddb(4)) on that address and hopefully catch the code that is corrupting the default route... I'm not familar w/ the routing system to help you figure out the address to watch on, etc... Maybe someone else can... Or you can try to read the code... Hope this helps... > Since mpd creates new interfaces for each new connection I see some route > being added/replaced from time to time. I first thought it was mpd's fault > because it was the only thing playing with routes but Krzysztof Barcikowski > doesn't use MPD and shares the use of IPFW and PF like me and has the same > default route gateway changing behaviour... > > > -- > > > > -Message d'origine- > De : John-Mark Gurney [mailto:j...@funkthat.com] > Envoyé : 4 octobre 2012 12:03 > À : Alexander V. Chernikov > Cc : Dominic Blais; freebsd-net@freebsd.org > Objet : Re: Default route destination changing without warning follow-up > > Alexander V. Chernikov wrote this message on Mon, Oct 01, 2012 at 01:07 +0400: > > On 01.10.2012 00:59, Dominic Blais wrote: > > >It's all about IPv4 in my case. > > > > It will be great to supply some more details (e.g. like FreeBSD > > version, interfaces configuration, netstat -rn output). > > > > How often does this happen ? > > (e.g. while true; do echo -n `date` ; route -n get default | grep > > gate; sleep 1; done can help) > > > > If this is reproducible, what actions precedes this change? > > Maybe some ARP traffic on that interface, or interface > > creation/deletion, or.. ? > > > > Is route monitor completely silent when the change happens? > > Just for refernece, Dominic brought this up in an earlier thread: > http://www.freebsd.org/cgi/mid.cgi?2de61b0869b7484997bca012845482c7ebe62dd...@win2008.domnt.abi.ca > > and at least on other person seems to have the same issue... > > quick question for you Dominic, do you see the correct number of routes, but > a new wrong one appear? or does the route just simply disapear? or does a > new one seem to replace the old one? > > The reason I ask is that if a new wrong one appears, it could be memory > corruption, but if a new one replaces the old one, for some reason when > allocating a new route, it could accidentatlly be replacing the default > route... > > Just some thoughts... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ 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: Default route destination changing without warning follow-up
On Thu, Oct 04, 2012 at 07:36:51PM +0200, Krzysztof Barcikowski wrote: > W dniu 2012-10-04 18:02, John-Mark Gurney pisze: > > Alexander V. Chernikov wrote this message on Mon, Oct 01, 2012 at 01:07 > > +0400: > >> On 01.10.2012 00:59, Dominic Blais wrote: > >>> It's all about IPv4 in my case. > >> It will be great to supply some more details (e.g. like FreeBSD version, > >> interfaces configuration, netstat -rn output). > >> > >> How often does this happen ? > >> (e.g. while true; do echo -n `date` ; route -n get default | grep gate; > >> sleep 1; done can help) > >> > >> If this is reproducible, what actions precedes this change? > >> Maybe some ARP traffic on that interface, or interface > >> creation/deletion, or.. ? > >> > >> Is route monitor completely silent when the change happens? > > Just for refernece, Dominic brought this up in an earlier thread: > > http://www.freebsd.org/cgi/mid.cgi?2de61b0869b7484997bca012845482c7ebe62dd...@win2008.domnt.abi.ca > > > > and at least on other person seems to have the same issue... > > > > quick question for you Dominic, do you see the correct number of routes, > > but a new wrong one appear? or does the route just simply disapear? or > > does a new one seem to replace the old one? > > > > The reason I ask is that if a new wrong one appears, it could be memory > > corruption, but if a new one replaces the old one, for some reason when > > allocating a new route, it could accidentatlly be replacing the default > > route... > > > > Just some thoughts... > > > > Hi, > > I don't see a second new route appearing in my case, just the default or > static route is replaced. > I'm not conviced of memory corruption, as it happens on 3 different > physical machines. Sorry for jumping into the middle of the thread (and apologies if this was asked/answered previously), however what are the settings for the following sysctls? net.inet.icmp.log_redirect net.inet.icmp.drop_redirect and potentially net.inet6.ip6.redirect net.inet6.icmp6.rediraccept Gary ___ 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"
A small cleanup patch
Folks, I came up with this while going through the lltable code.
kong@[/u/vijay/bsd/CODE/cur/sys]# svn diff net/if.c
Index: net/if.c
===
--- net/if.c(revision 241169)
+++ net/if.c(working copy)
@@ -691,12 +691,9 @@
if_attachdomain(void *dummy)
{
struct ifnet *ifp;
- int s;
- s = splnet();
TAILQ_FOREACH(ifp, &V_ifnet, if_link)
if_attachdomain1(ifp);
- splx(s);
}
SYSINIT(domainifattach, SI_SUB_PROTO_IFATTACHDOMAIN, SI_ORDER_SECOND,
if_attachdomain, NULL);
@@ -705,22 +702,17 @@
if_attachdomain1(struct ifnet *ifp)
{
struct domain *dp;
- int s;
- s = splnet();
-
/*
* Since dp->dom_ifattach calls malloc() with M_WAITOK, we
* cannot lock ifp->if_afdata initialization, entirely.
*/
if (IF_AFDATA_TRYLOCK(ifp) == 0) {
- splx(s);
return;
}
if (ifp->if_afdata_initialized >= domain_init_status) {
IF_AFDATA_UNLOCK(ifp);
- splx(s);
- printf("if_attachdomain called more than once on %s\n",
+ log(LOG_WARNING, "if_attachdomain called more than once on
%s\n",
ifp->if_xname);
return;
}
@@ -734,8 +726,6 @@
ifp->if_afdata[dp->dom_family] =
(*dp->dom_ifattach)(ifp);
}
-
- splx(s);
}
/*
___
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: Default route destination changing without warning follow-up
net.inet.icmp.log_redirect: 0 net.inet.icmp.drop_redirect: 0 net.inet6.ip6.redirect: 1 net.inet6.icmp6.rediraccept: 1 -- -Message d'origine- De : Gary Palmer [mailto:gpal...@freebsd.org] Envoyé : 4 octobre 2012 18:23 À : Krzysztof Barcikowski Cc : Alexander V. Chernikov; Dominic Blais; freebsd-net@freebsd.org Objet : Re: Default route destination changing without warning follow-up On Thu, Oct 04, 2012 at 07:36:51PM +0200, Krzysztof Barcikowski wrote: > W dniu 2012-10-04 18:02, John-Mark Gurney pisze: > > Alexander V. Chernikov wrote this message on Mon, Oct 01, 2012 at 01:07 > > +0400: > >> On 01.10.2012 00:59, Dominic Blais wrote: > >>> It's all about IPv4 in my case. > >> It will be great to supply some more details (e.g. like FreeBSD > >> version, interfaces configuration, netstat -rn output). > >> > >> How often does this happen ? > >> (e.g. while true; do echo -n `date` ; route -n get default | grep > >> gate; sleep 1; done can help) > >> > >> If this is reproducible, what actions precedes this change? > >> Maybe some ARP traffic on that interface, or interface > >> creation/deletion, or.. ? > >> > >> Is route monitor completely silent when the change happens? > > Just for refernece, Dominic brought this up in an earlier thread: > > http://www.freebsd.org/cgi/mid.cgi?2DE61B0869B7484997BCA012845482C7E > > be62dd...@win2008.domnt.abi.ca > > > > and at least on other person seems to have the same issue... > > > > quick question for you Dominic, do you see the correct number of > > routes, but a new wrong one appear? or does the route just simply > > disapear? or does a new one seem to replace the old one? > > > > The reason I ask is that if a new wrong one appears, it could be > > memory corruption, but if a new one replaces the old one, for some > > reason when allocating a new route, it could accidentatlly be > > replacing the default route... > > > > Just some thoughts... > > > > Hi, > > I don't see a second new route appearing in my case, just the default > or static route is replaced. > I'm not conviced of memory corruption, as it happens on 3 different > physical machines. Sorry for jumping into the middle of the thread (and apologies if this was asked/answered previously), however what are the settings for the following sysctls? net.inet.icmp.log_redirect net.inet.icmp.drop_redirect and potentially net.inet6.ip6.redirect net.inet6.icmp6.rediraccept Gary ___ 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: kern/172113: [panic] [e1000] [patch] 9.1-RC1/amd64 panices in igb(4): m_getjcl: invalid cluster type
Old Synopsis: [panic] [igb] [patch] 9.1-RC1/amd64 panices in igb(4): m_getjcl: invalid cluster type New Synopsis: [panic] [e1000] [patch] 9.1-RC1/amd64 panices in igb(4): m_getjcl: invalid cluster type Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Oct 5 03:27:58 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=172113 ___ 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: kern/171825: [ale] [patch] ale driver msix setup typo
Old Synopsis: ale driver msix setup typo New Synopsis: [ale] [patch] ale driver msix setup typo Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Oct 5 03:43:27 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=171825 ___ 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: kern/171739: [bce] [panic] bce related kernel panic
Old Synopsis: bce related kernel panic New Synopsis: [bce] [panic] bce related kernel panic Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Oct 5 03:48:51 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=171739 ___ 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: kern/171711: [dummynet] [panic] Kernel panic in dummynet
Synopsis: [dummynet] [panic] Kernel panic in dummynet Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Oct 5 03:50:42 UTC 2012 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=171711 ___ 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: Default route destination changing without warning follow-up
W dniu 2012-10-05 00:23, Gary Palmer pisze: On Thu, Oct 04, 2012 at 07:36:51PM +0200, Krzysztof Barcikowski wrote: W dniu 2012-10-04 18:02, John-Mark Gurney pisze: Alexander V. Chernikov wrote this message on Mon, Oct 01, 2012 at 01:07 +0400: On 01.10.2012 00:59, Dominic Blais wrote: It's all about IPv4 in my case. It will be great to supply some more details (e.g. like FreeBSD version, interfaces configuration, netstat -rn output). How often does this happen ? (e.g. while true; do echo -n `date` ; route -n get default | grep gate; sleep 1; done can help) If this is reproducible, what actions precedes this change? Maybe some ARP traffic on that interface, or interface creation/deletion, or.. ? Is route monitor completely silent when the change happens? Just for refernece, Dominic brought this up in an earlier thread: http://www.freebsd.org/cgi/mid.cgi?2de61b0869b7484997bca012845482c7ebe62dd...@win2008.domnt.abi.ca and at least on other person seems to have the same issue... quick question for you Dominic, do you see the correct number of routes, but a new wrong one appear? or does the route just simply disapear? or does a new one seem to replace the old one? The reason I ask is that if a new wrong one appears, it could be memory corruption, but if a new one replaces the old one, for some reason when allocating a new route, it could accidentatlly be replacing the default route... Just some thoughts... Hi, I don't see a second new route appearing in my case, just the default or static route is replaced. I'm not conviced of memory corruption, as it happens on 3 different physical machines. Sorry for jumping into the middle of the thread (and apologies if this was asked/answered previously), however what are the settings for the following sysctls? net.inet.icmp.log_redirect net.inet.icmp.drop_redirect and potentially net.inet6.ip6.redirect net.inet6.icmp6.rediraccept Gary ___ 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" Hi, net.inet.icmp.log_redirect: 0 net.inet.icmp.drop_redirect: 1 net.inet6.ip6.redirect: 1 net.inet6.icmp6.rediraccept: 1 Best regards! Krzysiek Barcikowski Krzysiek Barcikowski ___ 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"
