search for: fe61

...ablish a bridge. when I restart the network service, I get the bridge : 1.1 create network bridge [root@localhost ~]# ifconfig br0 Link encap:Ethernet HWaddr C2:CD:89:61:2C:F0 inet addr:192.168.1.189 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::c0cd:89ff:fe61:2cf0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:1080 (1.0 KiB) eth...

...ablish a bridge. when I restart the network service, I get the bridge : 1.1 create network bridge [root@localhost ~]# ifconfig br0 Link encap:Ethernet HWaddr C2:CD:89:61:2C:F0 inet addr:192.168.1.189 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::c0cd:89ff:fe61:2cf0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:1080 (1.0 KiB) eth...

...ED=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_ROUTER=no STP=off The output of ip a for these interfaces is as such: 5: eno1.11 at eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br11 state UP link/ether c0:3f:d5:61:c8:ec brd ff:ff:ff:ff:ff:ff inet6 fe80::c23f:d5ff:fe61:c8ec/64 scope link valid_lft forever preferred_lft forever 6: br11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP link/ether c0:3f:d5:61:c8:ec brd ff:ff:ff:ff:ff:ff inet6 fe80::c23f:d5ff:fe61:c8ec/64 scope link valid_lft forever preferred_lft forev...

...:00:1c.4:pcie04: Card present on Slot(0-1) Jun 6 07:40:50 gway02 kernel: e1000e 0000:02:00.0: eth0: Timesync Tx Control register not set as expected Jun 6 07:40:50 gway02 kernel: e1000e 0000:02:00.0: PCI INT A disabled Jun 6 07:40:51 gway02 ntpd[1238]: Deleting interface #67 eth0, fe80::225:90ff:fe61:74c0#123, interface stats: received=0, sent=0, dropped=0, active_time=229449 secs Jun 6 07:40:51 gway02 ntpd[1238]: Deleting interface #57 eth0, 216.185.64.54#123, interface stats: received=1122, sent=1122, dropped=0, active_time=229449 secs Jun 6 07:40:51 gway02 ntpd[1238]: 24.72.103.44 interfac...

...asiest time to reproduce this is during an initial VM disk format. This is a log from a test VM that was launched, and then partitioned and formatted with LVM / XFS: [2018-04-03 02:05:00.838440] W [MSGID: 109048] [dht-common.c:9732:dht_rmdir_cached_lookup_cbk] 0-ovirt-350-zone1-dht: /489c6fb7-fe61-4407-8160-35c0aac40c85/images/_remove_me_9a0660e1-bd86-47ea-8e09-865c14f11f26/e2645bd1-a7f3-4cbd-9036-3d3cbc7204cd.meta found on cached subvol ovirt-350-zone1-replicate-5 [2018-04-03 02:07:57.967489] I [MSGID: 109070] [dht-common.c:2796:dht_lookup_linkfile_cbk] 0-ovirt-350-zone1-dht: Lookup of /...

...this is during an initial VM disk format. This is a log from a > test VM that was launched, and then partitioned and formatted with LVM / > XFS: > > [2018-04-03 02:05:00.838440] W [MSGID: 109048] > [dht-common.c:9732:dht_rmdir_cached_lookup_cbk] 0-ovirt-350-zone1-dht: > /489c6fb7-fe61-4407-8160-35c0aac40c85/images/_remove_ > me_9a0660e1-bd86-47ea-8e09-865c14f11f26/e2645bd1-a7f3-4cbd-9036-3d3cbc7204cd.meta > found on cached subvol ovirt-350-zone1-replicate-5 > [2018-04-03 02:07:57.967489] I [MSGID: 109070] > [dht-common.c:2796:dht_lookup_linkfile_cbk] 0-ovirt-350-zone...

...  TX packets:204370 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 txqueuelen:1000           RX bytes:12723915 (12.1 MiB)  TX bytes:162430818 (154.9 MiB)           Memory:97a80000-97b00000 tap12.0   Link encap:Ethernet  HWaddr d6:fe:ff:61:dd:ce           inet6 addr: fe80::d4fe:ffff:fe61:ddce/64 Scope:Link           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1           RX packets:38 errors:0 dropped:0 overruns:0 frame:0           TX packets:9156 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 txqueuelen:500           RX bytes:3592 (3.5 KiB)  TX bytes:1003894 (...

I''m very new to shorewall. My setup is IP Gateway (CentOS 4 + Shorewall) with 3 NIC cards. Shorewall works great on the firewall machine. Bind also works (local net machines get IPs fine). Under firestarter, all works great. With shorewall, the loc machines can not route past the firewall. They can connect to the firewall, but not past it. Exactly what information should I post to get

Ian, Do you've a reproducer for this bug? If not a specific one, a general outline of what operations where done on the file will help. regards, Raghavendra On Mon, Mar 26, 2018 at 12:55 PM, Raghavendra Gowdappa <rgowdapp at redhat.com> wrote: > > > On Mon, Mar 26, 2018 at 12:40 PM, Krutika Dhananjay <kdhananj at redhat.com> > wrote: > >> The gfid mismatch

On Mon, Mar 26, 2018 at 12:40 PM, Krutika Dhananjay <kdhananj at redhat.com> wrote: > The gfid mismatch here is between the shard and its "link-to" file, the > creation of which happens at a layer below that of shard translator on the > stack. > > Adding DHT devs to take a look. > Thanks Krutika. I assume shard doesn't do any dentry operations like rename,

...> 161: v14 at if162: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc > noqueue state UP group default qlen 1000 > link/ether 7a:bf:29:61:5b:14 brd ff:ff:ff:ff:ff:ff link-netnsid 0 > inet 192.168.14.10/24 brd 192.168.14.255 scope global v14 > inet6 fe80::78bf:29ff:fe61:5b14/64 scope link > > ----------- > Checking file: /etc/hosts Fix the hosts file > > 127.0.0.1 localhost 827be14a-ffda-60f5-f7f9-b260c6cab739 > ::1 localhost ip6-localhost ip6-loopback > ff02::1 ip6-allnodes > ff02::2 ip6-allrouters > > 192.168.14.10 s...

...lt;BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc > > noqueue state UP group default qlen 1000 > > link/ether 7a:bf:29:61:5b:14 brd ff:ff:ff:ff:ff:ff > link-netnsid 0 > > inet 192.168.14.10/24 brd 192.168.14.255 scope global v14 > > inet6 fe80::78bf:29ff:fe61:5b14/64 scope link > > > > ----------- > > Checking file: /etc/hosts > > Fix the hosts file > > > > > 127.0.0.1 localhost 827be14a-ffda-60f5-f7f9-b260c6cab739 > > ::1 localhost ip6-localhost ip6-loopback > > ff02::1 ip6-allnodes >...

Hi, We have some issue with the reverse DNS in Samba AD. We're running Bind9_DLZ on Ubuntu 18.04. The DHCP server(Ubuntu 16.04) is different to the AD server and not in the same AD domain. The DHCP scope points to the Samba AD server as the DNS server When a machine with DHCP assigned address tries to update the DNS record, it is able to update the forward zone but not the reverse zone. The

...lt;BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc > > noqueue state UP group default qlen 1000 > > link/ether 7a:bf:29:61:5b:14 brd ff:ff:ff:ff:ff:ff > link-netnsid 0 > > inet 192.168.14.10/24 brd 192.168.14.255 scope global v14 > > inet6 fe80::78bf:29ff:fe61:5b14/64 scope link > > > > ----------- > > Checking file: /etc/hosts > > Fix the hosts file > > > > > 127.0.0.1 localhost 827be14a-ffda-60f5-f7f9-b260c6cab739 > > ::1 localhost ip6-localhost ip6-loopback > > ff02::1 ip6-allnodes >...