Modify

Opened 10 years ago

Closed 10 years ago

Last modified 4 years ago

#2386 closed defect (fixed)

compex np28g - unstable network connection

Reported by: xkennyx at seznam.cz Owned by: juhosg
Priority: high Milestone: Barrier Breaker 14.07
Component: kernel Version:
Keywords: compex adm5120 network np28g Cc:

Description

Hello,
there is problem with network stability (rev 8770) on compex np28g router (adm5120).
Steps to reproduce:

1.I flushed all iptables (set to ACCEPT)
2. set eth3 as wan
3. set eth1 as lan - 192.168.168.1  (100MB link)
4. ssh to router
5. then start typing something in
error: sometime unable type for few seconds (cca 20s ?)
in wireshark you can see retransmits

(sorry for english)

Attachments (0)

Change History (11)

comment:1 Changed 10 years ago by xkennyx at seznam.cz

update: there is probably problem in receiving packets from network. Receiving fail after bigger traffic (ssh login).

Here you can see number of packet transmited and received. I send arpping to my PC, where i see in wireshark the arp request and answer. But here is the receive counter at the same value.

root@OpenWrt:/# cat /proc/net/dev
Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
    lo:    3136      28    0    0    0     0          0         0     3136      28    0    0    0     0       0          0
  eth0:      60       1    0    0    0     0          0         0     4578     109    0    0    0     0       0          0
  eth1:    3060      51    0    0    0     0          0         0     1890      45    0    0    0     0       0          0
  eth2:       0       0    0    0    0     0          0         0       84       2    0    0    0     0       0          0
  eth3:   61940     594    0    0    0     0          0         0    48146     629    0    0    0     0       0          0
  eth4:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
  eth5:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
 wifi0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
root@OpenWrt:/# arping -i eth3 192.168.168.2
ARPING to 92.168.168.13 from 192.168.168.13 via eth3
Sent 9 probe(s) (9 broadcast(s))
Received 0 reply (0 request(s), 0 broadcast(s))
root@OpenWrt:/# cat /proc/net/dev
Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
    lo:    3136      28    0    0    0     0          0         0     3136      28    0    0    0     0       0          0
  eth0:      60       1    0    0    0     0          0         0     4578     109    0    0    0     0       0          0
  eth1:    3060      51    0    0    0     0          0         0     1890      45    0    0    0     0       0          0
  eth2:       0       0    0    0    0     0          0         0       84       2    0    0    0     0       0          0
  eth3:   61940     594    0    0    0     0          0         0    48524     638    0    0    0     0       0          0
  eth4:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
  eth5:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
 wifi0:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0

comment:2 Changed 10 years ago by juhosg

  • Owner changed from developers to juhosg
  • Status changed from new to assigned

comment:3 Changed 10 years ago by anonymous

arp -a
192.168.1.1 0x1 0x0 00:00:00:00:00:00 * br-lan

Asus wl-500gp Kamikaze 7.07 in 2007.10.04

comment:4 Changed 10 years ago by xkennyx at seznam.cz

Hello, i tryed revision 9285 and problem is still here :(

root@OpenWrt:/$ ping 192.168.168.2
PING 192.168.168.2 (192.168.168.2): 56 data bytes
64 bytes from 192.168.168.2: seq=0 ttl=64 time=1.642 ms
64 bytes from 192.168.168.2: seq=1 ttl=64 time=1.260 ms
64 bytes from 192.168.168.2: seq=2 ttl=64 time=45248.255 ms
64 bytes from 192.168.168.2: seq=3 ttl=64 time=44240.721 ms
64 bytes from 192.168.168.2: seq=4 ttl=64 time=43237.097 ms
64 bytes from 192.168.168.2: seq=5 ttl=64 time=42233.520 ms
64 bytes from 192.168.168.2: seq=6 ttl=64 time=41229.938 ms
64 bytes from 192.168.168.2: seq=7 ttl=64 time=40226.323 ms
64 bytes from 192.168.168.2: seq=47 ttl=64 time=14.727 ms
64 bytes from 192.168.168.2: seq=83 ttl=64 time=984.645 ms

--- 192.168.168.2 ping statistics ---

89 packets transmitted, 10 packets received, 88% packet loss
round-trip min/avg/max = 1.260/25741.812/45248.255 ms

I'm ready for some testing :)

comment:5 Changed 10 years ago by juhosg

Would you try it with [9330]?

comment:6 Changed 10 years ago by xkennyx at seznam.cz

oki :) on the weekend or soon :)

comment:7 follow-up: Changed 10 years ago by xkennyx at seznam.cz

I tried [9359] and it is worst:

arp
IP address       HW type     Flags       HW address            Mask     Device
192.168.168.2    0x1         0x0         00:00:00:00:00:00     *        eth3

arping -I eth3 192.168.168.2 - no response, but I see request on PC in wireshark.

ping 192.168.168.2 - the same

on PC side:

arping -I lan1 192.168.168.13
ARPING 192.168.168.13 from 192.168.168.2 lan1
Unicast reply from 192.168.168.13 [00:41:44:4D:51:23]  19.442ms
Sent 41 probes (1 broadcast(s))
Received 1 response(s)

arping -I lan1 192.168.168.13
ARPING 192.168.168.13 from 192.168.168.2 lan1
Unicast reply from 192.168.168.13 [00:41:44:4D:51:23]  18.892ms
Sent 10 probes (1 broadcast(s))
Received 1 response(s)


there is only response to ?unicast?

do you need some other information ?

best regards
Jarek

comment:8 in reply to: ↑ 7 Changed 10 years ago by juhosg

Replying to xkennyx at seznam.cz:

arping -I eth3 192.168.168.2 - no response, but I see request on PC in wireshark.


ping 192.168.168.2 - the same

Should be fixed with [9361].

comment:9 Changed 10 years ago by xkennyx at seznam.cz

it's working now :) thanks :)

comment:10 Changed 10 years ago by juhosg

  • Resolution set to fixed
  • Status changed from assigned to closed

comment:11 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.