- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- multi homing a single nic
Categories
Company
Local Language
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
Forums
Discussions
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
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО02-01-2001 12:36 PM
тАО02-01-2001 12:36 PM
multi homing a single nic
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-20-2001 12:46 AM
тАО02-20-2001 12:46 AM
Re: multi homing a single nic
in the directory: /etc/sysconfig/network-scripts
You have a file:
ifcfg-eth0 (depends on which card you want to alias)
copy this to the file:
ifcfg-eth0:0
Now edit this file with your other network settings, and you should then be able to bring the pseudo interface up with:
ifconfig eth0:0 up (or restart the network service)
voila ..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-23-2001 04:36 PM
тАО02-23-2001 04:36 PM
Re: multi homing a single nic
#: cat ifcfg-eth0:0
DEVICE="eth0"
BOOTPROTO="none"
IPADDR="192.168.1.8"
NETMASK="255.255.255.0"
ONBOOT="yes"
IPXNETNUM_802_2=""
IPXPRIMARY_802_2="no"
IPXACTIVE_802_2="no"
IPXNETNUM_802_3=""
IPXPRIMARY_802_3="no"
IPXACTIVE_802_3="no"
IPXNETNUM_ETHERII=""
IPXPRIMARY_ETHERII="no"
IPXACTIVE_ETHERII="no"
IPXNETNUM_SNAP=""
IPXPRIMARY_SNAP="no"
IPXACTIVE_SNAP="no"
#:
The error was received even after stopping and restarting networking.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-27-2001 05:57 AM
тАО02-27-2001 05:57 AM
Re: multi homing a single nic
Try doing it from the command line and report your error:
ifconfig eth0:0 192.168.5.5 netmask x.x.x.x up
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-27-2001 11:30 AM
тАО02-27-2001 11:30 AM
Re: multi homing a single nic
# ifconfig eth0:0 192.168.1.8 netmask 255.255.255.0 up
#
Then to check:
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:A0:B9:35:79:01
inet addr:206.42.138.8 Bcast:206.42.138.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3499620 errors:0 dropped:0 overruns:0 frame:0
TX packets:453836 errors:0 dropped:0 overruns:0 carrier:0
collisions:56 txqueuelen:100
Interrupt:11 Base address:0x6000
eth0:0 Link encap:Ethernet HWaddr 00:A0:B9:35:79:01
inet addr:192.168.1.8 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:11 Base address:0x6000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:69 errors:0 dropped:0 overruns:0 frame:0
TX packets:69 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
And then testing from another workstation:
# ping 192.168.1.8 PING 192.168.1.8: 64 byte packets
64 bytes from 192.168.1.8: icmp_seq=0. time=1. ms
64 bytes from 192.168.1.8: icmp_seq=1. time=0. ms
64 bytes from 192.168.1.8: icmp_seq=2. time=0. ms
But the computer itself is REALLLLLY slow to ping itself:
# ping 192.168.1.8 PING 192.168.1.8 (192.168.1.8) from 192.168.1.8 : 56(84) bytes of data.
64 bytes from 192.168.1.8: icmp_seq=0 ttl=255 time=0.1 ms
64 bytes from 192.168.1.8: icmp_seq=1 ttl=255 time=3526.6 ms
so I expect I've still gotten something wrong in the configuration somewhere. I checked the routing tables:
[root@linux2 markf]# netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
206.42.138.8 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
206.42.138.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 206.42.138.1 0.0.0.0 UG 0 0 0 eth0
Which looks OK to me.... Further ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-15-2001 03:18 AM
тАО03-15-2001 03:18 AM
Re: multi homing a single nic
try assigning your second IP in the routing table:
route add
that should speed thigs up
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-16-2001 11:16 AM
тАО03-16-2001 11:16 AM