Difference between revisions of "Ignacio Valdes Implementation Log/Episode3"
(navigation links) |
|||
| Line 1: | Line 1: | ||
| − | ==The Intracare Implementation Log [[Intracare Implementation Log|(Back to Log Homepage)]]== | + | ===The Intracare Implementation Log [[Episode2|(Back to Episode 2)]] [[Intracare Implementation Log|(Back to Log Homepage)]] [[Episode4|(On to Episode 4)]]== |
==IPv4 vs. IPv6== | ==IPv4 vs. IPv6== | ||
Ignacio Valdes Jul 15 2008, 3:30 pm | Ignacio Valdes Jul 15 2008, 3:30 pm | ||
| Line 20: | Line 20: | ||
IPv4: 128.171.103.1 | IPv4: 128.171.103.1 | ||
| − | |||
IPv6: 2001:0db8:85a3:08d3:1319:8a2e:0370:7334 | IPv6: 2001:0db8:85a3:08d3:1319:8a2e:0370:7334 | ||
| Line 55: | Line 54: | ||
tell. Oh, wait, we don't do callbacks anymore <slap forehead>! | tell. Oh, wait, we don't do callbacks anymore <slap forehead>! | ||
| − | [[Intracare Implementation Log| | + | [[Episode2|Episode 2]] [[Intracare Implementation Log|Log Homepage]] [[Episode4|Episode 4]] |
Revision as of 20:53, 7 May 2009
=The Intracare Implementation Log (Back to Episode 2) (Back to Log Homepage) (On to Episode 4)
IPv4 vs. IPv6
Ignacio Valdes Jul 15 2008, 3:30 pm
Tried to install WVEHR-VOE only we ran into a authentication problem with CPRS. We are running IPv6 and apparently that doesn't work yet. We're seeing about fixing that.
-- IV
Greg Woodhouse
That's a big one.
Ignacio Valdes
Like, showstopping big? -- IV
Chris U
IPv4: 128.171.103.1 IPv6: 2001:0db8:85a3:08d3:1319:8a2e:0370:7334
You will notice the differences in syntax; periods/dots (IPv4) versus colons (IPv6). Extending further, in IPv4, 128.171.103.1:443, the number after the colon is represented as the port; in this case port 443. In VistA, they use the colon as a delimiter to strip the port number.
Here is what I modified to get IPv6 working - http://pastebin.com/f6aa67ea
Mahalo, Chris
Nancy Anthracite
Chris, would you please submit these to the trac server for WorldVistA EHR at
http://trac.opensourcevista.net
Thanks for doing this! -- Nancy Anthracite
Greg Woodhouse
Hey...I'm impressed.
Woodhouse Gregory
The reason I'm impressed that a change to the exec executable wasn't needed is that there's a parameter to the socket() call indicating the address type. Of course, if you accept a connection, then you can tell. Oh, wait, we don't do callbacks anymore <slap forehead>!
