- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Configure source ip for serveral services e.g. tac...
Switches, Hubs, and Modems
1752472
Members
6968
Online
108788
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
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
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-05-2009 04:12 AM
08-05-2009 04:12 AM
Configure source ip for serveral services e.g. tacacs, logging, ntp
Hello,
my equipment is used behind a firewall. Therefore i've to enable all the specific traffic for management through the firewall.
How can i define the source IP address of all responses or logging services?
I would like to define all requests e.g. caused by tacacs or logging are coming from a defined interface. For the following services i would like to define a source IP:
- Tacacs
- Logging
- NTP
- telnet
- SSH
- TFTP / FTP
- DNS query
Would be great, if you could give me the command for it.
Thank you all for your support in advance.
my equipment is used behind a firewall. Therefore i've to enable all the specific traffic for management through the firewall.
How can i define the source IP address of all responses or logging services?
I would like to define all requests e.g. caused by tacacs or logging are coming from a defined interface. For the following services i would like to define a source IP:
- Tacacs
- Logging
- NTP
- telnet
- SSH
- TFTP / FTP
- DNS query
Would be great, if you could give me the command for it.
Thank you all for your support in advance.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2009 10:56 PM
08-05-2009 10:56 PM
Re: Configure source ip for serveral services e.g. tacacs, logging, ntp
im not sure, but i don't think there really is a single command to do that.
Normally the address of the "primary vlan" (default vlan-1) will be preferred for those packets.
But it's possible that the adress of the first interface that's "up" will be used.
If at some time this is not the primary vlan an other address may get selected.
You can control this by configuring a "loopback interface".
This loopback interface is the first interface to come "up" (as it needs no "link" to come up first).
And will subseqently be used as source address, if not otherwise configured for a service.
Normally the address of the "primary vlan" (default vlan-1) will be preferred for those packets.
But it's possible that the adress of the first interface that's "up" will be used.
If at some time this is not the primary vlan an other address may get selected.
You can control this by configuring a "loopback interface".
This loopback interface is the first interface to come "up" (as it needs no "link" to come up first).
And will subseqently be used as source address, if not otherwise configured for a service.
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