similar to: Kickstart IPv6 Gateway

On Thursday 21 of April 2016 9:08:09 AM Gordon Messmer wrote: > On 04/21/2016 03:11 AM, Marcin Trendota wrote: > > But from host in another location (connected through VPN): > What host serves the VPN? If it's another host, how is that host > connected to the router? If it's "chamber," what type of VPN is it? It's OpenVPN on chamber. I've just noticed

On Thursday 21 of April 2016 2:37:49 PM Gordon Messmer wrote: > On 04/21/2016 01:33 PM, Marcin Trendota wrote: > > It's OpenVPN on chamber. > What port is it using? I don't see the standard port listed in your > firewalld rules in either zone. 1194/udp. I added service openvpn and port 1194/udp (just to be sure) to both zones - no change. [root at chamber openvpn]#

I'm looking for some information regarding the interaction of KVM, VLANs, firewalld, and the kernel's forwarding configuration. I would appreciate input especially from anyone already running a similar configuration in production. In short, I'm trying to figure out if a current configuration is inadvertently opening up traffic across network segments. On earlier versions of CentOS

On 28 January 2017 at 13:44, Mike McCarthy, W1NR <sysop at w1nr.net> wrote: > firewalld isn't the only thing that will prevent services from accessing > the internet. I found that I needed to do a relabel before postfix could > access DNS and I have seen other issues as well. Have you tried > disabling the firewall to see if you can get connections to work? Then > try to

Hello everybody. Recently i moved external interface to zone "external" on my home server/router. And something strange is hapening. From my router (chamber, CentOS7) everything is fine: [root at chamber ~]# firewall-cmd --list-all home (default, active) interfaces: enp3s0 tun0 virbr0 sources: services: dhcp dhcpv6-client dns http https imaps ipp-client mdns nfs samba

Hi, I'm running CentOS 7 on all my servers, in three different contexts : 1. simple local server 2. public facing server 3. router/gateway/firewall I'm currently in the process of moving my KISS-style network-scripts-style configurations to something more orthodox based on NetworkManager. Scenarios (1) and (2) caused no problems, but (3) is giving me some headache. Let me

On 08/23/2018 04:10 PM, TE Dukes wrote: > Here's the link: > https://paste.fedoraproject.org/paste/MMNEJmqIrEzK-A4N3MR0ZA ip route show: default via 192.168.1.1 dev eno1 proto static metric 101 192.168.1.0/24 dev enp1s0 proto kernel scope link src 192.168.1.111 metric 100 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.110 metric 101 You have two physical devices using

I have brand new PC with this components: CPU Intel? Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1) When I restart the machine sometimes enp1s0 is missing. It is not

Hello all I have weird problem i can't understand and don't know where to look. [root at chamber ~]# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host

This is my system info: Debian Release: 10.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.60-1-pve (SMP w/16 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh

Dne 17.9.2019 v 15:25 Mauricio Tavares napsal(a): > On Tue, Sep 17, 2019 at 9:11 AM Miroslav Geisselreiter <mg at intar.cz> wrote: >> Dne 17.9.2019 v 14:02 Mauricio Tavares napsal(a): >>> On Tue, Sep 17, 2019 at 7:06 AM Miroslav Geisselreiter <mg at intar.cz> wrote: >>>> I have brand new PC with this components: >>>> CPU Intel? Pentium G5400,

Dne 17.9.2019 v 14:02 Mauricio Tavares napsal(a): > On Tue, Sep 17, 2019 at 7:06 AM Miroslav Geisselreiter <mg at intar.cz> wrote: >> I have brand new PC with this components: >> CPU Intel? Pentium G5400, LGA1151 >> motherboard ASUS PRIME B360M-C >> 16 GB RAM >> HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) >> NIC Intel X550-T1

Hi, Has any one know how to skip ix86 packages from installation in Centos kickstart? Most of our machines have 64bit Intel/AMD CPUs, and it make non-sense to still keep 32bit compatibility. Even worse of i*86 packages is, when upgrade we have to recompile both ix86 version and x86_64 version to get an automatic yum upgrade. I know we could use 'exclude' option to exclude i*86 packages

I have a three tinc server setup, similar to "4.3 How Connections Work" using the configuration mostly likehttp://ostolc.org/site-to-site-vpn-with-tinc.html The clients (Ubuntus, Debians and Windows 10s) can all ping (and SSH) to each other remotely. As far as that is concerned it's working great - thanks so much for some great software. However, on each of the Tinc servers (A and

Hello!  I had working Samba installation on openSUSE Tumbleweed server.  I made my previous OS update a month ago, and everything worked fine after it.  But today I updated the OS again, and smb.service failed to start. Version 4.9.1-git.96.c3bff26bf16SUSE-oS15.5-x86_64 I tried many things: - minimal config - removed Samba package with all the dependencies and installed it again and so

Guus, Thank you for your help (a)>>You said:- First, if you are already using "ip" to assign an address..... Why should I use "ip route" instead of "route add..." Surely both write same to the Routing table? (b) My problem was, that Tinc servers could not ping remote clients, whereas clients could ping successfully across VPNWhen pinging Client to Client

Machine is an internal server with zero need to provide or receive ip addresses using dhcp (all IPs are hard coded). Question: how do I disable dhcpv6-client on this box? [user at boxname user]# firewall-cmd --list-all public (active) target: default icmp-block-inversion: no interfaces: enp2s0 sources: services: cockpit dhcpv6-client http https ssh ports: protocols: masquerade:

Thank you, Parke and Guus. I have now understood and got it working. Because of my beginner belief, I assumed that the tinc vpn end points needed to be on the same network. I have now discovered that the tinc vpn IP end points addresses can be arbitrary, and different! So I have set the end points to be local to the LAN they connect, and added on each tinc server a dev route to ensure

On Tue, 18 Jun 2024 15:25:03 +0200 PaLi via samba <samba at lists.samba.org> wrote: > > on DC - dc31: > ------------- > $ sudo samba-tool testparm > > INFO 2024-06-18 13:09:06,760 pid:31797 /usr/lib/python3/dist- > packages/samba/netcmd/testparm.py #96: Loaded smb config files from > /etc/samba/smb.conf > INFO 2024-06-18 13:09:06,760 pid:31797

Now with firewalld, opening up ports is now 'better' done by opening services. So what do I need, for starters it seems: dns, dhcp, dhcpv6, samba, kerberos Here is the list of services: RH-Satellite-6 amanda-client bacula bacula-client dhcp dhcpv6 dhcpv6-client dns ftp high-availability http https imaps ipp ipp-client ipsec kerberos kpasswd ldap ldaps libvirt libvirt-tls mdns mountd