| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
| |
| |
| | |
Andrew Bartlett
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Went through and checked all string_subs I could to ensure they're being
used correctly.
Jeremy.
|
| | |
| |
| |
| | |
WinXP. This fixes setting security decsriptors from XP Professional.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
code
|
| | |
| |
| |
| |
| | |
this fixes the huge number of struct berval warnings on non-ads
compiles
|
| | |
| |
| |
| | |
server. We were rejecting them, leaving the name unregistered!
|
| | |
| |
| |
| | |
(ie. check for lp_dns_proxy())
|
| | | |
|
| | |
| |
| |
| |
| | |
broadcast addresses. This makes it far more likely that we will try to
talk to an interface that is routable from one of our interfaces.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
bytes which follow the header, not the full packet size.
[Yes, the length field is either 17-bits, or (per the RFCs) it is a
16-bit length field preceeded by an 8-bit flags field of which only
the low-order bit may be used. If that bit is set, then add 65536 to
the 16-bit length field. (In other words, it's a 17-bit unsigned
length field.)
...unless, of course, the transport is native TCP [port 445] in which
case the length field *might* be 24-bits wide.]
Anyway, the change is a very minor one. We were including the four bytes
of the header in the length count and, as a result, sending four bytes of
garbage at the end of the SESSION REQUEST packet.
Small fix in function cli_session_request().
|
| | |
| |
| |
| | |
systems
|
| | |
| |
| |
| |
| | |
to a tdb per-queue for scalability.
Jeremy.
|
| | |
| |
| |
| | |
Jeremy.
|
| | |
| |
| |
| | |
Jeremy.
|
| | |
| |
| |
| | |
str_list_copy(). Perhaps its proto should be fixed.
|
| | |
| |
| |
| | |
Jeremy.
|
| | | |
|
| | |
| |
| |
| | |
these errors happen all the time, so they shouldn't be level 0
|
| | |
| |
| |
| | |
warning
|
| | |
| |
| |
| | |
'valid.dat' warning
|
| | |
| |
| |
| |
| | |
Now let's keep this in sync !
Jeremy.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
to a Samba print server running HEAD in a while. This has been broken
since tridge's changes to make_connection() to not do the chdir()
to the connect_path. Sorry it took me so long to get around to fixing it.
The problem occured with our internal use of make_connection().
jerry
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We now cope wiith multiple WINS groups and multiple failover servers
for release and refresh as well as registration. We also do the regitrations
in the same fashion as W2K does, where we don't try to register the next
IP in the list for a name until the WINS server has acked the previos IP.
This prevents us flooding the WINS server and also seems to make for much
more reliable multi-homed registration.
I also changed the dead WINS server code to mark pairs of IPs dead,
not individual IPs. The idea is that a WINS server might be dead from
the point of view of one of our interfaces, but not another, so we
need to keep talking to it on one while moving onto a failover WINS
server on the other interface. This copes much better with partial
LAN outages and weird routing tables.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
(from jelmer)
Andrew Bartlett
|
| | |
| |
| |
| | |
prs_align() for sec_desc.
|
| | |
| |
| |
| | |
Jeremy.
|
| | |
| |
| |
| | |
kernel.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Jeremy.
|
| | |
| |
| |
| | |
Jeremy.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
accept an extended syntax for 'wins server' like this:
wins server = group1:192.168.2.10 group2:192.168.3.99 group1:192.168.0.1
The tags before the IPs don't mean anything, they are just a way of
grouping IPs together. If you use the old syntax (ie. no ':') then
an implicit group name of '*' is used. In general I'd recommend people
use interface names for the group names, but it doesn't matter much.
When we register in nmbd we try to register all our IPs with each group
of WINS servers. We keep trying until all of them are registered with
every group, falling back to the failover WINS servers for each group
as we go.
When we do a WINS lookup we try each of the WINS servers for each group.
If a WINS server for a group gives a negative answer then we give up
on that group and move to the next group. If it times out then
we move to the next failover wins server in the group.
In either case, if a WINS server doesn't respond then we mark it dead
for 10 minutes, to prevent lengthy waits for dead servers.
|
| | |
| |
| |
| |
| |
| | |
unicast subnet, so remove that parameter. That frees up userdata so I
can start using it to indicate which wins server tag we are
registering (more about wins 'tags' later ...)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
it is *completely* bogus for our client code to be doing wins
registrations. Not only is it slow as hell (think about when a wins
server is down) but how the heck is going to answer the queries that
will later come in for our name? And what happens when libsmbclient
sends registrations and nmbd then gets the WACK response from the wins
server? we end up losing our name!
Name registration is a job for nmbd, not for clients.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
cache the result!)
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
gives us a good grounding to properly support multiple wins servers
for different interfaces (which will be coming soon ...)
- fixed our wins registration failover code to actually do failover!
We were not trying to register with a secondary wins server at all
when the primary was down. We now fallback correctly.
- fixed the multi-homed name registration packets so that they work
even in a non-connected network (ie. when one of our interfaces is not
routable from the wins server. Yes, this really happens in the real
world).
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
