linuxdcpp-team team mailing list archive

[klondike <franxisco1988@xxxxxxxxx>]

This patch makes all the scripts use the get_level function to check the
user level. This makes it easier to have per session levels, or in
general any other kind of level handling since it is now registered.

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
https://bugs.launchpad.net/bugs/930960

Title:
  Adch++ doesnt work on ARM architecture

Status in ADCH++:
  New

Bug description:
  Hi,

  i compiled ADCH++ 2.7.0 on Debian Squeeze on an ARM machine (Seagate Dockstar). It starts, but when i try to connect via adc or adcs i get this error message "This hub requires BASE support". The TCP connection then closes.
  I compiled the same version on an x86_64 machine and used the same config files and there it worked perfectly.
  I compiled via "scons mode=release".
  I watched at the TCP traffic via wireshark and this is what i see:
  client --> hub: HSUP ADBAS0 ADBASE ADTIGR ADUCM0 ADBLO0
  hub --> client: ISTA 240 This\shub\srequires\sBASE\ssupport
  What can i do to make adch++ work on my ARM machine?

  EDIT: I just tried version 2.8.0 in debug mode, but its the same
  problem. Heres the output:

  Starting.Logging: 2012-02-12 14:52:15: core: Core initialized
  .Processing HubName
  Processing Description
  Processing Log
  Processing LogFile
  Processing MaxSendSize
  Processing MaxBufferSize
  Processing BufferSize
  Processing MaxCommandSize
  Processing OverflowTimeout
  Processing KeepSlowUsers
  Processing BufferSize
  Processing DisconnectTimeout
  Processing LoginTimeout
  .
  2.8.0 (r0) Debug running, press ctrl-c to exit...
  Logging: 2012-02-12 14:52:15: ScriptManager: Starting
  Logging: 2012-02-12 14:52:15: PluginManager: Script.so loaded
  Logging: 2012-02-12 14:52:15: SocketManager: Starting
  Logging: 2012-02-12 14:52:15: SocketManager: Listening on 0.0.0.0:3002 (Encrypted: No)
  Logging: 2012-02-12 14:52:15: SocketManager: Listening on [::]:3002 (Encrypted: No)
  V4S7 entering IDENTIFY
  V4S7 entering NORMAL
  BNGJ connected
  BNGJ ready
  BNGJ disconnecting because 12
  Removing BNGJ - AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
  ManagedSocket deleted
  SocketStream deleted

  
  Regards
  oopepe

To manage notifications about this bug go to:
https://bugs.launchpad.net/adchpp/+bug/930960/+subscriptions