Project

General

Profile

Actions

Bug #3434

closed

widentd

Added by lynn wilborn over 10 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/04/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

pfSense 2.1, 64bit, widentd 1.03_1

The 'Listening interface' selections don't work the way I expect. I'm testing from a remote machine, using telnet.

A successful attempt:

telnet www.domain.com auth

Trying XX.XXX.XXX.XXX...
Connected to domain.com.
Escape character is '^]'.
(pauses here, hit enter to continue and it spits out...)
1 , 1 : USERID : UNIX : user

And this command helps show which ip is listening:

ps uxawww | grep widentd

Problems I'm having:

1) Selecting WAN as the listening interface results in no connection.

2) Selecting LAN as the listening interface results in successful connection.

3) Selecting OPT1 (wifi) results in no connection. (expected result)

4) Selecting looback results in successful connection.

But its not consistent. For example, sometimes only selecting loopback results in successful identd connections, and at other times only selecting LAN allows it to work.

I think this is a problem with the code for the pull-down menu on the widentd service page. While writing this bug I stepped through the choices on my own firewall, (clicking 'Save' each time) and at one point the GUI crashed and displayed a 404 not found error for the page. I had to reinstalled the GUI components using the pfsense package manager.

Once you have successful identd connections there's no need to visit the GUI again, so it works well otherwise.

Actions #1

Updated by Kill Bill almost 9 years ago

Actions #2

Updated by Kill Bill almost 9 years ago

Merged -> fixed.

Actions #3

Updated by Chris Buechler almost 9 years ago

  • Status changed from New to Resolved

thanks

Actions

Also available in: Atom PDF