[axe][ue0] Device send packets but any host in network can not receive any packet from it.

Pyun YongHyeon pyunyh at gmail.com
Mon May 31 22:32:31 UTC 2010


On Sun, May 30, 2010 at 01:16:14AM +0500, Perevalov Sergey wrote:
> Pyun YongHyeon, I am really sorry, I have found you message in my spam 
> folder:-(
> And immediately I did by your instructions.
> I connected 2 Freebsd 8.0 hosts by one cable, and started tcpdump 
> -evvvvvvi rl0/ue0.
> 
> So, 192.168.2.15 is receiver (rl0) log: http://pastebin.com/pZ5udweh
> 
> 192.168.2.16 is sender (ue0) log: http://pastebin.com/BEDwUWBe
> 

It seems both ends does not see any frames at all. I thought axe(4)
sent wrong ethernet address to the other end but tcpdump output you
posted makes me wonder cabling issue. I'm not sure whether
rgephy(4) used in axe(4) can handle automatic MDI/MDIX crossover
but rlphy(4) surely lacks the capability. Can you retest it with
crossover cable instead of straight UTP cable?
Also your tcpdump seems to indicate both hosts are trying to send
packets. This makes it hard to know which part of NIC is not
working. Send ICMP echo request on one host(e.g. ping(8)) and
capture traffic on both sender and receiver side and post the
result again.

> Thank you for your help!
> 
> 
> 
> On 08.05.2010 02:05, Pyun YongHyeon wrote:
> >On Fri, May 07, 2010 at 10:30:21PM +0500, Perevalov Sergey wrote:
> >   
> >>Hi guys. I am beginner in FreeBSD.  And I got problem with my Gigabit
> >>usb to ethernet adapter with AX88178 chipset. It works in windows very
> >>well but doesn't work in FreeBSD 8.0. tcpdump shows log with received
> >>and sent packets, but any host in network doesn't receive them from it.
> >>I checked it with 2 FreeBSD hosts connected directly by cable. Can you,
> >>guys, advice to me something to fix or to find reason of this issue?
> >>I started thread on freebsd forums(
> >>http://forums.freebsd.org/showthread.php?t=13649 ) and also reported
> >>about problem ( http://www.freebsd.org/cgi/query-pr.cgi?pr=146153 ).
> >>
> >>     
> >It seems the PR shows tcpdump output on sender side(axe(4)
> >host 192.168.2.22). Would you capture the traffic on receiver side
> >(host 192.168.2.7) and post the result? Note, please use direct
> >cable to connect both systems and use option -e to capture traffic
> >on host 192.168.2.7. For instance, use
> >#ifconfig -envvvvvvi nic0
> >on receiver side.
> >
> >Also check whether the receiver agrees on the resolved speed/duplex
> >of established link. For your case, host 192.168.2.7 should show
> >100baseTX, full-duplex.
> >
> >   
> >>Here some information:
> >>
> >>dmesg:
> >>ugen4.2:<vendor 0x0b95>  at usbus4
> >>axe0:<vendor 0x0b95 product 0x1780, rev 2.00/0.01, addr 2>  on usbus4
> >>axe0: PHYADDR 0xe0:0x02
> >>miibus0:<MII bus>  on axe0
> >>rgephy0:<RTL8169S/8110S/8211B media interface>  PHY 2 on miibus0
> >>rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> >>1000baseT-FDX, auto
> >>ue0:<USB Ethernet>  on axe0
> >>ue0: Ethernet address: 00:0e:c6:88:09:4e
> >>
> >>usbconfig:
> >>laptop# usbconfig
> >>ugen0.1:<UHCI root HUB Intel>  at usbus0, cfg=0 md=HOST spd=FULL
> >>(12Mbps) pwr=ON
> >>ugen1.1:<UHCI root HUB Intel>  at usbus1, cfg=0 md=HOST spd=FULL
> >>(12Mbps) pwr=ON
> >>ugen2.1:<UHCI root HUB Intel>  at usbus2, cfg=0 md=HOST spd=FULL
> >>(12Mbps) pwr=ON
> >>ugen3.1:<UHCI root HUB Intel>  at usbus3, cfg=0 md=HOST spd=FULL
> >>(12Mbps) pwr=ON
> >>ugen4.1:<EHCI root HUB Intel>  at usbus4, cfg=0 md=HOST spd=HIGH
> >>(480Mbps) pwr=ON
> >>ugen4.2:<product 0x1780 vendor 0x0b95>  at usbus4, cfg=0 md=HOST
> >>spd=HIGH (480Mbps) pwr=ON
> >>ugen0.2:<Optical Mouse Genius>  at usbus0, cfg=0 md=HOST spd=LOW
> >>(1.5Mbps) pwr=ON
> >>
> >>ifconfig:
> >>ue0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>  metric 0 mtu 1500
> >>ether 00:0e:c6:88:09:4e
> >>inet 192.168.2.22 netmask 0xffffff00 broadcast 192.168.2.255
> >>media: Ethernet autoselect (100baseTX<full-duplex>)
> >>status: active
> >>
> >>Thank you for you help!
> >>     
> >   
> 
> 
> -- 
> Regards, Sergey.
> 


More information about the freebsd-net mailing list