loopback address being blocked?
-
do you have a route for loopback?
example
[2.4.5-RELEASE][admin@sg4860.local.lan]/root: netstat -rn | grep 127 127.0.0.1 link#7 UH lo0 [2.4.5-RELEASE][admin@sg4860.local.lan]/root:
There is mine..
That error in curl
Immediate connect fail for 127.0.0.1: Can't assign requested addressCan you ping localhost?
[2.4.5-RELEASE][admin@sg4860.local.lan]/root: ping localhost PING localhost (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.128 ms 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.063 ms
-
I can’t ping localhost:
Netstat results:
-
it's in the wrong interface
127.0.0.1 link#4 UH lo0should be lo0, not vmx0
idk how you ended up with something like this -
Yeah that is clearly Borked!!
-
Borked it is! I can see how to assign all other interfaces. Anyway to reassign the loopback?
-
Never seen such a thing.. Some weirdness with interfaces being re-arranged when interfaces added in esxi maybe?
I don't know how you would re-assign that to be honest.
I would start over with new VM..
-
That’s what I figured. I just backed up all my configurations and began setting up the new VM. It’ll have to wait for tonight because work from home and schooling from home. We need the internet for the day. I’ll let you guys know how it works out. Thanks for the help!
-
I would double check your lo0 assignment before you get to far into the config ;)
-
Are you taking about on the new VM? If so, that was my going to be step one.
-
Yeah on the new vm ;)
Do you have any other VMs running on this host that you could look to see how the lo0 is assigned?
-
I simply rebooted the pfsense VM and the loopback was reassigned to lo0. What a headache for apparently no reason!
-
I would of assumed you had done that already ;) When it wasn't working the first time?
-
Unfortunately no. I rarely if ever need to restart that VM. It’s uptime was 172 days prior to my restart.