- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- vlan# interface
Operating System - HP-UX
1748173
Members
4283
Online
108758
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-08-2011 09:50 PM
тАО06-08-2011 09:50 PM
Hi Folks,
I have an application which is getting binded to vlan0(virtual ip) interface even though its suppose to bind to the default interface.
The IP address of vlan interface is x.x.0.0.
It has the same ether address as the primary interface.
I have explored the configs for the app but no luck why its getting binded to that interface and not to the primary one.
What could be wrong here?
Thanks,
Allan.
I have an application which is getting binded to vlan0(virtual ip) interface even though its suppose to bind to the default interface.
The IP address of vlan interface is x.x.0.0.
It has the same ether address as the primary interface.
I have explored the configs for the app but no luck why its getting binded to that interface and not to the primary one.
What could be wrong here?
Thanks,
Allan.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2011 01:00 AM
тАО06-09-2011 01:00 AM
Solution
How can you even have interfaces like "vlan0" in HP-UX? Do you have some third-party networking software installed?
Which version of HP-UX are you running?
In HP-UX 11.31 native APA, VLANs would normally appear as high-numbered lan interfaces, e.g. lan5000 or above.
On the other hand, IP aliases (= multiple IPs for the same interface) would be named like lan0:1, lan0:2 etc.
Are you talking about incoming or outgoing connections?
Normally, outgoing connections are not bound into any particular interface by the application, so the OS is allowed to choose an appropriate source IP. The OS makes this choice by looking at the routing table to select the most direct route for delivering the connection to its destination, and choosing the source IP as appropriate for that route. If the same network entry has multiple applicable source IP addresses, the one that's listed first in the routing table is normally used.
If you haven't specified a netmask when configuring your interfaces or routes, a default netmask is chosen according to the old (pre-CIDR) class rules. For class A addresses (1-127.*.*.*), the default netmask is 255.0.0.0.
It is possible for the application to bind both incoming and outgoing connections to a particular local IP address, if that is desired. Normally, sockets listening for incoming connections are bound to a wildcard IP and a particular port: if a socket is bound to a specific local IP address, this behaviour is usually configurable, or somehow tied to the application's idea of the local hostname. Either way, this behaviour is application-specific: you might get a better answer by sending the question to the support services of your application.
If you want people on the forums to have any chance of analyzing this further, please show at least the outputs of "netstat -i" and "netstat -rnv" for analysis, if you're allowed to do that.
If disclosing that information to the Internet is not allowed, you'll have to find someone with the necessary knowledge (either within your organization or a consultant) who can sign an appropriate NDA and then be allowed to see the network parameters.
MK
Which version of HP-UX are you running?
In HP-UX 11.31 native APA, VLANs would normally appear as high-numbered lan interfaces, e.g. lan5000 or above.
On the other hand, IP aliases (= multiple IPs for the same interface) would be named like lan0:1, lan0:2 etc.
Are you talking about incoming or outgoing connections?
Normally, outgoing connections are not bound into any particular interface by the application, so the OS is allowed to choose an appropriate source IP. The OS makes this choice by looking at the routing table to select the most direct route for delivering the connection to its destination, and choosing the source IP as appropriate for that route. If the same network entry has multiple applicable source IP addresses, the one that's listed first in the routing table is normally used.
If you haven't specified a netmask when configuring your interfaces or routes, a default netmask is chosen according to the old (pre-CIDR) class rules. For class A addresses (1-127.*.*.*), the default netmask is 255.0.0.0.
It is possible for the application to bind both incoming and outgoing connections to a particular local IP address, if that is desired. Normally, sockets listening for incoming connections are bound to a wildcard IP and a particular port: if a socket is bound to a specific local IP address, this behaviour is usually configurable, or somehow tied to the application's idea of the local hostname. Either way, this behaviour is application-specific: you might get a better answer by sending the question to the support services of your application.
If you want people on the forums to have any chance of analyzing this further, please show at least the outputs of "netstat -i" and "netstat -rnv" for analysis, if you're allowed to do that.
If disclosing that information to the Internet is not allowed, you'll have to find someone with the necessary knowledge (either within your organization or a consultant) who can sign an appropriate NDA and then be allowed to see the network parameters.
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2011 10:26 AM
тАО06-09-2011 10:26 AM
Re: vlan# interface
Thanks Matt.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP