Debian Configuration :: Squeeze Hanging At Configuring Network Interfaces
Dec 20, 2010
Alright, every time I boot or shutdown my routing box, it hangs at configuring and deconfiguring network interfaces. Below is my interfaces file. I see no errors or warnings in my log and I am running a pure kernel, not tainted with proprietary drivers. All of my hardware is 100% supported.
I had one of those random system deaths, so reinstalled squeeze (daily netinst image I think...) on my eee 1000, which uses an rt2860 wireless chip. The new install only installed 2.6.32, which I had been avoiding using because of a few problems, including it dealing with networking slightly differently. I couldn't get it to work - even without encryption - using wicd. Having had a read of [URL]... , I had a look at /etc/network/interfaces, which read; This file describes the network interfaces available on your system and how to activate them. For more information, see interfaces(5).
ra0 is now called wlan0, as far as I'm aware. I've read in several places that it is best to expunge this file of all references to wifi, so I removed the bottom section (after '# The primary network interface'). I still got nothing. However, if I go ahead and change the 'ra0's to 'wlan0's, it seems to work - wicd connects. Not very familiar with Debian (spent more time on SUSE. Drop your tomatoes - I like it. Any idea what is happening? Is what I'm doing wrong? Conversely, is the file wrong? Should it be reported? Against which package? Including any particular files?
I have a rather urgent problem with my network, I got two virtual network interfaces one internal and one external. The problem is; I can't get connection to internet. The external NIC is set as a NAT and the internal is... internal.
I have a Dell PowerEdge SC430, Squeeze 6.0.2 box, Broadcom NetXtreme NIC which works fine DHCP. The network-manager package is not installed. I have now reconfigured /etc/network/interfaces for a static IP:
auto eth0 iface eth0 inet static address 192.168.1.2
i recently started sockets programming. In the process i began to look for relevant network information about my computer and realized that ifconfig wasn't displaying the same information that resides in my /etc/network/interfaces file. On the interfaces file my IP address is 192.168.1.109 for interface eth0 but ifconfig displays 192.168.1.101. I was under the impression that ifconfig got its information from the interfaces file but clearly doesn't. I tried re configuring the device with ifconfig and then disabling and re enabling the device with ifdown and ifup so that the device updated its information but it didn't.
I've been following this guide for squeeze: [URL] After getting the wireless-tools and firmware-ralink packages installed with no internet, I managed to installthe driver using modprobe rt2870sta (the 4th step). With the module loaded and the device plugged in (a RangePlusWireless Network USB Adapter with the WUSB100v2 chipset), iwconfig returned something like
and then ifconfig wlan0 up returned ERROR while getting interface flags: no available device
My ethernet and pppoe internet connection worked flawlessly in lenny. I erased my hard drive and installed squeeze and now only internet works. (There is a pop-up that says that my wired connection is disconnected and shortly after there is another pop-up saying that my internet is connected.)1.my user is in the netdev group2./etc/network/interfaces only contains:
auto lo iface lo inet loopback 3. /etc/NetworkManager/NetworkManager.conf only contains:
I am unable to figure out how to set up a net work printer with new squeeze installation. I have used cups ver 1.3.8 on lenny and have never had any difficulty, this new version 1.4.4 I'm unable to gain any ground with.I did a purge and re-install with no luck?
I would like to connect from squeeze to my windows network. Do I need samba server, smbclient is already installed? If I do a doubleclick -> Windows Network then get "Unable to mount location". If I use -> Connect to Server -> Windows Share then it works well. How to configure samba server that I can see Windows machines in "Windows Network"?
I have just updated my Squeeze system. The update included a newer version of network-manager (and it can not be more than a few hours old). After the update all network functionality on my machine (via knetwork-manager) is broken. The GUI applet has no effect.
Hence can anyone help me: a) Downgrade network-manager by one version; b) Find out what is causing knetworkmanager to break; c) See if the problem is with knetworkmanager or network-manager.
I upgraded from lenny to squeeze on a notebook and I can no longer connect to the wireless network. The computer is an LG notebook and the network card is ralink rt2860. I am using Gnome and NetworkManager. The wireless key is WEP hex. It was working fine with lenny till before the upgrade. After the upgrade, the network card stopped working. So, I checked
Then I reinstalled the driver with apt-get install firmware-ralink wireless-tools Then the network manager tray started working again and saw the network, but cannot connect. It was trying to connect but timed out and kept asking for the password. It is the correct password. I tried deleting the old connection and recreated a new one in the nm. But still does not work.
I have and old PC and for last years i had Debian Lenny on that and it was working great but after the Squeeze release, i downloaded the first CD image and did a fresh installation but after this it boots up with no problem (i must say since in Squeeze installation the option of creating a floppy diskette was not working properly i use SuperGrubDisk2 to boot the Debian), but few seconds after logging in, the system hangs (or maybe only the X11 since i use a historic nVidia TNT2 Riva graphic card!).
My new Squeeze machine detects all of my hardware including the LAN and WLAN cards, but only brings up the LAN card. There isn't even an entry for it in /etc/network/interfaces for me to modify. I tried adding the info manually but then the entire network wouldn't start. I had it configured as a static IP and I know the commands were correct due to them working on the LAN card. I believe that the name "wlan0" was causing the problem, but how else can I bring it up at boot?
I have two interfaces, gprs0 and gprs1, both connected to the Internet from the same HW device, but through two different access points I just read another blog entry with a guy who had two network cards, using one as a back up - I guess this is a little similar, but should be much easier I am guessing - I am just lost Using ifconfig (IP address given by the network) and route to setup the connection,
ifconfig gprs0 10.20.30.40 up route add default dev gprs0 ping 126.96.36.199 works fine afterwards
There is data being transmitted and received to device again, I guess the kernel just doesn't know where the incoming data should go without the correct routing tables? Or what exactly is going on?The question I have is how do I configure the device to do the correct routing, using only the ifconfig and route commands? Maybe too trivial for you guys, but I am getting tired of goofing around not knowing what is up and down anymore
I have a set of vm's with stable, testing, and sid to keep track of how things are going. When I did an apt-get dist-upgrade with squeeze last week, things seemed to OK (350 package updates) until the end. It didn't seem to like and / or was confused by a kernel dependency.
I am not too concerned yet. Because these are in vm's, I do a snapshot before any significant change. I can futz around with impunity because I have that backup.
I re-booted, and tried the apt-get dist-upgrade again with same results. I think I also tried apt-get -f install.
So I reverted to the snapshot, and will simply try again in the future. I recall that with lenny as testing, the font-desktop was really screwed up for about a period of 6 weeks.
However, just in case someone else runs into this:
1) a re-boot worked, but the failure of apt-get made me nervous enough to revert.
2) waiting for corrections has seemed to work in the past (with a single exception with a 4-disk SCSI software RAID10 update that failed to re-boot lenny successfully after what seemed to be a minor update -- that was on a real system, not a vm. I haven't gotten back to look at that.)
So I've always asked this in the past when I get on a Debian system. This makes no sense to me but I just don't see how I restart network interfaces (i.e. eth0) on a standard Debian install. If I change the static I.P. address listed in /etc/network/interfaces from x.x.x.100 to x.x.x.101, I then assume I can simply do any of the following:
- /etc/init.d/networking stop | start - ifdown eth0 - ifup eth0 - service networking stop - service networking start
All the commands above do nothing. My only solution I know that works and implements the changes I've made is a complete system reboot which to me in Linux, is ridiculous. I've struggled with this over and over and nothing I do correctly assigns the new I.P. in the 'interfaces' file to the actual adapter. This isn't my single isolated Debian machine but every Debian machine I can get my hands on. Servers, workstations, VM's, any release, etc etc etc. Below is my interfaces configuration file:
I recently just installed Squeeze on an ia64 system and was having some troubles with running VNC.I get the following error, more specifically for some reason I get a malloc - memory corruption error:
Xtightvnc(9165): unaligned access to 0x60000000001ea06c, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea074, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea07c, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea084, ip=0x4000000000268280
After display all the code above, it just stops. The port 5901 is still closed - if it runs properly, would it open automatically?Is there something that is incompatible? Or am I missing some system configuration component?
I'd like configuring NTP service on my Lenny Debian client to retrieve time from my local NTP server, so I thought to configure /etc/ntp.conf and to insert into crontab this command 'ntpd -qg', which is indicated in man. Can I run ntpd service to synchronize time for my client, avoiding to listen on port 123, beacuse my scope is to alignment time on client and to not give service to others, for this scope there is ntp server !
Today I decided to include again Debian Volatile and discovered that it doesn't exist anymore and that I can get the same packages using this line: deb [url] squeeze-updates main
And the first question is: is this the same than debian-security?
Then, I decided to use [url] to make things less confused, and this was the output:
The first line is Ok. The second line, I guest it's the same than my second line. But, the third, is something different. So, the main question is: what is the difference between squeeze-proposed-updates and squeeze-updates? Are those repos completely separated from squeeze/updates (in security.debian.org)? And, what else should I add to have an always up-to-date and secure system?