#6607: Public IP reset to LAN IP if domainname is used

[Pidgin]

#6607: Public IP reset to LAN IP if domainname is used
------------------------------------+---------------------------------------
 Reporter:  olmari                  |     Owner:  lschiere
     Type:  defect                  |    Status:  new    
Component:  unclassified            |   Version:  2.4.3  
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
 At the Pidgin settings -> network I can set public IP by hand.

 I am behind router. I can type in my dynamic DNS address but next time I
 check it has again my LAN IP set...

 So if it does allow domainname then it isn't working right, if it isn't
 supposed to take domainname then why can one put one there without error?

 I can put my current public IP there by hand and it stays there allright,
 but it doesn't help me when it changes again, hence I'd like to use my no-
 ip name there.

--
Ticket URL: <http://developer.pidgin.im/ticket/6607>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP reset to LAN IP if domainname is used
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere    
     Type:  defect                  |       Status:  pending    
Milestone:                          |    Component:  unclassified
  Version:  2.4.3                   |   Resolution:              
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by datallah):

  * status:  new => pending


Comment:

 Why don't you just use the "Autodetect IP address" checkbox (optionally
 entering a value for the STUN server) instead of entering a static value?

 If you enter a value, we take your word for it - arguably it could do
 better validation, but that isn't the real issue here.

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:1>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP reset to LAN IP if domainname is used
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere    
     Type:  defect                  |       Status:  pending    
Milestone:                          |    Component:  unclassified
  Version:  2.4.3                   |   Resolution:              
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by olmari):

  * status:  pending => new


Comment:

 Because with autodetect IP enabled it detects my LAN IP (appeared on that
 same box) which is obviously wrong too.

 So perfect solution would either correctly working autodetection, and/or
 the box should also accept domainname (handy for no-ip/dyndns or alike).

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:2>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP reset to LAN IP if domainname is used
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere    
     Type:  defect                  |       Status:  pending    
Milestone:                          |    Component:  unclassified
  Version:  2.4.3                   |   Resolution:              
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by datallah):

  * status:  new => pending


Comment:

 If we can't get a correct value from UPnP (which apparently is the case
 for you), you'll need to enter a value for the STUN server, at which point
 it should work fine.

 I don't much like the idea of resolving a domain name entered there.

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:3>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP reset to LAN IP if domainname is used
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere    
     Type:  defect                  |       Status:  pending    
Milestone:                          |    Component:  unclassified
  Version:  2.4.3                   |   Resolution:              
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by olmari):

  * status:  pending => new


Comment:

 Well... I use 64-bit Ubuntu if that matters anything.. I do have UPnP
 enabled on the router also (for being home with multiple users it's quite
 handy)..

 Let me ask it this way then: Why not be able to put domainname there? What
 would be the harm?

 Also by making it able to use domainname it would then make no need for
 "external" STUN server at all because I do have neccesary port forwards
 already manually for myself and no-ip domainname that router keeps up to
 date...

 If the scenario would work, it would only add more configurability for
 users, and I don't know what harm it could do either.

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:4>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP reset to LAN IP if domainname is used
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere    
     Type:  defect                  |       Status:  new        
Milestone:                          |    Component:  unclassified
  Version:  2.4.3                   |   Resolution:              
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------

Comment(by olmari):

 Also actually if I am not mistaken Pidgin doesn't even have to resolve the
 IP from the domain but it can use the domain directly instead of IP. I
 know this way works at least for ICQ, yahoo and XMPP file transfers in
 Trillian, this way also when the IP do change it is "detected"
 automatically as domainname resolves to the new IP.

 I don't put my neck on the line about how it works in trilly, but AFAIK it
 is this way.

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:5>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP reset to LAN IP if domainname is used
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere    
     Type:  defect                  |       Status:  pending    
Milestone:                          |    Component:  unclassified
  Version:  2.4.3                   |   Resolution:              
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by datallah):

  * status:  new => pending


Comment:

 You can't just use the domain instead of the IP for XMPP file transfers.
 I don't know about any of the other examples.

 There is already a supported way of doing this, and entering a domain in a
 field that accepts an IP isn't it.

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:6>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP reset to LAN IP if domainname is used
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere    
     Type:  defect                  |       Status:  pending    
Milestone:                          |    Component:  unclassified
  Version:  2.4.3                   |   Resolution:              
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by olmari):

  * status:  pending => new


Comment:

 For god sakes is this really the attitude? Why force using STUN-server if
 there isn't really need to? Why not give people the choice? Still I
 haven't heard what harm could resolving domain in this case would do?

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:7>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP detection via entry of DNS name
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere
     Type:  enhancement             |       Status:  pending  
Milestone:                          |    Component:  libpurple
  Version:  2.4.3                   |   Resolution:          
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by datallah):

  * status:  new => pending
  * type:  defect => enhancement
  * component:  unclassified => libpurple


Comment:

 What attitude?

 Nobody is forcing you to do anything.

 There are already 4 ways that the IP can be determined in libpurple and I
 haven't seen any evidence that we need to further complicate life with yet
 another one.

 I'm not disputing that it is possible to do in this way, I'm just
 questioning the necessity - just because something is possible doesn't
 make it worthwhile.  Adding complexity should be avoided unless it is
 necessary and I guess I believe that it is not.

 If someone submitted a good patch to do this, perhaps it'd be considered,
 but apart from that I don't think this will change.

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:8>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP detection via entry of DNS name
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere
     Type:  enhancement             |       Status:  pending  
Milestone:                          |    Component:  libpurple
  Version:  2.4.3                   |   Resolution:          
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by olmari):

  * status:  pending => new


Comment:

 good for dynamic IP for one and also makes STUN unneccesary (which adds
 need for working 3rd party STUN-server)...

 But I'd be happy also with working autodetection... As said my UPnP is up
 and working yet autodetection doesn't work...

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:9>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP detection via entry of DNS name
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere
     Type:  enhancement             |       Status:  pending  
Milestone:                          |    Component:  libpurple
  Version:  2.4.3                   |   Resolution:          
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by datallah):

  * status:  new => pending


Comment:

 Please get a debug log using `pidgin -n -d > debug.log` to get the startup
 debug information.

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:10>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP detection via entry of DNS name
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere
     Type:  enhancement             |       Status:  new      
Milestone:                          |    Component:  libpurple
  Version:  2.4.3                   |   Resolution:          
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by olmari):

  * status:  pending => new


--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:11#comment:>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP detection via entry of DNS name
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere
     Type:  enhancement             |       Status:  pending  
Milestone:                          |    Component:  libpurple
  Version:  2.4.3                   |   Resolution:          
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by datallah):

  * status:  new => pending


Comment:

 Your debug log doesn't contain any of the necessary info, please use the
 command that I posted above.

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:13>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP detection via entry of DNS name
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere
     Type:  enhancement             |       Status:  pending  
Milestone:                          |    Component:  libpurple
  Version:  2.4.3                   |   Resolution:          
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by olmari):

  * status:  pending => new


Comment:

 I did copypaste that command to console, which then started up pidgin, I
 connected my IM's and waited them to connect, then I closed pidgin and
 attached debug.log it produced.

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:14>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP detection via entry of DNS name
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere
     Type:  enhancement             |       Status:  pending  
Milestone:                          |    Component:  libpurple
  Version:  2.4.3                   |   Resolution:          
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by datallah):

  * status:  new => pending


Comment:

 The log doesn't contain the startup information, I'm not sure how that is
 possible if you did indeed start pidgin from the console.  We also don't
 need the stuff from when it is connecting, but that doesn't necessarily
 hurt anything.

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:15>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP detection via entry of DNS name
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere
     Type:  enhancement             |       Status:  pending  
Milestone:                          |    Component:  libpurple
  Version:  2.4.3                   |   Resolution:          
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------

Comment(by datallah):

 Actually, assuming that you actually have the "Autodetect IP" checkbox
 checked, the other possibility is that your router doesn't actually
 support UPnP.  I just realized that I was looking for the wrong thing in
 the debug log.

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:16>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP detection via entry of DNS name
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:  lschiere
     Type:  enhancement             |       Status:  pending  
Milestone:                          |    Component:  libpurple
  Version:  2.4.3                   |   Resolution:          
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by olmari):

  * status:  pending => new


Comment:

 Well I did check IP autodetection and then closed and restarted with
 copypaste of command you gave.

 And as I told you, my router supports DD-WRT and we are are using it
 "24/7".. The DD-WRT router and it's UPnP works, plenty of proof about
 that...

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:17>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP detection via entry of DNS name
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:          
     Type:  enhancement             |       Status:  new      
Milestone:                          |    Component:  libpurple
  Version:  2.6.2                   |   Resolution:          
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------
Changes (by olmari):

  * version:  2.4.3 => 2.6.2


Comment:

 For the sake of discussion, I'd still be interested about using DNS
 instead of IP in "Public IP", as I do have dynamic IP...

 While I know there is STUN and other methods of looking up public IP, I'd
 still would like to see simple DNS name to replace raw IP-number... I do
 have dynamic IP and thus it changes for time to time and only this way I'd
 be both free of 3rd party "IP detection" system and have settings made
 once and be done with it...

 I see that developers aren't that eager towards this, but yet I see this
 one "perfect" option to implement...

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:19>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP detection via entry of DNS name
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:          
     Type:  enhancement             |       Status:  new      
Milestone:                          |    Component:  libpurple
  Version:  2.6.2                   |   Resolution:          
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------

Comment(by eomanis):

 I'm totally with olmari on this one.

 I was about to give Miranda IM the boot for pidgin and ran into this
 problem when I tried to put my port forwarding to good use.

 I do not have UPnP enabled on my router since I think I can do perfectly
 well without random programs requesting port forwarding (just think of
 malware).
 Honestly, this is basic networking and really shouldn't be too hard to
 implement. I mean, how hard can it be to resolve a DNS name? Everybody can
 do that with a ping, come on...

 Besides, in my humble opinion, having to look up for a STUN server for use
 DOES add complexity. It could be so simple: Set the ports range, type in
 youre dynamic DNS address and off you go with file transfers and
 everything. What's the point in throwing wrenches into users' paths who
 want to use some basic and straightforward networking?

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:20>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker

[Pidgin]

#6607: Public IP detection via entry of DNS name
------------------------------------+---------------------------------------
 Reporter:  olmari                  |        Owner:          
     Type:  enhancement             |       Status:  new      
Milestone:                          |    Component:  libpurple
  Version:  2.6.2                   |   Resolution:          
 Keywords:  public IP, domain name  |  
------------------------------------+---------------------------------------

Comment(by eomanis):

 For anyone still interested, I made up a makeshift bash script that
 tampers with the libpurple configuration (using Cygwin). It

 a) resolves a hostname to an IP address,[[BR]]
 b) writes said address into the prefs.xml file and[[BR]]
 c) starts PidginPortable.

 It acts relatively to the path where it is located. In my case, I have it
 right beneath the PidginPortable.exe and it works from there, accessing
 the subfolders. Since I have configured Windows Explorer to open any .sh
 file with the Cygwin bash shell, I can double click on it and
 PidginPortable starts with the correct external IP set.

 I don't know where Pidgin usually stores its configuration on Linux, maybe
 you have a .purple folder in your home directory there. You'll have to
 change the paths then. Also, I don't think you'll need the "| unix2dos"
 part when operating on Linux (I even doubt the Windows Pidgin would mind,
 it's just there because the original prefs.xml had CR+LF line endings
 too).

 {{{
 #!/bin/sh
 # This script will launch PidginPortable on Windows using Cygwin while
 writing the external IP address into libpurple's config file
 var_hostname="your.dyndns.org" # Enter your hostname here
 var_path=`echo $0 | sed -r 's/[^\/]*$//'` # This is the path to the folder
 where the script is located
 echo "Resolving hostname..."
 var_ip=`nslookup $var_hostname 2> /dev/null | grep Address | tail -n 1 |
 sed -r 's/^[^0-9]*//'` # This is the IP the hostname has been resolved to
 echo "IP Address is $var_ip"
 echo "Tampering with the libpurple configuration..."
 # This line generates a new config file from the current one:
 sed -r
 "s/^([^0-9.]*name='public_ip'[^0-9.]*value=')[0-9.]*('[^0-9.]*)$/\\1${var_ip}\\2/"
 "${var_path}Data/settings/.purple/prefs.xml" | unix2dos 1>
 "${var_path}Data/settings/.purple/prefs_tmp.xml"
 # Yes, I know of the -i option in sed (update file in-place), but
 afterwards the prefs.xml file would always be read-only (what the heck?!),
 so Pidgin could not save configurations anymore
 rm -f "${var_path}Data/settings/.purple/prefs.xml" # Remove the old config
 file
 mv "${var_path}Data/settings/.purple/prefs_tmp.xml"
 "${var_path}Data/settings/.purple/prefs.xml" #Rename the new file
 echo "Starting PidginPortable..."
 ${var_path}PidginPortable &
 }}}

 Still, it would be nice if I could get rid of that junk script and this
 rather mundane feature would find its way into Pidgin. Mind you, people
 set up dynamic DNS addresses to NOT depend on complicated external
 services like that STUN server.

--
Ticket URL: <http://developer.pidgin.im/ticket/6607#comment:21>
Pidgin <http://pidgin.im>
Pidgin
_______________________________________________
Tracker mailing list
Tracker@...
http://pidgin.im/cgi-bin/mailman/listinfo/tracker