If I comment those off then no such problem, hence some how ppp0 executed automatically and there is no [auto ppp0] any where. How can I stop this forcefully ?
Suppose I have both a hardwired and a wireless network connection active on the same system at the same time. Can I tell my browser which one to use? Can I tell other programs which one to use? Or do they choose for themselves> Or does some automatic system protocol select which one to use for them?
I was just wondering if there's any point having both auto and allow-hotplug against the same interface in network/interfaces as allow-hotplug seems to bring an interface up at boot on its own.
I'm trying to use network-manager in sid and it's incredibly frustrating because every 2 minutes or so it seems to scan for wireless access points, during which time my SSH connections completely hang and screw up. Pings start dropping packets as well. By doing an "iwlist scan" I can reproduce the behavior. Has anyone else dealt with this? I haven't been using network-manager, but I am currently due to mobility and needed VPN functionality... WICD with no network-manager works better but there's no gui-based VPN support. I've got an Atheros wireless device and I've read that supposedly it should be doing background scanning since kernel 2.6.32, but I haven't seen anything like that, and I'm on 2.6.32-5-amd64 currently, 2.6.32-3-amd64 behaves the same too.
I have Debian Squeeze AMD64 bit release. It finds my wired ethernet connection and ues itfine, although nothing shows up in the top right corner under the networking icon.
When I plug my mobile phone in (HTC S620) it always uses this as the main internet connection and then even if disconnected wont use my wired connection until I reboot.
Is there a way to stop it doing this or at least have my wired connction as an option so I can just click to reconnect to my ethernet connection?
I press On-button, Debian boots, logs in and automatically connects to the Wireless network AND! to my local pc via LAN. It runs an ssh server, so I can ssh into debian over internet and communicate with the local pc (send a magic packet).Here are my problems:
1) I don't how to log in automatically. This and this doesn't work. 2) I need a network tool that can manage multiple connections and has a reconnect feature. With the default network manager I cannot even connect to more than one network simultaneously although I have two network devices of course.
And I guess I can run all that in console mode, right?
Alright, first Squeeze wouldn't create an initial RAM disk even with "--initrd" specified. Now I don't need one and it's creating one for me even though I don't want one! How do I stop this? I'm beginning to feel like I am using Windows in the sense that it's doing things on its own. Don't make me a RAM disk unless I say so!
i would like to prevent all users other than the user "parker" on my system from using the su or sudo commands. I have not attempted to modify the sudoers file so it just contains the standard root ALL = (ALL) ALL.
I have a PC that have a new Ethernet card that is not yet supported by Debian/Lenny.I downloaded the latests driver from the manufacturer and after a make;make install everything works like a charm.My problem is that one day after a probable update, Debian overrided my new driver by an other one causing my Ethernet card to shut down.After an other make install, everything work again like it should..But how do i do to prevent Debian to update my driver ?
I have a little problem with my Linux Suse 11.2 Server. I have unused network card with one port, and one with 4 ports and two used ports.
so-> eth1 is connected to a dsl-modem eth2 is connected to a switch
i want my suse server to route between modem and switch.
Somehow, I can't go in the internet via eth1. I have to create a bridge br0 to go in the internet. very strange, when i delete the bridge and set eth1 as primary device, i have no internet.
How can i route from eth2 (10.x.x.x) to (eth1 or br0 (80.109.145.x) to Modem (80.109.145.1)?
This past Friday as I was performing regular maintenance on my RHEL / CentOS servers, I ran yum upgrades on them and when they rebooted, I realized there were network issues and I could not longer access them via Ping or SSH. When I jumped on the console, I realized that it created a new 'ifcfg-eth0' file with none of my static information & the old 'ifcfg-eth0' file with all my static info had been renamed to 'ifcfg-eth0.bak'. It appears that the MAC address on the new file and the old .bak file are different and I have no idea why. I have no changed or altered anything on the server.
I'm trying to prevent GDM/Gnome from turning the screen off prior to login. It's current behavior, under 3.14, slowly fades the screen out and then enters DPMS mode after 10 minutes.I have zeroed out the following dconf settings, under both root and user, but the default behavior persists.
For Ubuntu 10.04, I can configure the network by "Network Connections". This configuration is done by doing the following operation sequences(System->Preferences->Network Connections->wired->auto eth0). Then I can connect to and browse the internet. If I type the command "ifconfig", I can see the ip I configured for eth0. Part of the content is as blow:
[Code]...
I think there should be other files that keep the eth0 configuration content. What are they?
I've got this old IBM thinkpad which has 128mb of ram, and I'm trying to configure a small mini.iso minimized ubuntu distro set up on it. From here: [URL] During the instillation, it requires that I connect to the internet to install and choose packages, the problem is the auto configuration always fails. I plugged in via Ethernet, but I'm still not exactly sure how to get it working.
Config: Squeeze, 2.6.32-5-amd64I just installed squeeze and the network is up and nm-manager deamon if working but the Gnome applet doesn't seem to work as usual. It indicates no network although the network is available as indicated by ifconfig and route below. When I switch WiFi on, the nm works flawlessly. When I click on the applet icon it says "Wired Network: device not supported" (or similar, msg in french is
I have b43 wireless. In network Configuration on system->administration the interface it appears as inactive it appers in hardware also as b43 associated to wlan0 but i cannot have access to any wireless network. What i have to do to put this b43 to work.
I'm renting a server which comes with 5 IP addresses, but only one network device. From what I can understand I'm able to create aliases by adding entries to /etc/networks/interfaces, I haven't tried I'm in the planning stages. Hypothetically, 192.168.22.30 is my primary IP and I want to set eth0:1 to have 192.168.22.31, and then after that I want to create a virtual machine (using kvm/qemu) that is able to communicate bidirectionally to the internet over eth0:1, and leave eth0 strictly for administrating (not for VM traffic).
The qemu guides I'm finding seem to assume that I want to use TAP or VDE, what I want to use is a sub-ip/alias. One guide I saw had me eliminate everything from eth0 and put it under br0. That would leave me unable to ssh into my server (and unable to administrate). Is there a way I can do something along the lines of: qemu [options] -net [option] -netdev=eth0:1 ?
Is is possible, via iptables or something similar, to bind a service running on a specific port to a specific interface? My case: I use a VPN service for privacy. I would like to have all traffic except ftp and ssh to run over tun0. Ports 21 and 22 will need to be accessible to the outside world (eth0) while the VPN is running.
The apt-get autoremove command, I use Debian 8 for some time now and I often install a package, test it for some minutes and remove it then. I noticed that in most cases (if not all, I'm not completely sure) all the dependencies that were installed with the package (mostly libraries, of course) stay installed on the system when I remove the package.
And there is no output of apt-get that there are unnecessary pacakges which I can remove with apt-get autoremove. The autoremove command does nothing.Before I changed to Debian, I used Ubuntu and there all the dependencies are removed with apt-get autoremove when I uninstalled a package.My question is now, is this normal? if there are fundamental differences in which packages "autoremove" removes between Debian and Ubuntu?
I have a "time-server". It's sending time to different devices through different ports/protocols. The problem is that it has no operator and that makes some extra difficulties.
Now when i try to start it using terminal Code: Select allsudo ./myprogram works fine and
Code: Select all./myprogram doesn't work.
It is so because without sudo i have no access to ports. As a result If i add my program to System->Preferences->Startup Applications it has the same problem. So i need to start it as root, auto-start, right after auto-login to system but without entering password cause nobody will do it.
Also I need to start ntpd but it also asks password sometimes I've tried googles but it offer a few ways with entering password that isn't suitable for me or writing some scripts/changing system files but with no example I'm afraid to break it all. So is there a way to start Myprogram and NTPD as root with no password entering?
My system is Debian 6.0.10 Squeeze, Kernel 2.6.32-5-686
I can use this at the end of bash_profile to autorun start x after logging on. code...
But what about to auto logout after killing the X session? I hit exit from fluxbox, but I could add a menu item I suppose to just kill the xsession. Wondering if there is a graceful way to do it with bash_profile.
Also, on a related note, if I switch to dash with the bash_profile method still work?
After updating and subsequently restarting today, I can no longer bring up my wireless interface:
ifup wlan0 SIOCSIFFLAGS: Unknown error 132 Could not set interface 'wlan0' UP SIOCSIFFLAGS: Unknown error 132 SIOCSIFFLAGS: Unknown error 132 Failed to bring up wlan0
iwconfig lo no wireless extensions. eth0 no wireless extensions.
wlan0IEEE 802.11abg ESSID: off/any Mode: Managed Access Point: Not-AssociatedTx-Power=off Retry long limit:7RTS thr: offFragment thr:off Encryption key:off Power Management:off
After installing Jessie, apt-get gives me a huge list of packages with the suggestion to autoremove them. Now, I've tried auto-remove once and was left with a naked Gnome, so I was wondering if there's another way to find out which packages I should keep and which I can safely remove. Is it safe to delete packages that cannot be found using the search function for the stable release? I checked them one by one here URL....How about linux images that won't appear in the above search?
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'm working on embedded debian. I do configuration to lightdm for autologin. My device start with autologin but sometimes I see login screen. ı will try it more than 20 times. 17 times its do autologin 3 times not do autologin and show login screen.