HP 635n HP Jetdirect Print Servers - Practical IPv6 Deployment for Printing an - Page 6

Vista1, Vista2

Get HP 635n - JetDirect IPv6/IPsec Print Server PDF manuals and user guides
UPC - 882780301016
View all HP 635n manuals
Add to My Manuals
Save this manual to your list of manuals

Page 6 highlights

` Vista2 ` MFP1 Vista1 Figure 1 - Link Local Let's assume the following values for each network device after boot up: • MFP1: 169.254.20.1, FE80::1, hostname "mfp1" • Vista1: 169.254.20.2, FE80::2, hostname "vista1" • Vista2: 169.254.20.3, FE80::3, hostname "vista2" A user on Vista1 types in the following at a Command Prompt: "ping mfp1". What happens? The "ping" application on Vista1 will attempt to do name resolution of the name "mfp1" in order to find the IP address associated with that name by calling a function called getaddrinfo(). This function is implemented by the Vista operating system and is part of the standard for implementing an IPv6 API. There are no servers (e.g., DNS, WINS) configured in this link local environment, so Vista1 will attempt to use the Link Local Multicast Name Resolution (LLMNR) protocol. This protocol works over IPv4 and IPv6 and Vista1 will try IPv6 first. An HP MFP with an Embedded Jetdirect version of V.37.XX and lower does not support LLMNR and the LLMNR packets go unanswered (Note: We will discuss Jetdirect's LLMNR implementation, available in a later firmware release, in another section). Next, Vista1 will use NetBIOS over IPv4 which the MFP will respond to and the MFP tells Vista1 its IPv4 address. This basic description is really what is seen on the network from a packet perspective. However, a lot more is happening behind the scenes. Let's cover this a little more in depth. Refer to Figure 2 - The Vista Resolver: 6

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
6
MFP1
`
Vista1
`
Vista2
Figure 1 - Link Local
Let’s assume the following values for each network device after boot up:
•
MFP1: 169.254.20.1, FE80::1, hostname “mfp1”
•
Vista1: 169.254.20.2, FE80::2, hostname “vista1”
•
Vista2: 169.254.20.3, FE80::3, hostname “vista2”
A user on Vista1 types in the following at a Command Prompt: “ping mfp1”.
What happens?
The “ping” application on Vista1 will attempt to do name resolution of the name “mfp1” in order to
find the IP address associated with that name by calling a function called getaddrinfo().
This function
is implemented by the Vista operating system and is part of the standard for implementing an IPv6
API.
There are no servers (e.g., DNS, WINS) configured in this link local environment, so Vista1 will
attempt to use the Link Local Multicast Name Resolution (LLMNR) protocol.
This protocol works over
IPv4 and IPv6 and Vista1 will try IPv6 first.
An HP MFP with an Embedded Jetdirect version of
V.37.XX and lower does not support LLMNR and the LLMNR packets go unanswered (Note: We will
discuss Jetdirect’s LLMNR implementation, available in a later firmware release, in another section).
Next, Vista1 will use NetBIOS over IPv4 which the MFP will respond to and the MFP tells Vista1 its
IPv4 address.
This basic description is really what is seen on the network from a packet perspective.
However, a lot more is happening behind the scenes.
Let’s cover this a little more in depth.
Refer to
Figure 2 – The Vista Resolver: