search for: inet4

...5. If you are using network-manager, what does nmtui or the graphical > tool say the gateway or default route is? Here is answers to your list. I have anonymized the some of the data: 1) Static ip configuration 2) This should be NetworkManager. nmcli output: eno1: connected to eno1 inet4 1.1.1.234/29 route4 1.1.1.232/29 route4 0.0.0.0/0 eno2: connected to eno2 inet4 192.168.0.5/24 route4 192.168.0.0/24 [root at server ~]# nmcli d show | grep IP4.GATEWA IP4.GATEWAY: 1.1.1.1.233 3) TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none D...

...tui or the graphical >> tool say the gateway or default route is? > > Here is answers to your list. I have anonymized the some of the data: > > 1) Static ip configuration > > 2) This should be NetworkManager. > nmcli output: > > eno1: connected to eno1 > inet4 1.1.1.234/29 > route4 1.1.1.232/29 > route4 0.0.0.0/0 > > eno2: connected to eno2 > inet4 192.168.0.5/24 > route4 192.168.0.0/24 > > [root at server ~]# nmcli d show | grep IP4.GATEWA > IP4.GATEWAY: 1.1.1.1.233 > > 3) > TYPE=Et...

...39;'m using vpnc to connect to a vpn. The VPN-GW wants me to use him as a default route. So I used source-routing to differ between my physical ethernet and the tunnel: ip rule add from w.x.y.z table 20 ip route add default via tun0 table 20 Everything works fine, as I have a client to set my inet4-srcaddress. My question is: Is there a way, to tell linux which is my default sourceaddress? Greets, Sebastian

Hi, Tonight I upgraded two CentOS 8 boxes to CentOS 8.1 (1911). Then after a reboot of the first server the network was unavailable. In IPMI console everything except the network was looking good. Network was unreachable. No errors in NetworkManager. I also restarted NetworkManager, but it did not help. Then I discovered that the default gateway suddenly was missing. Then I rebooted the

...; enabled; vendor preset: enabled) Active: active (running) since Thu 2017-02-16 08:19:34 UTC; 2h 19min ago * more stuff * nmcli eth0: connected to Wired connection 1 "Red Hat Virtio network device" ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500 ip4 default, ip6 default inet4 178.79.185.217/24 route4 178.79.187.246/32 inet6 2a01:7e00::825f:e564:ad53:72fc/64 inet6 fe80::a8ad:d312:4ef4:7272/64 route6 2a01:7e00::/64 * more stuff for other interfaces * -=- The output of sysctl -a | grep net.ipv6 : https://librelamp.com/sysctl.txt It looks from that like it should...

...n ago >> >> * more stuff * >> >> nmcli >> eth0: connected to Wired connection 1 >> "Red Hat Virtio network device" >> ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500 >> ip4 default, ip6 default >> inet4 178.79.185.217/24 >> route4 178.79.187.246/32 >> inet6 2a01:7e00::825f:e564:ad53:72fc/64 >> inet6 fe80::a8ad:d312:4ef4:7272/64 >> route6 2a01:7e00::/64 >> >> * more stuff for other interfaces * >> >> -=- >> >&g...

Hi, We just released Opus 1.1.4, which fixes a single bug. A specially-crafted Opus packet could cause an integer wrap-around in the SILK LSF stabilization code. This would cause an out-of-bounds read 256 bytes before a constant table. In most circumstances, the consequences are harmless and the result is simply noise in the audio. This was reported as CVE-2017-0381 [1]. Contrary to that report,

On 10/15/20 2:02 PM, jeremy ardley wrote: >> how/where do I configure (just) the dovecot smtp-client -> submission_relay_host to only connect IPv4? > > It appears your host has A and AAAA records in your DNS. The clients will try IPV6 first if they see an AAAA record. > > If you don't need IPV6 for your host remove the AAAA record. All connections will then only use

...Thu 2017-02-16 08:19:34 UTC; 2h 19min ago > > * more stuff * > > nmcli > eth0: connected to Wired connection 1 > "Red Hat Virtio network device" > ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500 > ip4 default, ip6 default > inet4 178.79.185.217/24 > route4 178.79.187.246/32 > inet6 2a01:7e00::825f:e564:ad53:72fc/64 > inet6 fe80::a8ad:d312:4ef4:7272/64 > route6 2a01:7e00::/64 > > * more stuff for other interfaces * > > -=- > > The output of > > sysctl -a | g...

...>>>> nmcli >>>> eth0: connected to Wired connection 1 >>>> "Red Hat Virtio network device" >>>> ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500 >>>> ip4 default, ip6 default >>>> inet4 178.79.185.217/24 >>>> route4 178.79.187.246/32 >>>> inet6 2a01:7e00::825f:e564:ad53:72fc/64 >>>> inet6 fe80::a8ad:d312:4ef4:7272/64 >>>> route6 2a01:7e00::/64 >>>> >>>> * more stuff for other in...

...re stuff * >>> >>> nmcli >>> eth0: connected to Wired connection 1 >>> "Red Hat Virtio network device" >>> ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500 >>> ip4 default, ip6 default >>> inet4 178.79.185.217/24 >>> route4 178.79.187.246/32 >>> inet6 2a01:7e00::825f:e564:ad53:72fc/64 >>> inet6 fe80::a8ad:d312:4ef4:7272/64 >>> route6 2a01:7e00::/64 >>> >>> * more stuff for other interfaces * >>>...

...gt;> eth0: connected to Wired connection 1 >>>>>> "Red Hat Virtio network device" >>>>>> ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500 >>>>>> ip4 default, ip6 default >>>>>> inet4 178.79.185.217/24 >>>>>> route4 178.79.187.246/32 >>>>>> inet6 2a01:7e00::825f:e564:ad53:72fc/64 >>>>>> inet6 fe80::a8ad:d312:4ef4:7272/64 >>>>>> route6 2a01:7e00::/64 >>>>>> &g...

...le in the version field of the bug report form). The patch for CVE-2008-1483 applied in this release has a side effect on Solaris (at least Solaris 10, I didn't test on other solaris versions). With this patch, openssh will do X forwarding on a port only if it successfully binded to it on the inet4 and inet6 address (if the latter was available). The problem is that on Solaris 10, even if ipv6 was not enabled at install time, the getaddrinfo will still return the ipv6 address in addition to the ipv4 address. As a result, when try to bind to port A, openssh will try to bind to 127.0.0.1:A an...

...li >>>>> eth0: connected to Wired connection 1 >>>>> "Red Hat Virtio network device" >>>>> ethernet (virtio_net), F2:3C:91:18:8A:7E, hw, mtu 1500 >>>>> ip4 default, ip6 default >>>>> inet4 178.79.185.217/24 >>>>> route4 178.79.187.246/32 >>>>> inet6 2a01:7e00::825f:e564:ad53:72fc/64 >>>>> inet6 fe80::a8ad:d312:4ef4:7272/64 >>>>> route6 2a01:7e00::/64 >>>>> >>>>> *...

On 02/16/2017 02:03 AM, James Hogarth wrote: > On 16 February 2017 at 09:09, Alice Wonder <alice at domblogger.net> wrote: >> On 02/16/2017 12:54 AM, Tony Mountifield wrote: >>> >>> In article <4cbb9dc4-f063-3434-b7a1-d4d0e6581b5e at domblogger.net>, >>> Alice Wonder <alice at domblogger.net> wrote: >>>> >>>>