DSM-G600, DNS-3xx and NSA-220 Hack Forum

lucien wrote:

Bonjour

J'ai fait de ping vers des pc, serveur d'impression, routeur ... rien n'y fais. La commande arp -an me renvoi "? (192.168.0.2) at <incomplete>  on eth0"
Le ping sur le dns fait bien clignoter les led du switch.

So you tried to ping 192.168.0.2 ? What is on this address? Your computer?
This shows that outgoing pings seem to work but nobody is sending the answer for the pings or it iis sending answers in the wrong direction.
This was the reason why I asked whether the gateway and the net mask  is the same for all of your components.
On what addresses are your router/gateway and your computer anyhow?

How about the Transmit counter on ifconfig?

If you change the ethtool command to
ethtool -S eth0

it will return the complete statistics for this interface.
On my box this looks like this:

# ethtool -S eth0
NIC statistics:
     rx_packets: 92
     tx_packets: 84
     rx_bytes: 6720
     tx_bytes: 10206
     rx_errors: 0
     tx_errors: 0
     rx_dropped: 0
     tx_dropped: 0
     good_octets_received: 7558
     bad_octets_received: 0
     internal_mac_transmit_err: 0
     good_frames_received: 96
     bad_frames_received: 0
     broadcast_frames_received: 1
     multicast_frames_received: 5
     frames_64_octets: 8
     frames_65_to_127_octets: 164
     frames_128_to_255_octets: 2
     frames_256_to_511_octets: 3
     frames_512_to_1023_octets: 1
     frames_1024_to_max_octets: 2
     good_octets_sent: 10596
     good_frames_sent: 84
     excessive_collision: 0
     multicast_frames_sent: 0
     broadcast_frames_sent: 23
     unrec_mac_control_received: 0
     fc_sent: 0
     good_fc_received: 0
     bad_fc_received: 0
     undersize_received: 0
     fragments_received: 0
     oversize_received: 0
     jabber_received: 0
     mac_receive_error: 0
     bad_crc_event: 0
     collision: 0
     late_collision: 0
     lro_aggregated: 0
     lro_flushed: 0
     lro_no_desc: 0
# arp -an
? (192.168.250.11) at 00:04:0e:a9:29:34 [ether]  on eth0
? (192.168.250.20) at 00:21:85:c5:7f:31 [ether]  on eth0
# ping 192.168.250.23
PING 192.168.250.23 (192.168.250.23): 56 data bytes
^C
--- 192.168.250.23 ping statistics ---
6 packets transmitted, 0 packets received, 100% packet loss
# arp -an
? (192.168.250.23) at <incomplete>  on eth0
? (192.168.250.11) at 00:04:0e:a9:29:34 [ether]  on eth0
? (192.168.250.20) at 00:21:85:c5:7f:31 [ether]  on eth0
#

As you can see here a ping to a non existing address (192.168.250.23)
results in an incomplete arp entry.

lucien wrote:

La commande "ethtool eth0" me renvoi
# ethtool eth0
Settings for eth0:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 8
        Transceiver: external
        Auto-negotiation: on
        Link detected: yes
#

Ethtool reports that it negotiated 100Mb/sec which shows clearly that things on the link level are working.
So please do the tests Joao proposed and report back.

À  tout  à  l'heure  !
Norbert

lucien wrote:

192.168.0.2 is my pc ip. netmask 255.255.255.0 and gateway 192.168.0.254 is in all the material.
when i ping 192.168.0.254 (my router), i have answer with the original dlink firmware but when i start Alt-f (. ./fun_plug.nogi), i have no answer.

# ethtool -S eth0
NIC statistics:
     tx_packets: 3
     rx_bytes: 0
     tx_bytes: 126
     rx_errors: 0
     tx_errors: 0
     rx_dropped: 0
     tx_dropped: 0
     good_octets_received: 0
============================ >
     bad_octets_received: 1572672
============================ > This is really strange!!!!!
     internal_mac_transmit_err: 0
     good_frames_received: 0
     bad_frames_received: 96
============================ > And this one, too!
     fragments_received: 96
============================ >

I have e question. when i switch autoneg as off the Link detected switch off too, is it normal?
an other question. at first the link is at 100Mb/s and when i disconnect and connect the cable, the link is at 10Mb/s. Is it normal?

Thank a lot for a old man (not so old ;-).

If you disable auto-negotiation on the DNS and remove and reconnect the cable, the DNS can not negotiate speed any more
and falls back to the lowest speed which is 10MBit/s.

Regarding the "strange" parts.
Does it really say "B1" on the label on the bottom of your DNS? This errors look a bit like those mushanga got with his
rev C1 board.

And do not flutter yourself beeing an old man: I'm 63. Can you top that ;-)

Norbert

lucien wrote:

hello

the 2 questions is separate.

-If i make "ethtool -s autoneg off" (with cable allways connected)  the answer with a "ethtool eth0" is than "auto negotiation  off" and  "link detected off".
-At first the link is at 100Mb/s and when i disconnect and connect the cable, the link is at 10Mb/s.
Yesterday i connected the dns with a right cable to a ubuntu pc. Ping have no answers PC to dns or dns to pc. I have connected the same ubuntu pc to a windows 7 pc in the same way and the ping have answers, Ubuntu to Win7 or win7 to pc is oK.

FN323E B1g
HW ver B1
And in the Mother board is B1 too.

thank a lot.

Hello,

On my DNS it reads:
P/N: ENS323M.....B1G
HW Ver.: B1
Serial Number:
S/N: P1B193000082

So it is most probably the same Printed Circuit Board. What we do not know is whether DLINK used the same chips.
Perhaps is the network chip a different version of the same family.

From the ethtool printout you sent in the previous message it looks like  in the kernel there is a bug / wrong pointer or so, because of
============================ >
     bad_octets_received: 1572672
============================ >
you kan not get millions of wrong octets when sending just three pings and even if the system thinks it got:
============================
     fragments_received: 96
============================

So, to solve this puzzle we would need someone with really deep understanding of
the LINUX network drivers.

.

Sorry for the delay

Yes it me who have clear my adresse mac (I'm a little paranoid)

answer arp -na from my pc ubuntu

luc@pcluc:~$ ping 192.168.0.171 -c 5
PING 192.168.0.171 (192.168.0.171) 56(84) bytes of data.
From 192.168.0.2 icmp_seq=1 Destination Host Unreachable
From 192.168.0.2 icmp_seq=2 Destination Host Unreachable
From 192.168.0.2 icmp_seq=3 Destination Host Unreachable
From 192.168.0.2 icmp_seq=4 Destination Host Unreachable
From 192.168.0.2 icmp_seq=5 Destination Host Unreachable

--- 192.168.0.171 ping statistics ---
5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 4024ms
, pipe 3
luc@pcluc:~$ arp -na
? (192.168.0.171) à <incomplet> sur eth0
? (192.168.0.254) à 00:14:bf::xx:xx:xx [ether] sur eth0
luc@pcluc:~$

Answers arping -Dw from my pc ubuntu

luc@pcluc:~$ arping -Dw 5 192.168.0.171
ARPING 192.168.0.171 from 0.0.0.0 eth0
Sent 6 probes (6 broadcast(s))
Received 0 response(s)
luc@pcluc:~$

Answers arping -Dbw from my pc ubuntu

luc@pcluc:~$ arping -Dbw 5 192.168.0.171
ARPING 192.168.0.171 from 0.0.0.0 eth0
Sent 6 probes (6 broadcast(s))
Received 0 response(s)
luc@pcluc:~$


luc@pcluc:~$ nmap -v -sP 192.168.0.0/24

Starting Nmap 5.00 ( http://nmap.org ) at 2010-05-22 08:43 CEST
NSE: Loaded 0 scripts for scanning.
Initiating Ping Scan at 08:43
Scanning 256 hosts [2 ports/host]
Completed Ping Scan at 08:43, 2.62s elapsed (256 total hosts)
Initiating Parallel DNS resolution of 256 hosts. at 08:43
Completed Parallel DNS resolution of 256 hosts. at 08:43, 0.00s elapsed
Host 192.168.0.0 is down.
Host 192.168.0.1 is down.
Host pcluc (192.168.0.2) is up (0.00015s latency).
Host 192.168.0.3 is down.
Host 192.168.0.4 is down.
Host 192.168.0.5 is down.
Host 192.168.0.6 is down.
Host pcVic (192.168.0.7) is up (0.0013s latency).
Host 192.168.0.8 is down.
Host 192.168.0.9 is down.
Host 192.168.0.10 is down.
Host 192.168.0.11 is down.
Host 192.168.0.12 is down.
Host 192.168.0.13 is down.
Host 192.168.0.14 is down.
Host 192.168.0.15 is down.
Host 192.168.0.16 is down.
Host 192.168.0.17 is down.
Host 192.168.0.18 is down.
Host 192.168.0.19 is down.
Host 192.168.0.20 is down.
Host 192.168.0.21 is down.
Host 192.168.0.22 is down.
Host 192.168.0.23 is down.
Host 192.168.0.24 is down.
Host 192.168.0.25 is down.
Host 192.168.0.26 is down.
Host 192.168.0.27 is down.
Host 192.168.0.28 is down.
Host 192.168.0.29 is down.
Host 192.168.0.30 is down.
Host 192.168.0.31 is down.
Host 192.168.0.32 is down.
Host 192.168.0.33 is down.
Host 192.168.0.34 is down.
Host 192.168.0.35 is down.
Host 192.168.0.36 is down.
Host 192.168.0.37 is down.
Host 192.168.0.38 is down.
Host 192.168.0.39 is down.
Host 192.168.0.40 is down.
Host 192.168.0.41 is down.
Host 192.168.0.42 is down.
Host 192.168.0.43 is down.
Host 192.168.0.44 is down.
Host 192.168.0.45 is down.
Host 192.168.0.46 is down.
Host 192.168.0.47 is down.
Host 192.168.0.48 is down.
Host 192.168.0.49 is down.
Host 192.168.0.50 is down.
Host 192.168.0.51 is down.
Host 192.168.0.52 is down.
Host 192.168.0.53 is down.
Host 192.168.0.54 is down.
Host 192.168.0.55 is down.
Host 192.168.0.56 is down.
Host 192.168.0.57 is down.
Host 192.168.0.58 is down.
Host 192.168.0.59 is down.
Host 192.168.0.60 is down.
Host 192.168.0.61 is down.
Host 192.168.0.62 is down.
Host 192.168.0.63 is down.
Host 192.168.0.64 is down.
Host 192.168.0.65 is down.
Host 192.168.0.66 is down.
Host 192.168.0.67 is down.
Host 192.168.0.68 is down.
Host 192.168.0.69 is down.
Host 192.168.0.70 is down.
Host 192.168.0.71 is down.
Host 192.168.0.72 is down.
Host 192.168.0.73 is down.
Host 192.168.0.74 is down.
Host 192.168.0.75 is down.
Host 192.168.0.76 is down.
Host 192.168.0.77 is down.
Host 192.168.0.78 is down.
Host 192.168.0.79 is down.
Host 192.168.0.80 is down.
Host 192.168.0.81 is down.
Host 192.168.0.82 is down.
Host 192.168.0.83 is down.
Host 192.168.0.84 is down.
Host 192.168.0.85 is down.
Host 192.168.0.86 is down.
Host 192.168.0.87 is down.
Host 192.168.0.88 is down.
Host 192.168.0.89 is down.
Host 192.168.0.90 is down.
Host 192.168.0.91 is down.
Host 192.168.0.92 is down.
Host 192.168.0.93 is down.
Host 192.168.0.94 is down.
Host 192.168.0.95 is down.
Host 192.168.0.96 is down.
Host 192.168.0.97 is down.
Host 192.168.0.98 is down.
Host 192.168.0.99 is down.
Host 192.168.0.100 is down.
Host 192.168.0.101 is down.
Host 192.168.0.102 is down.
Host 192.168.0.103 is down.
Host 192.168.0.104 is down.
Host 192.168.0.105 is down.
Host 192.168.0.106 is down.
Host 192.168.0.107 is down.
Host 192.168.0.108 is down.
Host 192.168.0.109 is down.
Host 192.168.0.110 is down.
Host 192.168.0.111 is down.
Host 192.168.0.112 is down.
Host 192.168.0.113 is down.
Host 192.168.0.114 is down.
Host 192.168.0.115 is down.
Host 192.168.0.116 is down.
Host 192.168.0.117 is down.
Host 192.168.0.118 is down.
Host 192.168.0.119 is down.
Host 192.168.0.120 is down.
Host 192.168.0.121 is down.
Host 192.168.0.122 is down.
Host 192.168.0.123 is down.
Host 192.168.0.124 is down.
Host 192.168.0.125 is down.
Host 192.168.0.126 is down.
Host 192.168.0.127 is down.
Host 192.168.0.128 is down.
Host 192.168.0.129 is down.
Host 192.168.0.130 is down.
Host 192.168.0.131 is down.
Host 192.168.0.132 is down.
Host 192.168.0.133 is down.
Host 192.168.0.134 is down.
Host 192.168.0.135 is down.
Host 192.168.0.136 is down.
Host 192.168.0.137 is down.
Host 192.168.0.138 is down.
Host 192.168.0.139 is down.
Host 192.168.0.140 is down.
Host 192.168.0.141 is down.
Host 192.168.0.142 is down.
Host 192.168.0.143 is down.
Host 192.168.0.144 is down.
Host 192.168.0.145 is down.
Host 192.168.0.146 is down.
Host 192.168.0.147 is down.
Host 192.168.0.148 is down.
Host 192.168.0.149 is down.
Host 192.168.0.150 is down.
Host 192.168.0.151 is down.
Host 192.168.0.152 is down.
Host 192.168.0.153 is down.
Host 192.168.0.154 is down.
Host 192.168.0.155 is down.
Host 192.168.0.156 is down.
Host 192.168.0.157 is down.
Host 192.168.0.158 is down.
Host 192.168.0.159 is down.
Host 192.168.0.160 is down.
Host 192.168.0.161 is down.
Host 192.168.0.162 is down.
Host 192.168.0.163 is down.
Host 192.168.0.164 is down.
Host 192.168.0.165 is down.
Host 192.168.0.166 is down.
Host 192.168.0.167 is down.
Host 192.168.0.168 is down.
Host 192.168.0.169 is down.
Host Brother (192.168.0.170) is up (0.017s latency).
Host 192.168.0.171 is down.
Host 192.168.0.172 is down.
Host 192.168.0.173 is down.
Host 192.168.0.174 is down.
Host 192.168.0.175 is down.
Host 192.168.0.176 is down.
Host 192.168.0.177 is down.
Host 192.168.0.178 is down.
Host 192.168.0.179 is down.
Host 192.168.0.180 is down.
Host 192.168.0.181 is down.
Host 192.168.0.182 is down.
Host 192.168.0.183 is down.
Host 192.168.0.184 is down.
Host 192.168.0.185 is down.
Host 192.168.0.186 is down.
Host 192.168.0.187 is down.
Host 192.168.0.188 is down.
Host 192.168.0.189 is down.
Host 192.168.0.190 is down.
Host 192.168.0.191 is down.
Host 192.168.0.192 is down.
Host 192.168.0.193 is down.
Host 192.168.0.194 is down.
Host 192.168.0.195 is down.
Host 192.168.0.196 is down.
Host 192.168.0.197 is down.
Host 192.168.0.198 is down.
Host 192.168.0.199 is down.
Host 192.168.0.200 is down.
Host 192.168.0.201 is down.
Host 192.168.0.202 is down.
Host 192.168.0.203 is down.
Host 192.168.0.204 is down.
Host 192.168.0.205 is down.
Host 192.168.0.206 is down.
Host 192.168.0.207 is down.
Host 192.168.0.208 is down.
Host 192.168.0.209 is down.
Host 192.168.0.210 is down.
Host 192.168.0.211 is down.
Host 192.168.0.212 is down.
Host 192.168.0.213 is down.
Host 192.168.0.214 is down.
Host 192.168.0.215 is down.
Host 192.168.0.216 is down.
Host 192.168.0.217 is down.
Host 192.168.0.218 is down.
Host 192.168.0.219 is down.
Host 192.168.0.220 is down.
Host 192.168.0.221 is down.
Host 192.168.0.222 is down.
Host 192.168.0.223 is down.
Host 192.168.0.224 is down.
Host 192.168.0.225 is down.
Host 192.168.0.226 is down.
Host 192.168.0.227 is down.
Host 192.168.0.228 is down.
Host 192.168.0.229 is down.
Host 192.168.0.230 is down.
Host 192.168.0.231 is down.
Host 192.168.0.232 is down.
Host 192.168.0.233 is down.
Host 192.168.0.234 is down.
Host 192.168.0.235 is down.
Host 192.168.0.236 is down.
Host 192.168.0.237 is down.
Host 192.168.0.238 is down.
Host 192.168.0.239 is down.
Host 192.168.0.240 is down.
Host 192.168.0.241 is down.
Host 192.168.0.242 is down.
Host 192.168.0.243 is down.
Host 192.168.0.244 is down.
Host 192.168.0.245 is down.
Host 192.168.0.246 is down.
Host 192.168.0.247 is down.
Host 192.168.0.248 is down.
Host 192.168.0.249 is down.
Host 192.168.0.250 is down.
Host 192.168.0.251 is down.
Host 192.168.0.252 is down.
Host 192.168.0.253 is down.
Host WRT54GSV4 (192.168.0.254) is up (0.0010s latency).
Host 192.168.0.255 is down.
Nmap done: 256 IP addresses (4 hosts up) scanned in 2.63 seconds
luc@pcluc:~$

thank a lot.
I hope that i costs more than a Guinea ;-)

Last edited by lucien (2010-05-22 10:02:34)

I confirm the results that Lucien reported when I use a Thomson router (or a direct cable connection to a Asus laptop).

The same exact results, including the  bad_octets_received,  bad_frames_received and fragments_received that ethertool -S reports; those numbers continue growing when one pings the unity. The frames seem to be received as garbage.

ethertool renegotiation or settings changes have no effect.

I now suspect that mushanga problem is related to this one and not specific to the rev-C1 board. He is also using a French router :-) and a direct connection to a Mac laptop works fine for him.

As mushanga says that he already tried other debian kernels, all with the same results, it has to be a more generic problem.
I will peek dlink kernel source code, to see if there are some changes to the PHY code. (but there are many boards/cards using the marvel network and PHY drivers, and googling does not shows sign of problems.)

I already tried compiling the net and PHY drivers as modules, not compiling the marvel 88e1111 PHY driver (using a generic one), using 2.6.33.4, etc, but nothing succeeds.

Is anybody with some deeper understanding of this kind of issues lurking around?

Thanks.
Joao

Last edited by jcard (2010-05-27 00:33:24)

lucien wrote:

hello

My case advance. I have connect the dns to a gigabit pc card and then the ping work, alt_f administration interface work to.

the marvell dont negotiat with the other eth card. It connect at 1000mb but not under.
it have a problem with the autoneg.

thank in advance.

It looks like auto-negotiation is defective and we can only use Gbit connections.

At home I always use a Gbit switch, and was not aware of this problem.
I can't  connect to a 100Mbit router nor to a 100Mbit network card on a notebook.
I can connect to a  iMac with a Gbit card, but only at GBit speed, I can't renegotiate lower speeds.
I already tried a 2.6.34 kernel with the same results.

By the end of the week I will try other 100 Mbit routers, switches and direct cable PCs with both 1Gbit and 100Mbits cards.

Norbert, are you using Giga or Mega bits cards/routers/modems?

Can anybody else confirm or rebut this hypothesis?

Last edited by jcard (2010-06-01 01:00:40)

jcard wrote:

hello


By the end of the week I will try other 100 Mbit routers, switches and direct cable PCs with both 1Gbit and 100Mbits cards.

Norbert, are you using Giga or Mega bits cards/routers/modems?

Can anybody else confirm or rebut this hypothesis?

I can confirm each end everyone of  your tests.
(Un)fortunatly I could not publish because I was getting ready
for our vacation.

When switching speed with ethtool or when changing the cable from a working
gigabyte switch to a 100Mb switch the LEDs on this switch show that the DNS is trying
to negotiate but fails.

Also "dmesg" shows always "setting speed to 1000Mb" messages.

Since I am about 900km away from my DNS323 I will be
of no help for the next couple of weeks.

b.t.w Weather is nice here in Italy.

Keep up the good work and I´m already eagerly awaiting the next
version of ALT-F. (after vacation)

Thanks Lucien, Norbert and mushanga for helping diagnose this problem.

Conclusion: Alt-F only works (for now!) with Gbit switches or network cards, because auto-negotiation is not working.

As mushanga noticed, there is some work on marvel PHYs on linux.ports.arm.kernel, hopefully 0.1B4 will have the issue solved.

After two weeks of forced inactivity on Alt-F, I have a one week time window before my holidays to release 0.1B3. I hope I can manage it.

congee, thanks for your offering to immolation :-)
Rev-C1 hardware is not yet supported by Alt-F. Leds, buttons and fan speed seems to be the only difference to rev-B1 boards, perhaps for 0.1B4 they wiil be sorted out -- and I will accept your offer.

Hi,

It seems Ben Herrenschmidt keeps a good pace
Its patches have been accepted in the last ARM Kernel tree : http://git.kernel.org/?p=linux/kernel/g … ;a=summary
When I have time I'll try to compile and test this kernel but I cannot tell you when...

Don't want to ask too much but jcard, could you build a test version around the orion git sources?

Last edited by mushanga (2010-06-30 14:32:30)

I'm trying to build the OpenWRT firmware for my DNS323 (rev B1), but am having much fun with u-boot, not wanting to write my new kernel to the flash.

Have you had any problems with this, and if so, how have you got around them?