similar to: Multi-homed faq or docs needed

> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Michael Jones via samba > Verzonden: maandag 18 mei 2020 11:34 > Aan: Rowland penny > CC: sambalist > Onderwerp: Re: [Samba] Best practice multi-homed AD DC > > On Mon, May 18, 2020 at 2:44 AM Rowland penny via samba < > samba at lists.samba.org> wrote: >

OK I have sufficient evidence now that my split route ( multipath routing ) is inducing kernel panic and also frequent connection lost. The split route may not be the culprit but I can safely say that without using the split route, my system is perfectly stable. I have set up the split route according to http://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.rpdb.multiple-links.html I could use

Hello all, I am going through the LARTC howto to understand how the iproute2 works. But some concepts like Policy Routing, RPDB etc are not clear to me. I am pretty new to iproute, beeing using route command for long... From what I understand 1. rules (ip rule) tell how to select packets for routing and route (ip route) tell where to route the selected packets. 2. A collection of rules is

On Sun, May 17, 2020 at 1:43 PM Rowland penny via samba < samba at lists.samba.org> wrote: > On 17/05/2020 19:30, Johannes Engel via samba wrote: > > Dear all, > > > > as I am currently planning a network with Samba AD DC I was wondering if > > you can recommend any best practice for a multi-homed AD DC. > > Best practise is: do not multi-home a DC. >

Can someone refer me to any links which explain how to configure a stand alone linux host (not a router) with 2 ISP links in such a way that the traffic is distributed between the 2 ISPs ? Thank you, _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

I'd suggest looking around the ifcfg-eth* files (somewhere in /etc/sysconfig/network-scripts I think) nad commenting out HWADDR= lines, if that works, then try reversing the HWADDR lines - this will reverse the numbers of the ethernet cards (ie making eth0 eth1 and eth1 eth0) but should result in a stable configuration till next hardware change. And you problem? IMHO, when the system

I have a wireless internet connection.the nat is done by linux machine. eth0----lan eth1---service-provider now the script.. tc qdisc add dev eth0 root handle 1: htb default 12 tc class add dev eth0 parent 1: classid 1:1 htb rate 512kbps ceil 512kbps tc class add dev eth0 parent 1:1 classid 1:10 htb rate 384kbps ceil 512kbps-----Admin-Network tc class add dev eth0 parent 1:1 classid 1:11 htb

Hi, I was wondering if somebody could assist me in the following I have a lan with a mail server, a fixed outside ip address leased line router at 10.1.1.1, and a dynamic outside ip address adsl router at 10.1.1.5 Our linux mail server always used to have the leased line router at 10.1.1.1, but now with our adsl, I''d like traffic to go across 10.1.1.5, I thought it would be straight

On Mon, May 18, 2020 at 2:44 AM Rowland penny via samba < samba at lists.samba.org> wrote: > On 17/05/2020 23:10, Michael Jones wrote: > > Why? > Amongst others, you may get: > > Slow / Failed logins > Replication issues > Group policy access issues > login script issues > > A multi-homed DC (for whatever reason) is a bad idea. > > Rowland > I

Hi, I connected a multi-homed Win95 machine (carrot, see below) to two networks (ankh-net and morpork-net) which a multi-homed Linux machine running Samba 1.9.18p10 (or whatever the latest <2 is) was also connected to (vimes) and wanted to see which of the two interfaces Win95 would pick... --------------------------------- ankh-net 134.225.241.0/24 | |

Most of my experience until recently has been in Asterisk 1.2, and I am just starting to make use of Asterisk 11 for new systems. I have a question about using SIP on a multi-homed machine. I have a customer who wants an Asterisk box with two network interfaces: one on the public Internet (no NAT), and one on a private LAN. The box will not do any IP forwarding between interfaces. They want to

http://bugzilla.netfilter.org/show_bug.cgi?id=616 Summary: Duplicate rules for multi-homed hostnames. IPv4 and IPv6 inconsistent treatment. Product: iptables Version: unspecified Platform: i386 OS/Version: All Status: NEW Severity: minor Priority: P4 Component: iptables

Hi, here I have another newcomer question :-) in the section 9.6.1 of this how too http://tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.qdisc.filters.html we can read commands about filters : ------------------------------------------ # tc filter add dev eth0 protocol ip parent 10: prio 1 u32 match \ ip dport 22 0xffff flowid 10:1 # tc filter add dev eth0 protocol ip parent 10: prio 1 u32 match \

Dear all, as I am currently planning a network with Samba AD DC I was wondering if you can recommend any best practice for a multi-homed AD DC. My current plan is to have one NIC for Samba services and a second one dedicated to management functions (e.g. SSH) on a separate network restricted to admin users. In a testbed scenario I already discovered that once both adapters exist, samba seems to

>From a security standpoint, if the default keytab (/etc/krb5.keytab) contains only ONE principal, does it matter if GSSAPIStrictAcceptorCheck is set to "yes" or "no"? My company uses an internally built OpenSSH package that includes the GSSAPI Key Exchange patch. Because we have 1000s of hosts, we need to use a "standard" sshd_config file that works for the

Hi, not sure if it will work, i''ve 2 leased lines, behind line 1 is a webserver, this server should answer all incomming http requests through leased line 1, the webserver self parses other webserver, this outbound traffic should go over leased line 2. i''ve successfully added fwmark with iproute, but if i set the policy for the webserver to use leased line 2 (for parsing other

Hey all, I'm experiencing a problem with chan_sip on a multi-homed machine. The machine has 1 interface to the rest of the world and 1 interface on a local network. The local network has public IP-addresses, though, and the IP-addresses of both interfaces are reachable from the outside world, but by default, outgoing traffic from that machine to the outside world will have the IP-address of

On 17/05/2020 19:30, Johannes Engel via samba wrote: > Dear all, > > as I am currently planning a network with Samba AD DC I was wondering if > you can recommend any best practice for a multi-homed AD DC. Best practise is: do not multi-home a DC. Rowland

Hi, (I think I posted this a few weeks ago, but I haven't found the solution and had no replies.) I have a multi-homed server, one interface of which is on the same subnet as the majority of clients and the other is on a different one (but still reachable, through a router). When connecting to the server, it seems to be chance which one of these interfaces I get. I believe DNS servers

On 13/05/2020 18:52, David Lomax via samba wrote: > Hi all, > > I have a question about a multi-homed Samba file server and interoperability > with AD. It's a bit complicated, so please bear with me. Your problem is probably because your DC knows your Samba ADS client by its 192.168.42.0/24 Ipaddress. Also, why only use 10G on part of your network, surely the network speed