HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: compartment network rules
Operating System - HP-UX
1838676
Members
4276
Online
110128
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
08-23-2006 01:00 AM
08-23-2006 01:00 AM
compartment network rules
Hello.
I would like to make all processes belonging to a certain compartment use a specific network interface for in- and out-bound traffic.
I have tried to create a virtual interface, and set the compartment-network-rules to only allow traffic from that interface.
The problem seems to be that the default route still goes via the lan0 interface.
Any suggestions?
This is what i have done:
lanadmin -V create vlanid 454 0
BASE=$(lanadmin -V basevppa)
ifconfig lan$BASE inet 10.0.0.12 netmask 255.255.255.0 up
cp /bin/bash ~/bash
setfilexsec -c test_cmpt ~/bash
~/bash
ping anotherhost
------
The ping command just hangs and "tcpdump -i lan$BASE" (from outside the compartment) doesn't show anything when I do the pinging.
/Niklas W.
I would like to make all processes belonging to a certain compartment use a specific network interface for in- and out-bound traffic.
I have tried to create a virtual interface, and set the compartment-network-rules to only allow traffic from that interface.
The problem seems to be that the default route still goes via the lan0 interface.
Any suggestions?
This is what i have done:
lanadmin -V create vlanid 454 0
BASE=$(lanadmin -V basevppa)
ifconfig lan$BASE inet 10.0.0.12 netmask 255.255.255.0 up
cp /bin/bash ~/bash
setfilexsec -c test_cmpt ~/bash
~/bash
ping anotherhost
------
The ping command just hangs and "tcpdump -i lan$BASE" (from outside the compartment) doesn't show anything when I do the pinging.
/Niklas W.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2006 01:23 AM
08-23-2006 01:23 AM
Re: compartment network rules
Shalom,
When you create a virtual lan, all the traffic actually transits the master lan ip address.
Users thinkg they are using the virtual lan, but tcpdump shows the actual traffic passed through the master interface.
The virtual ip address is a device to make users or applications think there is another ip address, but to the system running it, its almost like smoke and mirrors.
This appears to be normal function based on what you did.
SEP
When you create a virtual lan, all the traffic actually transits the master lan ip address.
Users thinkg they are using the virtual lan, but tcpdump shows the actual traffic passed through the master interface.
The virtual ip address is a device to make users or applications think there is another ip address, but to the system running it, its almost like smoke and mirrors.
This appears to be normal function based on what you did.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2006 07:44 PM
08-23-2006 07:44 PM
Re: compartment network rules
Ok, Thanks.
Do you know about any other way of creating virtual interfaces on HPUX (preferably supported by HP).
/Niklas
Do you know about any other way of creating virtual interfaces on HPUX (preferably supported by HP).
/Niklas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2006 05:29 AM
09-11-2006 05:29 AM
Re: compartment network rules
Hello HP-UX allows you to create virtual aliases for specific interface.
it's quite simple.
try to issue something like this:
ifconfig lan0:1 inet 10.0.0.3 netmask 255.255.255.0 up
this command allows you to create alias for lan0 named "1" with specified ip/netmask
netstat -i alliows you to display list of all your configured interfaces (aliased also)
it's quite simple.
try to issue something like this:
ifconfig lan0:1 inet 10.0.0.3 netmask 255.255.255.0 up
this command allows you to create alias for lan0 named "1" with specified ip/netmask
netstat -i alliows you to display list of all your configured interfaces (aliased also)
Omnia mea mecum porto
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP