Sponsored Content
Operating Systems BSD FreeBSD - Wireles Ad-hoc Networking with IP alias Post 302531548 by Govindaraj on Friday 17th of June 2011 06:52:56 AM
Old 06-17-2011
FreeBSD - Wireles Ad-hoc Networking with IP alias

Hello Friends,
I'm a newbie to FreeBSD. Trying to implement a IEEE paper : Energy consumption models for ad-hoc terminals (Computers).

The test setup with 3 Computers & Wireless NIC goes as follows:

Transmitter (A) --------------- Forwarder (B) -------------- Receiver (C)
10.0.1.1/24 ------- 10.0.1.2/24 (10.0.2.2/24) ---------- 10.0.2.1/24

Here Laptop B acts as a forwarder. It has 1 wireless NIC. I use ip alias to create a virtual NIC to forward the data to receiver. But the Laptop B is not forwarding the packet.

My /etc.rc.conf file is as follows:

Laptop A (Transmitter):

Code:
wlans_ath0="wlan0"
create_args_wlan0="wlanmode adhoc"
ifconfig_wlan0="inet 10.0.1.1 netmask 255.255.255.0 ssid energy"

Laptop B (Forwarder):

Code:
wlans_ath0="wlan0"
create_args_wlan0="wlanmode adhoc"
ifconfig_wlan0="inet 10.0.1.1 netmask 255.255.255.0 ssid energy"
ifconfig_wlan0_alias0="inet 10.0.2.2  netmask 255.255.255.0 ssid energy"


Laptop C (Receiver):

Code:
wlans_ath0="wlan0"
create_args_wlan0="wlanmode adhoc"
ifconfig_wlan0="inet 10.0.2.1 netmask 255.255.255.0 ssid energy"

Can some one help me, why the Laptop B is not forwarding the packets? Thanks in advance.

Last edited by pludi; 06-17-2011 at 07:58 AM..
 

6 More Discussions You Might Find Interesting

1. IP Networking

Wireles Lan in SunOS 10???

Hi, i´d like to know is if posible to configure a Wireless Lan in Sun OS 10.0?? I´m trying but no results... Please, how could i get internet acess using a Wireless Lan or a sample lan, whith IP protocol? Maybe my Wireles Card Lan don´t has support driver for UNIX(DLINK 520+PCI Adapter), but... (1 Reply)
Discussion started by: marpin
1 Replies

2. Solaris

Wireles Lan...

Someone know how to configure a Wireles NetWork Card (PCI Adapter) on Solaris 10 OS? After install the correct driver, what must i have to do? I´m a client desktop and i´m obrigatory to put an IP to get conection whith Server... Thanks... Help me please... (0 Replies)
Discussion started by: marpin
0 Replies

3. Shell Programming and Scripting

Doubt in Ad-hoc reports and Mail

Hi all, 1. How to create ad-hoc reports using Shell Scripts? 2. How to create Shell Scripts for sending email to alert users for erroneous records? Thanks in advance. (1 Reply)
Discussion started by: sgunasekaran
1 Replies

4. Solaris

Looking for a compartable Solaris wireles router

I have SURFboard SB6120 Modem which is compartable with Unix and I would like a wireless router with comparable speed and security. I have been looking at the Linksys wireless WRT610N model but I don't know if it is compartable with Solaris. I have been researching but I have not come across any... (2 Replies)
Discussion started by: Tenyhwa
2 Replies

5. UNIX for Dummies Questions & Answers

Defining an alias FreeBSD

I have defined this alias as quick way to find out which mount point to use for a USB drive after inserting it: # alias da='dmesg | grep da | grep MB' However, when invoking it, it states the following: # da da: Command not found. Can someone explain what is the issue here and how it can be... (3 Replies)
Discussion started by: figaro
3 Replies

6. AIX

Networking Issues - Opera, FreeBSD, AIX

(1) Hi, Am working on FreeBSD 7.4/i386 and installed Opera 11.01 through ports collection manually... But when I run first time am getting "opera: cannot connect X server. Error: Unknown error: 0" What is this error all about???? Please help me to sort out this issue!!! (2) Hi, currently am... (12 Replies)
Discussion started by: Priya Amaresh
12 Replies
WI(4)							   BSD Kernel Interfaces Manual 						     WI(4)

NAME
wi -- WaveLAN/IEEE and PRISM-II 802.11 wireless network driver SYNOPSIS
wi* at pcmcia? function ? wi* at pci? dev ? function ? DESCRIPTION
The wi driver provides support for Lucent Technologies WaveLAN/IEEE PCCARD adapters (also known as WaveLAN II cards) and various PCI/MiniPCI/PCCARD adapters which use Intersil PRISM-II and PRISM-2.5 chipsets. Note that while Lucent sells both ISA and PCMCIA Wave- LAN/IEEE devices, the ISA product is actually a PCMCIA card in an ISA to PCMCIA bridge adapter. Consequently, the wi driver is required for both the ISA and PCMCIA NICs. Also note that some of the PRISM-II adapters works only at 3.3V, hence cardbus(4) support is required for those cards to set VCC correctly, even though they are 16-bit cards. The core of the WaveLAN/IEEE is the Lucent Hermes controller. All host/device interaction is via programmed I/O with the Hermes. The Hermes supports 802.11 and 802.3 frames, power management, BSS, WDS and ad-hoc operation modes. The Silver and the Gold cards of the WaveLAN/IEEE also support WEP. Unlike the other IEEE 802.11 network cards, the WaveLAN Gold cards accept 104 bits key (13 characters) for WEP encryption. The Intersil PRISM-II controller supports WEP as well. The wi driver encapsulates all traffic as 802.11 frames, however it can receive either 802.11 or 802.3 frames. Transmit speed is selectable between 1Mbps fixed, 2Mbps fixed or 2Mbps with auto fallback. For WaveLAN/IEEE Turbo adapters, speeds up to 6Mbps are available. For Wave- LAN/IEEE Turbo 11Mbps adapters and PRISM-II adapters, speeds up to 11Mbps are available. The wi driver supports configuration of Lucent cards for special ad-hoc operation. In this mode, the nwid is ignored and stations can commu- nicate among each other without the aid of an access point. Note that this mode is specific to Lucent chips, and not in the IEEE 802.11 specification. Due to changes in the implementation of this special ad-hoc mode, Lucent-based cards with different firmware revisions may not interoperate in this mode. This mode is no longer the default and must be selected using the ifconfig(8) (media option ``adhoc,flag0'') utility. Recent versions of Lucent and PRISM-II firmware support IBSS creation. IBSS is the standard IEEE 802.11 ad-hoc mode. In this mode, the nwid should be specified. At least one node must be able to create IBSS. The IBSS mode is enabled by ``adhoc'' or ``ibss'' media option. IBSS creation is automatically enabled if supported. The wi driver defaults to infrastructure mode (i.e., using an access point). Recent versions of PRISM-II firmware support operating as an 802.11 Access Point. In this mode, the Access Point station should set the nwid. This will create a standard 802.11 network, and the Access Point station will show up in an Access Point scan. This mode is enabled using the ``hostap'' media option. For more information on configuring this device, see ifconfig(8) and ifmedia(4). HARDWARE
Cards supported by the wi driver include: Alvarion BreezeNET Lucent WaveLAN/IEEE 2.0Mb Bronze Lucent WaveLAN/IEEE 2.0Mb Silver Lucent WaveLAN/IEEE Turbo Lucent WaveLAN/IEEE Turbo 11Mbps Melco AIR CONNECT WLI-PCM-L11, WLI-PCM-L11G Melco AIR CONNECT WLI-CF-S11G Compaq WL100 11Mbps Wireless Corega Wireless LAN PCC-11, PCCA_11, PCCB_11 DEC/Cabletron RoamAbout 802.11 DS High Rate D-Link DWL-520 11Mbps PCI Card, Revs. A1,A2,B1,B2 D-Link DWL-520 11Mbps PCI Card, Rev. C1 not supported, see atw(4) D-Link DWL-520 11Mbps PCI Card, Rev. D not supported, see rtw(4) D-Link DWL-650 11Mbps WLAN Card D-Link DWL-650 11Mbps WLAN Card, Rev. P not supported (Prism 3 chipset) D-Link DCF-650W CF Card ELECOM Air@Hawk LD-WL11 ELSA AirLancer MC-11 Ericsson Wireless LAN Farallon Skyline 11Mbps Wireless Intel PRO/Wireless 2011 LAN PC Card ICOM SL-1100 IO-DATA WN-B11/PCM Intersil PRISM Mini-PCI Linksys Group, Inc. Instant Wireless Network PC Card, CF Card Linksys Group, Inc. Instant Wireless Network WMP11 PCI Card Linksys Group, Inc. Instant Wireless Network WMP11v4 PCI Card not supported NCR WaveLAN/IEEE NEC Wireless Card CMZ-RT-WP, PK-WL001, PC-WL/11C PLANEX GeoWave/GW-NS110 Symbol Spectrum24 Wireless Networker PC Card, CF Card TDK LAK-CD011WL SMC EZ Connect 11M Wireless CF Card SMC2642W SMC EliteConnect Wireless Adapter PC Card SMC2531W-B Z-Com XI-626 PCI Card The original PRISM-I chipset is supported by the awi(4) driver. DIAGNOSTICS
wi%d: init failed The WaveLAN failed to come ready after an initialization command was issued. wi%d: failed to allocate %d bytes on NIC The driver was unable to allocate memory for transmit frames in the NIC's on-board RAM. wi%d: device timeout The WaveLAN failed to generate an interrupt to acknowledge a transmit command. SEE ALSO
arp(4), ifmedia(4), netintro(4), pci(4), pcmcia(4), ifconfig(8), wiconfig(8) HCF Light programming specification, http://www.wavelan.com. HISTORY
The wi device driver first appeared in NetBSD 1.5. AUTHORS
The wi driver was written by Bill Paul <wpaul@ctr.columbia.edu>. BUGS
The execution of wiconfig(8) while the interface is down can produce some error messages. BSD
July 6, 2005 BSD
All times are GMT -4. The time now is 01:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy