REBOL3 tracker
  0.9.12 beta
Ticket #0002187 User: anonymous

Project:

Previous Next
rss
TypeWish Statussubmitted Date19-Nov-2014 05:34
Versionr3 master CategoryUnspecified Submitted bykealist
PlatformAll Severityminor Prioritynormal

Summary LOCAL-IP could return a block of possible IPV4 addresses
Description Whenever a port is opened with tcp://, it remains bound to the wildcard 0.0.0.0 (system/standard/net-info/local-ip). There is currently no way to determine a local ip address within REBOL.

Would it be possible to allow local-ip to contain a block of addresses that are currently available for whatever protocl is in use?

Or is there another possible way to include a local ip addresses that would be make more sense?



Example code
>> a: open tcp://:9090 
>> query a
== make object! [
   local-ip        tuple!    0.0.0.0
   local-port      integer!  9090
   remote-ip       tuple!    0.0.0.0
   remote-port     integer!  0
]


proposed change

>> query a
== make object! [
   local-ip        block!    [192.168.1.100 129.237.14.84]
   local-port      integer!  9090
   remote-ip       tuple!    0.0.0.0
   remote-port     integer!  0
]


Assigned ton/a Fixed in- Last Update19-Nov-2014 08:04


Comments

Date User Field Action Change
19-Nov-2014 08:04 kealist Description Modified -
19-Nov-2014 07:44 kealist Summary Modified LOCAL-IP not updated when a port is opened => LOCAL-IP could return a block of possible IPV4 addresses
19-Nov-2014 07:44 kealist Description Modified -
19-Nov-2014 07:44 kealist Code Modified -
19-Nov-2014 07:44 kealist Type Modified Bug => Wish
19-Nov-2014 05:34 kealist Ticket Added -