My laptop is Gateway M-6335 and I have problems with wireless drivers. I couldn't find any drivers for it. I searched in Software Centre and tried to google it but it didn't work. I have also problems with Bluetooth driver, but it's an other story. I'm using Ubuntu 10.10.
I am new in using Debian 5.0, my wireless doesn't work I make a search to know how to do it. So I open "Terminal" $ su (press enter) I wrote the pwd than when I wrote : # gedit/etc/apt/sources.list I found this: bash: gedit/etc/apt/sources.list: No such file or directory
I didn't know what to do, I proceed with: # apt-get install ipw3945 modules-$(uname-r) ipw3945d firmware-ip3945 bash: uname-r: command not found Reading package lists... Done Building dependency tree Reading state information... Done E: Couldn't find package ipw3945
i am wanting to turn my Debian box into a wireless AP, but for some unknown reason the wireless card won't switch into master mode when i run the command #iwconfig wlan1 mode master i get this Error for wireless request "Set Mode" (8B06): SET failed on device wlan1 ; Invalid argument. what does this mean and what do i need to configure/install to get it to work my wirless card is supported i checked it's a zydas chipset using the zd1211rw driver SMC EZ Connect SMCWUSB-G [URL]
I used to have an Ubuntu-Windows partition, but (what do you know?) Windows Crashed, and wouldn't boot anymore. So I reinstalled Windows, deleting my Ubuntu partition. Instead of reinstalling Ubuntu afterwards, I decided to give Debian a try. So here I am. I can't find drivers for my wireless network however, and it's quite annoying to have to plug in the Wired Connection with which I am writing this.
My main specs are: Sony Vaio VGN-CS390J Debian 5.04 AMd64
I have recently installed the intel-wireless-tools and now my laptop detects my wireless router and connects to it but when I go into a browser I can access the internet. If I connect to the wired network no problems(same router) no go on Wireless.
I am completely new to linux in any flavour. I installed ubuntu 10.4.1 64-bit on my Gateway NV59 laptop as a dual boot with Windows 7. The installation went just fine. When it comes to networking, I can connect to my home network when wired directly, wireless is another matter. I can connect wireless in windows just fine, so the card is physically fine.
My set up is as follows: Gateway NV59 laptop with Atheros AR928X PCI-E wireless adapter Linksys WRT54G router using WPA2 Personal and a class C address scheme (192.168.x.x) (If anyone thinks it would be necessary to post actual hardware specs of the laptop, I can, but don't think it really necessary). I have followed the Wifi Wireless Troubleshooting Guide found at [URL].
When connecting to my network wirelessly, I click the icon in the top right, and choose "Create New Wireless Network". When I input my settings (SSID - not broadcast, and security type and key - WPA), it then states I am connected under the "Wireless Networks" section found in that menu, and shows my network name with a strong signal and a computer/monitor icon. When I double-click the icon, it tells me I am connected and that the connection is active, yet the actual wireless icon on the top bar is grey, not white, and has a red exclamation mark on it. According to the steps in the troubleshooting guide, my wireless card is recognized and installed, with a driver of ath9k.
When I run lsmod, the driver is listed, therefore loaded, and ndiswrapper is NOT listed. I have verified that the driver is communicating with the kernel. When I scan for my router, it is listed under Cell 04, with the correct SSID and hardware address. There do not appear to be multiple drivers loaded, and my wifi is NOT disabled. When I check to see if I'm associated with a router, iwconfig shows my network ssid under wlan0, with the correct hardware address listed under Cell:, yet I cannot ping my router's internal ip address. At this point, I ran ifconfig, and for some reason, my wireless card has been given a class A address of 10.42.43.1.
When I try to assign an ip address via dhcp, DHCPDISCOVER runs for a number of intervals and then tells me "No DHCPOFFERS received", yet my router is using dhcp to assign ips with a pool of 50, more than enough ips for all the hardware in my network. When I run the command "sudo invoke-rc.d networking restart", I get the statement "Ignoring unknown interface wlan0=wlan0" - not sure what that means, but doesn't sound good to me, and retrying to accquire an ip address through dhcp still does not work. If I attempt to assign an ip address within my network range manually, I first run the command "sudo ifconfig wlan0 down", then just out of curiosity to see if the interface is really down.
I run ifconfig again, and wlan0 is no longer listed, but now there is eth0 (my regular ethernet interface) with no ip address. AND another interface is listed - eth0:avahi with the same hardware address as eth0, and an address of 169.254.4.42 - this seems to be the default address the OS will assign when it cannot get one via dhcp, but I have no idea why it has shown up as eth0::avahi... Anyway, after entering the command "sudo ifconfig ip addr 192.168.x.x netmask 255.255.255.0 broadcast 192.168.x.255 up" with the appropriate addresses, I receive the error "addr: Unknown host".
What I have NOT tried, are the following steps: 1. Change my router to an open signal (I would prefer not to do this, but will, if it is absolutely necessary for troubleshooting) 2. Try gtk wifi, or wifi radar 3. Try booting with kernel option pci=noacpi or acpi=off (not entirely sure how to do this just yet) 4. Try wpa supplicant (not sure what this is, just noted it was in the troubleshooting guide)
after a reboot of my Lenny system, the default gateway will lost. Then i must try "networking restart" and the gatway will be set
my interfaces looks :
# 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 am trying to manually configure my wireless interface similar to how I manually configure my wired interfaces on Ubuntu 10.10 (Maverick Meerkat). I have two wired interfaces that use static IP addresses. I set up these interfaces using /etc/network/interface file. I disabled network manager (it was never working correctly to start with). Now, I want to connect my wireless interface (wlan0) to an unsecured wireless private network. I know/can find out all the information about the wireless network (ssid, etc). Also, I need to do this without disconnecting either of my wired interfaces.
I have looked all over the internet/forums for information about how to set up this interface, but nothing I found meets my need. Is there any way I can use iwconfig or the interface file to connect to this wireless connection? Or is there any other tool that will allow me to manually do this?
I installed Debian 5.04. The Debian installer picked the Ethernet card but not the wireless (Atheros 9285). I followed these instructions to install it (found at [URL]...
But there was no wireless interface shown in the network interfaces entry of hardinfo, even though I wrote modprobe ath_pci in terminal window. My questions are: 1. I followed the instructions regarding updating the madwifi sources, installing them etc. Does this guarantee that apt downloaded and installed the right madwifi driver? 2. Will I be better off if I try to install the driver downloaded from the Atheros website? 3. How can I activate the wireless interface (since the driver is running should not the wireless interface somehow show up automatically)? 4. When I am running Ubuntu 9.10 it picks up the wireless. Can I somehow copy all the files for the wireless from Ubuntu and paste them in the Debian filesystem?
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 switched my girlfriend laptop from windows 7 to Kubuntu 9.4, then upgraded to karmic koala. I was able to, through the hardware manager, install a software modem driver, and a firmware unwrapper driver for her broadcom 4.X series wireless adapter. Whenever I attempted to install the broadcom 4.1, 4.2. ect driver itself a package update would fail, but wireless functionality still worked nonetheless. My girlfriend has a TX1000 HP laptop, similar to this one:[URL]..Product number in the bios is GA648UA#ABA System Board ID is 30BF
The wireless drivers she needs are proprietary. This worked for a while, although seemingly at random her wireless would go out, and her analog sound driver for her Nvidia chipsets would too. Usually logging out of the KDE environment and back in fixed the issue. Now wireless is completely gone; using a hard ethernet core to the router still works. Even connected to the internet, the proprietary drivers that used to be available in the hardware manager aren't there anymore. Right before the driver disappeared, I updated the system with all the latest round of updates, and installed the base package and some plugins for VLC. I don't know how to role back packages to see if an update killed the wireless, I uninstalled the VLC software but that didn't help.
Wireless is checked enabled on my taskbar, and I have checked my bios and haven't found any setting to disable the wireless adapter. Anything networking related has been enabled. At this point I am rather frustrated with the stability of Kubuntu overall and would prefer a hard solution that will permanently fix the problem.
Why isn't my laptop's wired ethernet not showing? I have a Toshiba Satellite PSAG8U-04001W.
The installation of Debian wasn't originally on this system: it was on an older laptop whose motherboard fried, so I rescued the hard drive as well as the Debian installation. However, I doubt this should have anything to do with lspci not even detecting the wired eth controller.
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.
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 am using debain 6 and using a Sierra modem c888 to connect internet. I am using wvdial package for connecting the modem. I am able to connect internet. The question I have is, how do get the gateway address of the newly created ppp0 interface?
Im trying to achieve the multiple uplinks/provider found on LARTC.org. I have to get the IP addresses from my interfaces (EF1 and EF2) by using a script, but i dont know where to look at for the default gateway from each interface which got their ip address from my ISP.
I am having some troubles using iptable rules on two Servers that act as Gateways pointed to one backend server with only one interface.
To be more exact, i have 3 Servers, 2 of those have a public and a private interface, with different public ips but common private interface ( they connect to the same switch ), the last one only has 1 private interface and is connected to that same switch.
Those 2 servers also act as a gateway and a firewall for the private network.
My problem is that i cannot seem able to route traffic from both of those to the third one and back to the same public ip that the request came from ( effectivly using two gateways on the machine with only one interface ).
As a testing scenario i am using ferm for applying iptable rules that forward ssh traffic ( for example ) to the backend server, and it works well when i do it with one gateway.
When i apply something like this in /etc/network/interfaces on the backend server though:
Even though forcing selection of an interface from the backend server ( like curl --interface ) seems to work well, meaning that the request to the curl appear to happen from the correct public ip, i can still only use one of the public ips to access the server with the ferm rules. Ideally i should be able to ssh to the backend server from both public ips using their ferm rules for forwarding traffic to the backend server.
I feel like i am missing some details on routing that should happen on the firewalls as the backend server seems to be able to use both gateways to access the internet and receive replies from it.
I am running Debian Squeeze on an old pc (AMD K62-500) which serves as my multiwan router and torrent box. Internet uplink is provided via a dsl line and 2 wireless canopy modules.
Setup has been generally fine except when connecting/downloading as free user from sites like rapidshare, hotfile, filesonic, etc. The problem arises when I am connected to these sites using the wireless uplinks because of the shared public ip. I don't really download that much using direct download methods so I don't really see myself being a premium user from these sites.
If these sites are on a specific ip or ip range, an entry on the static routing table would have been fine but when I tried using ping, a different ip would appear to reply each time.
I wonder if there can be a solution like using iptables where in traffic to and from these sites will only use the NIC connected to the dsl line.
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.
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.