Sponsored Content
Full Discussion: Wireless network not working
Operating Systems Linux Ubuntu Wireless network not working Post 302607878 by Corona688 on Thursday 15th of March 2012 02:23:29 PM
Old 03-15-2012
What do ifconfig and iwconfig show?

Can you ping anything? Your wireless router, for instance? ping -c 4 192.168.x.x where you should substitute your router's ip address for 192.168.x.x
 

9 More Discussions You Might Find Interesting

1. Cybersecurity

Wireless Network

At the moment, I have three computers at home. I want to use boardband for my three computers. But I don't want to use network at home. I have been looking for a product which call OriNoCo USB Cilent. How do I connect to the internet with my computer?? If I post this in a wrong place, please... (0 Replies)
Discussion started by: him
0 Replies

2. IP Networking

Wireless-G network

Hi, I have a laptop with a Linksys Wireless G PCMCIA card and a cable connection goin into a router and then a patch lead from the router going to a Linksys Wireless G access point IP 192.168.1.245 with DHCP disabled. I can connect to the access point from the laptop, but how do I get the... (1 Reply)
Discussion started by: perleo
1 Replies

3. UNIX for Dummies Questions & Answers

solaris 10 wireless network setup

I installed solaris 10 x86 on my dell laptop on a partition alongside windows xp. I am able to connect to the internet in xp with both my ethernet local area connection as well as through my wireless network card. But, however i do not have clue as to how to go about it in solaris. i did not... (0 Replies)
Discussion started by: stakes20
0 Replies

4. Linux

Wireless network card performance

I am running FC4: Linux maincomp 2.6.13-1.1532_FC4smp I recently changed the OS from windows XP, and have a feeling that for some reason my wireless network card is slower on Fedora Core 4. The Belkin PCI 802.11b card was automatically detected and configured by FC4 when I installed the OS,... (0 Replies)
Discussion started by: dangral
0 Replies

5. UNIX for Dummies Questions & Answers

Wireless network programming in Unix (question)

Greetings everyone, I've been using OpenWRT for some time primarly for research in the University. I've also started with some basic network programming (sending UDP packets for instance). But since most of the available tutorials on unix network programming are more related to ethernet... (4 Replies)
Discussion started by: aztroboy
4 Replies

6. Hardware

identify wireless network card

hi Howto identify wireless network card using Live CD? (2 Replies)
Discussion started by: ccc
2 Replies

7. Red Hat

[SOLVED] Wireless Network Setup

Hi, I am trying to set up a wireless internet connection on my centos OS (6). I can connect via the copper using the internal LAN but cannot get the wireless connection working. The 2 files that I have configured are: My wpa_supplicant.conf: ctrl_interface=/var/run/wpa_supplicant... (1 Reply)
Discussion started by: Duffs22
1 Replies

8. Android

Problem with wireless network

Good day, everybody! I have a mobile phone (LG Optimus L5) with Android 4.0.3 and a tablet (PocketBook SurfPad 2) with Android 4.1.1 and I have problem with wireless network on these devices. Laptops don't have such problem. My wireless network organisation is a modem connected with an access point... (11 Replies)
Discussion started by: qzxcvbnm
11 Replies

9. 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 07:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy