This repository has been archived by the owner on Feb 28, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 99
Issues in connecting to IPv6 TacacsPlus server #99
Comments
Is there a PR that goes with this? |
Thank You for your quick reply. No, i have not yet raised. I am just trying to test this code. |
Hi, I have fixed this issue.
thank you. |
Now is there a PR? |
fnc-bmh
added a commit
to fnc-bmh/pam_tacplus
that referenced
this issue
Sep 10, 2018
IPv6 Fix Test PR (Issue kravietz#99)
kravietz
added a commit
that referenced
this issue
Jan 14, 2020
Add check for ipv6 support (Issue #99)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi Team,
Just wanted to know if there are any open known issues in connecting to IPv6 Tacacs servers.
I have observed issues in connecting to IPv6 server.
Hence added the below fix:
file: support.c
function: tac_copy_addr_info
code modified:
removed the below line:
memcpy (p_dst->ai_addr, p_src->ai_addr, sizeof(struct sockaddr));
added below checks:
with the above changes, authentication works correctly.
But accounting does not work.
Issue:
Ipv6 address copied in to "active_server" seems to be getting junk characters in pam_sm_acct_mgmt.
for example, if we set the Tacacs server address as : 2001:DB8:0:1::9
In pam_sm_authenticate function, code can get and connect to active server;
but in pam_sm_acct_mgmt, code fetches this address as " 2001:db8:0:1:6970::9", hence connecting to server does not work.
not sure, how this extra "6970" got introduced into active_server.
Below is the error:
tac_connect_single: connection failed with 2001:db8:0:1:6970::9:49: Transport endpoint is not connected
is there any known issues and fixes for this issue ?
Thank You.
The text was updated successfully, but these errors were encountered: