Netgate sold you a FW-7535 with a CF card and either 1MB or 2MB of ram, originally.
You changed the ram and installed an SSD, reloaded pfSense, and now you want to complain that Netgate couldn’t… what, exactly? There are thousands of FW-75xx systems in the world, happily running pfSense. The problems we have tend to develop when people assume they know better about what the machine can support, and start treating it like a garden-variety PC. It’s not. It shares the Intel architecture, sure, but it’s an embedded system, with attendant requirements (mostly environmental) that no PC would deal with for long. I actually know that the replacement unit you received was running (“in service”) between two fiber connections. The one you received was one of the last remaining 7535s(*), in something like mint condition, which we could lay our hands on. It was pulled from a live environment, put back through the factory load process, and shipped to you. It goes without saying that there was no “packet corruption” evident when it was last in-service here. I, for one, would be curious to know if the ‘corruption’ which you accuse recurs with the original, as-shipped configuration. Jim (*) Another choice was to take the 7535 we have running Asterisk (FreePBX), and refurbish it to factory fresh. On Sep 29, 2013, at 7:45 AM, [email protected] wrote: > I finally was able to receive an advanced replacement from Netgate a few > weeks ago. I swapped it out leaving my old install intact and the problem > disappeared on the new device. After all the installs with the various > Netgate FW models over the years (not the m1n1wall, those have been awesome > but are too outdated for me to be using on 100meg+ internet), Their > reliability has been lacking and the issues that arise are always hard to > diagnose and prove (freezing, no response situations, corrupting packets). I > think I am just going to give up a few Ethernet ports that I don't end up > using anyways and start building my own. > > Jonathon > > On 8/20/2013 11:08 AM, [email protected] wrote: >> I switched out the memory and the SSD, reinstalled pfsense, and after a few >> weeks of operation, VPN traffic started corrupting again. >> >> A soft reset doesn't fix it. >> A hard reset (by pulling the power cord for a few seconds) does. >> >> I tried contacting Netgate and didn't receive a response. >> >> Does anyone know what could be going on here? >> >> Thanks, >> Jonathon >> >> On 7/26/2013 9:04 AM, [email protected] wrote: >>> Scanned the memory with memtest this morning and scanned the Intel SSD as >>> well, it's all fine. >>> >>> I did stumble across something that fixes it though. Pulling the power cord >>> for a few seconds. The act of removing power from my Netgate FW-7535 caused >>> everything to start working. I probably soft reset it from the console 10 >>> times and kept getting corrupted OpenVPN connections until I actually >>> pulled power from the thing. >>> >>> I am starting to lean towards something on it's motherboard being >>> defective. I will switch out the memory and SSD in a few days just to make >>> sure it's not them. >>> >>> Thanks, >>> Jonathon >>> >>> >>> On 7/25/2013 6:25 PM, Bob Gustafson wrote: >>>> >>>> On 07/25/2013 04:59 PM, [email protected] wrote: >>>>> The last few months I have been having issues with OpenVPN connections >>>>> from my road warriors. It appears that most of the traffic crossing the >>>>> link is corrupted. I can't use remote desktop, it always says "because of >>>>> an error in data encryption, the session will end". I can't use the >>>>> company intranet, it always displays the pages corrupted or doesn't load >>>>> them at all. What do I mean by corrupted? See how it butchered the page >>>>> load of the pfSense web admin interface. >>>>> >>>>> http://imgur.com/3B6EAAT >>>> >>>> This doesn't look too bad. I am assuming that you have sliced out the data >>>> for security purposes - or is that the corruption? >>>>> >>>>> All of this obvious data corruption and not a single peep in the logs. >>>>> Nothing, nowhere. I have 20 installs and this is the only one that has >>>>> ever given me an issue like this. Does anyone have any ideas? >>>> >>>> Are you saying 20 installs on different hardware, or 20 installs >>>> sequentially over several months/versions on the same box. >>>> >>>> If 20 on separate boxes, I would do a memory test on the failing box. >>>> >>>> Bob G >>>> >>>>> >>>>> Thanks, >>>>> Jonathon >>>>> _______________________________________________ >>>>> List mailing list >>>>> [email protected] >>>>> http://lists.pfsense.org/mailman/listinfo/list >>>> >>>> _______________________________________________ >>>> List mailing list >>>> [email protected] >>>> http://lists.pfsense.org/mailman/listinfo/list >>> >> > > _______________________________________________ > List mailing list > [email protected] > http://lists.pfsense.org/mailman/listinfo/list _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
