Networking :: Trying To Figure Out The Base (network Service)?
Jun 11, 2011
I have been suffering a connection problem with one of my VPSs recently and I really just can not seem to figure out what is causing the issue. First of all the issue only appears to hit my home computer/network and not other people, it might sound like a routing issue but it doesn't appear to be so. When I am hit by connection issues, I can resolve the issue by logging into Dom-0 (all other VPSs are also available) and consoling the offending VPS before running "service network restart". I personally can not think of anything that would require the network service being restarted and only hit myself (and only at home on top of that).
The VPS itself is dedicated to running minecraft server and is using CentOS, when it occurs I can not SSH the server either, all other ports and methods are disabled by firewall (iptables appears to have no effect in regards to this issue either). Fundamentally I am just thinking if anybody could think of any reason the VPS would only refuse connection to myself that restarting the network service would fix. A few other notes, the physical Server is hosted within a Datacenter, running 24/7 with a static IP. No other VPSs hosted on the machine have any such issues, the machine appears running normally via console and has no visible errors or logs that I know of reporting any issues that could be causing this.
I have recently installed CentOS onto an old machine to get it up and running as a basic web/mail server. Originally the Network Interface worked ok, however I have been editing /etc/sysconfig/network-scripts/ifcfg-eth0 to try and set the IP address to be static.Now when I run the 'service network restart' command it won't bring the eth0 interface up and comes up with the following errors;
ifcfg-eth0 Line 3 DEVICE: command not found missing config file ifcfg-ifcfg-eth0
It doesn't seem to like any of the command words, even though most of these were in the original file that worked and the ones I added to do static I have commented out.
If I restart the network service, not all interfaces come back up. Is this expected behaviour or does something need a kick?
Code: [root@@aspire3500 ~]$ service network restart Shutting down interface eth0: [ OK ] Shutting down interface wlan0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] [root@@aspire3500 ~]$
But, when I restart the network service this IPv6 address is gone. How could I make it as a permanent IPv6 address( that should be edited or deleted when I want but not when I only restart the network)to my interface?
The system will also crash when booting if it is not plugged in. However, this behaviour is not consistent. The crash is not really a crash so much as a complete system freeze, where not even the numlock light on the keyboard will turn on or off. I have to do a hard reset to get it going again.The last entry before the reboot in /var/log/messeges just shows eth0 link going down.
i want to run a stable service for downloading file in fedora 14 in a network with 800 users. i want to whole of users can connect to server and download my files.
I have recently installed Centos 5.4 on a server with 3 network cards. I am trying to enable IP forwarding which has been successful by executing the following command:
echo 1 > /proc/sys/net/ipv4/ip_forward
I tried to make this permanent by adding net.ipv4.conf.default.forwarding=1 to the /etc/sysctl.conf file.
When I restart the network service I get the following code...
I used to have my print server with cups in openSUSE 11.1 and it used to work perfect. I was able to print from both linux machines and windows. But since I Installed openSUSE 11.2, I'm only able to print from linux machines. In windows XP I'am able to find the printer and install the drivers, and everything seems to work, but when I send the print command, it creates an error. I have three XP pcs that were running perfectly, and now neither one of them print, so I know is a problem with the server itself. I have all the samba and cups services activated, and the firewall is set correctly, but can't figure out why it is working with linux machines and not with windows.
I have done a base install with CD#1 and can boot to a prompt and login with root. I cannot use the network. There is no system-config-network program for me to run. There is also no network-manager in chkconfig --list. There is a network item in chkconfig --list and I have turned it on and rebooted to no effect. Googling for base install has found me virtually no information to go on.
I know you've probably seen this type of request numerous times, but I just can't get it right.Objective: to get to grips with Linux network routers.Problem: Cannot ping across the router.On the router itself, I can ping to clients on ether side.Server: Ubuntu 10.10NIC1: connects to home broadband router. Static IP address. Eth1 has no problem pinging outside world.NIC2: Static IP address. This NIC is configured for DHCP server and will have a home machine or two connected to it assigned IP addresses from the DHCP server.Set ip forwarding from 0 to 1
/etc/sysctl.conf net.ipv4.ip_forward=1 Static assignment of IP addresses to the 2 NIC's of router.
I just want to know one thing. I had stop the network service in ubuntu, still i can able to ping google.com.what u think might be things to consider. these are the outputs see.
setting up a wireless network, so bear with me. I just bought a Cisco wireless router and the little USB plug ins (which if I may say, are overly expensive). I can not figure out how to install the router. It is a Linksys E1000 Wireless N Router. I tried to load the software via wine. No luck doing that. I also checked out on Linksys's website and they don't give any info on linux or Ubuntu. Does someone out there know something? Or should I just take this one back and purchase something else
I have a router that is 1000 Base T and two computers each with ethernet cards that support 1000 Base T. All are equipped with Cat 5e cable. Before I had a router that only went up to 100 Base T and I would setup one box with linux running proftpd. On the other box,I would use win xp pro and use firefox to ftp into the other box and download a file. Download speeds went up to 11.2 MB/sec. Now when I switched routers, I expected something like 120 MB/sec but I'm only getting 5.3 MB/sec. What do I need to change?
I've attempted to find the .inf for this card's driver, but to no avail. My plan was to use ndiswrapper to install the driver, but without the .inf I'm at a brick wall!
I use red hat linux. When I start up network service. I get below error in eth2 root@vls etc]# service network restart Shutting down interface eth2: [OK] Shutting down loopback interface: [OK] Bringing up loopback interface: [OK] Bringing up interface eth2: RTNETLINK answers: File exists Error adding address 10.1.1.82 for eth2. [OK]
I paste the ifcfg-eth2 in here [root@vls network-scripts]# cat ifcfg-eth2 # Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) DEVICE=eth2 BOOTPROTO=none BROADCAST=10.1.255.255 HWADDR=00:80:82:8F:B4:A2 IPADDR=10.1.1.82 NETMASK=255.255.0.0 NETWORK=10.1.0.0 ONBOOT=yes GATEWAY=10.1.1.249 TYPE=Ethernet USERCTL=yes IPV6INIT=no PEERDNS=yes So, what is the problem of error adding address?
i just finished installing CentOS 5 in my laptop. While I was trying to configure my Wireless network to connect internet, I found a guide in CentOS site which recommended to start "NetworkManger" service so as to setup wireless network. I followed and it Worked great.
But i would like to understand the difference between "Network" service and "NetworkManager" service. I had initially thought restarting "Network" service would help. explaining the basic difference between these 2 services.
I'd like to create a couple of upstart scripts for some network service daemons (eg. usenet downloading service, torrent service, media management services, etc).Basically they should start after the network service is started and the system is running (runlevel 2?) but I'm just wondering if anybody has an example script or more specific start/stop conditions that I can use.
I am unable start network service on my centos box. /etc/init.d/network start device eth0 does not seem to be present, delaying initialization lspci | grep Ethernet
Doesn't show any results. It seems os doesn't identify my NIC. I am using compaq presario model pc
I've 7 PC's on my network. I've to setup an internal mail service, to send mails inside the network. I've installed Fedora 12 on one machine and the rest run's on Windows XP. What all packages do I need? How can I configure it?
I have a problem with my Fedora system. Whilst I was messing around with my graphics drivers I managed to totally screw up the system, now my desktop won't start, leaving me with just the command prompt. In order to fix it I will need to get my wireless adapter connected to my home network, this is proving tricky. I understand that NetworkManager is responsible for bringing up the network but unfortunately without starting GNOME I don't have the settings available to me (through the nm-cli) or a way to configure it.
Is there a way to bring up whatever service holds the network settings without GNOME? In the meantime I am looking into alternative ways of configuring NM, perhaps through the DBUS interface? Even so, I suspect that I will still need a settings ervice at the end of it..
Updating my install of OpenSUSE from 11.0 to 11.3 and notice that the Nagios network monitor can no longer probe servers with self signed certs.It appears to be any monitor that used openssl 1.0.0 has an issue. If I install the openssl 0.9.8 libraries and use old plugins linked against it, they work fine.
When I ran updates and installed 9.10, this message appeared, "Network service discovery disabled. Your current network has a .local domain, which is not recommended and incompatible with the Avahi network service discovery. The service has been disabled." The computer will not respond to anything, completely frozen--I am not able to open any programs and the CPU itself seems to be running loudly.
