Sorry for replying to myself (AND top-posting!) twice in a row, but this
is become a huge concern. My first thought is that my provider changed
routers or router Ethernet ports, hence the MAC address change. They deny
this, plus I find the two MAC addresses:
00:17:e0:4f:b9:c0 to
On 11/02/2010 11:00, James Smallacombe wrote:
Sorry for replying to myself (AND top-posting!) twice in a row, but this
is become a huge concern. My first thought is that my provider changed
routers or router Ethernet ports, hence the MAC address change. They
deny this, plus I find the two
On Thu, 11 Feb 2010, Matthew Seaman wrote:
On 11/02/2010 11:00, James Smallacombe wrote:
Sorry for replying to myself (AND top-posting!) twice in a row, but this
is become a huge concern. My first thought is that my provider changed
routers or router Ethernet ports, hence the MAC address
On 11/02/2010 11:00, James Smallacombe wrote:
Sorry for replying to myself (AND top-posting!) twice in a row, but
this is become a huge concern. My first thought is that my provider
changed routers or router Ethernet ports, hence the MAC address
change. They deny this, plus I find the two
On 11/02/2010 12:22, James Smallacombe wrote:
It's not 'arp -s' that is used to change the MAC address on an
interface, but ifconfig(8) -- something like this:
# ifconfig re0 ether 00:17:e0:4f:b9:c0
See my second post. I screwed up in my first post. It wasn't the MAC
address of my NIC
This freaked me out a bit, so I'm just running it past the list to make
sure this is just a hardware issue...I've never seen it before.
My dedicated server provider replaced my defective server that had been up
for 6 months after it had apparent failures of a NIC and hard drives. It
had
Please disregard this...sleep deprication...the IP in questions (which I
should have disfuised anyway) was not my server's IP, but that of the
default gateway...the problem was external.
On Wed, 10 Feb 2010, James Smallacombe wrote:
This freaked me out a bit, so I'm just running it past
