Seriously, whats the secret to getting this working
-
If you are looking for changes to make to pfSense to stop the behavior you are describing there are none because it doesn't behave like that. There is some other problem with your environment at play.
-
You're doing something grossly wrong. The fact it's doing the same thing across multiple hypervisors that many of us use widely further points to that. Maybe putting WAN and LAN on the same subnet, which would result in intermittent and potentially unpredictable networking results (with anything). Whether or not ping works isn't necessarily telling at all when you screw up networking like that, ping can work where TCP gets out of state traffic messes from the conflicting networks.
-
If you are looking for changes to make to pfSense to stop the behavior you are describing there are none because it doesn't behave like that. There is some other problem with your environment at play.
Ahh yes it does behave like that, so id really like it if you didn't call me a liar on top of trying to seem superior…
And it even behaves as ive described in VMware where its detected and profiled to be hands off in configuring....so theres that
I don't just turn up on random It boards at 6am after a 20 hour day to get my jollies inventing things that aren't actually happening....
Give me some respect....ive probably been doing this twice as long as you have...
-
@cmb:
You're doing something grossly wrong. The fact it's doing the same thing across multiple hypervisors that many of us use widely further points to that. Maybe putting WAN and LAN on the same subnet, which would result in intermittent and potentially unpredictable networking results (with anything). Whether or not ping works isn't necessarily telling at all when you screw up networking like that, ping can work where TCP gets out of state traffic messes from the conflicting networks.
Nope, I was being careful, therefore after the first occurrence I isolated the subnets…same effect.
Im really not kidding folks, its bonkers
I notice a lot of people have had issues with 2.2.6, if you just want to tell me form your own experience or your longer exposure here what is the most stable version, ill be on my way...
-
Perhaps you should just get a UTM. 2.2.6 is the most stable version available.
I've been doing this since you had to set the jumpers on the card when adding hardware too. Sometimes things go wrong for a variety of reasons. If they didn't they would only need the people who answer the phones and ask you to reboot your computer and try again. How did you expect your reception to be when you come into an enthusiast forum and take a piss? I'm not trying to insult you, but you don't have a problem insulting everyone else who says the software works well for them and is not a buggy mess. You think you've ruled out everything but pfsense, but I've installed it hundreds of times and only had problems when I had bad hardware, a problem with the network, etc. Sometime it helps to step back, try an install on a physical machine hooked up to a laptop for the config, then connect it to the network, or try virtual. You could also try giving some more detailed information- is it just the webgui? can you ping the box? any errors?
EDIT- Make sure your install media is good. -
2.2.6 is perfectly fine. There are no such problems in it, and certainly aren't many people having issues. It really is as simple as that. There are tens of thousands of systems running just that particular version.
We're building 2.3-RC at this moment, if you want to grab something different, the most recent snapshot from snapshots.pfsense.org probably won't be far from RC or final release.
-
I'v installed pfSense 2.1.3 - 2.2.6 on ESXi, VmW and Virtualbox. It works fine. It's either your config or your environment. Unfortunately we have no details whatsoever to work with other then your general complaints so there isn't a whole lot we can do at the moment.
-
Do you start encountering problems from the get-go or only after installing Squid? What about if you unplug the WAN cable, is it still unreachable? Can you ping the router and telnet into it when you can't get into the GUI?
-
If you are looking for changes to make to pfSense to stop the behavior you are describing there are none because it doesn't behave like that. There is some other problem with your environment at play.
Ahh yes it does behave like that, so id really like it if you didn't call me a liar on top of trying to seem superior…
And it even behaves as ive described in VMware where its detected and profiled to be hands off in configuring....so theres that
I don't just turn up on random It boards at 6am after a 20 hour day to get my jollies inventing things that aren't actually happening....
Give me some respect....ive probably been doing this twice as long as you have...
With all due respect, I think you need to take a deep breath and step back a bit to clear your head of your obvious frustration and try not to bite back at the people who are trying to help you. There are many people who have no trouble installing PFS setups like yours - many on this forum - so despite your own years of experience it may do you some good to try being more pragmatic and little less shouty. From what I can see, nobody is questioning your professionalism - they're simply stating what is fact, nothing more.
-
So do you have other OSes on this VM setup without any issues. How exactly do you have the networking setup? Out of the box VB and vmW like to NAT your connections vs just bridging them to your actual physical interface. if your having connectivity issues to pfsense, can tell you its not pfsense. The only issues I have seen anything sim to yours is when usnig Xen/KVM and vmx3 drivers..
https://forum.pfsense.org/index.php?topic=88467.0
There are plenty of people here with just as much if not longer experience as you.. I myself have been paid in the field for 25+ years, and and been play/working with computers for 35+ Remember when got first TRS80, and before that having to walk to the library to use the PET, typing in programs via machine code from a magazine and then saving them on cassette, etc.
What I can tell you is pfsense is rock freaking stable, even on a VM.. So clearly you have something wrong in your setup/network/hardware..
Been running different versions of pfsense on esxi and other played with it on VB, its been solid on esxi since back with version 5 for sure.. So that was 5, 5.1 and then 5.5 and now 6 with all the different updates inbetween, etc. Before that ran pfsense sense on hardware.. I have never once had any sort of stability issues with it.. It runs and runs and runs until you reboot it or your hardware crashes..
-
Something that always works - and will make you more confident to make it work:
Do NOT use VM …. install (even temporally) pfSense on a dedicated device.
You'll will belong very quickly to 100 000++ users that made pfSense work in less then 5 minutes.
(and : bonus : you will have this positive feeling that [pfSense] is a go, and [pfSense in VM] is a no go, so you will be very motivated to find out why it will not work you right now - knowing that [pfSEnse] works ;)) -
While I agree he should take VM out of the mix to prove to himself that its not a pfsense thing.. I can assure you pfsense works on multiple flavors of VM just fine..
I also agree with the less than 5 minutes statement.. If its taking you more 10 min tops your doing something wrong that is for sure.. It really is turn it on, and it just works!!
-
…. I can assure you pfsense works on multiple flavors of VM just fine..
Well, I know. Probably thousands do so already. But I never did that myself. :)
-
personally i find it easier to run it on a hypervisor, in the sense that it eliminates the need to run on freebsd-compatible-hardware.
hypervisors tend to work well with any server-class hardware you throw at it …. freebsd tends to be a lot more picky ;) -
To all the superiorities…
I gave it another 5 goes at installing
On the last attempt at installing it finally worked, and continues to work...after a fashion
What did I change between install attempts? absolutely nothing
And I still maintain its buggy as quite often I get no response from the webgui - cant login (nothing to do with routing as the IP's are static and the route never changes), and at the same time squid fails to response (note the weblogin issue was one that I reported initially, and was apparent in of itself and not linked to squid being installed)
I have squid/squidguard and clamav all working fine...when it works. You cant "get it wrong" and have it working perfectly for up to 2 hours at a time with user config errors
Logging into the console and choosing 11 - restart web configurator does nothing to resolve the login issue
What does work is dropping to a shell and issuing:
./rc.restart_webgui
and
./rc.restart_reload allThen I can get an hour or two out of it before the issues reappear
Currently posting via a currently working pfsense.....
So there goes all the "you must doing something wrong" comments
Obviously its not a long term proposition, ill go back to my separate squid box, never been down a day in 4 years.
I stand by my original comment, it has bugs
-
To all the superiorities…
...
I stand by my original comment, it has bugsIf you've wanted to let off some steam about your being unable to get a properly working firewall up and running, then you've done sterling work. If you actually wanted some assistance in getting to the bottom of the issues you've faced, you've sadly failed. You've provided little or no technical information about your setup and ignored every bit of advice you've got so far, yet have railed about the instability of the OS you're using while being defensive about your professionalism and having a go at people who've tried to help.
If you are serious about wanting to know what the actual problem is, then provide some real information (VM details, such as memory being used, disk partition sizes, number of CPUs, VM host environment, etc) instead of ranting about the number of failed installation attempts you've made and calling anyone who makes a suggestion an elitist or something.
-
Hmmm lets see 1000's upon 1000's of installs, in less than 5 minutes for the vast majority of them. You without giving any details of what hardware, or what configuration of what VM software are having problems.. I can not get to the gui sometimes.. Can you ping it? Do you show mac in your arp table? What doe VM software show for the status of the VM? Can you get to the console via the VM software, via this console what does pfsense say about its networking and status?
All your years in the field - yet you can not provide the basics to troubleshooting a problem.. You just keep reinstalling… What exactly are you doing different in these installs that you think it will make a difference? Whats the saying about repeating the same thing and expecting different outcome ;)
But sure you go right ahead and stand by your claim that pfsense is just bug ridden.. Guess its true we must all be superior since we are not having any issues, and clearly you have given us so much to go on in helping you, we are just all asshats for not showing you the secret hidden button you have to click for it to work..
Let me sum up your info given. Your trying to install 2.2.6 on either vmware workstation or virtualbox. Yup there you go - that is all the info you have given us. How can we not see that its pfsense is just a buggy pos.. How blind we are.
So is that version 32 or 64 bit version? Actual live install or one of the nano images? What versions of vmw or vb, guess we assume latest?? What hardware?? Mac, PC, some DIY - what CPU in it?? What OS and setting did you pick when creating the virtual machine? etc. etc. etc.. Did you let it run for a few minutes without installing packages like squid?? Is that when it goes bonkers after you squid install?? We don't even know if your wired or wireless, etc.
So all these years in IT, guess you just turned shit off and on again was the limit of your troubleshooting?? And if that didn't work - what you would call said products tech support, and yeah your products not working.. Buggy POS.. Yes I tried reinstalling it a 100 times.. Its broke...
Fing Troll is my assumption to this whole thread.
-
Fing Troll is my assumption to this whole thread.
I second that. I also think it's best that anybody on this forum ignores any further nonsense spouted by this particular 'professional'. Unless, that is, he decides to start behaving professionally and not like some two-year-old throwing his rattle out of his pram.
-
@johnpoz, you probably knew this already but for others here a refresh to your question.
Albert Einstein definition of insanity: doing the same thing over and over again and expecting different results.
It is at times like this I miss Doktornotor and his eloquent style of reply.
-
I stand by my original comment, it has bugs
Its just the loose nut behind the wheel!
::)
