similar to: wicd problem 4: wicd restarts itself when as root user making terminal commands

greetings, following are command line problems as user using virtual terminals. ]$ ifconfig;date eth0 Link encap:Ethernet HWaddr 00:0F:FE:8F:8F:23 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::20f:feff:fe8f:8f23/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1419 errors:0 dropped:0

On 12/03/2014 04:15 PM, zep wrote: > >>> oh. the ARP packet suggests that MAC address is 192.168.1.144 >> that is how i see it. >> > is that 1.144 IP address in use by the machine you ran the lspci > from? somewhere. but i know not where. http://www.whoami.it/home/ shows me to be; adsl-184-41-28-86.mem.bellsouth.net for the hell of it, i pulled and

greetings, during past week or so, i have been having problems with mozilla firefox locking up kde desktop and i have to open a terminal to reboot system. to insure that i get kde back to a desired state, i make backups of ~/.kde path when ever i change any settings of kde. after system reboots and desktop manager is displayed, i <ctrl+alt+f1> to terminal, delete current ~/.kde, then copy

greetings, i find this strange because i see problems when using 'wicd'. 1st problem is that wicd allows network to be connected on reboot, even when network is disconnected at time of reboot. such does not seem to be good because i leave system up 24/7/365 and if there is a mains failure and ups takes system down, system will come back up with network connected, which i prefer not to

On 12/3/2014 3:09 PM, g wrote: > On 12/03/2014 04:15 PM, zep wrote: >> > >>>> >>>oh. the ARP packet suggests that MAC address is 192.168.1.144 >>> >>that is how i see it. >>> >> >> >is that 1.144 IP address in use by the machine you ran the lspci >> >from? > somewhere. but i know not where. > >

Possibly your system was installed or cloned using PartedMagic, and that left an entry in /etc/ethers mapping your default nic to the name 'PartedMagic'? K Kahlil (Kal) Hodgson GPG: C9A02289 Head of Technology (m) +61 (0) 4 2573 0382 DealMax Pty Ltd Suite 1416 401 Docklands Drive Docklands VIC 3008 Australia "All parts should go

Hello I am trying to get wicd to work on Cent 5.5 it installs fine but when i run wicd-curses i get this error wicd-curses File "/usr/share/wicd/curses/wicd-curses.py", line 505 class appGUI(): ^ SyntaxError: invalid syntax my versions of wicd and python-urwid are wicd-1.7.0-3.el5 python-urwid-0.9.8.4-3.el5 Has anyone been able to get wicd working

greetings, system: CentOS = 6.6 - current updates KDE = 4.3.4 Network Manager = 0.8.1 wicd = 1.7.0 (bzr-r552) from what i have read in threads, it appears that 'wicd' is recommended network controller over 'network manager'. because of this, i installed wicd and tried to use. i find this strange because i see problems when using 'wicd'.

greetings, wicd is preventing firefox and yumex to connect to internet. when i first try to connect to a web site with firefox, i get err message; Unable to connect when i click [Try Again], connection is made. all further connection attempts are ok. when i try to run yumex, i get error message; Not connected to a network. Do you want to continue selecting [Yes] continues starting

hi all , i'm now using wicd network manager instead of network-manager and got a strange problem again wicd can managae wireless network connection well now but when i connected to the network my wicd icon still display "not connected" , i googled a lot but nothing helped anybody here using wicd ? i'm now using the lastest stable version 1.5.7 , thx for help -- Keep It Simple

Hello, I am using SLC6 and wicd for wi-fi. Always during system booting wicd asks me to fill superuser password/or ignore (but in this case wi-fi works bad). I am using KDE ... Do you know the way how to remove this message (exactly small special window) from monitor? Thank you. Regards, Dusan

Hello All, I'm trying to figure out why xen-utils-common 3.2 doesn't suport bridging on multiple interfaces. I've been digging around /etc/xen/scripts/network-bridges. And modified it so that during boot, when executed the script writes into /tmp/netbr file, but I commented out code that actually creates bridges. I discovered that this script is called three times during boot, I

I have a server running Centos 5.2 as a Xen host. A problem that's shown up recently is that at boot, the dom0 interface eth0 doesn't come up properly, with the result that the host is only accessible via remote console. If I execute 'service network restart', eth0 comes up normally, with an IP address and the correct routing. Three guests have been created via virt-manager

Hello, A bit of history ================ 1) I''ve got a normal 2.6.20 x64 Fedora 6 Linux server running several things 2) I''ve downloaded and installed the XenSource Administrator Console for Windows 3) I''ve added 2.6.20-1.2962.fc6xen kernel, xen and vnc packages on my Linux server 4) I rebooted the Linux server, and started xend as per user guide Configuration

On Fri, Aug 25, 2017 at 10:06:59PM +0000, James Zuelow via samba wrote: > We have a wireless network that uses 802.1x authentication, in which domain joined computers use their machine credentials to connect. > > > Windows machines do this automatically, and until recently Linux computers could join using wicd, wpa-supplicant, and a simple script that would retrieve the machine

Has anyone ran into this issue before? 2 physical nics: eth0 hooked up to 10.175.8.0/21 eth1 hooked up to 10.150.8.0/24 Ifconfig -a looks like this: [root@mgixen1 ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:19:B9:F2:1B:C3 inet addr:10.175.8.158 Bcast:10.175.15.255 Mask:255.255.248.0 inet6 addr: fe80::219:b9ff:fef2:1bc3/64 Scope:Link UP

Hi all, my dom0 is centos5.2 and domU paravirtualized is centos5.1 I can play sound on dom0 but not in domU (name: gasphar), moreover I use wifi as my inet connection and on installing domU cento5.1, I used virt-manager. I know that libvirtd made virbr0 and when changing to xenbr0, I cannot connect to internet but ssh to dom0 is fine! so how do I enable sound device on domU and changing to

Hello, When I install xen via yum, using virt-manager to build a machine, I was displayed no options for Shared Physical Device. Here is a pic, just for show http://imgur.com/HiPiY Then, I did yum downgrade xen, got no network options at all. Do I need to restart something or run a script? I want to use peth0. packages (CentOS 5.4): gnome-applet-vm 0.1.2-1.el5 kernel-xen 2.6.18-164.15.1.el5

I have nic bonding (mode=802.3ad) setup on 2 servers, both running Centos 5.5 In the "Active Aggregator Info", on one reports 4 ports - which is correct - but the other only reports 3 ports. It's always eth0 that shows a different aggregator ID. Changing the cables around so it hits a different port on the switch makes no difference. The switch is correctly configured for the port

Hello I happen to have two network interfaces on my new, up-to-date, CentOS 6.2, named eth0 and virbr0 (3 of them if I include the lo interface). However the system APIs like getaddrinfo() only return the address for the virbr0 interface (which was created by the CentOS installation), when I would like to have them both. Even if I give the configured eth0 address explicitly to getnameinfo(),