Re: Created Computer-to-Computer Network ping error when Ethernet is enabled?
Re: Created Computer-to-Computer Network ping error when Ethernet is enabled?
- Subject: Re: Created Computer-to-Computer Network ping error when Ethernet is enabled?
- From: Ian Mark Salvame <email@hidden>
- Date: Thu, 30 Apr 2009 05:38:04 -0700 (PDT)
>>> First post here - be gentle.
>>> A
169.254.xxx.xxx address results when an interface asks for a DHCP
assignment but does not receive one. There is an RFC for this but >>> I
can't think of the number.
>>> Although you can in some
instances ping and use the address on such a configured interface,
other routers and switches may not route >>> that subnet at all. So why
not just manually configure the interfaces to a regular private subnet
(192.168... 10... 172...) until you can >>> rule out other problems?
Actually, en1 interface connects directly to Host2 (Adhoc connection) with self-assigned IP address(169.254.xxx.xxx), there's no router connection for en1. So I guess pinging the subnet broadcast for en1(169.254.255.255) will not be successfull and will return "host is down" error.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden