I have not looked how the time update is realised in the FW, i meaned if it isnt possible to generate the message when update succeedet, not when he tryes to.Originally Posted by Oleg
Greets
I try 3b now.
That was the problem....Originally Posted by Oleg
sorry for wasting your time....
Pipos (2xWL-500g, WDS-only mode, used as backbone for MAN network; 1xWL-500g in Client Mode with NAT)
I have not looked how the time update is realised in the FW, i meaned if it isnt possible to generate the message when update succeedet, not when he tryes to.Originally Posted by Oleg
Greets
I try 3b now.
My Stuff: WL-500g, Mapower H31x 10GB HD, Philips Webcam Vesta PRO, TerraTec Webcam PRO, USB Hub
This is in fact dropbear 0.44test4 bug - no host lookups flag is ignored...Originally Posted by pipos
Hi,
Seems I'm th only one with problem I've described here before... and I keep on fighting it!
So, Could some one explain to me why there are so much and identical dhcp logs? Is it normal?
Code:Jan 14 13:45:23 ntp client: time is synchronized to time.nist.gov Jan 14 13:46:01 dnsmasq[49]: DHCPDISCOVER(br0) 00:0e:35:39:d0:11 Jan 14 13:46:01 dnsmasq[49]: DHCPOFFER(br0) 192.168.1.28 00:0e:35:39:d0:11 Jan 14 13:46:04 dnsmasq[49]: DHCPDISCOVER(br0) 00:0e:35:39:d0:11 Jan 14 13:46:04 dnsmasq[49]: DHCPOFFER(br0) 192.168.1.28 00:0e:35:39:d0:11 Jan 14 13:46:07 dnsmasq[49]: DHCPDISCOVER(br0) 00:0e:35:39:d0:11 Jan 14 13:46:07 dnsmasq[49]: DHCPOFFER(br0) 192.168.1.28 00:0e:35:39:d0:11 Jan 14 13:46:10 dnsmasq[49]: DHCPDISCOVER(br0) 00:0e:35:39:d0:11 Jan 14 13:46:10 dnsmasq[49]: DHCPOFFER(br0) 192.168.1.28 00:0e:35:39:d0:11 Jan 14 13:46:13 dnsmasq[49]: DHCPDISCOVER(br0) 00:0e:35:39:d0:11 Jan 14 13:46:13 dnsmasq[49]: DHCPOFFER(br0) 192.168.1.28 00:0e:35:39:d0:11 Jan 14 13:46:16 dnsmasq[49]: DHCPDISCOVER(br0) 00:0e:35:39:d0:11 Jan 14 13:46:16 dnsmasq[49]: DHCPOFFER(br0) 192.168.1.28 00:0e:35:39:d0:11 Jan 14 13:46:16 dnsmasq[49]: DHCPREQUEST(br0) 192.168.1.28 00:0e:35:39:d0:11 Jan 14 13:46:16 dnsmasq[49]: DHCPACK(br0) 192.168.1.28 00:0e:35:39:d0:11 ulysse Jan 14 13:46:16 dnsmasq[49]: DHCPREQUEST(br0) 192.168.1.28 00:0e:35:39:d0:11 Jan 14 13:46:16 dnsmasq[49]: DHCPACK(br0) 192.168.1.28 00:0e:35:39:d0:11 ulysse Jan 14 13:46:22 dnsmasq[49]: DHCPREQUEST(br0) 192.168.1.28 00:0e:35:39:d0:11 Jan 14 13:46:22 dnsmasq[49]: DHCPACK(br0) 192.168.1.28 00:0e:35:39:d0:11 ulysse
Seems, some packets are get missed by your PC, but as soon as it got an IP address - every is fine, don't think about this. If these packets are from wireless clients and they've WPA enabled, then you could try playing with wireless drivers if you don't want for messages to appear multiple times.Originally Posted by Spot
Would it be possible to add an option to en/disable the usb speaker software (waveservermain) to the webinterface?
Probably.Originally Posted by Styno
Originally Posted by Oleg
Thaks oleg for your answer.
No param can give best results for me.
But I really suspect a compatibility issue with intel centrino... MAV is another user experimenting same problems as me...
Upgraded to 3b, and my router DID reconnect after my ISP terminated the connection!
Thanks Oleg!
Upgraded to 3b and found that /etc/smb.conf (default file was present on 2 version) was missing. This is what I used.
Note that I had to change 'force user' from root to admin.Code:[global] workgroup = WORKGROUP guest account = nobody security = share browseable = yes guest ok = yes guest only = yes log level = 1 max log size = 100 encrypt passwords = no dns proxy = no [share] path = /tmp/harddisk/ [share$] path = /tmp/harddisk/ writable = yes force user = admin browseable = no
This file is now produced automagically with correct options, once samba is enabled in the web interface and usb drive is plugged in. You could also customize it and save to flashfs - this way web settings will not have any effect on the file content.Originally Posted by sodb
Oops, I just did not see the whole new Sambe GUI under USB Applications. I installed samba manually. I give it a try through the user interface.
Styno, I'm a bit lazy. So, add these lines to post-boot instead:Originally Posted by Styno
Code:killall waveservermain rmmod audio rmmod soundcore
Hello!
When I upgraded 1.9.2.7-2 to 1.9.2.7-3b, I had a trouble with SSH access - it is not working now.
In log I have messages like this:
Jan 16 21:06:53 dropbear[103]: Child connection from 192.168.1.65:4741
Jan 16 21:06:58 dropbear[103]: password auth succeeded for 'pluto'
Jan 16 21:06:58 dropbear[103]: exit after auth (pluto): bad buf_getbyte
How can I make SSH work?
Use another ssh client software, there seems to be a bug in the dropbear.