I have upgraded my server to Debian 6.0 Squeeze but it looks like some of my sites are not compatible with PHP 5.3.x so I would like to revert to previous 5.2.6 version.So my question is what to do?a) Remove PHP 5.3.x from system via apt-get and install my old 5.2.6 from old archives at /var/cache/apt/archivesorb) just try to update from archives PHP to 5.2.6?
-rw-r--r--. 1 root root 2413316 May 11 2008 libapache2-mod-php5_5.2.0-8+etch11_i386.deb -rw-r--r--. 1 root root 2413290 Oct 6 2008 libapache2-
5.10 Breezy configured as machine controller. Works great eth0 is a fixed IP to communicate with controller comms board. Not easy at all to alter - the comms board is hard coded to listen on eth0 for commands.
I can use eth1 as the default gateway and ping google.com, etc. But when I now attempt to communicate with the controller with netcat, e.g.
Code: echo !HH | nc 192.168.1.6 80
I obviously never get an answer since the request is passed via eth1. Using the -g option with netcat doesn't work either. I had a look at iptables but it doesn't seem to be able to do what I want. How I can still use eth0 as my communication port to the controller whilst eth1 is the default gateway?
I have an adapter eth0 I need one shared folder to exchange files, with another machine configured as 192.168.0.3/255.255.0.0
ping is working fine between both machines, but I think my problem is in routing, or I need to add a shared resource and I am having trouble with that... not sure if maybe I need to mount something as nfs or what?
I installed Debian Squeeze on my system two days ago, using a wired connection to internet (which worked fine). After that, I had to install the non-free wireless package in order to scan wireless networks. It now works fine, and I can connect and get to internet. But with wired connection, i connect via eth0 and none of my applications work. And they're not in offline mode.Also, i already went here: URL,,, and I checked if that was my case. I tryed what they say several times in some different ways, but I still can't connect. Even more, if I change something like they say, I get "unmanaged device" and I can't even connect to the internet. And the wired connection works, I'm using it right now on my ubuntu 10.10.
If you want more information, I just tried to ping sites like google.com or ......com using network preferences and it does work, it gets 100% of the packages back around 50ms later, so the internet appears to work. Also, when I connect via wireless, everything works perfectly.
I noticed that when my server boots up, it's network interface on eth0 is always down and I always must run the 'ifup eth0' command in order to get it to work for some reason. I checked my configuration and it looks legit to me...
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).
Anyone know why my system is booting with out bringing up my eth0 interface? It's very annoying.
I recently set up a Debian-based gateway+router on a remote site. I've installed OpenVPN and made a VPN bridge to another network (that server is also Debian). The main network has all the resources and also a VoIP server (asterisk). Bridge seems to work fine, except that every time a Linksys phone is used to call - after a few seconds I get:
Jul 20 12:16:05 sklad kernel: [403987.817695] eth0: link down Jul 20 12:16:05 sklad kernel: [403987.817939] br0: port 1(eth0) entering disabled state Jul 20 12:16:07 sklad kernel: [403990.113701] eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
So whenever the phone is used, network falls down for a few seconds. And of course this breaks the call. There is also another Linksys box (analog-to-voip) and it works fine most of the time. However sometimes this "eth0 link down" happens too. There is nothing more in syslog to analyze, so I don't know where to dig. Physical device of eth0 is D-link DFE520.
When I stop/start vm(not restart), dhclient becomes up and ip is assigned by dhcp. Why? -------------------------------- yoshi@vbox:~$ uname -a Linux vbox 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GNU/Linux -------------------------------- yoshi@vbox:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5).
I'm trying to setup a DHCP server that serves several different VLANs, we have 5 in total. Our network is working correctly, with static IPs, we're able to ping across without any issues.
When I connect my debian box to an interface on VLAN5, statically assign an address in the correct range, it works. Similarly with all other VLANs.
To configure this box as a DHCP, I set one of the ports on the switch as trunk, connect that to the debian box to allow all VLAN traffic to reach my debian box.
I setup DHCP following the steps on [URL] ....
Then I configured different VLANs by following the steps on [URL] .....
However, with the vlans setup, I am unable to ping anything. This is essentially what I did.
Code: Select allSet the port on the switch to trunk with 802.1 encapsulation disable eth0 vconfig add eth0 5 # to add vlan 5 ifconfig eth0.5 192.168.5.254 netmask 255.255.255.0 up vconfig add eth0 5 # to add vlan 10 ifconfig eth0.5 192.168.10.254 netmask 255.255.255.0 up
I do not know why I am unable to get any connectivity through my VLAN interfaces.
I am connected to a network using any interface (eth0, eth1, or wlan0) that if my ip address was given out (dhcp) that my desktop responsiveness gets worse. Specifically the mouse has a sort of "sticky" feeling. I mean by that that I'm moving the physical mouse and the cursor is getting stuck here or there on the screen. It is extremely annoying. Here is my config file:
beethoven:~$ cat /etc/dhcp3/dhclient.conf # Configuration file for /sbin/dhclient, which is included in Debian's #dhcp3-client package. # # This is a sample configuration file for dhclient. See dhclient.conf's
I have setup a few machines within my house. The Debian Squeeze machines do not provide a host name in the DHCP client list on my router. Strangely, my Ubuntu, Android, and Blackberry machines do show host names. I have noticed the same behavior when wirelessly tethering my Debian laptop to my Android phone (which also uses DHCP). Is there something I need to enable to have the name show up on the router?
I am running : Linux ics385 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09) x86_64 GNU/Linux
Here's the situation
1. I'm trying to configure a WLAN using a D-Link DLR655 wifi router that is connected to eth1.
2. eth0 is connected to the ISP's DHCP router and has the IP 192.168.0.24
3. I've bridged eth0 to eth1 such that eth1 has the static IP 192.168.8.1
4. I've manually configured the router and it uses the 192.168.8.1 as the WAN address with its subnet on the 192.168.10.* address space.
5. I can connect a laptop to the D-Link using wifi and ping 192.168.8.1 but I can't ssh to it or to anything beyond it from the laptop.
6. If I'm on the server (192.168.0.24) I can ssh into either 192.168.0.24 or 192.168.8.1 but not if I'm on the laptop. I conclude from this that ssh is not the problem but the laptop says ssh: connect to 192.168.8.1 port 22: connection refused.
So, am I conceptually confused or is it that I have to open ssh up to the other sub-net address spaces or something like that?
I am very new to linux.I have a network camera which only has an Ethernet port but no WiFi. Sadly no Ethernet port is available close to the camera.
Therefore I now bought a raspberry pi and installed raspbian to create a bridge into the wireless network, for connecting the camera to the internet.I now played around with the interface- and bridge configuration but I have problems with it.This is how my interfaces file looks like:
(The WiFi is secured with WPA2 Enterprise)
Code: Select all# interfaces(5) file used by ifup(8) and ifdown(8)
# Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d
The WiFi is connection works fine and I am in the internet using the WiFi.But I am wondering about eth0. The network parameters I specified are not the same as the parameters ifconfig tells me.Ip, Broadcast, Mask, nothing is as specified.It would be nice to give the camera a static IP that I can access it always with the same IP from the RaspberryPi.The Raspberry Pi itself gets always a new IP from the WiFi network. How do I get the camera into the internet using the existing connection of the Pi?
Setup a DNS/DHCP/Directory server on Debian? I would like to configure the things in Debian so that can join Linux and Windows(if possible as m not sure yet) clients to the directory server. Any links to setup both Forward and Reverse lookup zone in the environment.
I'm new to the forum and actually to Debian as well. Have been running Ubuntu for the past few years. Just setup a small Dell laptop to use as a Squeezebox and Print server. It's been up 6 days without a hitch as far as serving music to the squeezebox and printing. The problem is that it loses it's static IP, so as long as I look it up and change the radio Squeezebox and printer definitions around on the clients everything keeps working.
Does anyone have any ideas?If the connection drops for some reason and the system has to re-initialize the connection, shouldn't it use the /etc/network/interfaces file and get back to the static IP that it is configured for?If anyone has any ideas of why this could be happening or have a solution, I would really appreciate the help.
I just put a pfSense firewall inbetween my ADSL router and my LAN. It's configured to have a cachng DNS server and a DHCP server. Among other things. For reasons beyond this post the address range served by DHCP changed from 10.0.0.x to 192.168.1.x. The new DHCP server gives 192.168.1.1 as gateway and DNS server name and not the public IP addresses of our internet provider.
After reconnecting our client machines everything worked just fine on the win-xp boxes, but the Debian Squeeze servers and Ubuntu 10.4 clients all started to get network timeouts. If I ping public websites it works but browsing to the same servers fails. Other services like POP3 and IMAP also fails. All machines use WiFi to connect and the access point is the same as before.
What could it be that make the debian boxes fail? My laptop runs squeeze too and also fails. But when connecting to various other access points at hotels and such I do not get this problem.
Another weird thing is that the debian server running virtualbox cannot do things online but the virtual windows boxes running on this machine can. Weird! Where should I start looking? How is networking/dhcp clients on Debian different from Windows XP?
I'm running gnome desktop on squeeze system. When I boot my system seems to be using my internet modem as its dhcp server. The rest of the machines on my lan are correctly using my router for that purpose. As a result, what happens then is that my debian machine frequently gets a duplicate ip address assigned to it. I would like to specify to my debian computer that I want it to use the specific fixed ip address of my router for dhcp purposes.
A few months back I performed a routine aptitude upgrade on a Squeeze installation on a DELL Vostro desktop. My eth0 upload speed is now very bad although download speed is good. I suspect that it could be related to my other problem [URL] which was caused by the OS enabling noveau driver instead of the installed NVIDIA proprietary drivers.
Alright, I edited "/etc/default/isc-dhcp-server" and set "eth0" as the only thing listed for interfaces. I also have the code below in "/etc/dhcp/dhcp3/dhcpd.conf" and I even copied it to "/etc/dhcp/dhcpd.conf" for good measure, and I can't get the DHCP server to start. As an intermediate to advanced user, I am under the high assumption that it is broken since everything in the docs has been set. I have googled for two days and cannot find a fix, so before I report it as a broken package, would somebody with more experience with the package chime in?
I hid my wireless setup because it contains my WiFi network info including key. This box is routing, doing DNS resolution, and firewalling just fine. I just cannot get the friggin' DHCP server to start no matter what I try.
Oh, and is it safe to delete "/etc/dhcp" or "/etc/dhcp3"? They appear to be duplicates of each other...
Up until very recently I've had a wired network, and at boot I'd see messages about DHCPREQUEST and DHCPOFFER and stuff as it set up the wired network.
Now I've just got wireless working instead, but it still tries to use DHCP on the no-longer-existing wired network. So it says "DHCPDISCOVER on eth0..." and waits for a bit, then again and waits again, and all the time the boot is waiting for a reply to its DHCP requests and it's not going to get one. It doesn't seem to do any harm, because once it's given up and proceeded with the boot then the wireless does seem to work fine, but I'd like to speed up the boot a little by cutting out this needless waiting. Has anyone got an idea how I can stop it? I tried in Preferences-Network connections and in Administration-Network, and in System Tools-Network tools, and also from the network icon in the task bar, but I can't find anything which lets me configure the wired network eth0 or disable it or disable the DHCP.
I have some beginner questions about DHCP, Avahi, and configuring a small home LAN.Suppose I have a dynamic IP address assigned by my ISP, which requires DHCP be enabled in my dsl modem/router/"firewall" [sic]. Suppose for simplicity I have just one PC behind the dsl modem.I think "enabling DHCP" in the modem/router means that a DHCP client runs on the router, which communicates with a DHCP server run by my ISP when I boot up a PC on my LAN. Is that guess correct? Can I get DHCP to assign a particular local IP, say 192.168.1.10 (which is not the one taken by the router--- for this discussion, let's say that is 192.168.1.0) to my PC each time I boot it up?
Now suppose I want to build a stand-alone firewall, so that my LAN will have the firewall and the first PC behind the modem, with the first PC virtually behind the firewall. By default, I think these will both have DHCP clients running which I need to configure properly. The firewall should also have a DHCP server which should control how local IP addresses are assigned, correct? I should try to arrange that the LAN has only DHCP server, only one NTP timeserver, only one DNS nameserver, correct?My first PC seems to have installed an autorun client called Avahi, which performs DNS multicast services and incorporates something called zeroconf which seems to have something to do with remote desktops, which I don't need and which is a potential security hazard. But it seems that Avahi is an intrinsic part of the KDE desktop and cannot be removed. Just want to be sure that Avahi can coexist comfortably with dhcp3-client, which is also installed on that PC. They perform different tasks, correct?If I can get the stand-alone firewall to work, I know I need to turn off the commercial firewall in the dslmodem/router/firewall device. Should I purchase a bridge and try to turn off the routing function also?
I have a home Debian server running, and i would like to set it up as a gateway. I have 2 networkcards in it. So internet comes from the modem and on the other card i want to setup a dhcp server and it has to share the internet. But i want it also to connect to a vpn and share the internet of the vpn.. Is that possible?