Port 1024 - 1025 Flood = Connection Loss?
-
Why are you obfuscating the source address?
If you control that host go there and figure out what is doing it and make it stop.
Nothing about what you are seeing should cause any connectivity problems. Especially with logging off.
Unless that is just a representation of what is actually thousands of connection attempts per second.
-
Why are you obfuscating the source address?
If you control that host go there and figure out what is doing it and make it stop.
Nothing about what you are seeing should cause any connectivity problems. Especially with logging off.
Unless that is just a representation of what is actually thousands of connection attempts per second.
The source address is my IP address which is what makes it so weird, it looks like my pfSense is trying to connect to my MoCA? (My IP going into my pfSense WAN IP being 192.168.1.3) I'm not sure what's causing it at all.
When I had my pfSense running on it's own hardware a few months back it had no issue like this, I'm using the same NIC now and the same MoCa with the same configs. I'm not sure what it is at this point, I'll reinstall pfSense again later to see if that fixes it though.
-
Sounds like you might have some sort of loop.
-
You know what I would believe that, I have all of my network interfaces on my ESXI set to VLAN ID 0 which I wondered about, I set LAN to 4095 like the wiki said. Would I set my Server Network to the same VLAN ID as LAN or would it be something below it?
Thanks!
-
" I set LAN to 4095 like the wiki said."
What wiki? Yes you would need/want to set your vswitch to that if your going to be sending tagged traffic to the VMs connected to that switch.
How exactly are you all connected? Im with Derelict here sure looks like you have a switching loop, or not actually a loop lack of isolation and or running multiple layer 3 networks over the same layer 2..
A drawing of your actually connected hardware and how that is tied to your vswitches and we can figure out what is not right.. If your doing vlans, you have a smart switch right? How it is configured?
-
" I set LAN to 4095 like the wiki said."
What wiki? Yes you would need/want to set your vswitch to that if your going to be sending tagged traffic to the VMs connected to that switch.
How exactly are you all connected? Im with Derelict here sure looks like you have a switching loop, or not actually a loop lack of isolation and or running multiple layer 3 networks over the same layer 2..
A drawing of your actually connected hardware and how that is tied to your vswitches and we can figure out what is not right.. If your doing vlans, you have a smart switch right? How it is configured?
I honestly have no idea where I saw the 4095 thing, I thought I clicked the wiki but I guess I didn't. I was half awake while typing that.
I hardly understand VLANs, would this cause a loop? The VSWitches all have the same settings as each other too. Could this be the issue?
Thanks!
-
What about the real connections?
So are you running vlans on your lan vswitch1 on the vms that are connected? Where does that go in the physical world?
Are you running a vlan on your server with the ID of 4094.. Why do you think you need to set that on the vswitch? Again how is that connected to the real world? What switch(es) are connected - how are they configured for vlans. Running 4095 would tell me that is a Trunk connection with all your other vlan running on it..
-
It's hooked up in the real world like this:
MoCA (192.168.1.3) –> WAN Port of my NIC --> LAN NIC --> My LAN switch for my computer
My server network (Vlan ID of 0 now) is virtual, it doesn't hook into any switch but is just there for my VM's to run on, it doesn't hook into anything physically.
The virtual switches are setup the same, all of them are setup like the default vswitch0.I noticed that my internet speeds have also tanked, I used to get 90~ mbps now I get 3mbps and lucky moments is 20mbps on my download.
-
I noticed that the loop destroys even my MoCA that is giving it internet. It loops straight back into my MoCA and shuts it down, cuts everyone off the network even who aren't connected through pfSense.
-
It turns out it was neither pfSense of eSXI, my MoCA was the problem. The NAT tables were too small or something because it'd spit out a bunch of NAT errors and flush the state table. I'm bridging the MoCA to pfSense to try and fix this. Thanks for the help, this post could help somebody else in the future.
