aMule Forum

English => en_Linux => Topic started by: sai on January 28, 2007, 11:01:10 AM

Title: [solved] wrong settings for OS / broken network card?
Post by: sai on January 28, 2007, 11:01:10 AM

Hi!

I got a message from my network admin, that my pc sends wrong tcp packages.
Now I try to find the solution.

The error messages are of this kind:

Code: [Select]

   1  134.109.96.85    83.59.70.235     (snort_decoder) WARNING: TCP Data Offset is less than 5!
    1  134.109.96.85    83.60.71.55      (snort_decoder) WARNING: TCP Data Offset is less than 5!
    1  134.109.96.85    83.76.248.212    (snort_decoder) WARNING: TCP Data Offset is less than 5!
    1  134.109.96.85    83.23.168.72     (snort_decoder): Truncated Tcp Options
Can it be linked in any way with aMule? Which settings could I try to change?

The admin also said, that my network card could be broken. But this is an onboard network card, I have the newest driver... could it still be broken in any way?

Mainboard: ASUS M2V
Chipsatz: Attansic Technology Corp. (rev. b0), version 0.1.40.6, atl1.7

Thanks a lot,
sai

Title: Re: wrong settings for OS / broken network card?
Post by: lfroen on January 28, 2007, 05:30:26 PM

Quote

Can it be linked in any way with aMule?

You should check source port in those TCP packets and compare it vs. port aMule using.

Quote

But this is an onboard network card, I have the newest driver

TCP header is not coming from card driver (but from protocol stack).

I don't see good way of debugging the problem except of setting up sniffer and analyzing it's log.

Title: Re: wrong settings for OS / broken network card?
Post by: sai on January 04, 2009, 04:21:21 PM

Jaa, I mean, don't you just hate it when you search the web and there is someone with the same problem as you but no solution?

All I had to do was to configure the network correctly, as follows:

Code: [Select]

ifconfig eth0 down
 ifconfig eth0 xxx.xxx.your-ip.xxx  netmask xxx.xxx.your-netmask.x;route add default gw xxx.xxx.your-gateway.xxx;echo "nameserver xxx.xxx.your-nameserver.xxx">>/etc/resolv.conf
ifconfig eth0 upAnd maybe all that resulted from a misconfiguration of the dhcp server.

However, problem solved! Had nothing to do with amule. Sorry for the late bump up.