LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
Reload this Page NS 2.35+ handoff between wifi and wimax
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
Page 4 of 5 « First 23 4 5
  Search this Thread
Old 02-28-2018, 07:58 PM   #46
knudfl
LQ 5k Club
 
Registered: Jan 2008
Location: Copenhagen DK
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511

Rep: Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641

Re #45.

Please do not apply the patch twice.
Instead unpack a new ns-allinone-2.35_gcc5.tar.gz for every new try.
I.e. it's safer with a clean ns-allinone-2.35 ...
 
Old 02-28-2018, 09:35 PM   #47
saranvellai
LQ Newbie
 
Registered: Feb 2018
Posts: 19

Rep: Reputation: Disabled
can you provide the steps to do unpack the ns-allinone-2.35_gcc5.tar.gz, clean and to install it
 
Old 03-01-2018, 05:43 AM   #48
knudfl
LQ 5k Club
 
Registered: Jan 2008
Location: Copenhagen DK
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511

Rep: Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641
Re #47.

cd [new empty folder]/
tar xvf <path to>/ns-allinone-2.35_gcc5.tar.gz
( Use <path to>/ ,,, or make a copy of ns-allinone-2.35_gcc5.tar.gz to [new folder]/

No install, just a build. And copy 'ns-name' to /usr/local/bin/

-
Last edited by knudfl; 03-01-2018 at 05:45 AM.
 
Old 03-01-2018, 10:10 AM   #49
saranvellai
LQ Newbie
 
Registered: Feb 2018
Posts: 19

Rep: Reputation: Disabled
I tried to build in the new directory mar1 and i get this....

ubuntu@ubuntu-VirtualBox:~/mar1$ sudo apt-get install build-essential
[sudo] password for ubuntu:
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version (12.1ubuntu2).
The following packages were automatically installed and are no longer required:
linux-headers-4.4.0-31 linux-headers-4.4.0-31-generic
linux-image-4.4.0-31-generic linux-image-extra-4.4.0-31-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 65 not upgraded.
 
Old 03-01-2018, 10:39 AM   #50
knudfl
LQ 5k Club
 
Registered: Jan 2008
Location: Copenhagen DK
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511

Rep: Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641
Re #49.

Not really related to ns2.

Packages to use for ns2 :
sudo apt install g++ autoconf libtool libxmu-dev xgraph
 
Old 03-01-2018, 11:51 AM   #51
knudfl
LQ 5k Club
 
Registered: Jan 2008
Location: Copenhagen DK
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511

Rep: Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641
@saranvellai

INFO, wimax-802.16j https://code.google.com/archive/p/ns...ptive-quantum/

A new package "wimax-802.16j-ns_2.35-1.el6_amd64.deb" was created.
Provides /usr/local/bin/ns235-wimax-802.16j-el6
Link: https://drive.google.com/file/d/1Cnn...ew?usp=sharing

Download, and install :
Code:
$ cd Downloads/
$ sudo gdebi ./wimax-802.16j-ns_2.35-1.el6_amd64.deb

--------- Simulation --------
$ ns235-wimax-802.16j-el6 wimax1.tcl
Etc. etc. simulation examples from "wimax-802.16j-examples.tar.gz"
https://drive.google.com/file/d/16iJ...ew?usp=sharing → ~70 examples.

-
 
Old 03-01-2018, 12:25 PM   #52
knudfl
LQ 5k Club
 
Registered: Jan 2008
Location: Copenhagen DK
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511

Rep: Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641
@saranvellai

Another ns executable you can install is /usr/local/bin/ns229-pmip6-nist-6LoWPAN-el6
→ nist-pmip6-6lowpan-ns_2.29-ubuntu12_i386.deb
https://drive.google.com/file/d/1UuX...ew?usp=sharing

$ sudo gdebi ./nist-pmip6-6lowpan-ns_2.29-ubuntu12_i386.deb
... some 32bits dependencies will also be installed.

Examples : "nist-mob_examples-01.18.tar.gz" ( wimax etc.)
https://drive.google.com/file/d/1zhe...ew?usp=sharing

-
 
Old 03-01-2018, 04:32 PM   #53
saranvellai
LQ Newbie
 
Registered: Feb 2018
Posts: 19

Rep: Reputation: Disabled
#51

when I tried to download the wimax80211.16j I get this meassage...
401: Anonymous caller does not have storage.objects.get access to google-code-archive/v2/code.google.com/ns2-802-16j-adaptive-quantum/downloads-page-1.json.
 
Old 03-01-2018, 05:17 PM   #54
knudfl
LQ 5k Club
 
Registered: Jan 2008
Location: Copenhagen DK
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511

Rep: Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641
Re #53.
Quote:
wimax80211.16j
? Which package ? The complete file name, please.

Links : I can supply other links → Dropbox. May work with your OS.


»» /code.google.com/ns2-802-16j-adaptive-quantum ««
Info only : The text says
Quote:
IEEE 802.16j Scheduling Algorithm with Adaptive Quantum - ns2

A scheduling algorithm developed for IEEE 802.16j module used on ns2.

This module is a WiMAX NIST based version improved for multihop relay support. The original files were copied from Chang-Lung Wu in a project known as ns2-multihop-relay, but it is not supported anymore by author
P.S. : The original source-archive.zip is 310MB → unzipped: 618MB.
I can upload the relevant part = "ns-allinone-2.31 + 802.16j" → trunk.tar.bz2 : 77.2MB

-
Last edited by knudfl; 03-01-2018 at 05:51 PM.
 
Old 03-01-2018, 06:19 PM   #55
saranvellai
LQ Newbie
 
Registered: Feb 2018
Posts: 19

Rep: Reputation: Disabled
When I try to execute the wimax1.tcl
ubuntu@ubuntu-VirtualBox:~$ ns235-wimax-802.16j-el6 wimax1.tcl
I get this error
Code:
 gap size=1
Configuration of hierarchical addressing done
num_nodes is set 3
Enter PropOFDMA::command
Number of arguments : 3
0th arg : cmd1st arg : topography2nd arg : _o10not match!
Enter PropOFDMA::command
Number of arguments : 3
0th arg : cmd1st arg : ITU_PDP2nd arg : PED_A
SelectedPDP in command() = PED_A
Enter PropOFDMA::LoadDataFile function
In LoadDataFile, SelectedPDP is PED_A
Path to the ns2 directory is: ./
Enter ReadTableFromFile()
Error opening file BLER_LookupTable.txt in directory ./
Error opening file BLER_LookupTable.txt in the current directory 


similarly for l2handover.tcl
ubuntu@ubuntu-VirtualBox:~$ ns235-wimax-802.16j-el6 l2handover.tcl
Configuration of hierarchical addressing done
num_nodes is set 3
sink node created
warning: no class variable Phy/WirelessPhy/OFDM::g_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable Mac/802_16/BS::algoritmo_ared_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable Mac/802_16/BS::maximum_delay_

warning: no class variable Mac/802_16/BS::tolerated_jitter_

warning: no class variable WimaxScheduler/BS::adaptive_quantum_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable WimaxScheduler/BS::update_pc_

warning: no class variable WimaxScheduler/BS::pc_

INITIALIZE THE LIST xListHead
Base Station 1 created
warning: no class variable Phy/WirelessPhy/OFDM::g_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable Mac/802_16/BS::algoritmo_ared_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable Mac/802_16/BS::maximum_delay_

warning: no class variable Mac/802_16/BS::tolerated_jitter_

warning: no class variable WimaxScheduler/BS::adaptive_quantum_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable WimaxScheduler/BS::update_pc_

warning: no class variable WimaxScheduler/BS::pc_

Base Station 2 created
Adding neighbor 2.0.0 (mac 1) in 1.0.0
Adding neighbor 1.0.0 (mac 0) in 2.0.0
warning: no class variable Phy/WirelessPhy/OFDM::g_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable Mac/802_16/SS::algoritmo_ared_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable Mac/802_16/SS::maximum_delay_

warning: no class variable Mac/802_16/SS::tolerated_jitter_

warning: no class variable WimaxScheduler/SS::adaptive_quantum_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable WimaxScheduler/SS::update_pc_

warning: no class variable WimaxScheduler/SS::pc_

wireless node created ...

    (_o103 cmd line 1)
    invoked from within
"_o103 cmd setflow UL 10000 BE 700 2 1 0.05 15 1"
    invoked from within
"catch "$self cmd $args" ret"
    invoked from within
"if [catch "$self cmd $args" ret] {
set cls [$self info class]
global errorInfo
set savedInfo $errorInfo
error "error when calling class $cls: $args" $..."
    (procedure "_o103" line 2)
    (SplitObject unknown line 2)
    invoked from within
"[$wl_node set mac_(0)] setflow UL 10000 BE 700 2 1 0.05 15 1 "
    (file "l2handover.tcl" line 212)
Please help me....
Last edited by saranvellai; 03-02-2018 at 06:04 PM.
 
Old 03-01-2018, 06:34 PM   #56
knudfl
LQ 5k Club
 
Registered: Jan 2008
Location: Copenhagen DK
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511

Rep: Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641
Re #55 : Please edit post #55 to CODE Tags around the text output
http://www.linuxquestions.org/questi....php?do=bbcode
I.e. [code]output text[/code]
Editing : That's the 'Edit' button in post #55.

My result is similar to the previous wimax1-Result.txt
https://www.dropbox.com/s/wh3i5ws2kb...lt.txt.gz?dl=0

$ ns235-wimax-802.16j-el6 wimax1.tcl > wimax1.tcl_run.txt
→ https://www.dropbox.com/s/k6c5h9v7a1...un.txt.gz?dl=0

? Which "wimax1.tcl" are you using ?
The default "wimax1.tcl" is not using the file "BLER_LookupTable.txt".

$ ns235-wimax-802.16j-el6 l2handover.tcl : OK.
I get 541,926 lines output →
https://www.dropbox.com/s/ql6hcg5gfk...lt.txt.gz?dl=0

Please download the examples, "wimax-802.16j-examples.tar.gz"
https://drive.google.com/file/d/16iJ...ew?usp=sharing

-
Last edited by knudfl; 03-01-2018 at 07:29 PM.
 
Old 03-02-2018, 10:36 AM   #57
saranvellai
LQ Newbie
 
Registered: Feb 2018
Posts: 19

Rep: Reputation: Disabled
While I try to execute the wimax0.tcl...
Code:
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pktwarning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pktc.......
similarly for datarate.tcl also....I'm getting the same message...
Last edited by saranvellai; 03-02-2018 at 06:03 PM.
 
Old 03-02-2018, 11:05 AM   #58
saranvellai
LQ Newbie
 
Registered: Feb 2018
Posts: 19

Rep: Reputation: Disabled
For wimax1.tcl I get some different output
https://www.dropbox.com/home?preview=wimax1

for l2handover.tcl
ubuntu@ubuntu-VirtualBox:~/ns-allinone-2.35/ns-2.35$ ns235-wimax-802.16j-el6 l2handover.tcl
Code:
Configuration of hierarchical addressing done
num_nodes is set 3
sink node created
warning: no class variable Phy/WirelessPhy/OFDM::g_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable Mac/802_16/BS::algoritmo_ared_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable Mac/802_16/BS::maximum_delay_

warning: no class variable Mac/802_16/BS::tolerated_jitter_

warning: no class variable WimaxScheduler/BS::adaptive_quantum_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable WimaxScheduler/BS::update_pc_

warning: no class variable WimaxScheduler/BS::pc_

INITIALIZE THE LIST xListHead
Base Station 1 created
warning: no class variable Phy/WirelessPhy/OFDM::g_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable Mac/802_16/BS::algoritmo_ared_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable Mac/802_16/BS::maximum_delay_

warning: no class variable Mac/802_16/BS::tolerated_jitter_

warning: no class variable WimaxScheduler/BS::adaptive_quantum_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable WimaxScheduler/BS::update_pc_

warning: no class variable WimaxScheduler/BS::pc_

Base Station 2 created
Adding neighbor 2.0.0 (mac 1) in 1.0.0
Adding neighbor 1.0.0 (mac 0) in 2.0.0
warning: no class variable Phy/WirelessPhy/OFDM::g_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable Mac/802_16/SS::algoritmo_ared_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable Mac/802_16/SS::maximum_delay_

warning: no class variable Mac/802_16/SS::tolerated_jitter_

warning: no class variable WimaxScheduler/SS::adaptive_quantum_

	see tcl-object.tcl in tclcl for info about this warning.

warning: no class variable WimaxScheduler/SS::update_pc_

warning: no class variable WimaxScheduler/SS::pc_

wireless node created ...
Running simulation
At 0.000170 in node 1.0.0, send update to node 2.0.0
frame number=0
At 0.002178 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	New neighbor detected...add entry for mac 0
	frame number=0 ccc=0
channel.cc:sendUp - Calc highestAntennaZ_ and distCST_
highestAntennaZ_ = 1.5,  distCST_ = 83.4
SORTING LISTS ...DONE!
At 0.277940 in node 2.0.0, send update to node 1.0.0
frame number=55
At 0.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	New neighbor detected...add entry for mac 1
	frame number=55 ccc=0
At 1.000170 in node 1.0.0, send update to node 2.0.0
frame number=199
At 1.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=199 ccc=0
At 1.277940 in node 2.0.0, send update to node 1.0.0
frame number=255
At 1.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=255 ccc=0
At 2.000170 in node 1.0.0, send update to node 2.0.0
frame number=399
At 2.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=399 ccc=0
At 2.277940 in node 2.0.0, send update to node 1.0.0
frame number=455
At 2.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=455 ccc=0
At 3.000170 in node 1.0.0, send update to node 2.0.0
frame number=599
At 3.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=599 ccc=0
At 3.277940 in node 2.0.0, send update to node 1.0.0
frame number=655
At 3.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=655 ccc=0
At 4.000170 in node 1.0.0, send update to node 2.0.0
frame number=799
At 4.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=799 ccc=0
At 4.277940 in node 2.0.0, send update to node 1.0.0
frame number=855
At 4.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=855 ccc=0
warning: Route to base_stn not known: dropping pkt
At 5.000170 in node 1.0.0, send update to node 2.0.0
frame number=999
At 5.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=999 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 5.277940 in node 2.0.0, send update to node 1.0.0
frame number=1055
At 5.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=1055 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 6.000170 in node 1.0.0, send update to node 2.0.0
frame number=1199
At 6.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=1199 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 6.277940 in node 2.0.0, send update to node 1.0.0
frame number=1255
At 6.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=1255 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 7.000170 in node 1.0.0, send update to node 2.0.0
frame number=1399
At 7.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=1399 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 7.277940 in node 2.0.0, send update to node 1.0.0
frame number=1455
At 7.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=1455 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 8.000170 in node 1.0.0, send update to node 2.0.0
frame number=1599
At 8.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=1599 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 8.277940 in node 2.0.0, send update to node 1.0.0
frame number=1655
At 8.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=1655 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 9.000170 in node 1.0.0, send update to node 2.0.0
frame number=1799
At 9.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=1799 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 9.277940 in node 2.0.0, send update to node 1.0.0
frame number=1855
At 9.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=1855 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 10.000170 in node 1.0.0, send update to node 2.0.0
frame number=1999
At 10.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=1999 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 10.277940 in node 2.0.0, send update to node 1.0.0
frame number=2055
At 10.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=2055 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 11.000170 in node 1.0.0, send update to node 2.0.0
frame number=2199
At 11.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=2199 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 11.277940 in node 2.0.0, send update to node 1.0.0
frame number=2255
At 11.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=2255 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 12.000170 in node 1.0.0, send update to node 2.0.0
frame number=2399
At 12.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=2399 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 12.277940 in node 2.0.0, send update to node 1.0.0
frame number=2455
At 12.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=2455 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 13.000170 in node 1.0.0, send update to node 2.0.0
frame number=2599
At 13.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=2599 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 13.277940 in node 2.0.0, send update to node 1.0.0
frame number=2655
At 13.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=2655 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 14.000170 in node 1.0.0, send update to node 2.0.0
frame number=2799
At 14.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=2799 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 14.277940 in node 2.0.0, send update to node 1.0.0
frame number=2855
At 14.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=2855 ccc=0
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
warning: Route to base_stn not known: dropping pkt
At 15.000170 in node 1.0.0, send update to node 2.0.0
frame number=2999
At 15.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=2999 ccc=0
At 15.277940 in node 2.0.0, send update to node 1.0.0
frame number=3055
At 15.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=3055 ccc=0
At 16.000170 in node 1.0.0, send update to node 2.0.0
frame number=3199
At 16.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=3199 ccc=0
At 16.277940 in node 2.0.0, send update to node 1.0.0
frame number=3255
At 16.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=3255 ccc=0
At 17.000170 in node 1.0.0, send update to node 2.0.0
frame number=3399
At 17.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=3399 ccc=0
At 17.277940 in node 2.0.0, send update to node 1.0.0
frame number=3455
At 17.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=3455 ccc=0
At 18.000170 in node 1.0.0, send update to node 2.0.0
frame number=3599
At 18.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=3599 ccc=0
At 18.277940 in node 2.0.0, send update to node 1.0.0
frame number=3655
At 18.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=3655 ccc=0
At 19.000170 in node 1.0.0, send update to node 2.0.0
frame number=3799
At 19.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=3799 ccc=0
At 19.277940 in node 2.0.0, send update to node 1.0.0
frame number=3855
At 19.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=3855 ccc=0
At 20.000170 in node 1.0.0, send update to node 2.0.0
frame number=3999
At 20.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=3999 ccc=0
At 20.277940 in node 2.0.0, send update to node 1.0.0
frame number=4055
At 20.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=4055 ccc=0
At 21.000170 in node 1.0.0, send update to node 2.0.0
frame number=4199
At 21.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=4199 ccc=0
At 21.277940 in node 2.0.0, send update to node 1.0.0
frame number=4255
At 21.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=4255 ccc=0
At 22.000170 in node 1.0.0, send update to node 2.0.0
frame number=4399
At 22.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=4399 ccc=0
At 22.277940 in node 2.0.0, send update to node 1.0.0
frame number=4455
At 22.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=4455 ccc=0
At 23.000170 in node 1.0.0, send update to node 2.0.0
frame number=4599
At 23.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=4599 ccc=0
At 23.277940 in node 2.0.0, send update to node 1.0.0
frame number=4655
At 23.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=4655 ccc=0
At 24.000170 in node 1.0.0, send update to node 2.0.0
frame number=4799
At 24.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=4799 ccc=0
At 24.277940 in node 2.0.0, send update to node 1.0.0
frame number=4855
At 24.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=4855 ccc=0
At 25.000170 in node 1.0.0, send update to node 2.0.0
frame number=4999
At 25.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=4999 ccc=0
At 25.277940 in node 2.0.0, send update to node 1.0.0
frame number=5055
At 25.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=5055 ccc=0
At 26.000170 in node 1.0.0, send update to node 2.0.0
frame number=5199
At 26.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=5199 ccc=0
At 26.277940 in node 2.0.0, send update to node 1.0.0
frame number=5255
At 26.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=5255 ccc=0
At 27.000170 in node 1.0.0, send update to node 2.0.0
frame number=5399
At 27.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=5399 ccc=0
At 27.277940 in node 2.0.0, send update to node 1.0.0
frame number=5455
At 27.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=5455 ccc=0
At 28.000170 in node 1.0.0, send update to node 2.0.0
frame number=5599
At 28.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=5599 ccc=0
At 28.277940 in node 2.0.0, send update to node 1.0.0
frame number=5655
At 28.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=5655 ccc=0
At 29.000170 in node 1.0.0, send update to node 2.0.0
frame number=5799
At 29.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=5799 ccc=0
At 29.277940 in node 2.0.0, send update to node 1.0.0
frame number=5855
At 29.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=5855 ccc=0
At 30.000170 in node 1.0.0, send update to node 2.0.0
frame number=5999
At 30.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=5999 ccc=0
At 30.277940 in node 2.0.0, send update to node 1.0.0
frame number=6055
At 30.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=6055 ccc=0
At 31.000170 in node 1.0.0, send update to node 2.0.0
frame number=6199
At 31.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=6199 ccc=0
At 31.277940 in node 2.0.0, send update to node 1.0.0
frame number=6255
At 31.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=6255 ccc=0
At 32.000170 in node 1.0.0, send update to node 2.0.0
frame number=6399
At 32.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=6399 ccc=0
At 32.277940 in node 2.0.0, send update to node 1.0.0
frame number=6455
At 32.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=6455 ccc=0
At 33.000170 in node 1.0.0, send update to node 2.0.0
frame number=6599
At 33.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=6599 ccc=0
At 33.277940 in node 2.0.0, send update to node 1.0.0
frame number=6655
At 33.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=6655 ccc=0
At 34.000170 in node 1.0.0, send update to node 2.0.0
frame number=6799
At 34.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=6799 ccc=0
At 34.277940 in node 2.0.0, send update to node 1.0.0
frame number=6855
At 34.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=6855 ccc=0
At 35.000170 in node 1.0.0, send update to node 2.0.0
frame number=6999
At 35.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=6999 ccc=0
At 35.277940 in node 2.0.0, send update to node 1.0.0
frame number=7055
At 35.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=7055 ccc=0
At 36.000170 in node 1.0.0, send update to node 2.0.0
frame number=7199
At 36.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=7199 ccc=0
At 36.277940 in node 2.0.0, send update to node 1.0.0
frame number=7255
At 36.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=7255 ccc=0
At 37.000170 in node 1.0.0, send update to node 2.0.0
frame number=7399
At 37.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=7399 ccc=0
At 37.277940 in node 2.0.0, send update to node 1.0.0
frame number=7455
At 37.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=7455 ccc=0
At 38.000170 in node 1.0.0, send update to node 2.0.0
frame number=7599
At 38.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=7599 ccc=0
At 38.277940 in node 2.0.0, send update to node 1.0.0
frame number=7655
At 38.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=7655 ccc=0
At 39.000170 in node 1.0.0, send update to node 2.0.0
frame number=7799
At 39.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=7799 ccc=0
At 39.277940 in node 2.0.0, send update to node 1.0.0
frame number=7855
At 39.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=7855 ccc=0
At 40.000170 in node 1.0.0, send update to node 2.0.0
frame number=7999
At 40.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=7999 ccc=0
At 40.277940 in node 2.0.0, send update to node 1.0.0
frame number=8055
At 40.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=8055 ccc=0
At 41.000170 in node 1.0.0, send update to node 2.0.0
frame number=8199
At 41.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=8199 ccc=0
At 41.277940 in node 2.0.0, send update to node 1.0.0
frame number=8255
At 41.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=8255 ccc=0
At 42.000170 in node 1.0.0, send update to node 2.0.0
frame number=8399
At 42.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=8399 ccc=0
At 42.277940 in node 2.0.0, send update to node 1.0.0
frame number=8455
At 42.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=8455 ccc=0
At 43.000170 in node 1.0.0, send update to node 2.0.0
frame number=8599
At 43.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=8599 ccc=0
At 43.277940 in node 2.0.0, send update to node 1.0.0
frame number=8655
At 43.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=8655 ccc=0
At 44.000170 in node 1.0.0, send update to node 2.0.0
frame number=8799
At 44.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=8799 ccc=0
At 44.277940 in node 2.0.0, send update to node 1.0.0
frame number=8855
At 44.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=8855 ccc=0
At 45.000170 in node 1.0.0, send update to node 2.0.0
frame number=8999
At 45.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=8999 ccc=0
At 45.277940 in node 2.0.0, send update to node 1.0.0
frame number=9055
At 45.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=9055 ccc=0
At 46.000170 in node 1.0.0, send update to node 2.0.0
frame number=9199
At 46.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=9199 ccc=0
At 46.277940 in node 2.0.0, send update to node 1.0.0
frame number=9255
At 46.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=9255 ccc=0
At 47.000170 in node 1.0.0, send update to node 2.0.0
frame number=9399
At 47.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=9399 ccc=0
At 47.277940 in node 2.0.0, send update to node 1.0.0
frame number=9455
At 47.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=9455 ccc=0
At 48.000170 in node 1.0.0, send update to node 2.0.0
frame number=9599
At 48.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=9599 ccc=0
At 48.277940 in node 2.0.0, send update to node 1.0.0
frame number=9655
At 48.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=9655 ccc=0
At 49.000170 in node 1.0.0, send update to node 2.0.0
frame number=9799
At 49.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=9799 ccc=0
At 49.277940 in node 2.0.0, send update to node 1.0.0
frame number=9855
At 49.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=9855 ccc=0
At 50.000170 in node 1.0.0, send update to node 2.0.0
frame number=9999
At 50.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=9999 ccc=0
At 50.277940 in node 2.0.0, send update to node 1.0.0
frame number=10055
At 50.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=10055 ccc=0
At 51.000170 in node 1.0.0, send update to node 2.0.0
frame number=10199
At 51.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=10199 ccc=0
At 51.277940 in node 2.0.0, send update to node 1.0.0
frame number=10255
At 51.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=10255 ccc=0
At 52.000170 in node 1.0.0, send update to node 2.0.0
frame number=10399
At 52.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=10399 ccc=0
At 52.277940 in node 2.0.0, send update to node 1.0.0
frame number=10455
At 52.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=10455 ccc=0
At 53.000170 in node 1.0.0, send update to node 2.0.0
frame number=10599
At 53.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=10599 ccc=0
At 53.277940 in node 2.0.0, send update to node 1.0.0
frame number=10655
At 53.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=10655 ccc=0
At 54.000170 in node 1.0.0, send update to node 2.0.0
frame number=10799
At 54.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=10799 ccc=0
At 54.277940 in node 2.0.0, send update to node 1.0.0
frame number=10855
At 54.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=10855 ccc=0
At 55.000170 in node 1.0.0, send update to node 2.0.0
frame number=10999
At 55.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=10999 ccc=0
At 55.277940 in node 2.0.0, send update to node 1.0.0
frame number=11055
At 55.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=11055 ccc=0
At 56.000170 in node 1.0.0, send update to node 2.0.0
frame number=11199
At 56.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=11199 ccc=0
At 56.277940 in node 2.0.0, send update to node 1.0.0
frame number=11255
At 56.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=11255 ccc=0
At 57.000170 in node 1.0.0, send update to node 2.0.0
frame number=11399
At 57.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=11399 ccc=0
At 57.277940 in node 2.0.0, send update to node 1.0.0
frame number=11455
At 57.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=11455 ccc=0
At 58.000170 in node 1.0.0, send update to node 2.0.0
frame number=11599
At 58.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=11599 ccc=0
At 58.277940 in node 2.0.0, send update to node 1.0.0
frame number=11655
At 58.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=11655 ccc=0
At 59.000170 in node 1.0.0, send update to node 2.0.0
frame number=11799
At 59.002201 in node 2.0.0, WimaxCtrlAgent received update message from 1.0.0
	frame number=11799 ccc=0
At 59.277940 in node 2.0.0, send update to node 1.0.0
frame number=11855
At 59.279971 in node 1.0.0, WimaxCtrlAgent received update message from 2.0.0
	frame number=11855 ccc=0
please check the output...
Is that correct?
Last edited by saranvellai; 03-02-2018 at 06:04 PM.
 
Old 03-02-2018, 12:21 PM   #59
knudfl
LQ 5k Club
 
Registered: Jan 2008
Location: Copenhagen DK
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511

Rep: Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641Reputation: 3641
@saranvellai.

Please edit your posts to use CODE Tags around the text outputs. To make the thread readable.
How : See #56.

When the posts are edited, you will get an answer.
 
Old 03-02-2018, 11:10 PM   #60
saranvellai
LQ Newbie
 
Registered: Feb 2018
Posts: 19

Rep: Reputation: Disabled
thank you for taking time to reply my queries...
I edited the post using code tags...kindly verify it
 
  


Reply
Page 4 of 5 « First 23 4 5

Tags
mih-multi-criteria, nist-mob, ns2, wimax-802.16j



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Vertical handover between wimax and wifi code najat Linux - Newbie 3 01-14-2016 07:26 AM
Vertical handover between wimax and wifi code IdaliaZimmerman Linux - Newbie 1 12-10-2015 08:31 AM
How can i create a topology that composed of WIFI-WIMAX and UMTS Master_Stu Linux - Networking 7 04-02-2015 02:49 PM
install wimax wifi lte ns2-allinone-2.35 abdennour Linux - General 1 03-24-2015 02:46 PM
WiFi Handoff Paris Heng Linux - Wireless Networking 0 02-22-2008 10:21 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 12:41 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration