Original LAN ip range not working VM traffic workd
-
I'm a network engineer and software engineer I know all this. I think I hit a bug in the web configuration.
-
@geramyl said in Original LAN ip range not working VM traffic workd:
I think I hit a bug in the web configuration.
Sorry but no... I ran pfsense on esxi for years... And currently run it test vms on multiple other platforms, etc. Pfsense sure and the hell does not set your lan for dhcp out of the box either... If you mean it will turn on the dhcpd on your lan after it asks you sure.
-
I don't give a shit about what it's supposed to do. Let's go over what it's not doing please and not waste time talking about what is and what is not.
-
Just because you had the opportunity to run it for a long time and I have too in other places does not mean you have had the opportunity to hit a bug.
-
Good freaking luck getting any help with that attitude ;)
Please provide some actual freaking info! Step through the doc you have been given and answer the questions and we will for sure find out where you F'd up mister network engineer ;)
we are not freaking mind readers
I try to leave the gateway to internet via the 10.11.1.xxx range it won't work.
how does that help us help you? It tells us NOTHING!
-
I can provide access to the config.
https://drive.google.com/a/jqluv.com/file/d/1-BevWnlRvxbj-PN3DShFSXnJMc_OXfMX/view?usp=drivesdk -
@geramyl If you're a network engineer who knows all this stuff, then you should have no problems figuring it out on your own. However, as @johnpoz pointed out, there is no general bug or issue with regard to using pfSense in a virtual environment. I've been running virtually for 6 years, currently on ESXi 6.7.
-
Thanks kom so I am also having networking issues with basic port forwarding to my lan interface, mind you I could have made a simple mistake it happens but I don't believe so. And I appreciate your help. Just not when someone tells me bugs don't exist. Bugs exist everywhere. I came here for help not too be mindlessly told I'm wrong. With no thought or reasoning, but I've used pfsense for years. That's not a reason.
-
I was hoping I could get a person who has more experience reading the xml config than I do and can pinpoint the issue. If anyone here would like to help me with that i would really appreciate it.
It's on my drive and when requested access I'll grant it. I do think I hit a configuration bug at the start of the install and it's lingering in there or pfsense kernel is not playing nice "freebsd" with my hypervisor Hyper-V I have a huge amount of experience with freebsd and am a ath10k developer for the freebsd distro. -
The reason is if there was a bug in the web gui for running pfsense on vm - the boards would be full of posts about them... There would be redmine about it... Kind of hard to believe there is a bug when only info is this
I try to leave the gateway to internet via the 10.11.1.xxx range it won't work.
And then wrong info about how pfsense sets your lan to dhcp - it sure and the F does not do that..
Good luck finding anyone willing to go through your xml - how about you post a couple of simple screenshots for the config..
-
Johnpz I'll start with the intent of I'll install a new pfsense later with a wan and lan where there is already a router on lan and then I'll see if it does again, I could be wrong this was 2am but I don't think I am. Anyways I posted the config. I'm sorry we have different opinions but everything is relevant to setup and environment I might be on the one update no one else is with a hyperv kernel patch that not a lot of people have that could cause an issue like this,not likely but it's also not very friendly to start out your wrong. That's all. And I agree there should be a bug report if this was wide spread.
-
Literally nobody is going to go through your config.xml. Do as @johnpoz asks and post screens of your WAN config (with public details like its IP address obscured) and you LAN config. You haven't said how you have it all connected in ESXi. What vswitches are you using? Which NICs are they mapped to? Etc etc etc.
-
I stated hyperv but it's fine let's just close this thread, there are ton of issues in this build I'm going to start fresh. Was trying to move from opnsense because it was unstable but this isn't any better I hope it was just one bad install. Also I want expecting someone too look for free, I don't have time to deal with this, I'll pay.
-
@geramyl said in Original LAN ip range not working VM traffic workd:
I don't have time to deal with this, I'll pay.
Here you go
https://www.netgate.com/support/I might be on the one update no one else is with a hyperv kernel patch that not a lot of people have
Impossible to know since you have not given any info at all to your setup.. Took you what like 9 posts before you even mention hyper-v.. What version even?
You would think a software eng would know how to document information if they feel they have found a bug..
-
@johnpoz I didn't come here to file a bug I came here to throw out some information and get some friendly feedback. It's like when you talk to your coworker and they say hey I've had that happen try looking here. They don't say sorry that's not possible. But I won't argue on this board with you. Thanks for the help I won't ever be posting on this forum ever again, it's about as helpful as a irc full of trolls well except kom. He was friendly.
-
@geramyl Conceptually, there is not much difference between Hyper-V and ESXi. However, in real life it seems that more people have issues with pfSense on Hyper-V then with VMware.
If you still want help, then please post what I asked for in my second reply. At the very least we can rule out any mistakes you might have made in pfSense. Anything after that is Hyper-V territory.
-
@KOM okay when I get the opportunity I will post that, I think I'm going to leave this pfsense VM a live just because I want to track down the real issue. Yeah I've seen a lot more users having issues with hyperv I agree.
