I cannot seem to get e2guardian to work. I went into Ice Weasel to adjust the proxy connections but that just blocks off all internet activity. The problem seems to be with the configuration settings in the browser. I tried Privoxy with a completely new Debian install and have the same problem.
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 have a debian 8.1.1 server running owncloud and a proxy server at home. I have everything working fine, with one exception. The proxy server won't start on boot. If I ssh into the server, then run "sockd -D" as root, it starts up and runs just fine. Any guides I find refer to the init.d script method that worked in Wheezy, but that isn't working. I think it has to do with Jessie switching to systemd? I had used someone elses script in init.d, and ran update-rc.d, but it still doesn't start.
With Jessie, how can I make "sockd -D" execute on system startup?
I would like to redirect traffic coming from a machine A through a SOCKS proxy (setted on machine B)Machine B run "ssh -D 4242". So that create a SOCKS proxy on machine B.Machine A would like to connect on the internet, but the only way is to use machine B SOCKS proxy. The problem is machine A don't know how to use SOCKS Proxy. (Actually, i can just set ip, netmask and gateway on machine A).So, I would like to set up something on machine B that will redirect all traffic coming from machine A throught the SOCKS proxy.
I was wondering if there was some kind of anti-spam proxy available for debian, that could serve as a layer between my ISP's mailserver and my email client. Something light, as it needs to be installed to a guruplug server with not much storage available. It would be great if I don't need to configure a fully fledged mail server but if it can function on it's own, only filtering spam messages. I already found assp and qpsmtp, but I find these very difficult to setup and assp is like huge.
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 installed apache2 and mysql database on a Debian system. It is using reverse proxy on apache to redirect requests to apache2 running on any machine which is on Xen server as a Virtual host. I tried to install Drupal on it. Every thing went fine till I pointed my browser to: http://IP[/url] of LAN where Drupal was installed/drupal then I see an installation page of Drupal which welcomes me. I click install in English then it can not proceed to connect with database. Database configuration: Your web server does not appear to support any common database types. Check with your hosting provider to see if they offer any databases that Drupal supports.
I have created a database and username for Drupal separately. What should I check to. There is one more error http://Public IP/some location/ Is showing me contents of Document Root but there is a folder named drupal on it. When I click on it I get error. Not Found. The requested URL /drupal/ was not found on this server. Apache/2.2.9 (Debian) PHP/5.2.6-1+lenny8 with Suhosin-Patch proxy_html/3.0.0 Server at
What things should I check in for? I am also getting errors like: - Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName on individual DomU's what should I check in. and on Dom0 when restarting apache2 I get following error. - Reloading web server config: apache2apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName [Wed Apr 14 15:23:05 2010] [warn] NameVirtualHost *:80 has no VirtualHosts
I am working on fc10. I connect to internet using two connections: with proxy and without proxy. Initially I had some problem in configuring yum for proxy and I resolved it by creating files proxy.sh and proxy.csh in /etc/profile.d with the required details (export_proxy).Now when I connect to my connection without proxy I have some problems .Whenever I try to do yum update I get the following error:
"[URL]: [Errno 12] Timeout: <urlopen error timed out> Trying other mirror. Error: failure: repodata/primary.xml.gz from adobe-linux-i386: [Errno 256] No more mirrors to try." what changes do I need to make in order to use yum in the connection without proxy?
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
My 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
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:
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
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 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.
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?
I 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.
Alright, 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?
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..
How 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.
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
I bought a bluetooth pen, I connect it via USB, my bluetooth connection is active but I can't find other therminals, and my debian machine it isn't visible to other terminals.
It seems that my bluetooth connection works, but it can't pair other terminals. I want to connect bluetooth speaker, but it seems impossible.
I 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.
I have a Dell Mini 9 with a Broadcom wireless adapter. I've had it working for months on Debian Sid, but recently I updated the entire OS to get KDE 4.4 (I also went from a 2.6.30 to a 2.6.32 kernel). Something in that upgrade caused wireless to cease to work properly. The problem is similar to the one described in this thread, but no resolution is mentioned there: viewtopic.php?f=5&t=50892 I've gone through all the steps to install the STA drivers/wl module for it, and it basically appears to be working. Using wicd, I can see all the wireless networks in the area.
The problem occurs when trying to connect. When I try to connect to my WPA wireless network, it eventually fails claiming a bad password. When I turned the wireless network into an unsecured network, it eventually fails claiming it's unable to get an IP. I've also tried at the command line with wpa_supplicant and it initially appears to work but in fact it hasn't. I've also got Kubuntu 10.04 installed on this machine, and it can connect without issue (using the proprietary driver that Ubuntu's hardware driver manager allows one to use).Does anyone know what has caused this? I even tried the earlier kernel, so that's not it.
How to verify that Debian is running at 100 Mbps or 1000 Mbps? I can view the report from 'ifconfig eth0' but I can't see how fast the link has been established.