Date   

Multiple nodes one router

Ted McArthur <ac7ii@...>
 

Is it possible to have 2 nodes that are behind a single router that has the
same IP address?

--
Ted McArthur
AC7II
ac7ii@...


Re: help on how to set static node computer ip centos 4.7 please

Phil Zocco
 

Hi Ricky,

Try this:

pico -w /etc/sysconfig/network-scripts/ifcfg-eth0

The file should look like this as it does in node 5960:

DEVICE=eth0
BOOTPROTO=static
IPADDR=192.168.1.180
GATEWAY=192.168.1.1
NETMASK=255.255.255.0
ONBOOT=yes
TYPE=Ethernet

Set IPADDR and GATEWAY to the IP address for the node and the gateway
settings respectively.

Make sure the IRLP ports are forwarded to your static IP address of the box.

Safe the file and then run:

service network restart

You should be good to go.

73,

Phil N1BOW
Node 5960
AMT MP 113.6
Niantic, CT USA

-----Original Message-----
From: irlp@... [mailto:irlp@...]On Behalf Of
screend00r
Sent: Friday, February 13, 2009 8:02 PM
To: irlp@...
Subject: [irlp] Re: help on how to set static node computer ip centos
4.7 please


--- In irlp@..., "rik1ply" <gm1ply_mm3rik@...> wrote:

over the last 4 days my node ip has changed its self 3 times

how do i set it to an static ip

tried setup comand but keep looseing connection to system

the default setting for network card dont seam to work for me

i know how to set ip for port forwarding in the router ( it stays
static) its the node thats changing by 1 digit on the end of the
address ie 101 to 102 to 103

any help would be good
please email to
gm1ply_mm3rik@...

thanks in advance rickie
don't use dhcp, set it manually.

Chuck,
N4YCW, IRLP 4124



------------------------------------

--- IRLP-Owners YahooGroups List ---Yahoo! Groups Links


Re: help on how to set static node computer ip centos 4.7 please

screend00r <n4ycw@...>
 

--- In irlp@..., "rik1ply" <gm1ply_mm3rik@...> wrote:

over the last 4 days my node ip has changed its self 3 times

how do i set it to an static ip

tried setup comand but keep looseing connection to system

the default setting for network card dont seam to work for me

i know how to set ip for port forwarding in the router ( it stays
static) its the node thats changing by 1 digit on the end of the
address ie 101 to 102 to 103

any help would be good
please email to
gm1ply_mm3rik@...

thanks in advance rickie
don't use dhcp, set it manually.

Chuck,
N4YCW, IRLP 4124


help on how to set static node computer ip centos 4.7 please

rik1ply <gm1ply_mm3rik@...>
 

over the last 4 days my node ip has changed its self 3 times

how do i set it to an static ip

tried setup comand but keep looseing connection to system

the default setting for network card dont seam to work for me

i know how to set ip for port forwarding in the router ( it stays
static) its the node thats changing by 1 digit on the end of the
address ie 101 to 102 to 103

any help would be good
please email to
gm1ply_mm3rik@...

thanks in advance rickie


Re: Backup for re-instal filename?

Jim WW4M
 

The instructions can be found linked from
http://www.irlp.net/new-node/. The reinstall script expects the file
to be named the same as the file created by the backup script.

Please sign messages posted to this list with your callsign and node
number.

73, Jim WW4M

--- In irlp@..., "jjbauerly" <jjbauerly@...> wrote:


Hello all;

Running CentOS 4.4

I have recently backup our local node to a usb stick. the resulting
filename ended up being 'floppy'. The file size was about 453KBytes. If
i understand the procedure this file will need to be in the /tmp
directory when needed for re-install. Will it ask for the filename or
does the re-install script look for a specific filename?


Re: Help - New Install -No eth0 detect

David Cameron - IRLP
 

Edit the config file using pico:

pico /etc/sysconfig/network-scripts/ifcfg-eth0

Remove any lines that say HWADDR

The file should look like this when you are done:

DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
TYPE=Ethernet

Then try the command

ifup eth0

Dave Cameron
VE7LTD


Re: Help - New Install -No eth0 detect

Dennis Griffin
 

See below comments..



From: irlp@... [mailto:irlp@...] On Behalf Of Jason
Stahls
Sent: Thursday, February 12, 2009 11:02 PM
To: irlp@...
Subject: Re: [irlp] Help - New Install -No eth0 detect



w4dg.geo wrote:
The PCI network card has a RTL8139C chip and is being detected by the
BIOS and shares no other IRQ address, which is 10.

I used APPENDIX A 3.1 modprobe ne io=0x and the common IO port arguments
suggested ie: io=0x280, 300, 320, 340 but the NIC is not recognized.
Ok, first off NE is the module for NE2000 compatible cards, old ISA
stuff, you very rarely need to specify IO and IRQ's to PCI devices.
Now, try 'lspci' while logged in as root and see that the RTL8139 shows
up on the PCI bus and enumerates properly. [Dennis Griffin] It detects the
NIC and states it's a Realtek Semiconductor co, RTL-8139/8139C/8139C+
(Rev10) If it's there try 'modprobe
8139too' and see if that comes up, also you can try 'modprobe
8139cp'.[Dennis Griffin] When I tried either command all I get in return is
the prompt returned, nothing more.
Failing it working, run 'dmesg' the last few lines may give you a clue
as to why the module failed to load.
[Dennis Griffin] I didn't see much info that reveled info of why the module
failed to load.

I still get that the MAC address detected was not expected message and the
system fails to recognize the NIC.

I had another identical NIC and it gives the same MAC address detected was
unexpected.

I will disassemble my working node and try my 3COM NIC card in it tomorrow
to see if it's just 2 identical NIC's that won't work with IRLP.

TNX for your suggestions!

73, Dennis Griffin - W4DG










--
Jason Stahls
VA3JSS


Re: Help - New Install -No eth0 detect

Jason Stahls
 

w4dg.geo wrote:
The PCI network card has a RTL8139C chip and is being detected by the
BIOS and shares no other IRQ address, which is 10.

I used APPENDIX A 3.1 modprobe ne io=0x and the common IO port arguments
suggested ie: io=0x280, 300, 320, 340 but the NIC is not recognized.
Ok, first off NE is the module for NE2000 compatible cards, old ISA stuff, you very rarely need to specify IO and IRQ's to PCI devices. Now, try 'lspci' while logged in as root and see that the RTL8139 shows up on the PCI bus and enumerates properly. If it's there try 'modprobe 8139too' and see if that comes up, also you can try 'modprobe 8139cp'. Failing it working, run 'dmesg' the last few lines may give you a clue as to why the module failed to load.

--
Jason Stahls
VA3JSS


Backup for re-instal filename?

jjbauerly
 

Hello all;

Running CentOS 4.4

I have recently backup our local node to a usb stick. the resulting
filename ended up being 'floppy'. The file size was about 453KBytes. If
i understand the procedure this file will need to be in the /tmp
directory when needed for re-install. Will it ask for the filename or
does the re-install script look for a specific filename?


Help - New Install -No eth0 detect

Dennis Griffin
 

Hello all:



I am installing a new node for a friend and have installed IRLP
Operating System (CentOS 4.4). I have successfully booted into the login
and password however, during the software loading when the PCI installed
network card eth0 load I receive a message that a different MAC addtess
has been detected and "ignoring", then the system goes to the root
command line.

The PCI network card has a RTL8139C chip and is being detected by the
BIOS and shares no other IRQ address, which is 10.

When I try the command ifup eth0 I get the same message as during the
loading sequence. Using ifconfig etho I receive NO IP address
information for inet.

I am behind a network (same network used for my working node) which the
router has been reconfigured and works with an assigned IP address of
192.168.10.

I used APPENDIX A 3.1 modprobe ne io=0x and the common IO port arguments
suggested ie: io=0x280, 300, 320, 340 but the NIC is not recognized.

I am appraently doing something wrong!

Any step-by-step help would be appreciated as I am a neebee to Linux and
understand very little of how it works!

My node install went without any problems the 1st. time following the
same instructions I am using for this NEW NODE INSTALL.

TNX & 73...de...Dennis, W4DG


Re: Environment File

k9dc
 

Either that or you could fuss with custom_decode and setup special codes to dial one or more reflectors and send the regular codes to the dumper

Dave Gingrich, K9DC
Could be anywhere

On Feb 12, 2009, at 12:52, "Nate Duehr" <nate@...> wrote:

The environment setting was actually for a feature that would allow a node
to call another node INTO a Reflector that never got implemented.

The lockout_list has always been the way to stop calls to Reflectors (or any
other node).

Nate WY0X


Re: Environment File

Nate Duehr <nate@...>
 

The environment setting was actually for a feature that would allow a node
to call another node INTO a Reflector that never got implemented.

The lockout_list has always been the way to stop calls to Reflectors (or any
other node).

Nate WY0X

-----Original Message-----
From: irlp@... [mailto:irlp@...] On Behalf Of David
McAnally
Sent: Thursday, February 12, 2009 12:31 PM
To: irlp@...
Subject: Re: [irlp] Environment File

That environment setting never was implemented in IRLP. Use this
method instead. This file is documented in the unofficial IRLP
manual.

Create the file /home/irlp/custom/lockout_list containing this line,
all upper case.

ALLREF

--
Regards,
David McAnally, WD5M


Re: Environment File

David McAnally
 

On Thu, Feb 12, 2009 at 1:24 PM, Marc Reitzell <marc@...> wrote:
We are having a problem with a user who brings up reflectors without
identifying himself. This particular user brings up the reflector and
then leaves it connected without using it.

To combat this, I tried to modify the ALLOW_CALL_TO_REFLECTORS to NO,
but that didn't take (I can still call reflectors). I noticed that the
comment above that line says ALLOW_CALL, so I changed the variable to
ALLOW_CALL, and that didn't work. What am I doing wrong?

I noticed that the environment file is executable and owned by user
repeater, although the IRLP web site says it is owned by root. When I
make modifications to the file, I type "source environment" after I am
done, and that didn't seem to work. I tried to reboot computer, and
that didn't work, either.

That environment setting never was implemented in IRLP. Use this
method instead. This file is documented in the unofficial IRLP
manual.

Create the file /home/irlp/custom/lockout_list containing this line,
all upper case.

ALLREF

--
Regards,
David McAnally, WD5M


Environment File

Marc Reitzell
 

We are having a problem with a user who brings up reflectors without
identifying himself. This particular user brings up the reflector and
then leaves it connected without using it.

To combat this, I tried to modify the ALLOW_CALL_TO_REFLECTORS to NO,
but that didn't take (I can still call reflectors). I noticed that the
comment above that line says ALLOW_CALL, so I changed the variable to
ALLOW_CALL, and that didn't work. What am I doing wrong?

I noticed that the environment file is executable and owned by user
repeater, although the IRLP web site says it is owned by root. When I
make modifications to the file, I type "source environment" after I am
done, and that didn't seem to work. I tried to reboot computer, and
that didn't work, either.

Marc, W6MAR
Node 3895


Re: THANK YOU, THANK YOU, THANK YOU, From Node 3362

wayne chapman <lk_side@...>
 

Hello Chris,
I believe you are asking the wrong guy, Dave, KL7M, orchestrated the solution and he is far more qualified to explain the engineering behind the solution. My best attempt at the explanation was first, to get the correct static IP addresses from Hughes. Then to get them correctly set in to the router. The other part was to do basically the same for the IRLP box. I think my main problem prior to Dave entering in the picture was, as I usually do, I was looking for a complicated solution, which was totally out of whack with the overall picture. I do have to add it would of been nice to know the correct Static IP address from the beginning, but then I may of never met Dave!
Take Care,
Wayne

----- Original Message -----
From: Chris Curtis
To: irlp@...
Sent: Wednesday, February 11, 2009 3:00 PM
Subject: RE: [irlp] THANK YOU, THANK YOU, THANK YOU, From Node 3362


Although I sold off my DirecPC 2way setup long ago (cable and dsl finally
came to town, er sticks), I'd like to know what the solution was.
I've been watching this thread, remembering my fun all the way back to my
first 1 way DirecPC system.
FAP == fair access policy. Was rough!

Chris
Kb0wlf
3185

-----Original Message-----
From: irlp@... [mailto:irlp@...] On Behalf Of
doberman20022003
Sent: Wednesday, February 11, 2009 3:43 PM
To: irlp@...
Subject: [irlp] THANK YOU, THANK YOU, THANK YOU, From Node 3362

Well, Hello Dear Group, let me begin by thanking all of you for
taking on my problem in addition to the ones that you may of already
had. It is in the true spirit of Ham Radio to be able to turn to
one's peers and get not only technical support but emotional support.
After over a month of trial and error, Node 3362 is back on the air.

--snip--

Thank You Dave
Thank All of You
Wayne


Re: THANK YOU, THANK YOU, THANK YOU, From Node 3362

chris curtis
 

Although I sold off my DirecPC 2way setup long ago (cable and dsl finally
came to town, er sticks), I'd like to know what the solution was.
I've been watching this thread, remembering my fun all the way back to my
first 1 way DirecPC system.
FAP == fair access policy. Was rough!

Chris
Kb0wlf
3185

-----Original Message-----
From: irlp@... [mailto:irlp@...] On Behalf Of
doberman20022003
Sent: Wednesday, February 11, 2009 3:43 PM
To: irlp@...
Subject: [irlp] THANK YOU, THANK YOU, THANK YOU, From Node 3362

Well, Hello Dear Group, let me begin by thanking all of you for
taking on my problem in addition to the ones that you may of already
had. It is in the true spirit of Ham Radio to be able to turn to
one's peers and get not only technical support but emotional support.
After over a month of trial and error, Node 3362 is back on the air.

--snip--

Thank You Dave
Thank All of You
Wayne


THANK YOU, THANK YOU, THANK YOU, From Node 3362

doberman20022003 <lk_side@...>
 

Well, Hello Dear Group, let me begin by thanking all of you for
taking on my problem in addition to the ones that you may of already
had. It is in the true spirit of Ham Radio to be able to turn to
one's peers and get not only technical support but emotional support.
After over a month of trial and error, Node 3362 is back on the air.
Those of you who have in the past questioned if IRLP will work with
Hughes Network, well let me say it has in the past, and is once again
operating on Hughes.Net. I must admit there were times during this
period I wanted to, and probably did cast blame on Hughes Net, but
inspite of the fact they did change my IP address during a
reregistration period, I have to formally appoligize, because I was
looking at far too complicated solutions, ones that would of never
given me the end results I have now.
Normally I would not single out just one person for the final
accomplisment, but in this case I must, Thank You Dave, KL7M, were it
not for your expertise, plus your vast resources I would still be
pounding my head against the wall. I want to add, although I do not
know all the people involved in that vast resource, but Thank You
too.
Before I hung up with Dave on the phone he asked me to post, If
anyone else is having a problem with the IRLP/Hughes combination, or
maybe just IRLP in general, To get in touch with Him, That to me is a
real tribute to Ham Operators world wide.
Thank You Dave
Thank All of You
Wayne


Regency RH256NB

Timothy Jacobs <kf4bzt@...>
 

Hi all,
I have one of my mobile Regency radio working and I need to see if anyone
on here might know where I can get the voltage for the COS line. I still
need to build a cable from the radio to the IRLP interface, but while I have
the case open I figured I would look for a voltage tap to tie into.

Thanks,
Tim
KF4BZT


THE 2009 VoIP TOPICAL CONFERENCE IS SATURDAY APRIL 18 Circus-Circus Las Vegas

w7aor
 

THE 2009 VoIP TOPICAL CONFERENCE IS SATURDAY APRIL 18, 2009 at Circus-
Circus in Las Vegas.

http://www.narri.org/Annual_VoIP_Conference.html

Topics include all the major VoIP systems in use by the amateur radio
community, i.e., IRLP, Echo link, EchoIRLP, All Star, D-Star and DV
Dongle.

Please Register for the Conference by MARCH 1, 2009
http://www.narri.org/VoIP_Conference_Registration_Form.html

Contact Kent W7AOR with questions
IRLP Ref 9250 and D-Star REF014
W7aor@...
702-452-4412


Re: [amsat-bb] Dieter Schliemann, KX4Y SK

Evans Mitchell KD4EFM / AFA4TH FL / WQFK-894
 

Thanks Nate, I use to talk to Dieter via email
a lot a few years ago with the promotion of the ARISS
stuff that I would replay on the nodes here in Florida.

I too am going to miss him greatly.

Evans

-----Original Message-----
From: irlp@... [mailto:irlp@...] On Behalf Of
Nate Duehr
Sent: Tuesday, February 10, 2009 1:38 PM
To: 'Frank H. Bauer'; amsat-bb@...; irlp@...
Subject: [irlp] RE: [amsat-bb] Dieter Schliemann, KX4Y SK

Dieter will be missed in the IRLP community also.

(Sending a copy of your announcement to the IRLP list, Frank. Thank
you.)

Nate Duehr, WY0X

-----Original Message-----
From: amsat-bb-bounces@... <mailto:amsat-bb-bounces%40amsat.org>
[mailto:amsat-bb-bounces@... <mailto:amsat-bb-bounces%40amsat.org>
] On Behalf Of Frank H. Bauer
Sent: Tuesday, February 10, 2009 11:16 AM
To: amsat-bb@... <mailto:amsat-bb%40amsat.org>
Subject: [amsat-bb] Dieter Schliemann, KX4Y SK

All,

It is with great sadness that I announce the passing of Dieter
Schliemann, KX4Y.

Those that knew Dieter recognized that he was a "class act"---a great
gentleman and colleague who will be sorely missed by all. Dieter was
instrumental in leading and supporting many key activities in AMSAT and
on the ARISS program.

For ARISS, Dieter led the school contact IRLP/Echolink initiative.
Through this amateur radio VOIP system, Dieter and his team
substantially extended our reach of the school contacts. And through his
efforts, tens of thousands of school students and ham radio operators,
world-wide, could listen to other school contacts, enhancing education
and giving all a better understanding of what it is like to live and
work on ISS. Dieter's diplomacy, teambuilding skills and attention to
the details were impeccable and were well respected within the team. He
rose to the challenge when I asked him to lead the IRLP/Echolink team.
At the time, there were strong, divergent opinions on the use of IRLP
and Echolink on ARISS. He singlehandedly developed a cohesive team that
is producing great results and are enjoying working together.

Over the past couple of years, Dieter fought a long and courageous
battle with Cancer. A month ago, all of us thought he was on the road to
recovery.
Unfortunately, that did not come to pass. Through it all, Dieter
remained the gentle, caring person that we all have grown to love. And
during his illness, he remained dedicated to his AMSAT and ARISS causes
and responsibilities. When he received the surprising news from the
doctors that he had only two weeks to live and despite being weak from a
long hospitalization, Dieter got on the e-mail and worked a transition
plan to ensure the IRLP/Echolink capabilities on ARISS continues. What a
great, compassionate, loving human being!

I first met Dieter behind the AMSAT Booth at Dayton, where he was one of
the mainstay individuals supporting AMSAT efforts at the Hamvention.
Reflecting on Dieter's support to AMSAT, AMSAT Board Member Gould Smith,
WA4SXM, stated, "Two years ago Dieter told me that the only reason he
came to Dayton was to work in the AMSAT booth and to talk with people
about AMSAT". And he supported AMSAT in many other ways, including his
efforts as an Area Coordinator, where he mentored a countless number of
satellite enthusiasts.
We are eternally grateful for all Dieter has done for AMSAT and the
ARISS program. And will miss him dearly.

On behalf of the ARISS and AMSAT teams, we wish to express our deepest
sympathy to the Schliemann family and friends. Especially his wife Tina
and his good friend Ron Arsenault, N1NYR, who helped Dieter and the
Schliemann family throughout Dieter's long illness.

Frank H. Bauer, KA3HDO
AMSAT-NA V.P. for Human Spaceflight Programs ARISS International
Chairman _______________________________________________
Sent via AMSAT-BB@... <mailto:AMSAT-BB%40amsat.org> . Opinions
expressed are those of the author.
Not an AMSAT-NA member? Join now to support the amateur satellite
program!
Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
<http://amsat.org/mailman/listinfo/amsat-bb>