Sponsored Content
Special Forums IP Networking my wireless usb adapter connect to net but the signal is very weak Post 302396373 by Corona688 on Thursday 18th of February 2010 09:11:27 AM
Old 02-18-2010
Okay, you even have an IP address so you seem to be able to talk to the router... How well we don't know yet.

It could potentially be an MTU problem. Try 'ifconfig wlan0 mtu 1364' and see if that helps.

If not, post the output of 'ping -c 4 192.168.1.1' so we can see how well your system can talk to the router. Then 'ping -c 4 66.82.4.8' to see if you can actually get through to the internet at all with it.
 

10 More Discussions You Might Find Interesting

1. IP Networking

strengthening wireless signal

How can I strengthen a 2.4 GHZ 802.11b wireless signal? (4 Replies)
Discussion started by: dangral
4 Replies

2. UNIX Desktop Questions & Answers

A recommended linux wireless usb adaptor

Hi guys, I've been a linux user for a day now and we are planning of moving from windows to gentoo. unfortunately were having a heck of a trouble in configuring linksys wusb adaptor on our linux box. we got so tired of looking for any linux drivers or ndiswrapper blah for these critters but... (1 Reply)
Discussion started by: 3rr0r_3rr0r
1 Replies

3. Linux

wireless USB

got a wireless usb network card. how can i make it work under redhat9?. it does not come with linux driver. (0 Replies)
Discussion started by: GJ2
0 Replies

4. Solaris

USB to Serial Adapter connection

Hi Community, I'm working on Sun Server V490 with my PC (with OS Vista). I'm using a USB to Serial Adapter to connect to Server directly. I've this problem, I'm connecting to Server with Putty client with this settings: boud rate 9600, 8 bit, 0 parity, 0 flow control, but after to have typed... (4 Replies)
Discussion started by: Sunb3
4 Replies

5. Solaris

Detecting wirelss USB Adapter

Hi, i try to plug in my USB wireless adapter to my sun solaris server. However, it cannot detect it. How do i set it so that it can detect it? (1 Reply)
Discussion started by: lkyow
1 Replies

6. Red Hat

Help reqd in installing wireless usb on fed 14

Hello all, I am fed up on trying to install my newly purchased usb wireless antenna to my fedora14 machine; so I seek help of all you linux masterminds out there. It worked well in my Win XP. Please help me in setting up it to my Fedora. . Details follows: The device model is : Aztech... (5 Replies)
Discussion started by: gsabarinath
5 Replies

7. Hardware

Configuring a D-Link DWA-130 Wireless Adapter

How do I configure my wireless adapter to access the internet? I am running PCLinuxOS 2010. (0 Replies)
Discussion started by: ryan352333
0 Replies

8. Red Hat

Cannot configure TL-WN727N wireless usb in centos 6.2

hi everybody, iam using 32 bit centos 6.2 on my machine. i have purchase TP-LINK, TL-WN727N wireless usb, but i was not able to install on my desktop. i was not able to find drivers for centos 6.2 official site of TPLINK. $ uname -a Linux workstation 2.6.32-220.el6.i686 #1 SMP Tue Dec 6... (0 Replies)
Discussion started by: paruhang
0 Replies

9. Hardware

Problematic RTL8188EE Wireless Network Adapter

Good Day All, There are numerous results when searching google on this issue, however, none seem to have a solution. I have read until my eyes bleed and banged my head on the table more than once! :) I am hoping to resolve this issue -- or at least have a decent workaround. It is a real... (13 Replies)
Discussion started by: RogerBaran
13 Replies

10. Ubuntu

Could not connect to wireless network

I run lubuntu from usb (try lubuntu, it's not install on my pc ) And i try to connect to network I see the network name And i put the pass But it's not connect.. I tried to open hot spot on my phone and try to connect and it's not connect I have edumax n150 Try to install new driver -... (0 Replies)
Discussion started by: popcoern
0 Replies
GRE(4)							   BSD Kernel Interfaces Manual 						    GRE(4)

NAME
gre -- encapsulating network device SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file: device gre Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_gre_load="YES" DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop. gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands. This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco routers. gre also supports Cisco WCCP protocol, both version 1 and version 2. The gre interfaces support a number of additional parameters to the ifconfig(8): grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option. enable_csum Enables checksum calculation for outgoing packets. enable_seq Enables use of sequence number field in the GRE header for outgoing packets. EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.* / / +------ the Internet ------+ Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal address 192.168.2.1, the following commands will configure the tunnel: On router A: ifconfig greN create ifconfig greN inet 192.168.1.1 192.168.2.1 ifconfig greN inet tunnel A B route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1 On router B: ifconfig greN create ifconfig greN inet 192.168.2.1 192.168.1.1 ifconfig greN inet tunnel B A route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1 NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8). For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop. The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero. SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8) A description of GRE encapsulation can be found in RFC 2784 and RFC 2890. AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org> Heiko W.Rupp <hwr@pilhuhn.de> BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as if they would belong to this interface. The sequence number field also used only for outgoing packets. BSD
November 7, 2014 BSD
All times are GMT -4. The time now is 04:48 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy