On Tue, March 3, 2009 18:30, Fred Crowson wrote:
> On 3/3/09, Nenhum_de_Nos <math...@eternamente.info> wrote:
>>
>> On Mon, March 2, 2009 21:04, Fred Crowson wrote:
>>> What's the output of: ifconfig -a ?
>>
>> # ifconfig -a
>> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33204
>>         groups: lo
>>         inet 127.0.0.1 netmask 0xff000000
>>         inet6 ::1 prefixlen 128
>>         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
>> vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>>         lladdr 00:11:85:e3:2a:17
>>         groups: egress
>>         media: Ethernet autoselect (100baseTX full-duplex)
>>         status: active
>>         inet6 fe80::211:85ff:fee3:2a17%vr0 prefixlen 64 scopeid 0x1
>>         inet 10.1.1.90 netmask 0xffffff00 broadcast 10.1.1.255
>> enc0: flags=0<> mtu 1536
>> aue0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>>         lladdr 00:60:6e:00:18:c0
>>         media: Ethernet autoselect (none)
>>         status: no carrier
>             ^^^^^^^^^^
> If the status is no carrier then that usually implies a cabling issue.
>
> Not sure if this is your problem.
>
> HTH
>
> Fred

thanks for asnwering, but it is not. this ifconfig was taken when I put
the cable on the other nic to access and send you what you wanted :)
I'd be really glad if that was my problem :)

thanks,

matheus

-- 
We will call you cygnus,
The God of balance you shall be

Reply via email to