About an hour ago i did an update on my Debian Squeeze. After the update was completed my LAN connection stopped working.. now i have to connect my computer to my router with a usb cable instead with my ethernet cable.. also, on the network connection, on the wired network section it says that the device(ethernet) has not been managed..
View 1 RepliesAMD 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?
View 5 Replies View RelatedI just installed the lastest stable Debian (gnome) today and what I was most afraid just happened: my laptop's wifi isn't working properly, it isn't turning on. This had already hapened on livecd.
In the laptop's chassis leds, the wifi led apears as green. When I click to turn on the wifi, as shown on the picture the button, quickly disappears and appears again not seeming to have any effect at all at turning on the wifi but not showing any error either!
Picture :
What's interesting about the wifi not working is that in the installation process I was able to connect to a wifi hotspot and it connected to the internet fine!
Now after installation was complete and my system did the reboot, I was no longer able to connect to the internet using wifi.
My wireless card is Atheros AR9565 and my LAN card is also Atheros.
Here is an output of lspci and lsmod which may have some leads about the problem.
lspci
Code: Select allquant@debian:~$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
[Code] ....
Noticed:
1. I installed WiFi radar and I ran this on the terminal:
# sudo ifconfig wlan0 up
after a long time I did a little upgrading of the packages...
bind9-host:amd64 (9.7.3.dfsg-1~squeeze1, 9.7.3.dfsg-1~squeeze2), linux-image-2.6.32-5-d64 (2.6.32-31.6.32-34squeeze1), dnsutils:amd64 (9.7.3.dfsg-1~squeeze1, 9.7.3.dfsg-1~squeeze2), linux-headers-2.6.32-5-common:amd64 (2.6.32-31, 2.6.32-34squeeze1),
[code]...
So I just installed Debian Lenny on my PC (the install went fine). After installing, I went into aptitude and noticed that most of the packages available in the repository are out of date (python 2.5, GCC 4.3). System Update tells me that I am up to date, and when I tell synaptic/aptitude to mark all updatable packages, it does nothing. I have tried typing apt-get update as root aswell. Nothing worked.
I installed Debian with the first DVD from [URL]. During the installation, I told it to download anything that wasn't on the DVD. Shortly after installing, I had manually edited my /etc/apt/sources.list and commented out the CD line. Could any of this have messed up APT?
I run a Squid 3 server that is acting as a web filter. It worked fine on Etch. The system stopped working properly due to two of the three SATA cables being bad. Before I figured that out, I tried doing updates. Since Etch updates were no longer available, I did a distupgrade to Lenny. Immediately, Squid stopped working properly. It would take up to two and a half minutes for it to respond to a web request and add it to the access.log. This was using the same configuration file that it was using before the update.
After I found the hardware problem, I did a clean install of Lenny. I used the basic squid.conf like I did on the previous system, only changing it to add my ACLs and because it wasn't saving an access.log to the default location unless I uncommented the path directive. Now, it won't respond to a request at all. Forwarding is enabled and the firewall seems to be set up correctly.
I've just upgraded my kernel to 2.6.32 and I cant use sound anymore!!! My card was detected ,here is the output of lspci |grep Audio
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
also frimware is installed ,gstreamer as well the sound is not on mute and it was working on the previous kernel .
I've been enjoying wireless for a long time on Squeeze (iwl3945) with KDE, but the recent network manager update stopped that. I've tried a few things, like going back to /etc/network/interfaces and ifup wlan0 that I use with Lenny, but still not working.
View 14 Replies View RelatedI 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).
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.
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 a very strange problem; when trying to apt-get update or aptitude update I get time out errors. At first it was resolving ipv6 adresses:
Cannot initiate the connection to ftp.litnet.lt:80 (2001:778::87). - connect (101: Network is unreachable) [IP: 2001:778::87 80] Err [URL] Cannot initiate the connection to security.debian.org:80 (2001:a78:5:1:216:35ff:fe7f:6ceb). - connect (101: Network is
unreachable) [IP: 2001:a78:5:1:216:35ff:fe7f:6ceb 80] As my host does not have normal ipv6 support, i just tried to disable ipv6: echo net.ipv6.conf.all.disable_ipv6=1 > /etc/sysctl.d/disableipv6.conf
[Code]....
I was trying to get the Windows one working again. Here's what fdisk -l reads:
[Code]...
I'll change these or do some grub configurations, if anyone knows what ones can work.
I have openssh running it was working last week then an update was done and now ssh does not work. removed the updates and the problem still exists.
Its CentOS 5.5 with all the latest updates for 64 bit!
Issue if as follows:
Connect locally to the loop back ip or remote ip the connection is disconnect right after the correct password is entered.
Here are copies of the log, sshd config.
sshd config:
I have a laptop Acer aspire 5100. I installed Ubuntu a while ago and it was working well. Last week I updated it using Update manager and ever since I haven't been able to connect either wireless or wired connection.
I get this:
Code:
The wireless card seems to have disappeared.
I reinstalled Ubuntu and the problem persists.
I'm having a bizarre problem where my network connection stops working randomly. At first I thought it was a DNS issue since Firefox simply chilled out on "Looking up [hostname]" until it timed out, but after further investigation (pinging IP's, "host" and "dig" being unable to reach servers) it became apparent that I couldn't even access the DNS servers i.e. the Wicked Connection of the East was most sincerely dead.
There are two strange things about this: one, there are no errors except "timeout". The network manager is happy, Firefox is happy until the lookup fails... Two, the failures only start *after* DHCP configuration. DHCP configuration never has any trouble sending or receiving packets. I'm going to try static IP and whatnot to see if that helps, more information later.
My Debian Jessie system started to bug after a separate /usr partition being full. After redimensioning and various packages reinstalls I fall on this:
systemctl --user status Failed to get D-Bus connection: Erreur inconnue -1
I am struggling to find out how to start the connection to my VPN on boot?
View 1 Replies View RelatedMy network configuration is in a weird situation, that I always need to run dhclient manually each time after a network connection is established. When my computer connects to a router, sometimes it won't get a valid IP, and it uses an automatically generated fake Internet IP. In this situation, it won't connect to the Internet at all. Sometimes it get a valid local network IP, but still cannot connect to WAN, and could only connect to my router's address (both through ping and through router's management webpage). In both situation, it can be solved by a simple dhclient run.
This is my /etc/network/interfaces file:
Code: Select all# 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
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
iface wlan0 inet dhcp
and this is my /etc/NetworkManager/NetworkManager.conf:
Code: Select all[main]
plugins=ifupdown,keyfile
dhcp=dhclient
#no-auto-default=FE:50:52:BE:46:4C,
I use Debian Jessie 8.2 and I am using a 3G connection using this modem => [URL] ....
The 3G connection works fine, except after 24 hours the connection drops and I cannot reconnect. If I reboot the computer, the connection will work again.
My guess is that my ISP gives me a new IP address after 24 hours and somehow my system cannot handle it.
How can I reconnect my 3G connection without rebooting?
I have already tried the following commands:
Code: Select allsudo service network-manager restart
Code: Select alldhclient -r eth0
dhclient eth0
Code: Select allsystemctl restart ModemManager
Results of journalctl and grepping my connection name (SFR)
Code: Select allsept. 22 17:58:19 ark1 NetworkManager[512]: <info> Policy set 'SFR Web / Prepaid 1' (eth0) as default for IPv4 routing and DNS.
sept. 23 18:17:07 ark1 NetworkManager[9446]: <info> new connection /etc/NetworkManager/system-connections/SFR Web * Prepaid 1
sept. 23 18:17:08 ark1 NetworkManager[9446]: <info> Auto-activating connection 'SFR Web / Prepaid 1'.
[Code] ....
As you can see sept 22 at time 17:58 is when the computer started up. And roughly 24 hours after it failed to reconnect.
Also I should mention that there is a script to run the command:
Code: Select allsudo service network-manager restart
if the computer cannot ping a server, ie if the connection is lost.
More journalctl info when the system tries to reconnect:
Code: Select allsept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Auto-activating connection 'SFR'.
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) starting connection 'SFR'
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
sept. 23 23:52:53 ark1 NetworkManager[9446]: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
[Code] ....
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
[Code] .....
I have been tol that for debugging purposes it is often useful to have a serial connection to a computer. I have some diskless workstations thats freezes during boot. I guess X has someting to do with this, but I'm not sure. Since the workstations are diskless, syslog is not stored locally so I cant se what is happening after the NiC stops working. When the worstation freezes, screen is going black, all lights on the keyboard turns on, lights on NiC is going black. It is not possible to ping the workstation.
View 1 Replies View RelatedI am getting this error when I try to bring up IPSec Tunnel.Starting connection with command /usr/sbin/ipsec auto --up 'paycode-to-vivacom' ..
104 "paycode-to-vivacom" #7: STATE_MAIN_I1: initiate
003 "paycode-to-vivacom" #7: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02_n] method set to=106
003 "paycode-to-vivacom" #7: ignoring Vendor ID payload [FRAGMENTATION c0000000]
[code]....
I have configured a RaLink wireless card to connecto to an 802.1x network. I connect by selecting the network, and the i give the credentials(username/password). How do i configure Debian to automatically connect to this network when a session begins?
View 2 Replies View RelatedI have installed GNU/Linux Debian on my computer (desktop) and i have ubuntu installed on my laptop. Now I want to start the ssh connection between both the computers. I want to make Debian as server and Ubuntu as client. Please can you guide me with this (installation and setup). Also the key values of the configuration file (ssh_config & sshd_config) are expected.
View 10 Replies View RelatedAlright, I was playing with the VPN capabilities in KDE4 on Squeeze AMD64 on my personal laptop (see my signature) and found it very easy to create a VPN connection and connect, but that's it. I made a VPN tunnel to one of my client locations as a test, but could use rdesktop to get into the server. Then I realized I couldn't ping the server either. I also lost all ability to browse the web and everything while the VPN was up. Upon checking ifconfig as root, I saw that it created "ppp0" and hat it had pulled an IP from the client network, but all of my networking capabilities were gone. What gives? What is it that I am missing?
View 4 Replies View RelatedWhen I click on Network Manager client in the Gnome Panel -> vpn connections -> configure vpn, the add button is not enabled.
View 5 Replies View RelatedHow to enable wifi? I downloaded and installed Debian 6.00 and as I couldn't get online with my Tenda USB Wireless Adapter. I downloaded Debian 6.00 again, this time the CD Net Install version with Firmware included. However, the added firmware version of Debian does not find my wireless either. My wireless adopter is shown as Bus 001 Device 003: ID 148f:3072 Ralink Technology, Corp. RT3072 Wireless Adapter. There is a Network Icon in the Panel which when clicked shows "Create New Wireless Network". I have put in my ISP related network and my password and rebooted, but all I get is the message on my desktop:
"The Network Connection has been disconnected."
That isn't very polite, is it? Who has disconnected it and why remains a mystery to everyone except the culprit(s). I think I must have missed a basic step in the Wifi Enabling process. I checked the Use Permissions and everything is fine there, as User I have permissions to use modems and do networking and so forth. Also I should like to try "modprobe" but I see the package isn't in Synaptic Package Manager.
In one of my customers, the new internet connection have no public IPV4(using GCNAT), only public IPV6.
And there are various services that require external access, like, vpn (openvpn), a java/web system, ssh, rdp(windows).
fileServer(by vpn).
All is running ok in IPV4.Maybe, the solution is a NAT 6to4. We know this is the future, no more public IPV4.
After upgrading to Debian 8, I'm having a bit of trouble with systemd, since I'm not used to it (seeing as it was all init when I started). I tried to use a tutorial to create a new service and one step in it was to run
Code: Select allsystemctl enable xxx.service
Unfortunately, every time I run systemctl - even without parameters - I get this error:
Code: Select allFailed to get D-Bus connection: Operation not permitted