[nos-bbs] problem with JNOS 2.0 and Linux Redhat 9.1
George (Skip) VerDuin
k8rra at ameritech.net
Mon Sep 11 09:06:16 EDT 2006
A couple small changes you might want to try also Joe:
Good luck with your mobile fleet...
On Sun, 2006-09-10 at 20:33 -0400, Joe Landers wrote:
> Hello Everyone
>
> I have a configuration problem and I cannot identify which is the
> problem I may give too much information but here it goes...
>
> The problem I have is on the JNOS side cannot connect to the Internet
> . I can ping up to the router but not outside the router to the Internet.
>
> On the Linux Side I can ping the Internet www.yahoo.com ...but not on JNOS.
>
> My host for my Internet is Comcast
>
> I also have forwarding on in linux.
>
> =========================================================
> Jnos ifconfig shows ...
>
> vhf IP addr 44.62.0.252 mtu 256 link excap AX25
> Link addr KE4EUE BBS ke4eue-8 paclen 256 irtt 1500
> BCtext : KE4EUE RACES mobile services Chesterfield Va.
> flags 0xcb0 trace 0x311 netmask 0x00000000 Broadcast 0.0.0.0
>
>
> tun0 IP addr 192.168.0.131 mtu 1500 link encap TUN
> flags 0x0 trace 0x0 netmask 0x00000255 broadcast 0.0.0.0
>
>
> loopback IP addr 127.0.0.1 mtu 65535 link encap none
> flags 0x0 trace 0x0 netmask 0xffffffff broadcast
> 255.255.255.255
>
> encap IP addr 0.0.0.0 mtu 65535 link encap none
> flags 0x0 trace 0x0 netmask 0xffffffff broadcast
> 255.255.255.255
>
> ============================================================
>
> Linux ifconfig shows
>
>
> eth0 Link encap: Ethernet HWaddr 00:04:5a:50:aa:e3
> inet addr 192.168.0.3 Bcast
> 192.168.0.255 mask 255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> rx packets : 319486 errors:0 dropped :0 overruns :0 frame:0
> tx packets : 9037 errors:0 dropped :0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:21172675 (20.1mb) TX bytes 1059932 (1.0mb)
> Interrupt :5 base address :0xb000
>
> lo link encap :local loopback
> ip addr 127.0.0.1 mask 255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets :663771 errors:0 dropped:0 overruns:0 frame:0
> TX packets: 663771 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> Rx bytes :45330598 (43.2mb) TX bytes : 45330598 (43.2mb)
>
> tun0 Link encap : point-to-point protocol
> inet addr:192.168.0.130 p-t-p:192.168.0.131 mask
> 255.255.255.255
> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 metric:1
> RX packets :1 errors:0 dropped:0 overruns:0 frame:0
> TX packets: 1 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:10
> Rx bytes :32 (32.0b) TX bytes : 32 (32.0b)
> ==================================================================
>
> Here is the routing from each
>
> Jnos
>
> Destination Len Interface
> Gateway Metric P timer use
> 44.0.0.0 8 vhf
> 1 man 0
> 192.168.0.1 32 tun0
> 1 man 1
> default 0 tun0
> 1 man 0
>
> ===========================================================================
> Linux
>
> Destination Gateway Genmask
> Flags Metric Ref use Iface
> 192.168.0.131 *
> 255.255.255.255 uh 0 0
> 0 tun0
This is OK if your gateway router can send packets here. In order for
the gateway to recognize the jnos end of tun0 ...131, you have two
choices to get this done:
Choice one: create an arp command at jnos initialization time to
announce to LAN the ...131 address with the MAC address of the eth0 port
Choice two: create a static route on the bridge router with the eth0 IP
as a gateway to ...131 netmask 255.255.255.255.
> 192.168.0.0 *
> 255.255.255.0 u 0 0
> 0 eth0
> 169.254.0.0 * 255.255.0.0
> u 0 0
> 0 eth0
> 127.0.0.0 * 255.0.0.0
> u 0 0
> 0 lo
> default 192.168.0.1 0.0.0.0
> ug 0 0
> 0 eth0
>
> =======================================================================================
>
> Here is my Autoexec.nos setup
>
> DNS server info
> domain addserver 192.168.0.1
> domain addserver 68.57.xxx.xxx (my Comcast ip)
The second address will usually be accessible by virtue of the
192.168.0.1 DNS, if you want another DNS you might want to choose a
non-ISP server.
>
>
> Ethernet setup
>
> ipaddress 44.62.0.252
> attach tun tun0 1500 0
> ifconfig tun0 ipaddress 192.168.0.131
> ifconfig tun0 netmask 255.255.255.0
> ifconfig tun0 mtu 1500
> pause 2
> shell ifconfig tun0 192.168.0.130 pointopoint 192.168.0.131 mtu 1500 up
>
> also down the line
> route add 192.168.0.1/36 tun0
There are only 32 bits in IPv4, and you have defined a Class C LAN, so
this probably would be well as a 192.168.0/24...
> route add default tun0
As pointed out before, this needs the gateway 192.168.0.1 parameter
added.
Some warnings exist against a "default" under jnos... Personally I have
not experienced a problem with it.
> route add 44/8 vhf
You probably don't mean this? This will send ALL 44 traffic to your one
radio but most of the world is unreachable...
Because you probably have 44... neighbors, you might want to add each
one individually as a RF route.
The AMPR.NET encap routes will allow you to reach the others - Check
into permissions to use these when you establish "public" Internet
neighbors.
> ===============================================================
>
> I hope I provided enough It seems like JNOS and Linux are not
> agreeing on the ports or jnos does not have permission but I am not
> sure how to set it if this is the problem.
>
> I would like some help with this as it is about the last thing I have
> on the ether net side to do .
>
>
> Thanks to everyone
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Joe Landers
> KE4EUE
> Assistant Emergency Radio officer for Chesterfield Co. Va.
> Owner: of the 145.390 repeater located in Chesterfield Co. Va.
> Advanced Skywarn Spotter Central Va. VCFD0022
> Director of Communications for Va. Special Olympics
> IRLP Node Owner on SySop for nodes 4407 & 4860
> Owner:Chesterfield RACES Mobile Communications Units
>
>
>
>
73
de Skip k8rra k
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20060911/05ad66ed/attachment.html>
More information about the nos-bbs
mailing list