Displaying 5 results from an estimated 5 matches for "f680".
Did you mean:
680
2016 Mar 12
2
The sad state of samba 4 adaption for home/small business routers.
...depend on samba misconfigurations,
> GPLv3 should guarentee that you can replace the Samba
> on *any* device. That's the whole point of GPLv3 - no
> DRM.
Yes, I know, but it's very difficult with a telco provided router
sourced by a chinese manufacturer. In this case it is a zte f680
supplied by jazztel (now orange) in Spain to ftth customers.
In fact it's not samba that's locked but the whole router (i.e. it has a
restricted shell, but thanks to samba I could access a full shell).
>
> If you find a Samba device using any Samba 3.2 or
> newer that doesn'...
2016 Mar 12
4
The sad state of samba 4 adaption for home/small business routers.
El 12/03/16 a les 12:37, Rowland penny ha escrit:
> Well yes, but these are usually a mass market product and will no doubt,
> in the fullness of time, get to use a version of Samba 4 seeing as how
> 3.6 has been EOL since March 2015.
You'd be surprised to see what old shi^H^H^H "carefully crafted with
backported fixes packages" router vendors put in their products.
In a
2016 Mar 12
0
The sad state of samba 4 adaption for home/small business routers.
On Sat, Mar 12, 2016 at 06:07:25PM +0100, Luca Olivetti wrote:
> Unfortunately it seems it is using a really old version of samba
>
> $ telnet x.x.x.x
> Trying x.x.x.x...
> Connected to x.x.x.x.
> Escape character is '^]'.
> F680
> Login: root
> Password:
>
> BusyBox v1.01 (2015.04.27-11:59+0000) Built-in shell (ash)
> Enter 'help' for a list of built-in commands.
>
> / # uname -a
> /bin/sh: uname: not found
> / # /mnt/usb1_1_1/busybox uname -a
> Linux F680 3.4.69 #366 SMP Mon Apr 27...
2011 Jul 09
10
Starting basic HVM -- where am I going wrong?
.../local/domain/5/device/console/0.
[2011-07-09 05:54:48 1161] DEBUG (DevController:97) DevController: writing {''domain'': ''basic'', ''frontend'': ''/local/domain/5/device/console/0'', ''uuid'': ''23d5f34c-e6ac-f680-c0b4-8a1a88e08933'', ''frontend-id'': ''5'', ''state'': ''1'', ''location'': ''3'', ''online'': ''1'', ''protocol'': ''vt100''} to...
2018 Dec 20
5
Samba AD DC replication error - 2, 'WERR_BADFILE'
Hello everyone,
I have setup two Samba AD DC's with BIND9_DLZ dns backend.
faiserver.example.corp is one of them hosting all FSMO Roles.
location-000001.example.corp is the second one.
Both are in different subnets but can reach each other.
Unfortunately replication only works from faiserver.example.corp ->
location-000001.example.corp.
In the other direction location-000001.example.corp