[9fans] Cannot access hosts outside of LAN

[9fans] Cannot access hosts outside of LAN

[Nils M Holm]

Hello, 9fans.

Back in the 90's, I played with 2nd Edition for some time, but
finally stuck with Unix (Coherent, to be exact).

A few months ago, I 'rediscovered' Plan 9, downloaded it and
meanwhile, a PC running Plan 9 has replaced my X-terminal.

I am quite happy with it but somehow, I must be missing
something, since I do not manage to get IP networking working
right.

What I have done is to set up /lib/ndb/local. A copy is attached
to the end of this message. I can ping and telnet all Unix hosts
on the LAN, but accessing hosts outside of the LAN fails:

term% telnet tcp!symmetry!80 # host on LAN
connected to tcp!symmetry!80 on /net/tcp/1

term% telnet tcp!134.155.50.51!80 # host on WAN
telnet: connection timed out

Our firewall blocks ICMP, so I am using telnet for testing.

Any hints would be really appreciated.

Thank you for your help,

Nils.

----- /lib/ndb/local follows -----

ipnet=local
	ip=10.0.0.0
	ipmask=255.255.255.0
	ipgw=10.0.0.10
	dns=134.155.50.51
	dns=194.25.2.129

sys=nine
	ip=10.0.0.90
	ether=00A0241D0BED
	dom=nine.local
	proto=il

sys=symmetry
	ip=10.0.0.10
	ether=0060086458AC
	dom=symmetry.local

etc...
-- 
Nils M Holm <nmh@t3x.org> -- http://www.t3x.org/nmh/

Re: [9fans] Cannot access hosts outside of LAN

[Fco.J.Ballesteros]

[-- Attachment #1: Type: text/plain, Size: 78 bytes --]

you must use ipconfig to setup your interface.
I think this is in the wiki.

[-- Attachment #2: Type: message/rfc822, Size: 3377 bytes --]

From: Nils M Holm <nmh@t3x.org>
To: 9fans@cse.psu.edu
Subject: [9fans] Cannot access hosts outside of LAN
Date: Thu, 11 Mar 2004 08:48:17 +0100
Message-ID: <2004031107481700-70208@Symmetry.UUCP>


Hello, 9fans.

Back in the 90's, I played with 2nd Edition for some time, but
finally stuck with Unix (Coherent, to be exact).

A few months ago, I 'rediscovered' Plan 9, downloaded it and
meanwhile, a PC running Plan 9 has replaced my X-terminal.

I am quite happy with it but somehow, I must be missing
something, since I do not manage to get IP networking working
right.

What I have done is to set up /lib/ndb/local. A copy is attached
to the end of this message. I can ping and telnet all Unix hosts
on the LAN, but accessing hosts outside of the LAN fails:

term% telnet tcp!symmetry!80 # host on LAN
connected to tcp!symmetry!80 on /net/tcp/1

term% telnet tcp!134.155.50.51!80 # host on WAN
telnet: connection timed out

Our firewall blocks ICMP, so I am using telnet for testing.

Any hints would be really appreciated.

Thank you for your help,

Nils.

----- /lib/ndb/local follows -----

ipnet=local
	ip=10.0.0.0
	ipmask=255.255.255.0
	ipgw=10.0.0.10
	dns=134.155.50.51
	dns=194.25.2.129

sys=nine
	ip=10.0.0.90
	ether=00A0241D0BED
	dom=nine.local
	proto=il

sys=symmetry
	ip=10.0.0.10
	ether=0060086458AC
	dom=symmetry.local

etc...
-- 
Nils M Holm <nmh@t3x.org> -- http://www.t3x.org/nmh/

Re: [9fans] Cannot access hosts outside of LAN

[Nils M Holm]

On 2004-03-11, "Fco.J.Ballesteros" wrote:
> you must use ipconfig to setup your interface.

I run ipconfig at boot time:
ipconfig -h nine.local -g 10.0.0.10 ether /net/ether0 10.0.0.90 255.255.255.0

Nils.

-- 
Nils M Holm <nmh@t3x.org> -- http://www.t3x.org/nmh/

Re: [9fans] Cannot access hosts outside of LAN

[lucio]

> What I have done is to set up /lib/ndb/local. A copy is attached
> to the end of this message. I can ping and telnet all Unix hosts
> on the LAN, but accessing hosts outside of the LAN fails:
> 
You need to check that /net/iproute conatins a reasonable routing
table, amongst other possibilities.  Note that the subnet width is in
bits for IPv6.

No harm checking /net/ndb and /net/ipifc/0/local, either, for sanity.

I use the "sys" name in the "ipgw" field for the network, but I'm not
sure if that matters.

++L

Re: [9fans] Cannot access hosts outside of LAN

[Nils M Holm]

On 2004-03-11, lucio@proxima.alt.za wrote:
> You need to check that /net/iproute conatins a reasonable routing
> table, amongst other possibilities.  Note that the subnet width is in
> bits for IPv6.
>
> No harm checking /net/ndb and /net/ipifc/0/local, either, for sanity.

The routing table looks alright. If I read it correctly, the first
entry should direct outbound packages to the IP gateway (10.0.0.10):

0.0.0.0         /96  10.0.0.10       4    none   -
10.0.0.0        /120 10.0.0.0        4i   ifc    0
10.0.0.0        /128 10.0.0.0        4b   ifc    -
10.0.0.90       /128 10.0.0.90       4u   ifc    0
10.0.0.255      /128 10.0.0.255      4b   ifc    -
10.255.255.255  /128 10.255.255.255  4b   ifc    -
255.255.255.255 /128 255.255.255.255 4b   ifc    -

/Net/ndb looks fine, too:

ip=10.0.0.90 ipmask=/120 ipgw=10.0.0.10
	sys=nine
	dom=nine.local

> I use the "sys" name in the "ipgw" field for the network, but I'm not
> sure if that matters.

If have tried it, but it does not make a difference.

What is /net/ipifc/0/local about? I cannot find it in the manual.

Nils.

-- 
Nils M Holm <nmh@t3x.org> -- http://www.t3x.org/nmh/

Re: [9fans] Cannot access hosts outside of LAN

[lucio]

> 
> The routing table looks alright. If I read it correctly, the first
> entry should direct outbound packages to the IP gateway (10.0.0.10):
> 
> 0.0.0.0         /96  10.0.0.10       4    none   -
> 10.0.0.0        /120 10.0.0.0        4i   ifc    0
> 10.0.0.0        /128 10.0.0.0        4b   ifc    -
> 10.0.0.90       /128 10.0.0.90       4u   ifc    0
> 10.0.0.255      /128 10.0.0.255      4b   ifc    -
> 10.255.255.255  /128 10.255.255.255  4b   ifc    -
> 255.255.255.255 /128 255.255.255.255 4b   ifc    -
> 
That resembles what I have, too.  Presumably that means ipgw is being
understood correctly.

Hm, not quite!  Note:

0.0.0.0         /96  172.24.16.129   4    none   0
172.24.0.0      /112 172.24.0.0      4i   ifc    0
172.24.0.0      /128 172.24.0.0      4b   ifc    -
172.24.16.12    /128 172.24.16.12    4u   ifc    0
172.24.255.255  /128 172.24.255.255  4b   ifc    -
255.255.255.255 /128 255.255.255.255 4b   ifc    -

there is a "0" at the end of the first line.  I think 10.0.0.10 is not
reachable as there isn't an interface assigned to it.  Only a guess,
mind you, nor do I know why that is the case.

> /Net/ndb looks fine, too:
> 
> ip=10.0.0.90 ipmask=/120 ipgw=10.0.0.10
> 	sys=nine
> 	dom=nine.local
> 
Yes, looks fine to me.  Except the ipmask ought to be 255.255.255.0,
I'm not sure if the /120 notation is just something I'm not familiar
with.  Maybe your arguments to ip/ipconfig are not exactly right?

> What is /net/ipifc/0/local about? I cannot find it in the manual.
> 
That's what ip/ipconfig produces, linking IP over the ether0
interface.  What do you have in there?  Try

cpu% lookman ipifc
man 2 ip # ip(2)
man 3 ip # ip(3)

Can you "ip/ping" the gateway or does it block ICMP that far back?  If
so, can you telnet there?

Also, take a peek at /net/arp.

I must confess I would expect your configuration to work, whatever is
wrong, it is not quite where I would expect it to be.

++L

Re: [9fans] Cannot access hosts outside of LAN

[Geoff Collyer]

What kind of machine is `symmetry'?  Does it correctly gateway
connections from other systems on your network 10?  What ports does it
allow through from the inside?

Re: [9fans] Cannot access hosts outside of LAN

[Nils M Holm]

On 2004-03-11, Geoff Collyer wrote:
> What kind of machine is `symmetry'?  Does it correctly gateway
> connections from other systems on your network 10?  What ports does it
> allow through from the inside?

Stupid me. Symmetry (a FreeBSD host acting as a gateway) did
not supply routing information to other hosts. After killing
routed(8) on the gateway and restarting it with the proper flags,
everything works like a charm.

Long story:

Some days ago, we a had a power outage that could not be
compensated by the UPS. After re-booting, Symmetry came up
with the default routing flags (quiet). I had started
'routed -s' manually months ago while upgrading the system.

I *knew* there was something, I wanted to fix in /etc/rc.conf.
No I know.

This error was not detected earlier, because all other clients
on the LAN are X-terminals that are connected directly to the
gateway.

Many thanks to all who replied and sorry for wasting your time.

Nils.

-- 
Nils M Holm <nmh@t3x.org> -- http://www.t3x.org/nmh/

RE: [9fans] Cannot access hosts outside of LAN

[Tiit Lankots]

> What is /net/ipifc/0/local about? I cannot find it in the manual.

I think lucio meant /net/ipselftab. See ip(3).

RE: [9fans] Cannot access hosts outside of LAN

[lucio]

>> What is /net/ipifc/0/local about? I cannot find it in the manual.
> 
> I think lucio meant /net/ipselftab. See ip(3).

No, I didn't ;-)

I wouldn't recognise an ipselftab if it bit me.

++L

Re: [9fans] Cannot access hosts outside of LAN

[David Presotto]

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

I can't see what you might have done wrong.

That routing table looks fine to me.  The gateway is correct
though the '-' at the end means that the default entry has
never been chosen as a route.  It is normally the next hop
interface for route.  It gets filled in whenever the route
is chosen for a packet; it's a cache to avoid the interface
lookup every time.  Did  you cat this out before trying to
connect to something off of the 10 net?

If this table was after failing to connect to an off LAN system,
then it means that it couldn't find an interface when you
tried to connect.  That I really don't understand.  What's
the output of 'netstat -i'?

Something you can do.

1) open a window, set it scrolling

echo set ip > /net/log
cat /net/log

2) open another window, set it scrolling

snoopy

3) open yet another window

tcp!134.155.50.51!80

If that doesn't immediately tell you something, send me all
the output.

[-- Attachment #2: Type: message/rfc822, Size: 3463 bytes --]

From: Nils M Holm <nmh@t3x.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Cannot access hosts outside of LAN
Date: Thu, 11 Mar 2004 10:45:02 +0100
Message-ID: <2004031109450200-70412@Symmetry.UUCP>


On 2004-03-11, lucio@proxima.alt.za wrote:
> You need to check that /net/iproute conatins a reasonable routing
> table, amongst other possibilities.  Note that the subnet width is in
> bits for IPv6.
>
> No harm checking /net/ndb and /net/ipifc/0/local, either, for sanity.

The routing table looks alright. If I read it correctly, the first
entry should direct outbound packages to the IP gateway (10.0.0.10):

0.0.0.0         /96  10.0.0.10       4    none   -
10.0.0.0        /120 10.0.0.0        4i   ifc    0
10.0.0.0        /128 10.0.0.0        4b   ifc    -
10.0.0.90       /128 10.0.0.90       4u   ifc    0
10.0.0.255      /128 10.0.0.255      4b   ifc    -
10.255.255.255  /128 10.255.255.255  4b   ifc    -
255.255.255.255 /128 255.255.255.255 4b   ifc    -

/Net/ndb looks fine, too:

ip=10.0.0.90 ipmask=/120 ipgw=10.0.0.10
	sys=nine
	dom=nine.local

> I use the "sys" name in the "ipgw" field for the network, but I'm not
> sure if that matters.

If have tried it, but it does not make a difference.

What is /net/ipifc/0/local about? I cannot find it in the manual.

Nils.

-- 
Nils M Holm <nmh@t3x.org> -- http://www.t3x.org/nmh/