44net-request@hamradio.ucsd.edu wrote:
Subject: Re: [44net] known good routers that pass rip/44-net friendly in uk? From: ve1jot ve1jot@eastlink.ca Date: 01/08/2014 09:43 AM
To: 44net@hamradio.ucsd.edu
Anyone know of a list of routers that pass ripv2? A ham in EU is trying to set up ripv2 with our help but ripv2 gateway announcements don't seem to be coming through the router...yes, the pi is in the DMZ, hi hi! He's on virginmedia, any issues with their modems known?
You mean the ipip tunneling is working with static routing but you cannot get RIP to work? Or is the situation merely "it does not work" and the diagnosis "there are no RIP announcements"?
I set up a Pi some time ago and I had a strange problem with RIP that I finally resolved, and submitted a patch to ampr-ripd that makes it work problemfree. I don't know if the other ripd was similarly modified, for sure it had the same issue.
The problem was that although RIP announcements made it all the way to the Pi, they were not properly received on the UDP socket the daemon created.
Rob
On 14-01-08 04:42 PM, Rob Janssen wrote: nope, ip encap not working neither is rip..even with a static tunnel defined no joy...I have a WRT-54GS spare that has dd-wrt on it that DOES work here on eastlink in canada, and will send it to him...just worried that the virginmedia cable modem might not pass ipencap to/from the router..
You mean the ipip tunneling is working with static routing but you cannot get RIP to work? Or is the situation merely "it does not work" and the diagnosis "there are no RIP announcements"?
I set up a Pi some time ago and I had a strange problem with RIP that I finally resolved, and submitted a patch to ampr-ripd that makes it work problemfree. I don't know if the other ripd was similarly modified, for sure it had the same issue.
The problem was that although RIP announcements made it all the way to the Pi, they were not properly received on the UDP socket the daemon created.
Rob
Which modem is he using? VM used to supply a cable modem and a DIR615 (which could be flashed with DD-WRT) but now they supply a combined Netgear modem/router. AAUI, this can be configured as a modem for use with the customer's own router.
Nick.
On 08/01/2014 20:49, ve1jot wrote:
(Please trim inclusions from previous messages) _______________________________________________
On 14-01-08 04:42 PM, Rob Janssen wrote: nope, ip encap not working neither is rip..even with a static tunnel defined no joy...I have a WRT-54GS spare that has dd-wrt on it that DOES work here on eastlink in canada, and will send it to him...just worried that the virginmedia cable modem might not pass ipencap to/from the router..
You mean the ipip tunneling is working with static routing but you cannot get RIP to work? Or is the situation merely "it does not work" and the diagnosis "there are no RIP announcements"?
I set up a Pi some time ago and I had a strange problem with RIP that I finally resolved, and submitted a patch to ampr-ripd that makes it work problemfree. I don't know if the other ripd was similarly modified, for sure it had the same issue.
The problem was that although RIP announcements made it all the way to the Pi, they were not properly received on the UDP socket the daemon created.
Rob
He tells me it's a Newlink 54M Model ROU5 - I cannot seem to find much information on the net about it...
On 14-01-08 05:09 PM, Nick G4IRX wrote:
(Please trim inclusions from previous messages) _______________________________________________ Which modem is he using? VM used to supply a cable modem and a DIR615 (which could be flashed with DD-WRT) but now they supply a combined Netgear modem/router. AAUI, this can be configured as a modem for use with the customer's own router.
Most of these el-cheapo routers will quite happily forward UDP and TCP but don't have any rules to forward a protocol. Sometimes the DMZ works, other times it doesn't. I've seen many people report this on the IPv6 tunnel broker forums where they are trying to forward Protocol 41 and the host is behind a NAT.
I'd suggest he gets something that supports DD-WRT. I've just seen John Wiseman's post from earlier today that he has this working on VM - it just needs a couple of firewall rules adding to DD-WRT which has to be done over a telnet connection. Unfortunately they won't persist between reboots so it may need a script to automate it.
Something like:
iptables -t nat -A PREROUTING -i eth1 -p 4 -j DNAT --to 192.168.1.2 iptables -t filter -A FORWARD -i eth1 -p 4 -d 10.0.1.2 -j ACCEPT
the check your firewall rules with iptables -t nat -L; iptables -t filter -L
Assuming eth1 is your public ip interface and 192.168.1.2 is the ip address of your host running rip44d, this would forward any incoming protocol 4 packets to 10.0.1.2.
HTH, Nick.
On 08/01/2014 21:48, ve1jot wrote:
He tells me it's a Newlink 54M Model ROU5 - I cannot seem to find much information on the net about it...
On 14-01-08 05:09 PM, Nick G4IRX wrote:
(Please trim inclusions from previous messages) _______________________________________________ Which modem is he using? VM used to supply a cable modem and a DIR615 (which could be flashed with DD-WRT) but now they supply a combined Netgear modem/router. AAUI, this can be configured as a modem for use with the customer's own router.
Correcting my previous typo!
Something like:
iptables -t nat -A PREROUTING -i eth1 -p 4 -j DNAT --to 192.168.1.2 iptables -t filter -A FORWARD -i eth1 -p 4 -d 192.168.1.2 -j ACCEPT
the check your firewall rules with iptables -t nat -L; iptables -t filter -L
Assuming eth1 is your public ip interface and 192.168.1.2 is the ip address of your host running rip44d, this would forward any incoming protocol 4 packets to 192.168.1.2.
73 Nick G4IRX
On 08/01/2014 22:13, Nick G4IRX wrote:
(Please trim inclusions from previous messages) _______________________________________________ Most of these el-cheapo routers will quite happily forward UDP and TCP but don't have any rules to forward a protocol. Sometimes the DMZ works, other times it doesn't. I've seen many people report this on the IPv6 tunnel broker forums where they are trying to forward Protocol 41 and the host is behind a NAT.
Nick,
You can make these changes persist across reboots in DD-WRT by using the Adminstration/Commands/Save Firewall feature. I have
iptables -t nat -I PREROUTING -p 4 -d 82.18.43.225 -j DNAT --to 192.168.1.31 iptables -t filter -I FORWARD -p 4 -d 192.168.1.31 -j ACCEPT
I had problems with -i eth1, maybe because I was using the wrong interface. (Should it be the bridge?) Specifying an address means I'll have to change it when my external address changes, but on Virgin Media this very rarely happens.
I have separate cable modem and router, but I've been on Diamond/NTL/Virgin for a very long time - maybe their current offering isn't so flexible.
73, John G8BPQ
-----Original Message----- From: 44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu [mailto:44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu] On Behalf Of Nick G4IRX Sent: 09 January 2014 09:14 To: 44net@hamradio.ucsd.edu Subject: Re: [44net] known good routers that pass rip/44-net friendly in uk?
(Please trim inclusions from previous messages) _______________________________________________ Correcting my previous typo!
Something like:
iptables -t nat -A PREROUTING -i eth1 -p 4 -j DNAT --to 192.168.1.2 iptables -t filter -A FORWARD -i eth1 -p 4 -d 192.168.1.2 -j ACCEPT
the check your firewall rules with iptables -t nat -L; iptables -t filter -L
Assuming eth1 is your public ip interface and 192.168.1.2 is the ip address of your host running rip44d, this would forward any incoming protocol 4 packets to 192.168.1.2.
73 Nick G4IRX
John,
Different versions of DD-WRT!
I've just found a WRT54G and the WAN interface (determined by running ifconfig command) is vlan1 Thanks for the tip about Adminstration/Commands/Save Firewall.
73 Nick G4IRX
On 09/01/2014 09:47, John Wiseman wrote:
(Please trim inclusions from previous messages) _______________________________________________ Nick,
You can make these changes persist across reboots in DD-WRT by using the Adminstration/Commands/Save Firewall feature. I have
iptables -t nat -I PREROUTING -p 4 -d 82.18.43.225 -j DNAT --to 192.168.1.31 iptables -t filter -I FORWARD -p 4 -d 192.168.1.31 -j ACCEPT
I had problems with -i eth1, maybe because I was using the wrong interface. (Should it be the bridge?) Specifying an address means I'll have to change it when my external address changes, but on Virgin Media this very rarely happens.
I have separate cable modem and router, but I've been on Diamond/NTL/Virgin for a very long time - maybe their current offering isn't so flexible.
73, John G8BPQ
I've just completed the pi-tnc and fired it up with my pi using jnos. It worked first time, but txd is way too short as I'm going through a mountain top digital repeater. Everything is configured for a kissmode tnc for use with jnos.
I'm miffed about how to get out of the software preset so I can use R6 to set txd.
After reading the instruction book for the tnc-pi, I'm still confused as to what to use.
Thanks, jerome - ve7ass
I've just completed the pi-tnc and fired it up with my pi using jnos. It worked first time, but txd is way too short as I'm going through a mountain top digital repeater. Everything is configured for a kissmode tnc for use with jnos.
.. how to get out of the software preset so I can use R6 to set txd.
Does the JNOS PARAM statement work? That's what we used in the past with the other KISS TNC's.
Bill, WA7NWP
PS. Does your repeater reach South? I know of one existing 1200 baud packet repeater just North of Seattle but I don't think they have any IP activity there (yet...)
you use the pitnc_setparams utility..... http://www.tnc-x.com/params.zip on my older 256m without the mounting holes the syntax for txdelay is: pitnc_setparams 0 0 1 40 newer board uses different address: pitnc_setparams 0 1 1 40 to use the potentiometer, set txdelay to 0...
I've found that I've had to power down and re-power the pi to accept any changes to txd...that's not in the manual, hi hi!
On 14-01-09 06:30 PM, Bill Vodall wrote:
(Please trim inclusions from previous messages) _______________________________________________
I've just completed the pi-tnc and fired it up with my pi using jnos. It worked first time, but txd is way too short as I'm going through a mountain top digital repeater. Everything is configured for a kissmode tnc for use with jnos.
.. how to get out of the software preset so I can use R6 to set txd.
Does the JNOS PARAM statement work? That's what we used in the past with the other KISS TNC's.
Bill, WA7NWP
PS. Does your repeater reach South? I know of one existing 1200 baud packet repeater just North of Seattle but I don't think they have any IP activity there (yet...) _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
On 14-01-09 06:48 PM, ve1jot wrote:
(Please trim inclusions from previous messages) _______________________________________________ you use the pitnc_setparams utility..... http://www.tnc-x.com/params.zip on my older 256m without the mounting holes the syntax for txdelay is: pitnc_setparams 0 0 1 40 newer board uses different address: pitnc_setparams 0 1 1 40 to use the potentiometer, set txdelay to 0...
I've found that I've had to power down and re-power the pi to accept any changes to txd...that's not in the manual, hi hi!
By the way, to use the utility, do it without anything attached such as jnos or kissattach...
OK John... got it all working correctly now. Thanks for your help! j
On 14-01-09 02:50 PM, ve1jot wrote:
(Please trim inclusions from previous messages) _______________________________________________
On 14-01-09 06:48 PM, ve1jot wrote:
(Please trim inclusions from previous messages) _______________________________________________ you use the pitnc_setparams utility..... http://www.tnc-x.com/params.zip on my older 256m without the mounting holes the syntax for txdelay is: pitnc_setparams 0 0 1 40 newer board uses different address: pitnc_setparams 0 1 1 40 to use the potentiometer, set txdelay to 0...
I've found that I've had to power down and re-power the pi to accept any changes to txd...that's not in the manual, hi hi!
By the way, to use the utility, do it without anything attached such as jnos or kissattach... _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Excellent Jerome, you'll love it! Great decoding ability...the tnc-pi too, hi hi! I SO wish the tnc-pi would do 300b HF tho, single or dual-port would satisfy me, hi..my poor old kams are getting long in the tooth, and draw 2x or more as much power as the pi+tnc-pi... On 14-01-09 09:10 PM, Jerome Schatten wrote:
(Please trim inclusions from previous messages) _______________________________________________ OK John... got it all working correctly now. Thanks for your help! j
There may one day be a 300 baud version of the TNC-PI. I've even bought the chips to experiment with, but as usual time is the enemy! I'm also working on ideas for a 9600 baud version.
73, John G8BPQ
-----Original Message----- From: 44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu [mailto:44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu] On Behalf Of ve1jot Sent: 10 January 2014 06:53 To: 44net@hamradio.ucsd.edu Subject: Re: [44net] set txd on Pi-tnc running jnos?
(Please trim inclusions from previous messages) _______________________________________________ Excellent Jerome, you'll love it! Great decoding ability...the tnc-pi too, hi hi! I SO wish the tnc-pi would do 300b HF tho, single or dual-port would satisfy me, hi..my poor old kams are getting long in the tooth, and draw 2x or more as much power as the pi+tnc-pi... On 14-01-09 09:10 PM, Jerome Schatten wrote:
(Please trim inclusions from previous messages) _______________________________________________ OK John... got it all working correctly now. Thanks for your help! j
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Oh 9600 sign me up.....faster is better :)
B
________________________________ From: John Wiseman john.wiseman@cantab.net To: 'AMPRNet working group' 44net@hamradio.ucsd.edu Sent: Friday, January 10, 2014 5:30:53 AM Subject: Re: [44net] set txd on Pi-tnc running jnos?
(Please trim inclusions from previous messages) _______________________________________________ There may one day be a 300 baud version of the TNC-PI. I've even bought the chips to experiment with, but as usual time is the enemy! I'm also working on ideas for a 9600 baud version.
73, John G8BPQ
-----Original Message----- From: 44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu [mailto:44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu] On Behalf Of ve1jot Sent: 10 January 2014 06:53 To: 44net@hamradio.ucsd.edu Subject: Re: [44net] set txd on Pi-tnc running jnos?
(Please trim inclusions from previous messages) _______________________________________________ Excellent Jerome, you'll love it! Great decoding ability...the tnc-pi too, hi hi! I SO wish the tnc-pi would do 300b HF tho, single or dual-port would satisfy me, hi..my poor old kams are getting long in the tooth, and draw 2x or more as much power as the pi+tnc-pi... On 14-01-09 09:10 PM, Jerome Schatten wrote:
(Please trim inclusions from previous messages) _______________________________________________ OK John... got it all working correctly now. Thanks for your help! j
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Oh 9600 sign me up.....faster is better :)
There's a much faster 'shield' at 900 MHz available for the PI. We hams have the UDRX and T3-9670 coming which should easily work plug and play with the PI. Both UDRX and T3 are showing 9600 as the first rev and much higher speeds after that. I'm thinking the limiter by the end of the year will be the lame networking in the PI (via the USB stack) rather than the RF channel - but I'm looking at 5 GHz...
Bill, WA7NWP
Hi Bill...
Nope... the jnos param statement seems to be ignored; I tried changing it in autoexec.nos.
The repeater is on 145.07/67 rx/tx it's at almost 3000 feet facing south on Mt.Seymoure in North Vancouver. I'm sure it can be heard for a few hundred miles towards the south. It's been up for ages.
Best, jerome ve7ass/yvrass On 14-01-09 02:30 PM, Bill Vodall wrote:
(Please trim inclusions from previous messages) _______________________________________________
I've just completed the pi-tnc and fired it up with my pi using jnos. It worked first time, but txd is way too short as I'm going through a mountain top digital repeater. Everything is configured for a kissmode tnc for use with jnos.
.. how to get out of the software preset so I can use R6 to set txd.
Does the JNOS PARAM statement work? That's what we used in the past with the other KISS TNC's.
Bill, WA7NWP
PS. Does your repeater reach South? I know of one existing 1200 baud packet repeater just North of Seattle but I don't think they have any IP activity there (yet...) _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
-
Antonio Querubin -
Bill Vodall -
Bob Scanferla -
Jerome Schatten -
John Wiseman -
Nick G4IRX -
Rob Janssen -
ve1jot