Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
On 9/3/07, Lance Peterson [EMAIL PROTECTED] wrote: Hadn't thought about it being a FreeBSD problem with limited driver support for common home user NIC's. That very well may be the problem, in my case. Fortunately, I didn't have to buy new, higher level NIC's to get my Linux firewall up and running without connection issues. Good for you, now can we get back on topic please? --Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
Bill Marquette wrote: On 9/3/07, Lance Peterson [EMAIL PROTECTED] wrote: Hadn't thought about it being a FreeBSD problem with limited driver support for common home user NIC's. That very well may be the problem, in my case. Fortunately, I didn't have to buy new, higher level NIC's to get my Linux firewall up and running without connection issues. Good for you, now can we get back on topic please? hah.. indeed. For the record, I've had no worse or better luck with Linux and crap NIC's than FreeBSD, Windows, or any other OS. Lance, get a clue and some tact while you're at it, some hardware just sucks no matter what you run on it. Of course FreeBSD isn't immune to driver bugs, just like every other OS, but I use Windows and Linux as much as FreeBSD and of the three, only Windows has measurably less hardware problems. Most hardware I have that doesn't work right in FreeBSD doesn't work right in Linux either, and vice versa. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
Bill Marquette wrote: I have two connections to Comcast through two different modems (their voip capable modem and their business modem - static IPs) at my house and have _never_ had an issue with the connection. The Comcast user with issues is likely a hardware issue. I didn't realize somebody on Comcast hijacked this thread. There is a problem specific to one .NZ ISP and at least one if not a couple of the people seeing it replied earlier in the thread. What I posted about earlier re: the trace was specific to this ISP in New Zealand. There does seem to be some sort of problem with dropping offline if you have two NIC's plugged into the same broadcast domain. Since cable ISP's use absurdly huge broadcast domains, if you have multiple cable modems, unless they're drastically different like a business vs. residential, you're going to have two interfaces on the same broadcast domain. I have no idea what that problem is, haven't had a chance to try to replicate it. But I recall a couple people in the forum reporting a problem where it seemed to be narrowed down to this, and now I guess somebody in this thread is another. But these are two very different issues. The .NZ users are seeing issues with single WAN connections. I'm not sure I have anything more to add to David's issue though - it's obviously not hardware. Question for Chris on the trace. Does it show the upstream router sending arp requests for the local IP and getting a response? Not sure if there's a way to force a gratuitous arp in FreeBSD without installing some third party tool like nemesis, but that might be worth looking at I 'spose. I don't think I saw any for the public IP on the system itself, but I assume it's likely in the router's ARP cache. I don't have the trace handy at the moment, I'll look later. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
On 9/2/07, Tortise [EMAIL PROTECTED] wrote: Thanks Bill They are static IP's, so I assume (you may know better?) DHCP lease times are (or should be?) irrelevant. Not sure if this what you mean but this might answer? No worries, if it's static assigned and not a dhcp static assignment then you won't have the files I was looking for. Honestly not sure what else to look at here. This doesn't appear to be due to traffic inactivity. I'm not sure how any other system would work any better :-/ --Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
I'm a home user with a cable modem connected to a small firewall computer built up with one Linksys 10/100 card, one Netgear 10/100 card, and PFSense installed. I started experiencing connection problems with computers attached to this small network within 24 hours. I reloaded, reconfigured, started and stopped services, etc. and nothing permanently fixed my connection issues. Then I formatted and installed Smoothwall Express using all the same hardware -- problem solved -- no more lost connections. Definately seems like a PFSense problem, in my opinion. Sorry if this is a little off topic or already discussed, I just scanned though these replies and wanted to post my experience with lost connections. On 9/3/07, Bill Marquette [EMAIL PROTECTED] wrote: On 9/2/07, Tortise [EMAIL PROTECTED] wrote: Thanks Bill They are static IP's, so I assume (you may know better?) DHCP lease times are (or should be?) irrelevant. Not sure if this what you mean but this might answer? No worries, if it's static assigned and not a dhcp static assignment then you won't have the files I was looking for. Honestly not sure what else to look at here. This doesn't appear to be due to traffic inactivity. I'm not sure how any other system would work any better :-/ --Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
considering smoothwall is based on linux whereas pfSense is based on FreeBSD, I lean towards it being a driver issue with your setup. using cheapo cards like the linksys or Netgear ones can cause this. try and get a higher level card like a 3com 3c905c or intel card. I personally run the gigabit Netgear card with hardware offloading internally and a 3com WAN side and it runs with zero issue. -Sean - Original Message - From: Lance Peterson To: support@pfsense.com Sent: Monday, September 03, 2007 2:28 PM Subject: Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM I'm a home user with a cable modem connected to a small firewall computer built up with one Linksys 10/100 card, one Netgear 10/100 card, and PFSense installed. I started experiencing connection problems with computers attached to this small network within 24 hours. I reloaded, reconfigured, started and stopped services, etc. and nothing permanently fixed my connection issues. Then I formatted and installed Smoothwall Express using all the same hardware -- problem solved -- no more lost connections. Definately seems like a PFSense problem, in my opinion. Sorry if this is a little off topic or already discussed, I just scanned though these replies and wanted to post my experience with lost connections. On 9/3/07, Bill Marquette [EMAIL PROTECTED] wrote: On 9/2/07, Tortise [EMAIL PROTECTED] wrote: Thanks Bill They are static IP's, so I assume (you may know better?) DHCP lease times are (or should be?) irrelevant. Not sure if this what you mean but this might answer? No worries, if it's static assigned and not a dhcp static assignment then you won't have the files I was looking for. Honestly not sure what else to look at here. This doesn't appear to be due to traffic inactivity. I'm not sure how any other system would work any better :-/ --Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
Sean I guess you saw we've gone down that road, the cards I am currently using are in the subject line and would seem to be of the type you advocate, however perhaps you were inquiring the NIC types used by Lance? Are you also behind a Motorola SB 51xx cable modem? The fix I posted has now proven to perform the necessary rescue several times. It is such a refreshing change to be off site running a terminal session, to be cut out, and to know it will come back within a minute! (Assuming the issue is the one that is the subject of this thread!) Its not perfect but it is a significant advance! If I knew how to reference and extract the WAN driver type (e.g. em0) I could have the script fully cross machine, so it might then be considered for the image. So I don't have to add it in manually with every upgrade! Even if it is there so that the appropriate CRON line would only remain to be added or commented in. Kind regards David Hingston - Original Message - From: Sean Cavanaugh To: support@pfsense.com Sent: Tuesday, September 04, 2007 8:11 AM Subject: Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM considering smoothwall is based on linux whereas pfSense is based on FreeBSD, I lean towards it being a driver issue with your setup. using cheapo cards like the linksys or Netgear ones can cause this. try and get a higher level card like a 3com 3c905c or intel card. I personally run the gigabit Netgear card with hardware offloading internally and a 3com WAN side and it runs with zero issue. -Sean - Original Message - From: Lance Peterson To: support@pfsense.com Sent: Monday, September 03, 2007 2:28 PM Subject: Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM I'm a home user with a cable modem connected to a small firewall computer built up with one Linksys 10/100 card, one Netgear 10/100 card, and PFSense installed. I started experiencing connection problems with computers attached to this small network within 24 hours. I reloaded, reconfigured, started and stopped services, etc. and nothing permanently fixed my connection issues. Then I formatted and installed Smoothwall Express using all the same hardware -- problem solved -- no more lost connections. Definately seems like a PFSense problem, in my opinion. Sorry if this is a little off topic or already discussed, I just scanned though these replies and wanted to post my experience with lost connections. On 9/3/07, Bill Marquette [EMAIL PROTECTED] wrote: On 9/2/07, Tortise [EMAIL PROTECTED] wrote: Thanks Bill They are static IP's, so I assume (you may know better?) DHCP lease times are (or should be?) irrelevant. Not sure if this what you mean but this might answer? No worries, if it's static assigned and not a dhcp static assignment then you won't have the files I was looking for. Honestly not sure what else to look at here. This doesn't appear to be due to traffic inactivity. I'm not sure how any other system would work any better :-/ --Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
I haven't closely followed this particular thread, but a couple months back I got some pcap files from one of the people with this issue. It got buried in my inbox, and I never got back around to it until now. The capture from that time, with the same issue, shows ARP working fine, traffic going out fine, but it never sees any responses. SYN's go out and never see a SYN ACK, ICMP echo requests go out and never see a reply. As is typical with cable modems, there were over 100,000 ARP requests are replies in the capture (with a couple dozen non-ARP frames). So I have no idea what's happening - it definitely looks like an ISP issue since the traffic is going out properly and never sees replies, ARP is working fine, and the cable modem is obviously up and the NIC is receiving traffic from it fine given the amount of ARP frames in the capture. Rebooting does temporarily fix it, which makes absolutely no sense. Given that it's limited to this one particular ISP, and there doesn't seem to be any other ISP in the world that has the same problem, it definitely looks like something strange with their network. The captures don't show anything to indicate what that might be. Tortise wrote: Sean I guess you saw we've gone down that road, the cards I am currently using are in the subject line and would seem to be of the type you advocate, however perhaps you were inquiring the NIC types used by Lance? Are you also behind a Motorola SB 51xx cable modem? The fix I posted has now proven to perform the necessary rescue several times. It is such a refreshing change to be off site running a terminal session, to be cut out, and to know it will come back within a minute! (Assuming the issue is the one that is the subject of this thread!) Its not perfect but it is a significant advance! If I knew how to reference and extract the WAN driver type (e.g. em0) I could have the script fully cross machine, so it might then be considered for the image. So I don't have to add it in manually with every upgrade! Even if it is there so that the appropriate CRON line would only remain to be added or commented in. Kind regards David Hingston - Original Message - *From:* Sean Cavanaugh mailto:[EMAIL PROTECTED] *To:* support@pfsense.com mailto:support@pfsense.com *Sent:* Tuesday, September 04, 2007 8:11 AM *Subject:* Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM considering smoothwall is based on linux whereas pfSense is based on FreeBSD, I lean towards it being a driver issue with your setup. using cheapo cards like the linksys or Netgear ones can cause this. try and get a higher level card like a 3com 3c905c or intel card. I personally run the gigabit Netgear card with hardware offloading internally and a 3com WAN side and it runs with zero issue. -Sean - Original Message - *From:* Lance Peterson mailto:[EMAIL PROTECTED] *To:* support@pfsense.com mailto:support@pfsense.com *Sent:* Monday, September 03, 2007 2:28 PM *Subject:* Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM I'm a home user with a cable modem connected to a small firewall computer built up with one Linksys 10/100 card, one Netgear 10/100 card, and PFSense installed. I started experiencing connection problems with computers attached to this small network within 24 hours. I reloaded, reconfigured, started and stopped services, etc. and nothing permanently fixed my connection issues. Then I formatted and installed Smoothwall Express using all the same hardware -- problem solved -- no more lost connections. Definately seems like a PFSense problem, in my opinion. Sorry if this is a little off topic or already discussed, I just scanned though these replies and wanted to post my experience with lost connections. On 9/3/07, *Bill Marquette* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: On 9/2/07, Tortise [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Thanks Bill They are static IP's, so I assume (you may know better?) DHCP lease times are (or should be?) irrelevant. Not sure if this what you mean but this might answer? No worries, if it's static assigned and not a dhcp static assignment then you won't have the files I was looking for. Honestly not sure what else to look at here. This doesn't appear to be due to traffic inactivity. I'm not sure how any other system would work any better :-/ --Bill
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
I have two connections to Comcast through two different modems (their voip capable modem and their business modem - static IPs) at my house and have _never_ had an issue with the connection. The Comcast user with issues is likely a hardware issue. I'm not sure I have anything more to add to David's issue though - it's obviously not hardware. Question for Chris on the trace. Does it show the upstream router sending arp requests for the local IP and getting a response? Not sure if there's a way to force a gratuitous arp in FreeBSD without installing some third party tool like nemesis, but that might be worth looking at I 'spose. --Bill On 9/3/07, Sean Cavanaugh [EMAIL PROTECTED] wrote: David, sorry, I was referencing Lance in my response. Personally I am using a Dlink DCM-202 on my comcast service. I also have it set up at another persons house running on the small square ?motorola? cable modem with no issues (actually used it to replace a crappy linksys router) also on comcast but in a different county/service area. -Sean - Original Message - From: Tortise To: support@pfsense.com Sent: Monday, September 03, 2007 4:33 PM Subject: Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM Sean I guess you saw we've gone down that road, the cards I am currently using are in the subject line and would seem to be of the type you advocate, however perhaps you were inquiring the NIC types used by Lance? Are you also behind a Motorola SB 51xx cable modem? The fix I posted has now proven to perform the necessary rescue several times. It is such a refreshing change to be off site running a terminal session, to be cut out, and to know it will come back within a minute! (Assuming the issue is the one that is the subject of this thread!) Its not perfect but it is a significant advance! If I knew how to reference and extract the WAN driver type (e.g. em0) I could have the script fully cross machine, so it might then be considered for the image. So I don't have to add it in manually with every upgrade! Even if it is there so that the appropriate CRON line would only remain to be added or commented in. Kind regards David Hingston - Original Message - From: Sean Cavanaugh To: support@pfsense.com Sent: Tuesday, September 04, 2007 8:11 AM Subject: Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM considering smoothwall is based on linux whereas pfSense is based on FreeBSD, I lean towards it being a driver issue with your setup. using cheapo cards like the linksys or Netgear ones can cause this. try and get a higher level card like a 3com 3c905c or intel card. I personally run the gigabit Netgear card with hardware offloading internally and a 3com WAN side and it runs with zero issue. -Sean - Original Message - From: Lance Peterson To: support@pfsense.com Sent: Monday, September 03, 2007 2:28 PM Subject: Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM I'm a home user with a cable modem connected to a small firewall computer built up with one Linksys 10/100 card, one Netgear 10/100 card, and PFSense installed. I started experiencing connection problems with computers attached to this small network within 24 hours. I reloaded, reconfigured, started and stopped services, etc. and nothing permanently fixed my connection issues. Then I formatted and installed Smoothwall Express using all the same hardware -- problem solved -- no more lost connections. Definately seems like a PFSense problem, in my opinion. Sorry if this is a little off topic or already discussed, I just scanned though these replies and wanted to post my experience with lost connections. On 9/3/07, Bill Marquette [EMAIL PROTECTED] wrote: On 9/2/07, Tortise [EMAIL PROTECTED] wrote: Thanks Bill They are static IP's, so I assume (you may know better?) DHCP lease times are (or should be?) irrelevant. Not sure if this what you mean but this might answer? No worries, if it's static assigned and not a dhcp static assignment then you won't have the files I was looking for. Honestly not sure what else to look at here. This doesn't appear to be due to traffic inactivity. I'm not sure how any other system would work any better :-/ --Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
Hadn't thought about it being a FreeBSD problem with limited driver support for common home user NIC's. That very well may be the problem, in my case. Fortunately, I didn't have to buy new, higher level NIC's to get my Linux firewall up and running without connection issues. On 9/3/07, Sean Cavanaugh [EMAIL PROTECTED] wrote: considering smoothwall is based on linux whereas pfSense is based on FreeBSD, I lean towards it being a driver issue with your setup. using cheapo cards like the linksys or Netgear ones can cause this. try and get a higher level card like a 3com 3c905c or intel card. I personally run the gigabit Netgear card with hardware offloading internally and a 3com WAN side and it runs with zero issue. -Sean - Original Message - *From:* Lance Peterson [EMAIL PROTECTED] *To:* support@pfsense.com *Sent:* Monday, September 03, 2007 2:28 PM *Subject:* Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM I'm a home user with a cable modem connected to a small firewall computer built up with one Linksys 10/100 card, one Netgear 10/100 card, and PFSense installed. I started experiencing connection problems with computers attached to this small network within 24 hours. I reloaded, reconfigured, started and stopped services, etc. and nothing permanently fixed my connection issues. Then I formatted and installed Smoothwall Express using all the same hardware -- problem solved -- no more lost connections. Definately seems like a PFSense problem, in my opinion. Sorry if this is a little off topic or already discussed, I just scanned though these replies and wanted to post my experience with lost connections. On 9/3/07, Bill Marquette [EMAIL PROTECTED] wrote: On 9/2/07, Tortise [EMAIL PROTECTED] wrote: Thanks Bill They are static IP's, so I assume (you may know better?) DHCP lease times are (or should be?) irrelevant. Not sure if this what you mean but this might answer? No worries, if it's static assigned and not a dhcp static assignment then you won't have the files I was looking for. Honestly not sure what else to look at here. This doesn't appear to be due to traffic inactivity. I'm not sure how any other system would work any better :-/ --Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
Few ISPs (especially home users offers) reset their connection every 24h. I don't live in New Zealand, so I don't know Telstraclear Network, but are you really sure is it an equipment issue or a line problem (e.g. interferences, etc...)? If you can, try another cable modem. Bye! --- Tortise [EMAIL PROTECTED] wrote: I was not surprised that the Motorola 5100 cable modem on the Telstraclear Network in New Zealand also lost connectivity within the first 24 hours of operation. For pfSense the 5100 seems no more compatible than the 5101. Given there seem to be no reports of people having problems on other networks with these modems, what is it about the Telstraclear cable network? Kind regards David Hingston ___ Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
On 9/2/07, tester [EMAIL PROTECTED] wrote:
Few ISPs (especially home users offers) reset their
connection every 24h. I don't live in New Zealand, so
I don't know Telstraclear Network, but are you really
sure is it an equipment issue or a line problem (e.g.
interferences, etc...)?
If you can, try another cable modem.
I think you missed the first half dozen messages in this thread. The
cable modem has been replaced (and others on Telstraclear have had the
same issue apparently). Most likely it's some wierd dhcp lease
expiration or MAC expiration. Although, unlikely to be MAC expiration
if the icmp polling isn't keeping the mac tables fresh.
This is DHCP right? Check out /var/db/dhclient.leases.*
lease {
interface sis0;
fixed-address 24.1.x.x;
option subnet-mask 255.255.254.0;
option routers 24.1.66.1;
option domain-name-servers 68.87.72.130,68.87.77.130;
option host-name topell;
option domain-name hsd1.il.comcast.net.;
option broadcast-address 255.255.255.255;
option dhcp-lease-time 345600;
option dhcp-message-type 5;
option dhcp-server-identifier 68.87.72.44;
renew 2 2007/9/4 06:43:38;
rebind 3 2007/9/5 18:43:38;
expire 4 2007/9/6 06:43:38;
}
It'd be interesting to see what the lease times are.
--Bill
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
Thanks Bill
They are static IP's, so I assume (you may know better?) DHCP lease times are
(or should be?) irrelevant.
Not sure if this what you mean but this might answer?
$ ls /var/db/
entropy
ipsecpinghosts
pingmsstatus
pingstatus
pkg
rrd
Kind regards
David Hingston
- Original Message -
From: Bill Marquette [EMAIL PROTECTED]
To: support@pfsense.com
Sent: Monday, September 03, 2007 3:58 PM
Subject: Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1,
Intel Pro/1000GT NICs with 370M RAM
On 9/2/07, tester [EMAIL PROTECTED] wrote:
Few ISPs (especially home users offers) reset their
connection every 24h. I don't live in New Zealand, so
I don't know Telstraclear Network, but are you really
sure is it an equipment issue or a line problem (e.g.
interferences, etc...)?
If you can, try another cable modem.
I think you missed the first half dozen messages in this thread. The
cable modem has been replaced (and others on Telstraclear have had the
same issue apparently). Most likely it's some wierd dhcp lease
expiration or MAC expiration. Although, unlikely to be MAC expiration
if the icmp polling isn't keeping the mac tables fresh.
This is DHCP right? Check out /var/db/dhclient.leases.*
lease {
interface sis0;
fixed-address 24.1.x.x;
option subnet-mask 255.255.254.0;
option routers 24.1.66.1;
option domain-name-servers 68.87.72.130,68.87.77.130;
option host-name topell;
option domain-name hsd1.il.comcast.net.;
option broadcast-address 255.255.255.255;
option dhcp-lease-time 345600;
option dhcp-message-type 5;
option dhcp-server-identifier 68.87.72.44;
renew 2 2007/9/4 06:43:38;
rebind 3 2007/9/5 18:43:38;
expire 4 2007/9/6 06:43:38;
}
It'd be interesting to see what the lease times are.
--Bill
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
I was not surprised that the Motorola 5100 cable modem on the Telstraclear Network in New Zealand also lost connectivity within the first 24 hours of operation. For pfSense the 5100 seems no more compatible than the 5101. Given there seem to be no reports of people having problems on other networks with these modems, what is it about the Telstraclear cable network? Kind regards David Hingston - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
I think we may have got this fixed, (all be it as a Kludge?) Essentially the fix is to ping the static IP's first hop, if this is down then flick the WAN NIC state down and up, this restores the lost connection where the motorola 5101 has stopped sending packets (presumably for some incompatibility reason) The motorola 5101 has today been replaced with a 5100, the ISP tell me most commercial lines are running the 5100 as they say it is more router compatible than the newer 5101. I'll advise if the 5100 exhibits the same behaviour(!) however if it does the following should address it within a minute. If you are copying it be sure to copy it exactly as spaces in the wrong place stuff it upetc!! For both the lists and my record it is done by: = in /etc/crontab add */1 * * * * root /usr/bin/pinger.sh = from edit.php create / write into new file /usr/bin/pinger.sh #!/bin/sh ping -c1 Insert_1st_Gateway_Hop_Here_commonly_Static_IP_a.b.c.1 if [ $? -eq 2 ]; then ifconfig em0 down ifconfig em0 up echo 'Gateway Down' else echo 'Gateway Up' fi = from exec.php run chmod u+x /usr/bin/pinger.sh = from exec.php run ls -l /usr/bin/pinger.sh and check there is an x in the file permissions (for executable) It will have run when you see a log series of commands starting with Sep 1 11:32:13 kernel: em0: link state changed to UP Sep 1 11:32:11 kernel: em0: link state changed to DOWN The only problem I see with this approach is that whenever the Internet is down for whatever reason the WAN interface is going to be disconnected and reconnected every minute, as well as filling the logs with this info, but that seems only of concern from the perspective of filling the log with rubbish. I might tinker with it to send me an email to advise me when the code has also run . Whilst we could have changed to a different router (non freebsd) I really like the pfsense and its monowall heritage, and wanted to give back something by solving this problem in some sort of gratitude and small contribution, I hope this helps someone and goes in some small way to contribute to what is a great piece of software - and the leaders and community behind it. Thanks to Vivek, Sean, Bill, Raj, Paul and others also! Kind regards David Hingston - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
Thank you Paul We are awaiting the ISP replacing the cable modem. I think your suggestion is interesting but probably not the explanation in our case. A number of people have tried multiple NIC's on different hardware (myself included) and still experienced the same problem. If the replaced modem does not fix the problem I will however try anything! Kind regards David Hingston - Original Message - From: Paul M [EMAIL PROTECTED] To: support@pfsense.com Sent: Tuesday, August 28, 2007 10:28 PM Subject: Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM Tortise wrote: Buy hardware that's not faulty. pfsense is *way* more robust than what it seems to be for you. what network interfaces do you have? if other than broadcom or Intel, switch to Intel. In frustration I have purchased 2 new Intel Pro/1000GT NIC's. They have lasted almost 48 hours before the internal disconnection between the LAN and WAN recurred yet again. The state table is reported as having showed 56 entries on index.php. Fixed by rebooting. Nothing else. (Cheaper cards have lasted longer!) we had a lot of problems with linux drivers and the intel giga nics onboard our tyans; we turned off power management in the intel's eeprom. maybe the same problem affects freebsd? the script to fix it is here: http://e1000.sourceforge.net/wiki/index.php/Issues#82573.28V.2FL.2FE.29_TX_Unit_Hang_messages to use this fix on our pfsense box, I booted a linux rescue disk (suse 10.2 cd 1 as it happened) and downloaded and ran the script mentioned here: this might or might not help... good luck! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
Dear List
Until we find a permanent solution it seems I may be able to do a temporary fix.
Firstly I note that during a download I can run
ifconfig em0 down; ifconfig em0 up
without apparently interrupting the download! This fixes the problem - until
it occurs again. Looking around (using Google and
Diagnostics: Edit File ) it seems I may be able to edit this file /etc/crontab
thus:
{start}
SHELL=/bin/sh
PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin
HOME=/var/log
#minute hourmdaymonth wdaywho command
#
#
# pfSense specific crontab entries
# Created: August 26, 2007, 7:50 am
#
0 * * * * root /usr/bin/nice -n20 newsyslog
1,31 0-5 * * * root /usr/bin/nice -n20 adjkerntz -a
1 * 1 * * root /usr/bin/nice -n20 /etc/rc.update_bogons.sh
*/60 * * * * root /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600
sshlockout
1 1 * * * root /usr/bin/nice -n20 /etc/rc.dyndns.update
*/60 * * * * root /usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600
virusprot
*/60 * * * * root /usr/bin/nice -n20 /usr/local/sbin/expiretable -t 3600 snort2c
*/5 * * * * root /usr/local/bin/checkreload.sh
*/5 * * * * root /etc/ping_hosts.sh
*/300 * * * * root /usr/local/sbin/reset_slbd.sh
#DH Addition Start
# Hopefully his will run every minunte
#ping returns 1 when successful
#run ping to the first hop gateway (a.b.c.1) , if it fails run the fix...
*/1 * * * * root if (ping -c1 a.b.c.1 != 1) then ifconfig em0 down; ifconfig
em0 up endif
#DH Addition End
#
# If possible do not add items to this file manually.
# If you do so, this file must be terminated with a blank line (e.g. new line)
#
{end}
Is this correct syntax? Can I just paste it into the window and save it?
Anything else needed?
The immediate goal here is to be able to continue remote terminal sessions and
keep the site up! (Or be able to log back in within
a minute, instead of having to wait maybe hours until someone is on site to fix
it...)
Any guidance would be greatly appreciated.
Kind regards
David Hingston
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
On Aug 29, 2007, at 6:20 AM, Tortise wrote: we had a lot of problems with linux drivers and the intel giga nics onboard our tyans; we turned off power management in the intel's eeprom. maybe the same problem affects freebsd? I've not had any issues with Intel NICs across several dozen FreeBSD systems of varying vintage (from the 10/100 fxp devices thru the 1Gb em devices). Broadcom NICs on the other hand have been mostly nothing but trouble until the most recent FreeBSD releases. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] LAN / WAN Disconnections continue in 1.2-RC1, Intel Pro/1000GT NICs with 370M RAM
Tortise wrote: Buy hardware that's not faulty. pfsense is *way* more robust than what it seems to be for you. what network interfaces do you have? if other than broadcom or Intel, switch to Intel. In frustration I have purchased 2 new Intel Pro/1000GT NIC's. They have lasted almost 48 hours before the internal disconnection between the LAN and WAN recurred yet again. The state table is reported as having showed 56 entries on index.php. Fixed by rebooting. Nothing else. (Cheaper cards have lasted longer!) we had a lot of problems with linux drivers and the intel giga nics onboard our tyans; we turned off power management in the intel's eeprom. maybe the same problem affects freebsd? the script to fix it is here: http://e1000.sourceforge.net/wiki/index.php/Issues#82573.28V.2FL.2FE.29_TX_Unit_Hang_messages to use this fix on our pfsense box, I booted a linux rescue disk (suse 10.2 cd 1 as it happened) and downloaded and ran the script mentioned here: this might or might not help... good luck! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
