I think it would be very useful if it would be possible to set log_ip from the webinterface. I have now set it with SSH:

<shell>

  uci set system.@system[0].log_ip=192.168.254.1
  uci commit
  reboot

</shell>

But I think that it could be useful for other people.

If setting log_ip all syslog messages gets sent to that IP address (where a syslog server should be running).

I was able to successfully install syslog-ng3 on Gargoyle TPlink WR1043ND and logging to remote syslog running on my Debian home server.

<shell> opkg update opkg install syslog-ng3 </shell> and missing dependency, syslog-ng won't start without it

<shell> opkg install libdbi </shell>

Configuration: Edit syslog-ng.conf

<shell> root@Gargoyle:~# cat /etc/syslog-ng.conf @version:3.0

options {

      chain_hostnames(no);
      create_dirs(yes);
      flush_lines(0);
      keep_hostname(yes);
      log_fifo_size(256);
      log_msg_size(1024);
      stats_freq(0);
      flush_lines(0);
      use_fqdn(no);

};

source src {

      internal();
      unix-stream("/dev/log");

};

source net {

      udp(ip(0.0.0.0) port(514));

};

source kernel {

      file("/proc/kmsg" program_override("kernel"));

};

destination messages {

      file("/var/log/messages");

}; destination d_udp { udp(“192.168.0.113” port(514)); }; log {

      source(src);
      source(net);
      source(kernel);
      destination(d_udp);

# destination(messages); }; </shell>

I am using my Debian home server and syslog server, here are the relevant lines from syslog server config

<shell> destination routermsg { file(“/var/log/router.log”); }; filter f_router { host(192.168.0.1); }; log { source(remoteudp); filter(f_router); destination(routermsg); }; </shell>