Debian Configuration :: No Internet Connection After Reboot
Feb 20, 2016
I rebooted my vServer (Debian 8) and it doesn't came back up. Well, I used the rescue console on my server and the server seems to be running fine, except the network was broken. So I tried 'ifconfig' but nothing came up. So I tried to enable my interface with 'ifconfig venet0 up', and now it appears in my ifconfig list
Code: Select allroot@i67svof:/var/www# ifconfig
venet0Â Â Link encap:UNSPECÂ HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00Â
     UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
     RX packets:557 errors:0 dropped:0 overruns:0 frame:0
     TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
     collisions:0 txqueuelen:0
     RX bytes:36463 (35.6 KiB) TX bytes:0 (0.0 B)
My HWaddr doesn't look that well :) 'ip addr' prints this result:
Code: Select allroot@i67svof:/var/www# ip addr
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
These are the last lines in /var/log/syslog:
Code: Select allroot@i67svof:/var/www# tail /var/log/syslog
Feb 20 11:34:16 i67svof systemd[1]: Stopping memcached daemon...
Feb 20 11:34:16 i67svof systemd[1]: Stopping Network Name Resolution...
Feb 20 11:34:16 i67svof systemd[1]: Stopping Regular background program processing daemon...
Feb 20 11:34:16 i67svof systemd[1]: Stopping Login Prompts.
[Code] .....
And finally my network config in /etc/network/interfaces
Code: Select all# Auto generated lo interface
auto lo
iface lo inet loopback
# Auto generated venet0 interface
auto venet0
I have been using this fresh Debian 8.2 install for 3 days without any network problems.
What I did this morning :
- Booted in my windows partition and rebooted immediately just to remove the system from the sleep state - Mounted a NTFS hard drive and copied some file to my .wine drive_c
Thats when I noticed that my connection was down.
I verified all the physical layer. My laptop has access to the internet tried to connect on an another router with eht0, changed the wire, nothing worked.
It seems like the interface can't get a dhcp ipv4 address even when I try to force is with dhclient, I get no offer when my laptop works just fine.
- Booted on my windows partition without changing any connection and my internet was working. - Booted back on debian still not working...
1 linksys router: gets the net from PPPOE and give the network DHCP. The router IP is 192.168.1.1. 1 windows laptop that work wireless and wired. 1 debian desktop that work wired and not working wireless. THe problem with the debian desktop is like this: I have a TP-Link TL-WN321G installed and found by lsusb command. I make a wireless connection WPA Personal (just like the router settings) it says i am connected to the wl network but no internet connection. the route command give me this:
[code]....
I tryed with wicd who said that the connection is WEP (and it's not, it is setup to WPA on the router and the network-manager conncetion) and when i try to connect i get bad password. I tryed with network-manager uninstalled and no chance.
I am using Empathy IM client to access to gadu gadu and to message with my friends. The strange thing that is happening is that I keep on being connected and then disconnected and then connected again even if I am continuously connected to my internet connection (no problem when surfing or using skype for example)It also seems to come only from me because when my girlfriend is using the same gadu gadu on her windows laptop simultaneously, she doesn´t get disconnected (whether when she is at home and using the same connection as I am or when she is outside, meaning that it doesn´t seem to come from the whole gadu gadu network)maybe it has something to do with the ports that gadu gadu is using but it is strange that sometimes it is working for a period of time and then not and then again.
I have just installed Debian Squeeze on my spare computer (dual booted with Ubuntu 11.04) and I cannot connect to the internet using Squeeze. Due to my ISP, I have to manually connect this computer and on Ubuntu copying and pasting a text file such as this into the terminal works with no problems.What do I need to do to manually configure my Squeeze internet connection?
I replaced my motherboard and processor but am keeping my old hard drive without reformatting it. Things work well except that I cannot connect to the internet. I am thinking that I just need to reconfigure the connection to see the new network hardware. I tried /etc/init.d/networking restart but that doesn't do anything. What am I missing? By the way it is a wired connection - not wireless.
AMD 64 Upgrade to testing last night killed my internet connection. The lan works, I can ping the dns server from my IP, however no mail, browser possible. Is something in testing broken again?
I'm going to start using Debian as my desktop system rather than Ubuntu since I'm not really liking all the crazy eye candy and just wanted a fast and simple system. My main problem is networking, I guess I'll start off with my system specs and other information for problem solving.
I have a Realtek RTL8111/8168B Ethernet Adapter builtin to my motherboad which I am using, I could only get a basic connection, by basic I mean that it allowed me to connect to my local area network but not the internet. I then modified /etc/NetworkManager/NetworkManager.conf to change to managed=true this allowed me to use the internet, but the problem is, that it is a very unstable connection, the speed is very slow and it drops a lot! I have to carry on running /etc/init.d/network-manager restart twice to get my connection back, which lasts for about a minute.
I have no idea how I managed this, but I am able to connect to the internet but NetworkManager doesn't show any connection. This means that until I kill it, I cannot log in with Pidgin, because it is waiting for a connection.
Do I disable NetworkManager completely or do I try to make it recognize that I am connected to the Internet? If the latter, then how should I go about? (Please let me know which files I need to show you, because I know I've messed around with a couple).
I had some trouble with the netinst CD and I had to install lenny with the 6DVDs instead. My internet connection only works after I edit the interfaces and resolv.conf files manually. So my question is: can I do that from the netinst CD before it actually needs the connection to install everything? (otherwise I'll just need to use the DVDs.
I am *finally* getting around to rebuilding my file-sharing computer. I'll be sharing files with both Linux and Windoze machines. It's a home network, so there's nothing fancy needed. I know I have to tweak my smb.conf file until I'm satisfied with the features and security. I'm using SWAT and I'm starting with a bare-bones conf file. It's not secure but I can see the server and selected files/directories from my other Linux box.
My really dumb question is, do I have to reboot both the server and the client machines every time I change the SAMBA configuration? I thought I just had to stop and restart the SAMBA service in the SWAT software - but then the server disappears from my client. It looks like I need to reboot both machines for the client to see the server.
The situation: The office has a WiFi network on one DSL line, which is used for our VoIP call center, and a wired network for our internal network and the majority of web surfing/traffic . Part of the office must be temperature controlled/monitored - we have a rather nice digital thermometer which is WiFi enabled.I have a Debian Wheezy box with a WiFi card and ethernet connection
What I'm trying to accomplish:Connect wifi enabled thermometer to WiFi network so it can automatically send temp updates (currently I have to do it manually via USB)Have the Wheezy box accept the downloaded file then send it to a back up server in the wired network
Side things that may be useful : Prefer to use wired connection for internet and apt and suchWiFi connection will really just be used for connecting to the thermometer
This [URL] .... topic got me thinking that there might be a way to bring the two networks together, but I don't know if that will wreak havoc on things. I know, the Windows and Mac OS don't like having ethernet and wifi at the same time, might Linux be better for this?
v&n had this to offer in the prior thread [URL] .... which I'll be doing more research on.
I have installed Firestarter, and set it up following some manual (just a simple, baseline setting, nothing fancy). However, after restart I got error message: Starting the Firestarter firewall... failed! and then, later: startpar: service(s) returned failure: firestarter ... failed! Why this happens?
Upgraded webserver to Jessie as an upgrade to Wheezy produced errors, and before reboot everything was up and running, but as all upgrade docs and info I read, I rebooted the server. However it never came back. I have the original backup files before I did the Wheezy upgrade. I also have access by Rescue to the server.Made a back up of critical files and have a 24GB tar file and I can connect by SFTP.
how to check the Debian files... Grub etc.. I would prefer to find the issue than start again.I am not able to sudo from Putty. I cannot run apt-get update. I did go to chroot, but then I get unable to resolve host errors and Could not open lock file because Permission denied errors and asking if I am root.There is information by googling for start up issues, but as I am working remotely with a Rescue set up, a lot of the commands I see and have tied do not work.
A couple of days ago I asked why my pc changes the wireless card name.It switches between AR9285 ( right) and AR5008 ( wrong). Well, it is not the case. When system identified with AR9285,it loads ath9k and I can connect to the router. When system identifies my card as AR5008, no kernel module is present at all ( lspci -k). The wrong card name occurs only when system rebooted. If I gracefully shut down the system, it always comes up with a right name for the card( AR9285). So, how to force the system identify my card right no matter if I reboot or shut down?
after a reboot of my Lenny system, the default gateway will lost. Then i must try "networking restart" and the gatway will be set
my interfaces looks :
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback
I've an Blade 1500, sparc64 IIIi with 2 hard disks and 2go of RAM. The computer run with debian 7.7.0 and BSD (opensxce) for each hard disks.
1/ When it's run under BSD there are no problems, the uptime are on many hours. 2/ when it's run under debian with XFCE x-window, the uptime is 4 hours 30 minutes and computer reboot automatically !
Into the control panel i've deactivate the hibernation, screensaver and power management ! I want to find the files for manage the time down. I think that the problem is in XFCE window manager.
I've upgraded a server on our LAN from fully functioning Wheezy to Jessie. All seems fine except remote administering using Putty from my windows workstation when issuing reboot from command line, it goes down and reboots but stops at login prompt asking for username and password and does not come back on the LAN network. This server does not normally have a monitor or keyboard so my ability to remote admin this server in effect is disabled.
If I log on, it will come back on the LAN network. I've checked the logs but can't see any errors. Is it in the configuration of Jessie somewhere or perhaps a Grub issue. I have 5 other production Wheezy servers that I intend to update to Jessie once I understand how to deal with this problem.
I'm getting weird behaviour while setting up an mdadm RAID1 array on debian 8.2.
After I set-up the array, lsblk shows:
Code: Select allsimon@debian-server:~$ lsblk NAME             MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT sda               8:0  0 931.5G 0 disk `-sda1             8:1  0 931.5G 0 part  `-md0             9:0  0 931.4G 0 raid1 sdb               8:16  0 931.5G 0 disk
[Code] ....
After a reboot, lsblk shows:
Code: Select allsimon@debian-server:~$ lsblk NAME             MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT sda               8:0  0 931.5G 0 disk `-sda1             8:1  0 931.5G 0 part  `-md0             9:0  0 931.4G 0 raid1   |-md0p1          259:0  0 811.6G 0 md
[Code] ...
I don't know where the md0p1 and md0p2 partitions are coming from. My /etc/fstab and /etc/mdadm/mdadm.conf both have nothing about this in them.
parted shows one partition on md0:
Code: Select allsimon@debian-server:~$ sudo parted /dev/md0 print Model: Linux Software RAID Array (md) Disk /dev/md0: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: loop Disk Flags: Number Start End   Size  File system Flags  1   0.00B 1000GB 1000GB ntfs
Where the md0p1 and md0p2 partitions are coming from?
I'm setting up the array by doing as follows:
Delete existing device (I've done this a few times):
I've been using various distros of Linux for over 20 years - but I'm stumped.
Was running Mint. But after taking an update a few weeks ago the network stopped working. After a lot of time and effort decided to give up on Mint and switch distros to Debian 8 Jessie.
But after changing the Network settings from default DHCP to my usual IPV4 static 10.net configuration and rebooting the network will not work.
I have several systems on a 10.100.0.0/16 LAN behind another Linux system acting as firewall/gateway.
Now, after about 7 hours of mining the Internet, I still can't get basic networking to work:
- Have tried a few combinations, with and without Network Manager and eth0 in interfaces - /etc/network/interfaces is configured with a static IP and relevant parameters - ifconfig shows eth0 and the correct information - netstat -rn shows the basic default route to the gateway - have tried with IPV6 enabled and disabled; it is not used on my LAN
The box is a desktop system, ASUS Maximum VI Formula mobo with onboard Ethernet, dual GTX 780 cards. Nothing very weird.
It all LOOKS right, but ping can't get off the box "destination unreachable", and no other system on the LAN can ping it.
I'm amazed a basic static IPV4 network setup completely breaks it. This is my main workstation - a dual-boot system where Windows runs fine - so it's not hardware.
EDIT: This has been solved. See the solution post: [URL]
I have recently come across a Debian installation page for powerpc: viewtopic.php?t=20481. It got me motivated to fix the Debian I have on my iBook G4. I have a Debian Lenny installed on my iBook G4 -- but I have been having some sort of problem (mostly likely due to hardware) which causes the system to crash. After the latest crash, the clock on iBook has been readjusted. For this reason, I cannot reboot Debian completely.
Every time I turn on the computer it begins the booting process but before I get to my desktop I encounter numerous error messages concerning my clock. After either OK'ing or canceling these error messages, I get to my desktop but the system by then is either frozen or else not working at all. Worse, I can't even turn off the computer since the upper right corner of the desktop is completely blank and I have no menu to turn off or reboot the system.
It took this computer to a local Apple store and they ran many different hardware diagnostic tests on it. They concluded there's "technically" nothing wrong with the computer. But they said although the system has successfully passed all hardware tests, there may still remain some complicated but slight hardware glitch/es which the hardware diagnostics could not pick up.
last week while I was using ssh to the computer1 inside a NAT as usual, I made another tunnel from the computer1 that I was connecting to, to another computer2 inside that NAT (ssh 192.168.1.130) and after making some changes in computer2 I typed reboot. The computer2 rebooted but the tunnel totally hung and I had to kill it in my laptop. Since that day I haven't been able to ssh to the computer1 as I am used to.
Here is some more information:
debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Offering public key: /home/une/.ssh/id_rsa
I am having slight issue with setting up file sharing. I have a windows 7 pc and hp proliant microserver running. I have a raid array which I am using as a share for storing music, pictures etc. When I reboot the debian server I can't connect to the server from the windows 7 PC (I have mapped a network drive) until I go on to the server and restart samba with /etc/init.d/samba restart - then everything works fine. I can ping the server with both ip and hostname but the network drive does not connect - this is straight after a reboot. Is the /etc/init.d/samba restart doing something differently to when the server boots? I have read several posts relating to printer sharing issues which point to samba not starting before cups so I am wondering if samba is starting before some of the relevant networking services.
running Debian Squeeze (standard 32bit squeeze Kernels linux-image-2.6.32-5-486 and linux-image-2.6.32-5-686) happily without trouble on a 64bit capable Samsung laptop featuring an Intel T3200 Dualcore processor. However, when I try to boot using the squeeze 64bit kernel (linux-image-2.6.32-5-amd64) the system proceeds through a few text lines immediately after Grub, and then performs a warm start.
The text output I get immediately after Grub look similar to the ones I get booting the 486 and 686 kernels, without any indication for the reboot behavior. The rebooting also seems to happen before any entry is written into the boot/system log files (logging is enabled). This behavior also occured when I first tried to prime the machine from the Debian squeeze install CD using the amd64 kernel. I'm generally happy with the 32bit kernels, but I'd like to use the amd64 support to do some Java compatibility testing for 64bit architectures.
The Laptop is a Samsung R510-Aura T3200 Delfina with the following Hardware and Setup (using Grub as boot loader):
- Intel Pentium Dual CPU T3200 @ 2.00GHz (see http://ark.intel.com/Product.aspx?id=37160 for details) - NVIDIA GeForce 9200M GS - 3GB RAM + 1GB reserved for GeForce - Konfiguration Details: -- Phoenix Bios
[Code]....
Maybe a strange BIOS-Setting that works with the 32bit kernels but not with the 64bit kernel? I've seen a post on here that indicates someone is running the amd64 kernel on a T3200 successfully, and the chip is definitely 64bit capable, so the reboot behavior is a complete mystery for me
I am running Ubuntu 10.10, and I would like to use my computer to share the internet connection from an ethernet port. For example, I would like to set up my computer as a wireless access point so I can create a network that other computers can connect to for internet.
