search for: fe9e

On Sun, 4 Aug 2019, John Pierce wrote: > your DNS settings are in /etc/resolv.conf, just like every other unix > system since forever. Much to my surprise, I found this: # Generated by NetworkManager search midcoip.net nameserver 192.168.0.1 nameserver 2001:48f8:3004:2ce:5a19:f8ff:fe9e:a4bc I doubt it's the source of my problems, but the second line looks like something midco did to me somehow. I have noticed a midco search when I wasn't expecting one. My problems predate midco. -- Michael hennebry at web.cs.ndsu.NoDak.edu "Sorry but your password must contain a...

...er(mrm): Indexed 1 messages in INBOXNov ?1 13:25:19 thebighonker exim[6519]: H=(ylmf-pc) [69.64.78.83]:57747 I=[192.147.25.65]:25 rejected EHLO or HELO ylmf-pc: CHECK_HELO: ylmf-pcNov ?1 13:25:27 thebighonker dovecot: imap-login: Login: user=<ler>, method=PLAIN, rip=2001:470:1f0f:3ad:223:7dff:fe9e:6e8a, lip=2001:470:1f0f:3ad:223:7dff:fe9e:6e8a, mpid=6583, TLS, session=<mEXVckFAIEcgAQRwHw8DrQIjff/+nm6K>Nov ?1 13:25:27 thebighonker dovecot: imap(ler): Debug: Loading modules from directory: /usr/local/lib/dovecotNov ?1 13:25:27 thebighonker dovecot: imap(ler): Debug: Module loaded: /usr/l...

On Mon, Dec 02, 2019 at 06:51:44PM -0600, Michael Hennebry wrote: > I've chacked on that. > I've made what seemed like promissing changes to > /etc/sysconfig/network-scripts/ifup-post and > /etc/sysconfig/network-scripts/network-functions . > No go. > I still get the search line in resolv.conf . > I've tried putting in search google.com , > but on reboot, it

...ome other internet connectivity) you should have an ifcfg- file for the interface. Look at the output of 'ip link' to see all the interfaces you have configured. > Currently I have > # Generated by NetworkManager > # search midcoip.net > nameserver 2001:48f8:3004:2ce:5a19:f8ff:fe9e:a4bc > nameserver 192.168.0.1 > > My understanding is that the network manager > generates resolv.conf and DHCP edits it. > Does the network manager include nameservers? > Would putting PEERDNS=no in a ifcfg-eth0 file > result in an empty resolv.conf ? > I realize I could j...

doveadm -D -vvvvvv index \#ARCHIVE/\* garners the below for ALL mailboxes in the namespace: doveadm(ler): Error: Mailbox #ARCHIVE/2013/04/clamav-rules: Status lookup failed: Internal error occurred. Refer to server log for more information. [2016-11-01 13:25:21] doveadm(ler): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable doveadm(ler): Error: Mailbox

...ns8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen > 1000 > link/ether 52:54:00:9e:23:26 brd ff:ff:ff:ff:ff:ff > inet 192.168.33.250/25 brd 192.168.33.255 scope global ens8 > valid_lft forever preferred_lft forever > inet6 fe80::5054:ff:fe9e:2326/64 scope link > valid_lft forever preferred_lft forever > > _______________________________________________ > libvirt-users mailing list > libvirt-users@redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users Update: I have captured packets on virbr0 using tcpdu...

On Sun, 4 Aug 2019, Michael Hennebry wrote: > I'm finding elinks hard to navigate, > but at least it's not slowing stuff to a crawl either. Might have written too soon. elinks is starting to slow down, e.g. down arrow sometimes takes a full minute to respond. -- Michael hennebry at web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a

...rote: > > > your DNS settings are in /etc/resolv.conf, just like every other unix > > system since forever. > > Much to my surprise, I found this: > # Generated by NetworkManager > search midcoip.net > nameserver 192.168.0.1 > nameserver 2001:48f8:3004:2ce:5a19:f8ff:fe9e:a4bc > > I doubt it's the source of my problems, > but the second line looks like something midco did to me somehow. > I have noticed a midco search when I wasn't expecting one. > My problems predate midco. > > -- > Michael hennebry at web.cs.ndsu.NoDak.edu > &q...

...; Address: 9.9.9.9#53 > > Non-authoritative answer: > Name: google.com > Address: 172.217.5.238 Here is the current resolv.conf: > # Generated by NetworkManager > # search midcoip.net > nameserver 9.9.9.9 > nameserver 192.168.0.1 > nameserver 2001:48f8:3004:2ce:5a19:f8ff:fe9e:a4bc When I point elinks at 192.168.0.1 I get http://192.168.0.1/login.php above a big blank window. -- Michael hennebry at web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin."...

...om hijacking searches. Keeping midco's DHCP from adding a search line to resolv.conf seems to be the key. I'll hard-code DNS servers if I have to, but that is not the point of this. Currently I have # Generated by NetworkManager # search midcoip.net nameserver 2001:48f8:3004:2ce:5a19:f8ff:fe9e:a4bc nameserver 192.168.0.1 My understanding is that the network manager generates resolv.conf and DHCP edits it. Does the network manager include nameservers? Would putting PEERDNS=no in a ifcfg-eth0 file result in an empty resolv.conf ? I realize I could just try it and see, but I do not know ho...

...gt; mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 00:23:7d:4d:98:89 brd ff:ff:ff:ff:ff:ff [root at localhost ~]# >> Currently I have >> # Generated by NetworkManager >> # search midcoip.net >> nameserver 2001:48f8:3004:2ce:5a19:f8ff:fe9e:a4bc >> nameserver 192.168.0.1 > Since there's no ifcfg file, I suspect you're using NetworkManager to > manage your network. ... I'm using the default I got when I installed centos 7. Was not aware of any alternatives. > ... Run 'nmcli con' to get a list of y...

18. Juli 2017 16:45, "Michal Privoznik" <mprivozn@redhat.com> schrieb: > On 07/18/2017 04:31 PM, c.monty@web.de wrote: > >> Hello! >> >> I have upgraded all libvirt packages to version 3.5.0-655.1 and restarted host. > > That wasn't necessary. It's not Windows ;-) > >> This is the current default network config: >> ld4004:~

...ULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen >> 1000 >> link/ether 52:54:00:9e:23:26 brd ff:ff:ff:ff:ff:ff >> inet 192.168.33.250/25 brd 192.168.33.255 scope global ens8 >> valid_lft forever preferred_lft forever >> inet6 fe80::5054:ff:fe9e:2326/64 scope link >> valid_lft forever preferred_lft forever >> >> _______________________________________________ >> libvirt-users mailing list >> libvirt-users@redhat.com >> https://www.redhat.com/mailman/listinfo/libvirt-users > > Update: > I have...

...) > > > > ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc > fq_codel state UP group default qlen 1000 > > link/ether 86:ba:b4:9e:2b:5c brd ff:ff:ff:ff:ff:ff > > inet 10.0.0.3/24 brd 10.0.0.255 scope global ens18 > > inet6 fe80::84ba:b4ff:fe9e:2b5c/64 scope link > > > > So if you check the output of hostname -s an hostname -i ( > and -f for the full name. ) > > You should see the correct hostname and ip > > If not then that needs correcting first in /etc/hosts > > > > > > The default smb.co...

Hello, I''ve checked out my rails tree from svn into the location I intend to run in production mode. However, I am unclear on what exactly needs to change for it to work in production mode. Yes I have: "bin-environment" => ("RAILS_ENV" => "production") When I switch to the externally routed IP address instead of 0.0.0.0:3000 and try running: %

...route. ( route -n |grep default ) > > ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 > link/ether 86:ba:b4:9e:2b:5c brd ff:ff:ff:ff:ff:ff > inet 10.0.0.3/24 brd 10.0.0.255 scope global ens18 > inet6 fe80::84ba:b4ff:fe9e:2b5c/64 scope link > > So if you check the output of hostname -s an hostname -i ( and -f for the full name. ) > You should see the correct hostname and ip > If not then that needs correcting first in /etc/hosts > > > The default smb.conf is based on a stand alone server and i...

...t;>> ens18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc >> fq_codel state UP group default qlen 1000 >>> link/ether 86:ba:b4:9e:2b:5c brd ff:ff:ff:ff:ff:ff >>> inet 10.0.0.3/24 brd 10.0.0.255 scope global ens18 >>> inet6 fe80::84ba:b4ff:fe9e:2b5c/64 scope link >>> >>> So if you check the output of hostname -s an hostname -i ( >> and -f for the full name. ) >>> You should see the correct hostname and ip >>> If not then that needs correcting first in /etc/hosts >>> >>> >&g...

Hi, Louis, Rowland, thanks for you answer. @Louis All packages were installed. I change my config file following your advices, the problem is still here. I already followed guides from thctlo's github. @Rowland Yes, my dns domain was different, but answered also to test.lan. It's now set to 'kdc=dc.foo.lab' I have my user vincent with uidNumber 10010 and gidNumber 13010