Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Nov 2010 21:31:05 +0100
From:      Gabor Radnai <gabor.radnai@gmail.com>
To:        pyunyh@gmail.com
Cc:        freebsd-net@freebsd.org
Subject:   Re: Problem with re0
Message-ID:  <AANLkTink1rmvvKQC6rdHP=ptenfci7p-B-L98QyZm=HK@mail.gmail.com>
In-Reply-To: <20101112225320.GC22460@michelle.cdnetworks.com>
References:  <AANLkTinNydUwkyC9zb21P4DPbvBkEDKpNXbp3Nap%2BRvT@mail.gmail.com> <20101111212648.GF17566@michelle.cdnetworks.com> <AANLkTimHu2tjdRLc_F_m22FQxRN81jtAGeZKTUyLGOJd@mail.gmail.com> <20101112225320.GC22460@michelle.cdnetworks.com>

next in thread | previous in thread | raw e-mail | index | archive | help
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

options=389b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC>
    ether d8:5d:4c:80:b4:88
    inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
    media: Ethernet autoselect (1000baseT <full-duplex>)
    status: active
nfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
    options=80008<VLAN_MTU,LINKSTATE>
    ether 00:1a:92:38:dc:95
    inet 192.168.0.200 netmask 0xffffff00 broadcast 192.168.0.255
    media: Ethernet autoselect (1000baseT <full-duplex,flag0,flag1>)
    status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
    options=3<RXCSUM,TXCSUM>
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
    inet6 ::1 prefixlen 128
    inet 127.0.0.1 netmask 0xff000000
    nd6 options=3<PERFORMNUD,ACCEPT_RTADV>


On Fri, Nov 12, 2010 at 11:53 PM, Pyun YongHyeon <pyunyh@gmail.com> wrote:

> On Fri, Nov 12, 2010 at 10:18:40PM +0100, Gabor Radnai wrote:
> > Hi,
> >
> > I hope you are interested in inet section it looks like this (will able
> to
> > send the exact output only a bit later unfortunately as removed the card)
> :
> > inet 0.0.0.0 netmask 255.255.255.255
> >
>
> This might be caused by dhclient(i.e. dhclient(8) failed to receive
> DHCP ACK).
> BTW, you still didn't show me the output of ifconfig re0 after UP
> the interface(i.e. ifconfig re0 up).
>
> > Thanks,
> > Gabor
> >
> > On Thu, Nov 11, 2010 at 10:26 PM, Pyun YongHyeon <pyunyh@gmail.com>
> wrote:
> >
> > > On Thu, Nov 11, 2010 at 09:56:26PM +0100, Gabor Radnai wrote:
> > > > Hi,
> > > >
> > > > I have an Asus M2NPV-VM motherboard with integrated Nvidia MCP51
> Gigabit
> > > > Ethernet NIC and
> > > > TP-Link TG-3468 PCIe network card which is using Realtek 8111 chip.
> > > >
> > > > I have problem with the re driver: the Nvidia network interface is
> > > working
> > > > properly but the other
> > > > though it seems recognized by OS I cannot use. Sporadically it
> remains
> > > down
> > > > and if it gets up then
> > > > does not get ip address via DHCP nor help if I set static ip address.
> Can
> > > > manipulate via ifconfig but
> > > > unreachable via IP.
> > > >
> > > > I replaced cable, interchanged cable working with Nvidia, restarted
> > > > switch/router but no luck so far.
> > > > Also using this nic in a Windows machine - it works. Using my Asus
> mob
> > > with
> > > > Ubuntu Live CD - card works.
> > > >
> > > > Can it be a driver bug or this type of chip is not supported by re
> > > driver?
> > > >
> > >
> > > Eh, you already know the answer, recognized by re(4) but does not
> > > work so it's a bug of re(4). Would you show me the output of
> > > ifconfig re0 after UP the interface(i.e. ifconfig re0 up).
> > >
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTink1rmvvKQC6rdHP=ptenfci7p-B-L98QyZm=HK>