|
|
Why your ifconfig wasn't working
ifconfig eth0:2 192.168.1.132 up
You were having trouble with this because the syntax is wrong for a BSD (ie: OSX). The command you would need for OSX would be something like:
The article at AFP548 states you should use netmask 255.255.255.255 or you will run into trouble. I ignored that and used my standard 255.255.255.0 and other items the same as my original IP.
The netmask you should use "depends". If the additional IP you are adding is on the same network as the existing IP, then the netmask should be 255.255.255.255. If the IP is on a different network (eg, if you were adding something like 10.0.0.1 as an alias) then you should use whatever the netmask for that network is. Additional IPs added on that network would use an IP of 255.255.255.255. This is the "right" way to do it, although many ifconfig commands will accept "wrong" netmasks. However, if you look at the output of an "ifconfig interface" command, you will probably find the netmask has been automatically set to 255.255.255.255 anyway.
Why your ifconfig wasn't working
I'm having trouble figuring out exactly how to use Multiple Network Interfaces with Multiple Networks.
Why your ifconfig wasn't working
I had no problems getting this to work EVEN with the wrong netmask. Do you have a firewall in place blocking your new ip?
Why your ifconfig wasn't working
Does anyone have any information of Etherchannel on 10.2 and 10.2Server. Also, is it possible to have two network cards in one Mac with different protocols being served out on the same network? |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.07 seconds |
|