rasmus@napc.uucp (Rasmus Lerdorf) (03/22/91)
I have accepted a job in Porto Alegre, Brazil, and would like to know where and who to contact for either direct or indirect net access. Failing decent Internet or uucp networks, is there a satellite down there I could pop through via an RF modem just for a mail connection? -- Rasmus Lerdorf calgary!ajfcal!napc!rasmus 1020-64 Ave NE, Calgary NovAtel Advanced Product Concept Development Alberta, Canada T2E 7V8
pc@ctt.ctt.bellcore.com (03/29/91)
In article <1991Mar22.075213.5185@napc.uucp> rasmus@napc.uucp (Rasmus Lerdorf) writes: > I have accepted a job in Porto Alegre, Brazil, and would like to know > where and who to contact for either direct or indirect net access. > Failing decent Internet or uucp networks, is there a satellite down there > I could pop through via an RF modem just for a mail connection? i would investigate using the packet-radio network. phil karn (ka9q@thumper.bellcore.com) was good enough to develop TCP for just such use, with a PC. of course, you should be a licensed radio amateur for this. peter clitherow, bellcore, pc@bellcore.com 444 hoes lane, room 1h-213, piscataway, nj 08854-4182 (908) 699-3322
rasmus@napc.uucp (Rasmus Lerdorf) (03/30/91)
In article <1991Mar22.075213.5185@napc.uucp> rasmus@napc.uucp (Rasmus Lerdorf) writes: > I have accepted a job in Porto Alegre, Brazil, and would like to know > where and who to contact for either direct or indirect net access. > Failing decent Internet or uucp networks, is there a satellite down there > I could pop through via an RF modem just for a mail connection? In <1991Mar29.011537.10303@bellcore.bellcore.com> pc@ctt.ctt.bellcore.com writes: >i would investigate using the packet-radio network. phil karn >(ka9q@thumper.bellcore.com) was good enough to develop TCP for just such >use, with a PC. >of course, you should be a licensed radio amateur for this. Yes, that was what I meant when I asked about the satellite. I was referring to the sun-synchronous satellites the ham radio guys use. I do not have a ham radio license, but that can be fixed now that they don't require you top learn morse code anymore. I would feel a bit silly going through all the trouble of buying a radio, RF modem, getting a license and hacking the software and arrive to find full Internet access right in town. -- Rasmus Lerdorf calgary!ajfcal!napc!rasmus 1020-64 Ave NE, Calgary NovAtel Advanced Product Concept Development Alberta, Canada T2E 7V8
erhall@cdp.UUCP (04/03/91)
You may want to check with PeaceNet (institute for Global Communications, San Francisco (415)923-0900, <cdp!support@labrea.stanford.edu>). They've got access to the net via their mail and conference systems and access in Brazil via a network called AlterNex. AlterNex is based in Rio, but I would hope they'd have access from Porto Alegre. (AlterNex's number in Rio is +55 (21) 286-0348
hta@isolde.er.sintef.no (Harald Tveit Alvestrand) (04/09/91)
There are some simple tools available, you know....
Yes, there IS an Internet contact in Brazil.
Both the WHOIS database and the DNS agree about this.
The TRACEROUTE tells me that their main nameserver is 14 hops away from
Norway, but I can reach it.
I enclose the printouts...
Harald Tveit Alvestrand
Searcher of networks
Norway
isolde% whois br-dom
Fundacao de Amparo a Pesquisa do Estado de Sao Paulo (BR-DOM)
Rua Pio XI 1500 - CEP 05060
Sao Paulo
BRAZIL
Domain Name: BR
Administrative Contact:
Sala, Oscar (OS12) SALA%BRFAPESP.BITNET@CUNYVM.CUNY.EDU
+005511 261-0460
Technical Contact, Zone Contact:
Gomide, Alberto Courrege (ACG8) GOMIDE%BRFAPESP.BITNET@CUNYVM.CUNY.EDU
+005511 261-0460
Record last updated on 26-Mar-91.
Domain servers in listed order:
FPSP.FAPESP.BR 143.108.1.1
FNMFE.FNAL.GOV 131.225.17.150
Top Level domain for the Federative Republic of Brazil
For information concerning this domain, please consult
the Administrative Contact listed above.
isolde% query -t AXFR -h br.
br. 86400 IN SOA fpsp.fapesp.br. system.f
psp.fapesp.br. (
910204 ; serial
7200 ; refresh
7200 ; retry
3600000 ; expire
86400 ) ; min
br. 86400 IN NS fpsp.fapesp.br.
fpsp.fapesp.br. 86400 IN A 143.108.1.1
fpsp.fapesp.br. 86400 IN A 192.74.212.6
br. 86400 IN MX 0 fapq.fapesp.br.
br. 86400 IN MX 30 cunyvm.cuny.edu.
usp.br. 86400 IN NS fox.cce.usp.br.
fox.cce.usp.br. 86400 IN A 143.107.1.1
usp.br. 86400 IN NS fpspux.fapesp.br.
fpspux.fapesp.br. 86400 IN A 143.108.1.3
usp.br. 86400 IN MX 0 fapq.fapesp.br.
usp.br. 86400 IN MX 30 cunyvm.cuny.edu.
*.br. 86400 IN MX 0 fapq.fapesp.br.
*.br. 86400 IN MX 30 cunyvm.cuny.edu.
fapesp.br. 86400 IN NS fpsp.fapesp.br.
fpsp.fapesp.br. 86400 IN A 143.108.1.1
fpsp.fapesp.br. 86400 IN A 192.74.212.6
fapesp.br. 86400 IN MX 0 fapq.fapesp.br.
fapesp.br. 86400 IN MX 30 cunyvm.cuny.edu.
inpe.br. 86400 IN NS dem.inpe.br.
dem.inpe.br. 86400 IN A 143.108.1.1
inpe.br. 86400 IN MX 0 fapq.fapesp.br.
inpe.br. 86400 IN MX 30 cunyvm.cuny.edu.
isolde% traceroute 143.108.1.1
traceroute to 143.108.1.1 (143.108.1.1), 30 hops max, 40 byte packets
1 runit-gw.runit.sintef.no (129.241.1.2) 25 ms 10 ms 10 ms
2 no-gw.runit.sintef.no (128.39.9.1) 13 ms 12 ms 12 ms
3 nsf-gw.nordu.net (192.36.148.20) 235 ms 262 ms 72 ms
4 us-gw.nordu.net (192.36.148.65) 451 ms 895 ms 1019 ms
5 nss.jvnc.net (192.12.211.1) 682 ms * 299 ms
6 princeton.nj.nss.nsf.net (129.140.8.75) 369 ms 521 ms *
7 college_park.md.nss.nsf.net (129.140.73.8) 781 ms 253 ms 334 ms
8 college_park.md.nss.nsf.net (129.140.9.74) 455 ms 129.140.9.10 (129.140.9.1
0) 748 ms *
9 esnet.sura.net (192.80.214.252) 1344 ms 359 ms 228 ms
10 134.55.6.34 (134.55.6.34) 284 ms 816 ms 895 ms
11 * 134.55.5.225 (134.55.5.225) 777 ms 809 ms
12 134.55.5.161 (134.55.5.161) 809 ms 593 ms *
13 131.225.17.150 (131.225.17.150) 710 ms 1415 ms 963 ms
14 143.108.1.1 (143.108.1.1) 1795 ms 2410 ms *