This is embarrassing. I can't get a wireless address from my router with dhclient. The distribution is sid/lxde/liquorix kernel with no network manager on /dev/sdb1.
root@sid:/home/jheaton5# dhclient -4 -v wlan0
Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
[code]....
i have the basic knowledge of networking. a week ago i installed debian Lenny version on an old pentium 3. in addition i installed a ddclient configured it according to many tutorials.i searched google a few days but didnt find my case. i ran the folowing command :
ddclient -daemon=0 -debug -verbose -noquiet
output:
debian:~# ddclient -daemon=0 -debug -verbose -noquiet
=== opt ====
opt{cache} : <undefined>
[Code]...
i installed ddclient before installing apache. the 10.0.0.10 address is the server address in my d link router behind NAT.
I have running Raspbian on my Raspberry Pi
I have two usb wifi dongles that both work and connect to my router when testing.
- Edimax EW-7811UN
- Adafruit Miniature WiFi (802.11b/g/n)
However when I try to change the Mac Address's of either of these usb devices when only one is plugged in and in use at one time I cannot do it as the effects seem to not take place.
I have tried using cmd
Code: Select all  ifconfig wlan0 down
  ifconfig wlan0 hw ether 00:00:11:11:00:00
  ifconfig wlan0 up
and also editing /etc/network/interfaces file wlan0 entry
Code: Select all  iface wlan0 inet static
      hwaddress ether 01:01:01:01:01:01
      address 192.168.1.100
      netmask 255.255.255.0
After doing this and running ifconfig I can see that either of the two USB'S device has the same MAC.
I have also tried rebooting the device but the mac address is the same.
I have heard there is a package called macchanger but I would like to do this without it, how could I go about doing this?
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).
[code]...
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?
From yesterday on, I am not able to connect my Laptop to my WiFi Router automatically when logging in to gnome desktop.
The following is the message found in /var/log/messages.
Its Lenny 5.0.4 and I can see my wifi LED ON till the gdm login page. After the login, while loading my desktop, the LED goes OFF and I have to restart the network-manager for enabling the wifi again. Why is this happening? Do I have to change the configuration settings in /etc/dbus-1/system.d/ to fix this. I really don't know what change needs to be done there and where.
The same day when this problem started while logging in I got an error message from nautilus. The screen-shot is attached with this mail. Does this error have anything to do with the network issue?
I've recently installed Debian. But the wireless network is not working. In Gnome it says "Device not configured" And if i try a ifup it says: root@accroft-msi:/home/accroft# ifup wlan0Internet Systems Consortium DHCP Client 4.1.1-P1Copyright 2004-2010 Internet Systems Consortium.All rights reserved.
Listening on LPF/wlan0/My mac address here
Sending on LPF/wlan0/My mac address here
Sending on Socket/fallback
[code]....
I'm having problems getting my wireless network working. The same problem exists in both Debian 5.04 and Ubuntu 8.04. I'm using a Sonet ZEW2500P USB wireless card, which shows up when I look at lsusb. The card works under Windows, so its not a hardware problem.
When I run iwconfig, wlan0 simply doesn't show up on the list. It doesn't go by any other name either. I've tried adding iface wlan0 inet dhcp auto wlan0 to my /etc/network/interfaces file, but to no effect. I've tried using both the rt2000usb driver and the old rt2570 driver, and made sure both are not loaded at the same time using lsmod, but this doesn't help.
I wanted to try the CONFIG_NET_RADIO enable/rebuild kernel technique, but I can't find CONFIG_NET_RADIO anywhere in my autoconf.h file!
I assume someone will want to see a log file of some kind - just let me know which one (and where I can find it).
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
[code]....
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?
I've installed firmware-iwlwifi I've modprobe -r'd and modprobed the iwlagn module I CAN scan, using iwlist wlan0 scanning, and I can see my essid, hovering in the distance. it is definitely broadcasting.
I use wicd and wicd-curses. No wireless show up in wicd-curses. ifup wlan0 gives me no dhcp offers received and slumbers again. from iwconfig:
wlan0 IEEE 802.11abgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
from lspci:
03:00.0 Network controller: Intel Corporation WiFi Link 5100
My setup: Debian Squeeze;4 physical partitions, 3 of those create 1 volume group, 13 logical volumes within that vg; 1 unencrypted(boot); all others encrypted including swap.As stated in the man crypttab:The order of records in crypttab is important because the init scripts sequentially iterate through crypttab doing their thing.
View 2 Replies View RelatedI have a firewall script setup to run in rc2.d. There is a K99 for it and then an S99. The problem however, is that it isn't being called. No errors, no logs, nothing. The symlinks in /etc/rc2.d point to /etc/init.d/script, but nothing ever happens on boot or shutdown. I can manually do /etc/init.d/script start and it will start just fine, including printing a line that it is starting. What's going on here? The permissions are the same as the other scripts in the init directory, so I doubt that is a problem.
View 4 Replies View RelatedI recently tried to install php5-gd package on my debian vmware server and it failed at libc6 - i386.
Afterwards every command other than CD caused a Segmentation fault and the server would no long boot, showing the following error
[ 4.808086] init[1]: segfault at 0 ip (null) sp bff4645c error 14 in init[8048000+8000]
[ 4.808372] Kernel panic - not syncing: Attempted to kill init!
[ 4.808442] Pid: 1, comm: init Not tainted 3.2.0-4-686-pae #1 Debian 3.2.65-1
i have this problem i install android sdk, and i install libreries: libstdc++5, lib32stdc++6, lib32ncurses5 and libstdl1.2-dev,
now if i use ldd comand don't have problem, but when i use eclipse and i compile a simple example (hello word example), i have this
error: [Emulator] SDL init failure, reason is: No available video device i have a notebook toshiba satellite A300-1RI whit ATI Radeon 3650, i install the amd driver and all work well.
I installed the latest Debian on a computer to make a backup appliance. No GUI.When the computer starts, everything is okay. The DHCP client is running, the network interface have an address, fine.If I do a /etc/init.d/network restart (or stop + start), no more DHCP client. t is stopped when the interface is down. When the interface is up, I have to start it manually.1 - is it normal ?2 - isn't ifup's job to launch the dhcp client ?3 - can /etc/network/if-up.d be the right place to resolve this ?
View 4 Replies View RelatedI'm trying to make a script that loads at boot and asks for user input before doing it's stuff. So I created a script in /etc/init.d/ following the example given there (skeleton file) and used update-rc.d to make it load before GDM.
But when my script requests user input, init doesn't stop, and goes on loading other services and loads GDM. I have to CTRL+F1 to get to my script. I want my script to pause the init system till it ends doing it's stuff and the the other services can go on loading.
I tried
#X-interactive: true to no avail.
I haven't been active in Debian for two years back when Lenny was still in 'testing' and noticed that for some reason it is no longer protocol to restart network services using the 'init.d' scripts. I also noticed the same for Ubuntu (which I don't use or could care about) and am trying to understand what is the correct way now for Debian and what changed? I did a search on Google but didn't turn up any results. Is it no longer correct to run:
Code:
/etc/init.d/network restart
I am tring to get my linksys wireless router to connect to my laptop that i recently installed Fedora 10 on. Well it is actully running of an external HD. Any way when i boot in windows it connects and works fine, but when i try to activate wlan0 it says "Cannot activate network divice wlan0!" "determining IP info failed..."
View 11 Replies View RelatedRecently, I've set up Ubuntu Server 9.10 x86_64 (no GUI). I have two NIC cards in this machine. One is a wireless card that I would like to set a static IP address to. The other is an integrated NIC. Everything works just fine when I have everything set up under DHCP. I can ping both NIC cards with no issues. But as soon as I change over to a static setting, things work unexpectedly...
Things to keep in mind:
-All machines are running under the same subnet
-All machines are connected to a wireless router (freshly flashed with the latest firmware)
-This is a fresh install of Ubuntu Server 9.10 x86_64
--Static IP address on the WIRED (eth0) NIC works great. No issues. Can ping from my wireless laptop, and can ping from the machine to the outside world (ping google.com) as well as the gateway itself with excellent response times.
If I then turn on the WIRESLESS (wlan0) NIC after setting up a static address for it in /etc/network/interfaces, then turning the wlan0 on by issuing "sudo ifconfig wlan0 up", wlan0 shows up, but does not have an IP address associated with it, even though I set it up as static. I also cannot ping wlan0 from my laptop. I assumed that was because I needed to restart the networking service. So after issuing "sudo /etc/init.d/networking restart", I am able to ping wlan0 from my laptop with no issues.
Here is where things get strange. Lets say that I physically pull the plug on eth0. After dong this, wlan0 stops responding to the ping request that was initiated by my laptop at the same exact time. If I plug the cable back in, both eth0 and wlan0 begin to respond once again. But soon after I try to SSH to wlan0, wlan0 decides that it no longer wants to respond to the ping. I should note that it does ask me for a username and a password, but after I entered my password, the ping stops responding. Why should the wlan0 be affected in any way if something happens to eth0?
This all started when I set the server up with only a static configuration on wlan0. It appeared to be working well. I was able to ping the machine from my laptop as well as SSH into the machine. I went to bed and the next morning, I was no longer able to ping the machine. I let the ping run for a small amount of time with a few responses here and there. Then after a little more time of letting ping run, it tends to respond. Almost like I bothered it enough to decide that it was appropriate to start working again.
Ideally, I would like to have ONLY a wireless connection. But if I need to have eth0 up, it would be great to have option work as well. Bottom line is that my wireless is flukey. And I would like to find out why.
change my WLAN0 MAC address in my Kubuntu Natty 64 bit at every boot. I have done quite a bit of searching and found some procedures that appear to have worked back in 9.04 and before days but I have been unable to get anything to work for me in my 11.04 install. I have tried adding a script to if.pre-up.d and also tried adding a bootmisc.sh and either I did them wrong or they are not working. I want to make sure that every time I bring the wireless up in Kubuntu that I have the changed MAC address. I usually keep wireless disabled and turn it on just when I need it.
Background so you don't think I am doing something nefarious... I am going on a cruise soon. The cruise line sells wireless internet subscriptions for the duration of the cruise but they tie it to a MAC address. I am bringing my CDMA android phone that unless I use VOIP will be unable to call at all or at least with very high charges. But I also want to be able to browse the internet with my laptop. I figure it will be easier to spoof my phones MAC with the PC than the other way around. I just need to turn one device off if I am using the other. I need the MAC address to be semi permanent so I don't turn it on by mistake and have forgotten to change the MAC.
I installed squeeze on virtualbox on arch linux.After squeeze is booted up, ifconfig says no ip address is given to eth0.I tried ifdown/up eth0, then an ip address was properly given.Does anyone have the same problem or know how to solve this?The network of virtualbox is set to bridged adapter.The host os has only eth0, no br0 and wiredly connected to a wifi router which has the dhcpd.
View 4 Replies View Relatedbrand new Squeeze box built toady - I'm trying to install a init script and I want it to start last and only in runlevel 2...
The script "test" is executable and located in /etc/init.d
so I run update-rc.d -f test start 2 95 - I expect /etc/rc2.d/S95test but instead get S01test
On my Lenny boxes symlinks in /etc/rc2.d are in the S10 - S99 range but the Squeeze box has the same services in the S01-S06 range?
Did something change in Squeeze?
I also tried creating the symlinks in rc2.d manually but the script never ran...
I got the Raspberry pi 2 Model B. I flashed my sdcard with raspberian Jessie kernel 4.1 (latest).Also tried wheezy and NOOBS, same behavior.With a ethernet cable (known working), I tried connecting my Pi to my home router, and I got a invalid ip address 169.254.xxx.xxx, and therefore no linkup. I got the same results by connecting my Pi directly to my modem (wired).
I know that /etc/dhcpd.conf is the new /etc/network/interfaces for network configurations.So I tried the debug option, and I noticed that the router doesn't seems to response to the DISCOVER command from the Pi (dhcp v4 protocol).Here's a dump of by /var/log/syslog | grep dhcp
Code: Select allDec 28 12:00:02 raspberrypi systemd[1]: Starting dhcpcd on all interfaces...
Dec 28 12:00:02 raspberrypi dhcpcd[349]: version 6.7.1 starting
Dec 28 12:00:02 raspberrypi dhcpcd[349]: udev: starting
Dec 28 12:00:02 raspberrypi dhcpcd[349]: dev: loaded udev
Dec 28 12:00:02 raspberrypi dhcpcd[349]: eth0: disabling kernel IPv6 RA support
[code]...
ANd if i use raspbian flesh out of installation, I get this when i run
dhcpcd -k
dhcpcd eth0
eth0: probing for an IPv4ALL address
eth0: using IPv4ALL address 169.154.202.224
Seems like my home router TP-link (default setup) doesn't send a response to the dhcp request.
Is there any elegant (and preferably uniform) way to determine IP address assigned to a DHCP/PPP interface inside a post-up command?
View 2 Replies View RelatedMy sources list for updates is a bit wonky as in needs the correct uk repositories listed, for Lenny main, could someone point me to where I can find the uk repositories so I can enter then in the software sources option from the menu?
View 2 Replies View RelatedI'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.
View 9 Replies View RelatedGot this while installing the kernel development tools on my Squeeze system being used as a router/firewall. Setting up update-inetd (4.36) ... Setting up cvs (1:1.12.13-12) ... Ignoring install-info called from maintainer script The package cvs should be rebuilt with new debhelper to get trigger support Ignoring install-info called from maintainer script The package cvs should be rebuilt with new debhelper to get trigger support Setting up autopoint (0.17-11) ...
Is that an issue that I need to address prior to building the latest kernel (2.6.33.4)?
Hey guys. I have a client computer PXE booting from my host computer and it is supposed to give the client the ip address 172.16.0.100 however instead it gives it the ip address 172.16.0.208.
I have this set up working with two other computers and there is no noticeable difference other than mac addresses for the network card.
Here is an extract from my '/etc/dhcp3/dhcpd.conf' file...
ddns-update-style-none;
option domain-name "example.org";
default-lease-time 600;
max-lease-time 7200;
[Code]....
I have quadruple checked the mac address of the client and it is definitely "00:07:E9:32:16:81" so why is it not giving it the IP address that I have specified?
I have a Debian VM on Windows that is not getting an IP address assigned by the DHCP. I tried, ifdown eth0 and then ifup eth0 and still no IP address. my interfaces file looks like this:
# 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
[code]....
I want to configure multiple virtual ethernet interfaces over a single physical ethernet interface (eth0) and for each virtual interface the MAC address must be unique and the IP address must be Static.Finally all the virtual interfaces must be able to communicate both internally and externally and the traffic should be captured using wireshark.
I need to have such kind of setup to communicate devices individually using one physical ethernet device.
Because I was fiddling with few kernel modules like MACVLAN and MACVTAP and successfully enabled those modules and rebuild kernel. Using macvlan and macvtap I can configure virtual interfaces with unique mac address and static IPs but while capturing packets using wireshark interfaces behave weirdly.
For example say on HOST machine I have 1 physical interface and created 3 virtual interfaces as shown below.
Interfaces :
eth0 (physical ethernet interface)
IP: 192.168.A.A
MAC: aa:aa:aa:aa:aa:aa
[Code] ....
First from above interfaces I started pinging eth0 internally from host machine in which it worked as usually.
Second I did same externally from other machine which is connected to the same network of Host machine, and this did work as usually.
Third I pinged first virtual interface veth0 both internally and externally and this also works and after that I did check source and destination MAC address using wireshark tool-where both showed up there respective MAC address.
Now triggers the issue, where I pinged second virtual interface same like I did for first one, but this time ping was success and where as in wireshark tool the MAC address for veth0 is picked by veth1. This is where I got stuck and this issue happened for all the remaining virtual interfaces.
I couldn't see any virtual interface showing their respective MAC address, as of the remaining except the first virtual interface has been picking the first veth0 mac address.
I have Debian 8.2 with KDE 4.14 and everything runs perfect, except for the internet connection. This problem happens randomly when I turn on my machine. Sometimes when the desktop loads, the connection is already settled.
But sometimes when the desktop loads, the wifi icon is still loading and keeps stuck at "setting network address". Since this problem happens randomly I really don't know what is happening here. My wifi chip is this:
Code: Select all01:00.0 Network controller: Intel Corporation Centrino Wireless-N 130 (rev 34)
This is the problem:
I installed Debian with non-free firmware because of this chip.