Project

General

Profile

Actions

Bug #9000

closed

Haproxy does not send ipv6 traffic to backend after updating to Pfsense 2.4.4

Added by Anonymous over 5 years ago. Updated over 5 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
10/03/2018
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
amd64

Description

After the update, the accesses from ipv6 addresses do not work in any case. Before the update worked perfectly.

Access from ipv4 addresses without incident.

Actions #1

Updated by Pi Ba over 5 years ago

Works for me.. at least with current version:

pkg info | grep haproxy
haproxy-1.8.14                 Reliable, high performance TCP/HTTP load balancer
pfSense-pkg-haproxy-devel-0.59_13 pfSense package haproxy-devel

You probably used a slightly older version, but there is no reason for me to think it didn't work with that.

Actions #2

Updated by Jim Pingle over 5 years ago

  • Status changed from New to Not a Bug
  • Priority changed from Urgent to Normal

Judging by this person's other reported issues, they have some general config/environment problem wholly unrelated to HAProxy, so it probably isn't a bug.

Actions #3

Updated by Anonymous over 5 years ago

Jim Pingle wrote:

Judging by this person's other reported issues, they have some general config/environment problem wholly unrelated to HAProxy, so it probably isn't a bug.

i have some pfsense configurations, the other report refers to a virtualized environment. this is on a dedicated machine, asrock motherboard & cpu combo j3455b-itx. i could give more details if i saw any interest, but it's useless.

it turns out that the configuration i have for two years and with this board for 6 months and has worked haproxy well with direction wan ipv4 and ipv6.

only when doing the update to pfsense 2.4.4 this problem arose and only with haproxy in this hardware environment, everything else works.

the reports that i have made are absolutely real and serious, could give more data if requested, but in this as in the other report has only been closed with the indication that it is not a bug. it is possible that it is a problem with certain hardware environments that is presenting freebsd and / or pfsense, those things usually happen, but you have to investigate them, if you do not want to do it, i can not do anything.

my version of haproxy was this:

pkg info | grep haproxy
haproxy-1.7.11 Reliable, high performance TCP/HTTP load balancer
pfSense-pkg-haproxy-0.59_11 pfSense package haproxy

i just updated to the version that has pi ba and the same thing happens. the current version is this:

pkg info | grep haproxy
haproxy-1.8.14 Reliable, high performance TCP/HTTP load balancer
pfSense-pkg-haproxy-devel-0.59_13 pfSense package haproxy-devel

finally i would like to delete the two reports, because i do not see any sense in remaining if they already judged about it and do not want to investigate. i did not manage to delete them from my user, but maybe you can do it. i would appreciate it. i will look for other solutions, maybe you opnsense

my native language is spanish, i am using an online translator.

thank you

Actions #4

Updated by Jim Pingle over 5 years ago

You should post on the Spanish language category of the forum -- https://forum.netgate.com/category/11/espa%C3%B1ol

We're not saying you don't have an issue, only that nobody else can seem to reproduce it, so it appears to be specific to your configuration and/or environment and not a bug. Just because it worked before and doesn't work now that doesn't make it a bug. This ticket system isn't the place to discuss and diagnose issues, however, so you can post to the forum and have others help get to the bottom of what your problem may be.

Actions

Also available in: Atom PDF