Bug? - Debian does not assign IP address after reboot?
Hi, After I reboot my Debian machine it does not assign an IP to eth0. It brings the interface up after a reboot, but does not set the IP on it! Running a cronjob every min to set the IP address is the only way to fix this, but why does it happen? Is this some sort of bug? My interfaces file is as follows: auto lo iface lo inet loopback auto eth0 allow-hotplug eth0 iface eth0 inet static address 172.16.0.30 netmask 255.255.0.0 allow-hotplug wlan1 iface wlan1 inet static wpa-ap-scan 1 wpa-scan-ssid 1 wpa-ssid connect wpa-psk linuxthefish address 192.168.43.200 netmask 255.255.255.0 Please can someone tell me why this happens? :( Thanks!
Re: Bug? - Debian does not assign IP address after reboot?
Hi, I removed allow-hotplug eth0 and it still does not auto configure :( Where would i find log files to diagnose this? Thanks On 16 September 2015 at 20:55, Sven Hartge wrote: > linuxthefish wrote: > > > After I reboot my Debian machine it does not assign an IP to eth0. It > > brings the interface up after a reboot, but does not set the IP on it! > > Running a cronjob every min to set the IP address is the only way to > > fix this, but why does it happen? Is this some sort of bug? > > > My interfaces file is as follows: > > > auto eth0 > > allow-hotplug eth0 > > iface eth0 inet static > > address 172.16.0.30 > > netmask 255.255.0.0 > > You cannot have both "auto eth0" _and_ "allow-hotplug eth0". Choose one. > > S° > > -- > Sigmentation fault. Core dumped. > >
Re: RAID 1 System Installation Question
Tim, >From what I remember it's best to set it up when you installing the system, then you can install the bootloader to /boot in RAID 1. https://blog.sleeplessbeastie.eu/2013/10/04/how-to-configure-software-raid1-during-installation-process/ is what I followed. Thanks, Edmund On 18 September 2015 at 22:11, Tim McDonough wrote: > I've used Debian Linux for a number of years but up until now always with a > single hard drive. > > I want to build a new system that will have a pair of 1TB drives configured > as a RAID-1 mirror. In reading the mdadm Wiki the discussion begins with > installing mdadm. > > My goal is to have a system where if either drive fails things will a) > continue to run from a single drive, and b) be able to replace the failed > drive with a new one of the same size and have the system rebuild into a > mirrored array again. > > It is not clear to me how I need to begin the installation sequence. > > My question: Do I install Debian to a single drive and will installing mdadm > then allow me to add the second disk and setup RAID? Do I need to configure > each drive in some way before installing Debian and then mdadm? > > If there is an up-to-date "how to" that describes this please just point me > there. I have not found anything that seems to start at the point where I > just have bare metal. > > Regards, > > Tim >
Re: Debian tracker
Tracker is down here also! On 19 September 2015 at 11:03, mls wrote: > Hi all, > > when I try to download debian ISO images via bittorrent I get an error > message: > > Error: invalid data from tracker > > when accessing http://bttracker.debian.org:6969/announce. > > Using wget I see > > #wget http://bttracker.debian.org:6969/announce > --2015-09-19 09:52:43-- http://bttracker.debian.org:6969/announce > Resolving bttracker.debian.org (bttracker.debian.org)... 130.239.18.146, > 2001:6b0:e:2018::146 > Connecting to bttracker.debian.org (bttracker.debian.org)| > 130.239.18.146|:6969... connected. > HTTP request sent, awaiting response... No data received. > Retrying. > > Any idea? > > Thanks/regards, > > mls >
Major bug with wired/wireless connections in Debian 7
Hello, It looks like Debian will only connect to a wireless network when the ethernet cable has been plugged in and unplugged. Both the wired and wireless connections are set to automatically come up - but wireless will not come up and fails to respond to ping unless a ethernet cable has been plugged in. This even applies if the ethernet cable was plugged into a random network, or a switch with no other ports in use! auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 172.16.0.4 gateway 172.16.0.1 netmask 255.255.0.0 allow-hotplug wlan0 iface wlan0 inet static wpa-conf /etc/wpa_supplicant/wpa_supplicant0.conf address 172.16.0.5 gateway 172.16.0.1 netmask 255.255.0.0 Thanks! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAJMAWMv5MjuO8J+fCG2q5X03sYUTidFa=wHe7hSEHOhrgurP=q...@mail.gmail.com
Re: Major bug with wired/wireless connections in Debian 7
Hey guys, Thanks so much for your help! I can confirm removing the default gateway from eth0 solved this! I don't use ethernet much, so it's not a big deal to add the default gateway manually when I do so. Thanks On 16 Jun 2015 20:24, "Bob Proulx" wrote: > Reco wrote: > > linuxthefish wrote: > > > auto lo > > > iface lo inet loopback > > > > > > auto eth0 > > > iface eth0 inet static > > > address 172.16.0.4 > > > gateway 172.16.0.1 > > > netmask 255.255.0.0 > > > > > > allow-hotplug wlan0 > > > iface wlan0 inet static > > > wpa-conf /etc/wpa_supplicant/wpa_supplicant0.conf > > > address 172.16.0.5 > > > gateway 172.16.0.1 > > > netmask 255.255.0.0 > > > > You're configuring a default gateway for both network interfaces, which > > is a big no-no, unless you know what you're doing. You also set IP > > addresses from the same network, and that is one of the best ways to > > have your host's IP routing going haywire. > > Good observations! I missed seeing both of those when I commented in > my response. (I hang my head in embarrassment.) Both are very > critical no-no's. Both configuration problems should be avoided. > > I wonder if those are clues as to why the reporter said that it needed > a cable plugged/unplugged? Because I think that would rotate the > order of the default routes. That might account for the odd behavior. > > Bob >
