Levantamento Parcial da Rede Informática do ISCTE

Transcrição

Instituto Superior de Ciências do Trabalho e da Empresa
SISTEMAS DE COMUNICAÇÃO INTEGRADOS
UIÃO
Levantamento Parcial da
Rede Informática do ISCTE
Docente: Professor Doutor Miguel Dias
Discente:
João Nascimento
Lisboa, 11 de Abril de 2001
Sistemas de Comunicação Integrados
Guião
ÍNDICE
I. Introdução ..........................................................................................................................1
II. Aplicação dos Comandos (Dos) .......................................................................................2
ANEXO I - Comandos Utilizados (Dos) .............................................................................21
1. ARP (Address Resolution Protocol) ......................................................................................................22
2. Ping ........................................................................................................................................................22
3. Route......................................................................................................................................................23
4. FTP (File Transfer Protocol)..................................................................................................................25
5. TELNET (File Transfer Protocol)..........................................................................................................25
6. IPCONFIG .............................................................................................................................................26
7. TRACERT .............................................................................................................................................26
8. NETSTAT..............................................................................................................................................27
9. Nslookup................................................................................................................................................27
ANEXO II - Comandos Utilizados (Unix) ..........................................................................29
FTP ............................................................................................................................................................30
TRACEROUTE .........................................................................................................................................39
ARP............................................................................................................................................................43
NSLOOKUP(1C).......................................................................................................................................46
PING ..........................................................................................................................................................50
NVRAM ....................................................................................................................................................54
IFCONFIG .................................................................................................................................................55
NETSTAT..................................................................................................................................................57
TELNET ....................................................................................................................................................59
ANEXO III ............................................................................................................................69
ANEXO IV ............................................................................................................................99
ANEXO V ...........................................................................................................................108
M estrado e m Ge stã o d e Siste ma s d e Info rma ç ã o
2000/2001
i
Guião
I. Introdução
Este trabalho é o resultado da realização, passo a passo, do Guião proposto para o
levantamento parcial da rede informática do ISCTE. Após um breve momento de
familiarização com os comandos próprios para conseguir realizar as tarefas incluídas no
guião, deu-se início aos trabalhos. A rede do ISCTE encontra-se baseada na família de
protocolos TCP/IP, apesar de ligar equipamentos informáticos utilizando pelo menos os
sistemas operativos UNIX, Windows NT e LINUX. Por este motivo foram utilizados os
comandos:
Ao nível do MS-Dos: ftp, telnet, Ping, tracert, arp, ipconfig, netstat, nslookup e route.
Qualquer informação mais detalhada sobre qualquer um destes comandos, pode ser
encontrada no Anexo I – Comandos Utilizados (MS-Dos).
A nível do UNIX: Ping, traceroute, arp, nvram, ifconfig e netstat. Qualquer informação
mais detalhada sobre qualquer um destes comandos, pode ser encontrada no Anexo II –
Comandos Utilizados (Unix). Dado que o sistema operativo não disponibiliza informação em
português, não foi possível realizar a tradução do texto em tempo útil, pelo que a Lista de
comandos Unix encontra-se em Inglês.
Os comandos utilizados em UNIX são idênticos aos utilizados em Dos, existindo as seguintes
correspondências:
Comando em DOS
ARP
Ping
Route
FTP
telnet
IPConfig
Tracert
Netstat
nslookup
Comando em UNIX
arp
ping
ftp
telnet
ifconfig
traceroute
netstat
nslookup
2000/2001
Diferenças
-
1
Guião
II. Aplicação dos Comandos (Dos)
Questão 5.
A pergunta 5 do guião pretende que, a partir do Dos, se faça a caracterização do
computador onde o trabalho foi desenvolvido.
a) começando pela camada física, esta alínea pede explicitamente o endereço ETHERNET
do computador. Este endereço, também conhecido por MAC Address (Medium Access
Control Address – Endereço de Controlo de Acesso ao Meio), encontra-se definido ao
nível físico do protocolo TCP/IP, sendo atribuído à placa de rede instalada no
computador pelo fabricante da mesma. Este código é único no mundo, não existindo
duas placas com Endereços MAC iguais. Para obter esta identificação a partir do
MSDOS é necessário utilizado o comando IPCONFIG com a opção /ALL.
Para poder responder a esta pergunta foi executado o comando:
C:>IPCONFIG /ALL
O resultado do comando foi:
Windows NT IP Configuration
Host Name . . . . . . . . . : i0s05-14.students.iscte.pt
DNS Servers . . . . . . . . : 10.10.10.2
193.136.188.1
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : No
Ethernet adapter RTL81391:
Description . . . . .
Physical Address. . .
DHCP Enabled. . . . .
IP Address. . . . . .
Subnet Mask . . . . .
Default Gateway . . .
DHCP Server . . . . .
Lease Obtained. . . .
Lease Expires . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
:
:
:
:
:
:
:
:
:
Realtek 8139-series PCI NIC
00-4F-4E-00-0C-92
Yes
10.10.10.112
255.255.255.0
10.10.10.254
10.10.10.2
Quarta-feira, 28 de Março de 2001 13:24:01
Quinta-feira, 29 de Março de 2001 09:24:01
Através deste quadro é possível dizer que o Endereço ETHERNET da placa de rede instalada
no computador é 00-4F-4E-00-0C-92. Este valor é dado pela rubrica Physical Address.
b) Passando agora para um nível acima na pilha de protocolos TCP/IP, são pedidas
informações da camada de rede. Em primeiro lugar o Número IP. Este número que é
atribuído a um computador da rede, pelo administrador do sistema, ou pelo serviço
DHCP identifica numericamente o computador perante a rede. É constituído por quatro
segmentos de 8 bits cada, prefazendo 32 bits de informação. Ao serem traduzidos para
base decimal, são apresentados num intervalo de 0 a 255.
2000/2001
2
Guião
O comando utilizado a nível do MS-DOS, para saber o endereço IP do computador é o
mesmo que foi utilizado no ponto anterior (IPConfig /ALL). Através do resultado
anteriormente, é possível obter o número pretendido no campo IP Address. Neste
campo pode observar-se o número: 10.10.10.112. Pode então concluir-se que foi
adoptado um número para redes privadas, dado que o endereço começa por 10.
Este
número
é
o
resultado
da
conversão
do
código
00001010.00001010.00001010.01110000 em binário (código efectivamente tratado
pelo computador) para o sistema decimal.
De seguida é solicitada a Máscara de Rede. Esta configuração permite estabelecer subredes, estabelecendo divisões lógicas no interior de uma rede. O comando IPConfig
/ALL também permite, neste ambiente (MS-DOS), saber a Máscara da Rede a que o
computador está ligado. Através do campo Subnet Mask, no quadro anterior, obtém-se
255.255.255.0. É, portanto, uma rede tipo C, dado que apenas dispõe de 8 bits (último
segmento a zero) dedicados a hosts (computadores) e os restantes (primeiros três
segmentos a 255 – que em linguagem binário corresponde a 11111111) são utilizados
para identificar a rede.
Na sub-rede identificada, podem ser atribuídos endereços de IP entre 10.10.10.1 até ao
10.10.10.254. Isto porque a Máscara de Sub-rede é 255.255.255.0, o que quer dizer que
os primeiros octetos (10.10.10) são fixos para os hosts que queiram pertencer à sub-rede
e o último segmento pode variar. Como a composição de cada octeto tem um
comprimento de 8 bits (8 dígitos binários), podem ser atribuídos número de 00000000
até 11111111. Em decimal 0 a 255. No entanto o 0 (em binário - 00000000) é atribuído
à rede (10.10.10.0) e o 255 (em binário – 11111111) é o endereço broadcast
(10.10.10.255), ou seja o endereço comum a todos os computadores (ao ser lançado na
rede uma mensagem para este endereço todos os computadores farão a sua leitura).
O nome DNS (Domain Name Server – Servidor de Nomes dos Domínios) do
computador actual, é o nome pelo qual ele é conhecido na rede, em alternativa ao
endereço de IP a ao MAC Address. Por uma questão de facilidade para os humanos em
decorar nomes e não números criou-se este conceito. Esta identificação pode ser obtida
também pelo comando anterior IPConfig /ALL. No campo Host Name, é possível ler
i0s05-14.students.iscte.pt, que é, no fundo, o nome que está associado ao
Endereço de IP 10.10.10.112.
O número do router por defeito, ou seja, a identificação na rede do dispositivo a quem é
entregue toda a informação enviada pelo computador actual para a rede, é também
obtido no resultado do comando IPConfig /All. Este comando, devido à opção /ALL,
devolve um grupo importante de informação. No campo Default Gateway, pode ler-se o
que se pretende neste ponto, ou seja: 10.10.10.254. Este é o endereço responsável por
reencaminhar correctamente a informação que sai do computador onde decorre a
execução deste guião.
2000/2001
3
Guião
Por fim, nesta questão é ainda solicitada informação adicional sobre o router por
defeito. Neste caso o Nome, em vez do Endereço IP. Para se obter esta informação, o
comando utilizado até aqui não basta. É necessário utilizar um outro – nslookup. Este
permite traduzir (resolver) um determinado endereço IP para o Nome respectivo. De
facto, ao executar este comando com um endereço IP é solicitado ao DNS Server
(também visível através do comando IPConfig /all, como sendo 10.10.10.2 ou
193.136.188.1) o nome correspondente. Neste caso, para responder à questão foi
necessário executar o comando: nslookup 10.10.10.254, tendo-se obtido o seguinte
resultado:
nslookup 10.10.10.254
Server: socrates.students.iscte.pt
Address: 10.10.10.2
Name:
fwi.students.iscte.pt
Address: 10.10.10.254
Isto permite dizer que o nome do Router por defeito é fwi.students.iscte.pt.
Questão 6.
A pergunta 6 do guião pretende que se faça a caracterização do Servidor de Nomes de
Domínio. Este é o elemento da rede que armazena uma tabela que relaciona o Endereço
de IP dos computadores e o seu nome agradável ao utilizador. Este elemento é o
responsável por determinar a localização do computador de destino de uma mensagem e
de a encaminhar para ele através da rede.
Para responder à questão colocada sobre o Nome do Servidor de Nomes de Domínio,
existem, pelo menos, duas formas: utilizando o nslookup sobre um qualquer Endereço
IP da rede, ou utilizar o comando nslookup sobre o endereço IP determinado através do
IPConfig /all. No primeiro caso, basta olhar para o resultado do último comando
executado anteriormente e retirar a primeira indicação de Server:. A segunda forma
seria executar o comando nslookup 10.10.10.2
nslookup 10.10.10.2
Server: socrates.students.iscte.pt
Address: 10.10.10.2
Name: socrates.students.iscte.pt
Address: 10.10.10.2
Seja como for, o resultado obtido é o mesmo: socrates.students.iscte.pt
2000/2001
4
Guião
A segunda questão colocada neste ponto do guião pretende que se proceda à
identificação do Endereço IP do Servidor de Nomes de Domínio. Esta informação foi
obtida anteriormente com o comando IPConfig /All, no campo DNS Servers como
sendo 10.10.10.2. Ainda é possível observar que o Endereço de IP do Servidor de
DNS Secundário é 193.136.188.1. Fazendo o nslookup a este endereço, fica-se a
saber que tem o nome iscte.iscte.pt.
Questão 7.
A pergunta 7 do guião pretende que se identifique o endereço Ethernet do router por
defeito, ou seja, pretende-se saber qual o endereço físico da placa de rede instalada no
Router por defeito (e pela qual ele comunica). Para se obter a resposta a esta questão
tem de se seguir um conjunto de passos: 1º realizar o Ping ao endereço IP (conhecido
através do campo Default Gateway, do comando IPConfig /all, como sendo
10.10.10.254) desse elemento da rede, por forma a que os seus dados sejam
armazenados na ARP Table e, posteriormente, através do comando arp –a, obter todos
os dados dessa tabela (que agora incluem o do router por defeito. Os passos foram
realizados e deram estes resultados:
Ping 10.10.10.254
Pinging 10.10.10.254 with 32 bytes of data:
Reply from 10.10.10.254: bytes=32 time<10ms
Arp -a
Interface: 10.10.10.112
Internet Address
10.10.10.8
10.10.10.10
10.10.10.12
10.10.10.254
on Interface 2
Physical Address
00-80-5f-0d-2d-e0
00-d0-b7-d3-60-0b
00-80-5f-bb-68-f4
00-4f-4e-06-a9-d7
TTL=255
TTL=255
TTL=255
TTL=255
Type
dynamic
dynamic
dynamic
dynamic
Pelo que se pode ver, o Physical Address (ou seja o Endereço Ethernet) do router por
defeito é 00-4f-4e-06-a9-d7.
Questão 8.
Nesta questão é solicitada uma descrição pormenorizada de todas as rotas IP que estão
configuradas no computador onde decorre o teste. O comando a utilizar para obter
informação de base à resposta a esta questão é route com a opção print. O resultado é o
seguinte:
2000/2001
5
Guião
route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 4f 4e 00 0c 92 ...... Realtek 8139-series PCI NIC
===========================================================================
===========================================================================
Active Routes:
Network Destination
Netmask
Gateway
Interface Metric
0.0.0.0
0.0.0.0
10.10.10.254
10.10.10.112
1
10.10.10.0
255.255.255.0
10.10.10.112
10.10.10.112
1
10.10.10.112 255.255.255.255
127.0.0.1
127.0.0.1
1
10.255.255.255 255.255.255.255
10.10.10.112
10.10.10.112
1
127.0.0.0
255.0.0.0
127.0.0.1
127.0.0.1
1
224.0.0.0
224.0.0.0
10.10.10.112
10.10.10.112
1
255.255.255.255 255.255.255.255
10.10.10.112
10.10.10.112
1
===========================================================================
A primeira linha evidencia a configuração do router por defeito, ou seja, qualquer endereço
desconhecido deverá ser encaminhado para o endereço aqui especificado (10.10.10.254).
A segunda linha da tabela de rotas mostrada em cima, servirá para quando o Computador
estiver a trabalhar em modo local. Os recursos serão procurados no interior do próprio
computador.
A terceira linha, como se pode ver tem o Network Destination igual ao Endereço de IP do
computador actual. Esta linha servirá para indicar à camada IP que o endereço 10.10.10.112 é
o próprio computador. Permite ainda verificar se o IP está configurado, ou não
Na quarta linha é possível definir o endereço da rede de broadcast.
Na quinta linha aparece a rota criada pelo protocolo TCP/IP. Esta existe em todos os
computadores.
As duas linhas seguintes identificam ambas rotas para redes IP. O endereço 224.0.0.0
identifica o endereço para rede IP multicast e a última linha especifica o endereço da própria
rede a que o computador pertence. Qualquer mensagem que seja dirigida a esta rede é também
entregue neste computador, independentemente de a ler ou rejeitar.
Questão 9.
Até a este momento do guião, o sistema operativo em que se baseavam as perguntas era
o MS-Dos (dentro no Windows NT). A partir daqui, para experimentar os mesmos
efeitos num outro sistema operativo para além do Ms-Dos, irá ser utilizado o UNIX.
Este sistema operativo encontra-se instalado numa outra máquina remota, que é
necessário aceder através do software TELNET, por forma a poder executar comandos
nessa máquina e, assim tentar responder às questões colocadas e caracterizar a máquina
em questão.
O computador em causa está identificado na rede como indy1.adetti.iscte.pt.
Neste momento a informação disponível sobre esta máquina, é apenas o nome DNS e o
login e password para podermos iniciar uma sessão TELNET.
2000/2001
6
Guião
Para aceder à máquina remota (que se encontra ligada ao computador actual) é
necessário executar o comando: TELNET indy1.adetti.iscte.pt. Com isto
será pedida uma Login e uma Password, às quais é necessário responder acertadamente.
Uma vez em sessão é possível começar a responder às questões.
A
primeira
questão
é
o
Endereço
ETHERNET
do
computador
(indy1.adetti.iscte.pt). Já que estamos em sessão, basta utilizar o comando
nvram, para obtermos uma lista completa das características da máquina.
nvram
dbaud=9600
tapedevice=
root=
swap=
showconfig=isfalse
initfile=
initstate=
swaplo=
nswap=
sync_on_green=
console=g
gfx=alive
keybd=
nogfxkbd=
cpufreq=200
monitor=
pagecolor=
screencolor=
logocolor=
diskless=0
srvaddr=
netaddr=192.0.2.1
diagmode=
hostname=
dlserver=
dlgate=
dllogin=
maxpmem=
debug_bigmem=
eaddr=08:00:69:08:27:b2
rdebug=
dbgmon=
nodbgmon=
volume=80
scsiretries=
scsihostid=
scsi_syncenable=
SystemPartition=scsi(0)disk(1)rdisk(0)partition(8)
OSLoadPartition=scsi(0)disk(1)rdisk(0)partition(0)
OSLoader=sash
2000/2001
7
Guião
OSLoadFilename=/unix
OSLoadOptions=auto
AutoLoad=Y
sgilogo=y
rbaud=
passwd_key=
rebound=
scsihostid=
prompoweroff=
impactgm=
triton_invall=
Com base neste resultado, consegue-se facilmente chegar ao que se pretende através do
campo eaddr – Ethernet Address. Como é possível ver, trata-se do endereço
08:00:69:08:27:b2.
A alínea b) da questão pretende que se faça a identificação do endereço IP do
computador em que decorre a sessão remota (indy1.adetti.iscte.pt). Para tal
é necessário utilizar o comando próprio do Unix: ifconfig. Este comando requer uma
interface que foi disponibilizada pelo Professor como sendo ec0. Executando o
comando completo:
ifconfig ec0
ec0: flags=c63<UP,BROADCAST,NOTRAILERS,RUNNING,FILTMULTI,MULTICAST>
inet 193.136.190.34 netmask 0xffffffe0 broadcast 193.136.190.63
obtém-se diversas informações necessárias a esta alínea e às seguintes. É visível o
Endereço IP, no início da última linha - inet 193.136.190.34.
Uma questão se coloca ao chegar a este ponto: “ sendo as redes completamente distintas
na forma de se identificar (note-se que o primeiro computador, onde se iniciou este
guião, tinha um endereço 10.10.10.112 e o actual tem um endereço IP 193.136.190.34),
como se conseguem encontrar na rede. Sim, porque ao executar o Telnet os
computadores têm de estar ligados física e logicamente. Se têm endereços tão distintos,
à partida não se conseguiriam avistar na rede. A resposta a esta questão encontra-se
mais à frente quando o caminho inverso for percorrido. Nessa altura veremos que existe
um ponto em comum entre as duas redes.
Através do comando anterior, é também possível identificar a Máscara de Rede
(netmask). Neste caso temos a indicação de que o computador se encontra numa subrede com a máscara 0xffffffe0. Esta informação encontra-se num formato hexadecimal,
sendo necessário traduzir este número para a base decimal, por forma a ter uma
representação na forma mais comum. Procedendo dessa forma obtemos a máscara de
rede 255.255.255.224. Esta informação é relevante, pois permite compreender um
pouco mais de como a rede está segmentada.
2000/2001
8
Guião
O facto de o último octeto da máscara de rede se encontrar preenchido com o número
224, deixa perceber que os 3 bits mais significativos do último octeto estão reservados
para sub-redes. É possível chegar a esta conclusão quando traduzimos o número para
binário (224(10) = 11100000(2)). Por este motivo, podemos concluir que o computador
está inserido numa rede segmentada em 6 sub-redes (23 – 2 = 6). O operando 23 - porque
ao termos 3 bits temos combinações possíveis de redes. Subtrai-se 2 porque a sub-rede
não pode ser identificada pela combinação 000 nem 111. Retirando estas duas
combinações ficamos com 6. Podemos ainda inferir que, em cada sub-rede, apenas é
possível ter 30 hosts. Isto porque, dos 8 bits do octeto, ficam disponíveis apenas 5 bits
para estes elementos. Fazendo contas 25 – 2 = 30 . Novamente se subtraem 2 (00000 e
11111). Desta forma apenas se podem utilizar 180 endereços dos 254 disponíveis (se
octeto estivesse preenchido com 0 - Zero). Isto representa uma percentagem de
utilização de 71%.
Para responder à questão “Quais os números de rede IP que são válidos nesta subrede?”, ter-se-á de realizar alguns cálculos. O endereço IP do computador em análise é,
como já se disse, 193.136.190.34. O 34 decomposto em binário ficará em 00100010.
Atendendo à explicação feita no parágrafo anterior, estamos em presença de um
computador na primeira sub-rede, uma vez que encontramos 1s apenas no bit menos
significativo de entre os bits atribuídos às sub-redes (os três mais significativos).
0
0 1
Sub-rede
0
0
0 1
Hosts
0
0
0 1
Hosts
0
Como não podemos ter o endereço: 000
0
0 0
Sub-rede
0
A primeira sub-rede é efectivamente 001.
Como não é possível ter o endereço 00000, na componente Hosts, nem 11111, o
intervalo permitido situa-se entre 00001 e 11110. Associando à componente de sub-rede
temos um intervalo final entre 00100001 e 00111110. Traduzindo para decimal obtémse o intervalo 33 a 62. Compondo todo o endereço completo teremos u intervalo de
193.136.190.33 a 193.136.190.62. Por último, pode inferir-se que o endereço da rede
será 193.136.190.32 (que não se pode atribuir a nenhum host e que resulta de ter a parte
host a zero – 00100000 = 32) e o endereço broadcast será 193.136.190.63 (que também
não se pode atribuir a nenhum host e que resulta de ter a parte host tudo a 1 – 00111111
= 63), tal como se pode comprovar no campo broadcast do resultado do comando
ifconfig ec0.
A resposta à questão “Qual o seu nome DNS” é a mais óbvia de todo o guião, já que foi
exactamente por aí que se começou a segunda parte do mesmo (a entrada no UNIX).
Para ser possível o acesso utilizou-se precisamente o Nome de DNS. Portanto, a
resposta será, obviamente, indy1.adetti.iscte.pt.
A próxima questão solicita que seja indicado o IP do router por defeito. Este endereço
tem de estar dentro da sub-rede, por forma a que o computador possa colocar os seus
pedidos directamente. Para ter acesso a esta informação é necessário recorrer ao
comando netstat. Utilizando os parâmetros nr (n, para ver os endereços em formato
numérico e r, para mostrar as rotas). Podemos obter o seguinte:
2000/2001
9
netstat -nr
Routing tables
Destination
127.0.0.1
193.136.190.34
default
224.0.0.0
193.136.190.32
Gateway
Flags
127.0.0.1
UH
127.0.0.1
UH
193.136.190.59
UG
193.136.190.34
U
193.136.190.34
U
Guião
MTU
0
0
0
0
0
RTT RTTvar
0
0
0
0
0
0
0
0
0
0
Use Interface
1171 lo0
1086 lo0
56882 ec0
2604 ec0
26842 ec0
Deste resultado, pode retirar-se a informação pretendida. Na coluna Destination,
encontra-se a descrição default. Nesta linha o valor encontrado na coluna Gateway dá o
endereço do Gateway (router) por defeito. Neste caso é 193.136.190.59.
A questão seguinte, inevitavelmente, solicita o Nome DNS do router por defeito. Entre
as várias formas de obter este informação, pode consultar-se utilizando o comando Arp
–a para consultar a tabela ARP. Procedendo desta forma, obtém-se:
Arp -a
indigoxz.adetti.iscte.pt (193.136.190.33) at 8:0:69:7:67:2b
o2video.adetti.iscte.pt (193.136.190.35) at 8:0:69:5:bb:7a
lablin1.adetti.iscte.pt (193.136.190.36) at 8:0:0:52:36:7
labserver.adetti.iscte.pt (193.136.190.49) at 0:60:8:1f:cd:67
lablin2.adetti.iscte.pt (193.136.190.51) at 0:0:e8:3d:be:5a
? (193.136.190.57) at 0:c0:7b:7b:d2:63
gtadetti.adetti.iscte.pt (193.136.190.59) at 0:0:e8:49:89:bc
fore-switch-eth.adetti.iscte.pt (193.136.190.62) at 0:80:42:9:c:99
Como é possível observar o nome do host a que corresponde o endereço IP em questão
é encontrado na 8ª linha: gtadetti.adetti.iscte.pt (193.136.190.59). A resposta
é: gtadetti.adetti.iscte.pt
Se, eventualmente, este endereço ainda não se encontrasse nesta tabela, poder-se-ia
utilizar o comando Ping ao endereço em questão, por forma ser acrescentado. Logo de
seguida, ao executar o comando Arp, poder-se-ia então obter a informação.
Questão 10.
Passando à questão 10, será agora feita a caracterização do Servidor de Nomes de
Domínio. Começando por tentar obter o Endereço IP, pode obter-se de seguida o Nome.
Para tal utilizar-se-á o comando nslookup, sem qualquer parâmetro. Desta forma apenas
responderá o Servidor de Nomes de Domínio, entrando em sessão.
nslookup
Default Server: iscte.iscte.pt
Address: 193.136.188.1
>
2000/2001
10
Guião
Com o endereço IP é, então, possível saber o nome DNS, através do mesmo comando,
mas agora utilizando como parâmetro este endereço:
nslookup 193.136.188.1
Server: iscte.iscte.pt
Address: 193.136.188.1
Name: iscte.iscte.pt
Address: 193.136.188.1
Pode dizer-se que o Servidor de Nome de Domínio tem o endereço IP: 193.136.188.1 e
o Nome iscte.iscte.pt.
Voltando um pouco atrás no guião, na questão 6 (ainda na máquina NT) obteve-se o
mesmo endereço para o Servidor de Nomes de Domínio Secundário. É precisamente
neste ponto que as redes se cruzam (a do Unix e a do NT). É esta a máquina que faz a
interligação entre as redes, permitindo que ambas se vejam.
Questão 11.
Neste ponto do Guião, é necessário recorrer de novo ao comando Arp –a por forma a
identificar o endereço ETHERNET do router por defeito.
Arp -a
labserver.adetti.iscte.pt (193.136.190.49) at 0:60:8:1f:cd:67
? (193.136.190.57) at 0:c0:7b:7b:d2:63
Com o resultado deste comando, sabendo ainda que o router por defeito tem o endereço
IP 193.136.190.59 (como ficou provado na parte final da resposta à questão 6), basta
procurá-lo na lista e verificar o que diz a última coluna da linha correspondente.
Verifica-se que a linha do router por defeito é, neste caso, a penúltima. Assim sendo, o
endereço Ethernet é 0:0:e8:49:89:bc.
Questão 12.
À semelhança do que foi feito na questão 8 (ainda em Ms-Dos), é agora necessário
descrever as rotas configuradas no computador Unix. Para ser possível fazê-lo, é
necessário obter informação com o comando netstat –nr, tal como o foi naquela altura.
O resultado é ligeiramente diferente, dado que se trata de um equipamento diferente,
como se pode ver no resultado do comando que se mostra a seguir:
2000/2001
11
netstat -nr
Routing tables
Destination
Interface
127.0.0.1
193.136.190.34
default
224.0.0.0
193.136.190.32
Guião
Gateway
127.0.0.1
127.0.0.1
193.136.190.59
193.136.190.34
193.136.190.34
Flags
UH
UH
UG
U
U
MTU
0
0
0
0
0
RTT RTTvar
0
0
0
0
0
0
0
0
0
0
1192
1126
60309
2616
26928
Use
lo0
lo0
ec0
ec0
ec0
O conjunto de linhas que se encontra acima, permite concluir que existe duas rotas definidas
para Host (UH), como sendo 127.0.0.1 e 193.136.190.34; uma rota definida por omissão
(UG), como sendo 193.136.190.59; e, por fim, duas rotas de redes (U), como sendo 224.0.0.0
e 193.136.190.32.
A primeira linha da tabela de rotas mostrada em cima, servirá para quando o Computador
estiver a trabalhar em modo local. Os recursos serão procurados no interior do próprio
computador.
A segunda linha, como se pode ver tem o Destination Interface igual ao Endereço de IP do
computador actual. Esta linha servirá para indicar à camada IP que o endereço 193.136.190.34
é o próprio computador.
A terceira linha evidencia a configuração do router por defeito, ou seja, qualquer endereço
desconhecido deverá ser encaminhado para o endereço aqui especificado (193.136.190.59).
As duas linhas seguintes identificam ambas rotas para redes IP. O endereço 224.0.0.0
identifica o endereço para rede IP multicast e a última linha especifica o endereço da própria
rede a que o computador pertence. Qualquer mensagem que seja dirigida a esta rede é também
entregue neste computador, independentemente de a ler ou rejeitar.
Questão 13.
Para fazer o levantamento de toda a informação relativa à rede, tanto num computador
(NT/Dos) com no outro (Unix), seria necessário fazer o Ping aos endereços de
broadcast de cada computador da rede por forma a acrescentá-los à tabela ARP. Só
desta forma, posteriormente com o comando arp –a seria possível obter a totalidade da
informação sobre cada um dos computadores.
No entanto, ao fazer o Ping aos endereços broadcast das redes, foi devolvido um erro,
pelo que era necessário proceder ao contacto directo computador a computador. Como,
em princípio, existem 253 computadores ligados ao computador onde decorre o teste,
seria um trabalho exaustivo, digitar um a um o comando Ping seguido do endereço
respectivo. Para evitar esse trabalho exaustivo, criou-se um conjunto de ficheiros batch
(Vizinhos.BAT, V2.BAT e V3.BAT) para o Ms-Dos. Estes ficheiros permitem obter
toda a informação necessária
De seguida são mostrados os conteúdos de cada ficheiro Batch.
2000/2001
12
Guião
Vizinhos.BAT
Echo off
for %%y in (0 1 2) do call v2 %%y
arp –a
V2.BAT
if %1==2 for %%y in (0 1 2 3 4 5) do call V3 %1%%y
if %1==0 for %%y in (1 2 3 4 5 6 7 8 9) do call V3
if %1==1 for %%y in (0 1 2 3 4 5 6 7 8 9) do call V3 %1%%y
V3.BAT
if %1==25 for %%z in (0 1 2 3 4) do ping –a 10.10.10.%1%%z
if not %1==25 for %%z in (0 1 2 3 4 5 6 7 8 9) do ping –a 10.10.10.%1%%z
O resultado obtido pela execução dos ficheiros em Bacth do Ms-Dos encontra-se em
anexo (Anexo III).
No Unix, a programação em shell é bastante mais versátil, permitindo obter todas as
linhas com um só ficheiro (vizinhos). De qualquer forma, no computador Unix, o
número de hosts na sua vizinhança directa é bastante mais limitado devido à máscara de
rede inserida. Em ambos os sistemas operativos, pretende-se colocar os endereços de IP
de cada computador (cujo endereço esteja dentro do aceitável dentro da vizinhança do
computador actual), um a um, na tabela ARP, para posterior consulta com o comando
Arp -a. Em simultâneo é também feito o levantamento dos nomes DNS de cada
endereço dentro do grupo possível. Isto repete-se para Unix. Só desta forma foi possível
em tão pouco tempo realizar o levantamento completo.
O Ficheiro Shell Script (Unix, tem o seguinte aspecto)
Vizinhos
for i in 3 4 5 6
do
for j in 0 1 2 3 4 5 6 7 8 9
do
ping –c 1 193.136.190.$i$j
nslookup 193.136.190.$i$j
done
done
arp –a
O resultado obtido pela execução dos ficheiros em Shell Script do Unix, encontra-se em
anexo (Anexo IV).
Para além de verificar os endereços de IP que se encontram em torno de ambos os
computadores, é também importante saber qual o caminho que é percorrido até sair da
rede o ISCTE, em direcção à internet. Para tal, foi utilizado o comando Tracert (em
Dos) e Traceroute (em Unix), com um parâmetro que consiste num endereço da
internet. O resultado foi o seguinte:
2000/2001
13
Guião
traceroute www.telepac.pt
traceroute to www.telepac.pt (194.65.79.10), 30 hops max, 40 byte packets
1 gtadetti.adetti.iscte.pt (193.136.190.59) 2 ms (ttl=64!) 1 ms (ttl=64!) 1 ms (ttl=64!)
2 gtiscte.iscte.pt (193.136.188.254) 1 ms 1 ms 1 ms
3 193.136.5.254 (193.136.5.254) 595 ms 759 ms 1066 ms
4 ROUTER14.ATM0-0-0.3.Lisboa.rccn.net (193.136.1.190) 1080 ms 1072 ms 974 ms
5 ROUTER16.ATM3-0.3.Lisboa.rccn.net (193.136.1.1) 1084 ms (ttl=252!) 1248 ms (ttl=252!) *
6 PIX.telepac.pt (193.136.250.30) 990 ms (ttl=251!) 838 ms (ttl=251!) 1360 ms (ttl=251!)
7 194.65.12.157 (194.65.12.157) 719 ms (ttl=250!) 780 ms (ttl=250!) 995 ms (ttl=250!)
8 lcatrt1.telepac.net (213.13.135.105) 1153 ms (ttl=249!) 863 ms (ttl=249!) 973 ms (ttl=249!)
9 213.13.135.70 (213.13.135.70) 1125 ms (ttl=248!) 736 ms (ttl=248!) 1018 ms (ttl=248!)
10 * * *
Para tentar perceber como os computadores estão interligados (NT/Dos e Unix),
utilizou-se o comando Tracert, por forma a que fossem desenhadas as rotas de um a
outro. Neste caso, partindo no computador NT/Dos, executou-se o comando Tracert -h
10 193.136.190.34. A opção –h 10, permite que ao 10º salto o computador desista de
procurar o endereço indicado. O endereço IP indicado corresponde, exactamente, ao
computador UNIX. O resultado foi o seguinte:
tracert -h 10 193.136.190.34
Tracing route to indy1.adetti.iscte.pt [193.136.190.34]over a maximum of 10
hops:
1
<10 ms
<10 ms
<10 ms fwi.students.iscte.pt [10.10.10.254]
2
<10 ms
<10 ms
<10 ms gtalunos.iscte.pt [193.136.191.10]
3
*
*
*
Request timed out.
4
*
*
*
Request timed out.
5
*
*
*
Request timed out.
6
*
*
*
Request timed out.
7
*
*
*
Request timed out.
8
*
*
*
Request timed out.
9
*
*
*
Request timed out.
10
*
*
*
Request timed out.
Trace complete.
Como é possível verificar, a partir do computador gtalunos.iscte.pt, não foi possível passar.
Da mesma forma, do lado do computador Unix foi executado o comando traceroute na
direcção do computador NT/Dos. O resultado foi o seguinte:
Traceroute 10.10.10.112
1
gtadetti.adetti.iscte.pt (193.136.190.59)
2 ms (ttl=64!)
(ttl=64!) 1 ms (ttl=64!)
2 gtiscte.iscte.pt (193.136.188.254) 1 ms 1 ms 1 ms
3 fwe.iscte.pt (193.136.191.9) 2 ms 1 ms 1 ms
4
10.10.10.112 (10.10.10.112)
1 ms (ttl=125!)
3 ms (ttl=125!)
(ttl=125!)
2000/2001
1
ms
1 ms
14
Guião
Questão 14.
Por último, resta agora desenhar, com símbolos próprios, a rede que foi levantada ao
longo do guião, compilando toda a informação recolhida. Por se tratar de uma rede com
uma dimensão tão alargada, será apresentado um esquema que incluí apenas alguns dos
computadores encontrados na pesquisa anterior. A omissão destes equipamentos, tem
como único objectivo possibilitar a representação de uma maior diversidade de
elementos, em detrimento da quantidade. A preocupação principal foi ilustrar os
elementos mais importantes da rede (com funções específicas) e não a representação
total da rede (facto que tornaria pouco legível o diagrama). O resultado encontra-se no
Anexo V.
2000/2001
15
Guião
ANEXO I - Comandos Utilizados (Dos)
2000/2001
21
Guião
1. ARP (Address Resolution Protocol)
a) Função
Mostra e modifica as tabelas de tradução dos endereços IP para
físicos utilizadas pelo protocolo de resolução de endereços (ARP).
b) Sintaxe do comando
ARP -s end_inet end_fis [end_interf]
ARP -d end_inet [end_interf]
Arp -a [end_inet] [-N end_interf]
c) Opções
Mostra as entradas ARP actuais interrogando os actuais dados do
protocolo. Se end_inet é especificado, os endereços IP e físicos apenas
-a
para o computador especificado são mostrados. Se mais que uma
interface de rede usa ARP, as entradas de cada tabela ARP são mostradas.
O mesmo que -a.
-g
Especifica um endereço Internet.
end_inet
Mostra as entradas ARP para a interface de rede especificada por
-N end_interf
end_interf.
Adiciona o sistema anfitrião e associa o endereço Internet end_inet ao
endereço físico end_fis. O endereço físico é dado em 6 bytes
-s
hexadecimais separados por hífenes. A entrada é permanente.
Elimina o sistema anfitrião especificado por end_inet.
-d
Se presente, especifica o endereço Internet da interface cuja tabela de
tradução devia ser modificada. Se não está presente, a primeira interface
end_interf
aplicável será utilizada.
Especifica um endereço físico.
end_fis
d) Resultado
Interface: 192.9.200.200 on Interface 0x2000003
Endereço Internet
Endereço físico
Tipo
192.9.200.151
00-00-e8-69-a1-af
dinâmico
2. Ping
a) Função
Mostra informação sobre o tempo de resposta de um determinado
sistema na rede.
Ping [-t] [-a] [-n número] [-l tamanho] [-f]
[-i TTL] [-v TOS] [-r número] [-s número]
[[-j lista de anfitrião] | [-k lista de
anfitrião]]
[-w tempo de espera] lista de destino
2000/2001
22
Guião
c) Opções
-t
-a
-n número
-l tamanho
-f
-i TTL
-v TOS
-r número
-s número
-j lista de anfitr.
-k lista de anfitr.
-w tempo de espera
Espera eco do anfitrião especificado até ser
interrompido.
Para
ver
estatísticas
e
continuar prima Control-Break, para parar
prima Control-C.
Resolve endereços a nomes de anfitrião.
Número de pedidos de eco a enviar.
Tamanho de memória intermédia de envio.
Determina que o pacote não seja fragmentado.
Tempo de duração.
Tipo de serviço.
Distribuição para esta quantidade de saltos.
Data e hora para esta quantidade de saltos.
Distribuição de origem lata na lista de
anfitriões.
Distribuição origem restrita na lista de
anfitriões.
Tempo de espera em milisegundos para cada
resposta.
d) Resultado
A enviar para 192.9.200.151 com 32 bytes de dados:
Resposta de
espera=128
Resposta de
espera=128
Resposta de
espera=128
Resposta de
espera=128
192.9.200.151: bytes=32 tempo=1ms Tempo de
192.9.200.151: bytes=32 tempo<10ms Tempo de
192.9.200.151: bytes=32 tempo<10ms Tempo de
192.9.200.151: bytes=32 tempo=1ms Tempo de
Estatística de 'Ping' para 192.9.200.151:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% loss),
Tempos aproximados de ida e volta em milissegundos:
Mínimo = 0ms, Máximo = 1ms, Média = 0ms
3. Route
a) Função
Manipula tabelas de atribuição de rede.
ROUTE [-f] [comando [destino] [MASK máscara]
[porta de ligação] [METRIC métrica]]
c) Opções
Limpa as tabelas de distribuição de todas as en
da porta de ligação. Se for usado conjuntament
-f
um dos comandos, as tabelas são limpas antes do
comando ser executado.
2000/2001
23
Guião
Um de quatro:
PRINT - Imprime um encaminhamento
Comando ADD - Adiciona um encaminhamento
DELETE - Elimina um encaminhamento
CHANGE - Altera um encaminhamento existente
Destino Especifica o anfitrião destino.
MASK
Especifica que o próximo parâmetro é o valor p
Todos os nomes simbólicos para este destino são consultados
na base de dados NETWORKS da rede. Os nomes simbólicos para
a porta de ligação são consultados na base de dados HOSTS
do anfitrião.
Se o comando é PRINT ou DELETE, devem ser usados caracteres
universais para o destino e porta de ligação, ou o
argumento da porta de ligação deve ser omitido.
Exemplos:
> route print
> route ADD 157.0.0.0 MASK 255.0.0.0 157.55.80.1 METRIC 3
> route print
> route delete 157.0.0.0
> route print
Notas de diagnóstico:
MASK inválido gera um erro, isto é, quando (DEST &
MASK) != DEST.
Exemplo> route ADD 157.0.0.0 MASK 155.0.0.0 157.55.80.1
Falhou a adição do encaminhamento: 87
Exemplos:
> route PRINT
> route
ADD 157.0.0.0
^destino
MASK 255.0.0.0
^máscara
157.55.80.1
METRIC
^porta de lig.
3
^métrica
> route PRINT
> route DELETE 157.0.0.0
> route PRINT
d) Resultado
Encaminhamentos activos:
Endereço de rede
Máscara Endereço de porta de ligação
Interface
0.0.0.0
0.0.0.0
192.9.200.201
192.9.200.200
127.0.0.0
255.0.0.0
127.0.0.1
127.0.0.1
192.9.200.0
255.255.255.0
192.9.200.200
192.9.200.200
192.9.200.200 255.255.255.255
127.0.0.1
127.0.0.1
192.9.200.255 255.255.255.255
192.9.200.200
192.9.200.200
224.0.0.0
224.0.0.0
192.9.200.200
192.9.200.200
255.255.255.255 255.255.255.255
192.9.200.200
0.0.0.0
2000/2001
24
Métrica
1
1
1
1
1
1
1
Guião
4. FTP (File Transfer Protocol)
a) Função
Estabelece uma ligação de um computador (onde se executa o
comando) a outro (remoto), para transferencia de ficheiros entre
ambos.
FTP [endereço IP | Nome DNS]
c) Opções
Endereço IP
Nome DNS
Número de identificação da máquina a
que se pretende ligar.
Nome
pelo
qual
o
computador
é
conhecido na rede.
d) Resultado
Entrada em modo comando, para executar ordens próprias do
interpretador do FTP:
!
delete
literal
prompt
send
?
debug
ls
put
status
append
dir
mdelete
pwd
trace
ascii
disconnect
mdir
quit
type
bell
get
mget
quote
user
binary
glob
mkdir
recv
verbose
bye
hash
mls
remotehelp
cd
help
mput
rename
close
lcd
open
rmdir
5. TELNET (File Transfer Protocol)
a) Função
Estabelece uma ligação de um computador (onde se executa o
comando) a outro (remoto), para execução de comandos de modo a
comandar a máquina à distância.
TELNET [endereço IP| Nome DNS]
c) Opções
Endereço IP
Nome DNS
Nome
pelo
qual
o
computador
é
conhecido na rede.
d) Resultado
Entrada em modo comando na máquina de endereço IP
especificado, para executar ordens como se estivesse
sentado em frente ela.
2000/2001
25
Guião
6. IPCONFIG
a) Função
Configuração IP do Windows 98.
TELNET [endereço IP| Nome DNS]
c) Opções
/All
/Batch [fich]
/renew_all
/release_all
/renew N
/release N
Mostra informações detalhadas.
Escreve
num
ficheiro
ou
./WINIPCFG.OUT
Renova todas as placas.
Liberta todas as placas.
Renova a placa N.
Liberta a placa N.
em
d) Resultado
Configuração IP do Windows 98
0 Ethernet adapter :
Endereço IP. . . . . . . . . : 0.0.0.0
Máscara de sub-rede . . . . . . : 0.0.0.0
Porta de ligação predefinida. . :
1 Ethernet adapter :
Endereço IP. . . . . . . . . : 192.9.200.200
Máscara de sub-rede . . . . . . : 255.255.255.0
Porta de ligação predefinida. . : 192.9.200.201
7. TRACERT
a) Função
Faz o rasteio dos nós percorridos para chegar ao contacto com um
computador definido.
tracert [-d] [-h máximo_saltos] [-j
lista_anfitriões] [-w tempo de espera]
nome_destino
c) Opções
Não resolver endereços para nomes de anfitriões.
-d
-h máximo_de_saltos N.º máximo de saltos para procurar o destino.
Encaminhamento de origem lato pela lista de
-j lista_anfitriões
anfitriões.
Aguardar 'tempo de espera' milisegundos por cada
-w tempo de espera
resposta.
d) Resultado
A rastear o encaminhamento para NOGUEIRO [192.9.200.151]
até um máximo de 30 saltos:
2000/2001
26
Guião
1
1 ms.
<10 ms.
Rasteio concluído.
1 ms.
NOGUEIRO [192.9.200.151]
8. NETSTAT
a) Função
Mostra informação
TCP/IP de rede.
sobre
as
ligações
actuais
NETSTAT [-a] [-e] [-n] [-s] [-p proto] [-r] [intervalo]
c) Opções
-a
Mostra todas as ligações e portas de recepção.
Mostra
estatísticas
Ethernet.
Pode
ser
-e
combinada com a opção -s
Mostra endereços e números de portas sob forma
-n
numérica.
Mostra ligações para o protocolo especificado
por proto; proto deve ser TCP ou UDP.
Se
-p proto utilizada com a opção
-s
para mostrar
estatísticas por protocolo, proto deve ser TCP,
UDP, ou IP.
-r
Mostra a tabela de encaminhamento.
Mostra
estatísticas
por
protocolo.
Por
redefinição, as estatísticas são mostradas para
-s
TCP, UDP e IP; a opção -p pode ser utilizada
para especificar um subconjunto do intervalo
predefinido
Volta a mostrar as estatísticas seleccionadas,
esperando
'intervalo'
segundos
entre cada amostragem. Prima CTRL+C para parar
intervalo
esta amostragem das estatísticas. Se omitido,
netstat imprimirá uma vez a informação sobre a
configuração actual.
d) Resultado
Ligações activas
Proto
Estado
Endereço local
Endereço externo
9. Nslookup
a) Função
Mostra informação sobre o nome atribuído a um
determinado IP no âmbito do DNS (Domain Name
Server).
2000/2001
27
Guião
nslookup Endereço IP
c) Opções
Endereço IP
d) Resultado
Default Server: socrates.students.iscte.pt
Address: 10.10.10.2
2000/2001
28
Guião
ANEXO II - Comandos Utilizados (Unix)
2000/2001
29
Guião
FTP
NAME
ftp - Internet file transfer program
SYNOPSIS
ftp [ -v ] [ -d ] [ -i ] [ -n ] [ -g ] [ host ]
DESCRIPTION
Ftp is the user interface to the Internet standard File Transfer
Protocol. The program allows a user to transfer files to and from a
remote network site.
The client host with which ftp is to communicate may be specified on the
command line. If this is done, ftp will immediately attempt to establish
a connection to an FTP server on that host; otherwise, ftp will enter its
command interpreter and await instructions from the user. When ftp is
awaiting commands from the user the prompt "ftp>" is provided to the
user. The following commands are recognized by ftp:
! [ command [ args ] ]
Invoke an interactive shell on the local machine. If there are
arguments, the first is taken to be a command to execute directly,
with the rest of the arguments as its arguments.
$ macro-name [ args ]
Execute the macro macro-name that was defined with the macdef
command. Arguments are passed to the macro unglobbed.
account [ passwd ]
Supply a supplemental password required by a remote system for
access to resources once a login has been successfully completed.
If no argument is included, the user will be prompted for an account
password in a non-echoing input mode.
append local-file [ remote-file ]
Append a local file to a file on the remote machine. If remote-file
is left unspecified, the local file name is used in naming the
remote file after being altered by any ntrans or nmap setting. File
transfer uses the current settings for type, format, mode, and
structure.
ascii
Set the file transfer type to network ASCII. This is the default
type if ftp cannot determine the type of operating system running on
the remote machine or the remote operating system is not UNIX.
bell Arrange that a bell be sounded after each file transfer command is
completed.
binary
Set the file transfer type to support binary image transfer. This
is the default type if ftp can determine that the remote machine is
running UNIX.
bye
Terminate the FTP session with the remote server and exit ftp.
end of file will also terminate the session and exit.
An
case Toggle remote computer file name case mapping during mget commands.
2000/2001
30
Guião
When case is on (default is off), remote computer file names with
all letters in upper case are written in the local directory with
the letters mapped to lower case.
cd remote-directory
Change the working directory on the remote machine to remotedirectory.
cdup Change the remote machine working directory to the parent of the
current remote machine working directory.
chmod mode file-name
Change the permission modes for the file file-name on the remote
sytem to mode.
close
Terminate the FTP session with the remote server, and return to the
command interpreter. Any defined macros are erased.
cr
Toggle carriage return stripping during ascii type file retrieval.
Records are denoted by a carriage return/linefeed sequence during
ascii type file transfer. When cr is on (the default), carriage
returns are stripped from this sequence to conform with the UNIX
single linefeed record delimiter. Records on non-UNIX remote
systems may contain single linefeeds; when an ascii type transfer is
made, these linefeeds may be distinguished from a record delimiter
only when cr is off.
delete remote-file
Delete the file remote-file on the remote machine.
debug [ debug-value ]
Toggle debugging mode. If an optional debug-value is specified it
is used to set the debugging level. When debugging is on, ftp
prints each command sent to the remote machine, preceded by the
string "-->".
dir [ remote-directory ] [ local-file ]
Print a listing of the directory contents in the directory, remotedirectory, and, optionally, placing the output in local-file. If
interactive prompting is on, ftp will prompt the user to verify that
the last argument is indeed the target local file for receiving dir
output. If no directory is specified, the current working directory
on the remote machine is used. If no local file is specified, or
local-file is -, output comes to the terminal.
disconnect
A synonym for close.
form format
Set the file transfer form to format.
The default format is "file".
get remote-file [ local-file ]
Retrieve the remote-file and store it on the local machine. If the
local file name is not specified, it is given the same name it has
on the remote machine, subject to alteration by the current case,
ntrans, and nmap settings. The current settings for type, form,
mode, and structure are used while transferring the file.
glob Toggle filename expansion for mdelete, mget and mput. If globbing
is turned off with glob, the file name arguments are taken literally
2000/2001
31
and not expanded.
Guião
Globbing for mput is done as in csh(1).
For
mdelete and mget, each remote file name is expanded separately
the remote machine and the lists are not merged. Expansion of
directory name is likely to be different from expansion of the
of an ordinary file: the exact result depends on the foreign
operating system and ftp server, and can be previewed by doing
`mls remote-files -'. Note: mget and mput are not meant to
transfer entire directory subtrees of files. That can be done
transferring a tar(1) archive of the subtree (in binary mode).
on
a
name
by
hash Toggle hash-sign (‘‘#'') printing for each data block transferred.
The size of a data block is 1024 bytes.
help [ command ]
Print an informative message about the meaning of command. If no
argument is given, ftp prints a list of the known commands.
idle [ seconds ]
Set the inactivity timer on the remote server to seconds seconds.
If seconds is omitted, the current inactivity timer is printed.
lcd [ directory ]
Change the working directory on the local machine.
is specified, the user's home directory is used.
If no directory
ls [ remote-directory ] [ local-file ]
Print a listing of the contents of a directory on the remote
machine. The listing includes any system-dependent information that
the server chooses to include; for example, most UNIX systems will
produce output from the command "ls -lA". (See also nlist.) If
remote-directory is left unspecified, the current working directory
is used. If interactive prompting is on, ftp will prompt the user
to verify that the last argument is indeed the target local file for
receiving ls output. If no local file is specified, or if localfile is -, the output is sent to the terminal.
macdef macro-name
Define a macro. Subsequent lines are stored as the macro macroname; a null line (consecutive newline characters in a file or
carriage returns from the terminal) terminates macro input mode.
There is a limit of 16 macros and 4096 total characters in all
defined macros. Macros remain defined until a close command is
executed. The macro processor interprets '$' and '\' as special
characters. A '$' followed by a number (or numbers) is replaced by
the corresponding argument on the macro invocation command line. A
'$' followed by an 'i' signals that macro processor that the
executing macro is to be looped. On the first pass '$i' is replaced
by the first argument on the macro invocation command line, on the
second pass it is replaced by the second argument, and so on. A '\'
followed by any character is replaced by that character. Use the
'\' to prevent special treatment of the '$'.
mdelete [ remote-files ]
Delete the remote-files on the remote machine.
mdir remote-files local-file
Like dir, except multiple remote files may be specified. If
interactive prompting is on, ftp will prompt the user to verify that
the last argument is indeed the target local file for receiving mdir
2000/2001
32
Guião
output.
mget remote-files
Expand the remote-files on the remote machine and do a get for each
file name thus produced. See glob for details on the filename
expansion. Resulting file names will then be processed according to
case, ntrans, and nmap settings. Files are transferred into the
local working directory, which can be changed with `lcd directory';
new local directories can be created with `! mkdir directory'.
mkdir directory-name
Make a directory on the remote machine.
mls remote-files local-file
Like nlist, except multiple remote files may be specified, and the
local-file must be specified. If interactive prompting is on, ftp
will prompt the user to verify that the last argument is indeed the
target local file for receiving mls output.
mode [ mode-name ]
Set the file transfer mode to mode-name.
"stream" mode.
The default mode is
modtime file-name
Show the last modification time of the file on the remote machine.
mput local-files
Expand wild cards in the list of local files given as arguments and
do a put for each file in the resulting list. See glob for details
of filename expansion. Resulting file names will then be processed
according to ntrans and nmap settings.
newer file-name
Get the file only if the modification time of the remote file is
more recent that the file on the current system. If the file does
not exist on the current system, the remote file is considered
newer. Otherwise, this command is identical to get.
nlist [ remote-directory ] [ local-file ]
Print a list of the files of a directory on the remote machine. If
remote-directory is left unspecified, the current working directory
is used. If interactive prompting is on, ftp will prompt the user
to verify that the last argument is indeed the target local file for
receiving nlist output. If no local file is specified, or if
local-file is -, the output is sent to the terminal.
nmap [ inpattern outpattern ]
Set or unset the filename mapping mechanism. If no arguments are
specified, the filename mapping mechanism is unset. If arguments
are specified, remote filenames are mapped during mput commands and
put commands issued without a specified remote target filename. If
arguments are specified, local filenames are mapped during mget
commands and get commands issued without a specified local target
filename. This command is useful when connecting to a non-UNIX
remote computer with different file naming conventions or practices.
The mapping follows the pattern set by inpattern and outpattern.
Inpattern is a template for incoming filenames (which may have
already been processed according to the ntrans and case settings).
Variable templating is accomplished by including the sequences '$1',
'$2', ..., '$9' in inpattern. Use '\' to prevent this special
treatment of the '$' character. All other characters are treated
2000/2001
33
Guião
literally, and are used to determine the nmap inpattern variable
values. For example, given inpattern $1.$2 and the remote file name
"mydata.data", $1 would have the value "mydata", and $2 would have
the value "data". The outpattern determines the resulting mapped
filename. The sequences '$1', '$2', ., '$9' are replaced by any
value resulting from the inpattern template. The sequence '$0' is
replace by the original filename. Additionally, the sequence
'[seq1,seq2]' is replaced by seq1 if seq1 is not a null string;
otherwise it is replaced by seq2. For example, the command "nmap
$1.$2.$3 [$1,$2].[$2,file]" would yield the output filename
"myfile.data" for input filenames "myfile.data" and
"myfile.data.old", "myfile.file" for the input filename "myfile",
and "myfile.myfile" for the input filename ".myfile". Spaces may be
included in outpattern, as in the example: nmap $1 |sed "s/ *$//" >
$1 . Use the '\' character to prevent special treatment of the '$',
'[', ']', and ',' characters.
ntrans [ inchars [ outchars ] ]
Set or unset the filename character translation mechanism. If no
arguments are specified, the filename character translation
mechanism is unset. If arguments are specified, characters in
remote filenames are translated during mput commands and put
commands issued without a specified remote target filename. If
arguments are specified, characters in local filenames are
translated during mget commands and get commands issued without a
specified local target filename. This command is useful when
connecting to a non-UNIX remote computer with different file naming
conventions or practices. Characters in a filename matching a
character in inchars are replaced with the corresponding character
in outchars. If the character's position in inchars is longer than
the length of outchars, the character is deleted from the file name.
open host [ port ]
Establish a connection to the specified host FTP server. An
optional port number may be supplied, in which case, ftp will
attempt to contact an FTP server at that port. If the auto-login
option is on (default), ftp will also attempt to automatically log
the user in to the FTP server (see below).
prompt
Toggle interactive prompting. Interactive prompting occurs during
multiple file transfers to allow the user to selectively retrieve or
store files. If prompting is turned off (default is on), any mget
or mput will transfer all files, and any mdelete will delete all
files.
proxy ftp-command
Execute an ftp command on a secondary control connection. This
command allows simultaneous connection to two remote ftp servers for
transferring files between the two servers. The first proxy command
should be an open, to establish the secondary control connection.
Enter the command "proxy ?" to see other ftp commands executable on
the secondary connection. The following commands behave differently
when prefaced by proxy: open will not define new macros during the
auto-login process, close will not erase existing macro definitions,
get and mget transfer files from the host on the primary control
connection to the host on the secondary control connection, and put,
mput, and append transfer files from the host on the secondary
control connection to the host on the primary control connection.
Third party file transfers depend upon support of the ftp protocol
PASV command by the server on the secondary control connection.
2000/2001
34
Guião
put local-file [ remote-file ]
Store a local file on the remote machine. If remote-file is left
unspecified, the local file name is used after processing according
to any ntrans or nmap settings in naming the remote file. File
transfer uses the current settings for type, format, mode, and
structure.
pwd
Print the name of the current working directory on the remote
machine.
quit A synonym for bye.
quote arg1 arg2 ...
The arguments specified are sent, verbatim, to the remote FTP
server.
recv remote-file [ local-file ]
A synonym for get.
reget remote-file [ local-file ]
Reget acts like get, except that if local-file exists and is smaller
than remote-file, local-file is presumed to be a partially
transferred copy of remote-file and the transfer is continued from
the apparent point of failure. This command is useful when
transferring very large files over networks that are prone to
dropping connections.
remotehelp [ command-name ]
Request help from the remote FTP server. If a command-name is
specified it is supplied to the server as well.
remotestatus [ file-name ]
With no arguments, show status of remote machine. If file-name is
specified, show status of file-name on remote machine.
rename [ from ] [ to ]
Rename the file from on the remote machine, to the file to.
reset
Clear reply queue. This command re-synchronizes command/reply
sequencing with the remote ftp server. Resynchronization may be
necessary following a violation of the ftp protocol by the remote
server.
restart marker
Restart the immediately following get or put at the indicated
marker. On UNIX systems, marker is usually a byte offset into the
file.
rmdir directory-name
Delete a directory on the remote machine.
runique
Toggle storing of files on the local system with unique filenames.
If a file already exists with a name equal to the target local
filename for a get or mget command, a ".1" is appended to the name.
If the resulting name matches another existing file, a ".2" is
appended to the original name. If this process continues up to
".99", an error message is printed, and the transfer does not take
place. The generated unique filename will be reported. Note that
2000/2001
35
Guião
runique will not affect local files generated from a shell command
(see below). The default value is off.
send local-file [ remote-file ]
A synonym for put.
sendport
Toggle the use of PORT commands. By default, ftp will attempt to
use a PORT command when establishing a connection for each data
transfer. The use of PORT commands can prevent delays when
performing multiple file transfers. If the PORT command fails, ftp
will use the default data port. When the use of PORT commands is
disabled, no attempt will be made to use PORT commands for each data
transfer. This is useful for certain FTP implementations which do
ignore PORT commands but, incorrectly, indicate they've been
accepted.
site arg1 arg2 ...
The arguments specified are sent, verbatim, to the remote FTP server
as a SITE command.
size file-name
Return size of file-name on remote machine.
status
Show the current status of ftp.
struct [ struct-name ]
Set the file transfer structure to struct-name.
structure is used.
By default "stream"
sunique
Toggle storing of files on remote machine under unique file names.
Remote ftp server must support ftp protocol STOU command for
successful completion. The remote server will report unique name.
Default value is off.
system
Show the type of operating system running on the remote machine.
tenex
Set the file transfer type to that needed to talk to TENEX machines.
trace
Toggle packet tracing.
type [ type-name ]
Set the file transfer type to type-name. If no type is specified,
the current type is printed. The default type is network ASCII.
umask [ newmask ]
Set the default umask on the remote server to newmask.
is omitted, the current umask is printed.
If newmask
user user-name [ password ] [ account ]
Identify yourself to the remote FTP server. If the password is not
specified and the server requires it, ftp will prompt the user for
it (after disabling local echo). If an account field is not
specified, and the FTP server requires it, the user will be prompted
for it. If an account field is specified, an account command will
2000/2001
36
Guião
be relayed to the remote server after the login sequence is
completed if the remote server did not require it for logging in.
Unless ftp is invoked with "auto-login" disabled, this process is
done automatically on initial connection to the FTP server.
verbose
Toggle
server
when a
of the
verbose mode. In verbose mode, all responses from the FTP
are displayed to the user. In addition, if verbose is on,
file transfer completes, statistics regarding the efficiency
transfer are reported. By default, verbose is on.
? [ command ]
A synonym for help.
Command arguments which have embedded spaces may be quoted with quote (")
marks.
ABORTING A FILE TRANSFER
To abort a file transfer, use the terminal interrupt key (usually CtrlC). Sending transfers will be immediately halted. Receiving transfers
will be halted by sending a ftp protocol ABOR command to the remote
server, and discarding any further data received. The speed at which
this is accomplished depends upon the remote server's support for ABOR
processing. If the remote server does not support the ABOR command, an
"ftp>" prompt will not appear until the remote server has completed
sending the requested file.
The terminal interrupt key sequence will be ignored when ftp has
completed any local processing and is awaiting a reply from the remote
server. A long delay in this mode may result from the ABOR processing
described above, or from unexpected behavior by the remote server,
including violations of the ftp protocol. If the delay results from
unexpected remote server behavior, the local ftp program must be killed
by hand.
FILE NAMING CONVENTIONS
Files specified as arguments to ftp commands are processed according to
the following rules.
1)
If the file name "-" is specified, the stdin (for reading) or stdout
(for writing) is used.
2)
If the first character of the file name is "|", the remainder of the
argument is interpreted as a shell command. Ftp then forks a shell,
using popen(3) with the argument supplied, and reads (writes) from
the stdout (stdin). If the shell command includes spaces, the
argument must be quoted; e.g., ""| ls -lt"". A particularly useful
example of this mechanism is: "dir |more".
3)
Failing the above checks, if ‘‘globbing'' is enabled,
names are expanded according to the rules used in the
the glob command. If the ftp command expects a single
(e.g., put), only the first filename generated by the
operation is used.
4)
For mget commands and get commands with unspecified local file
names, the local filename is the remote filename, which may be
altered by a case, ntrans, or nmap setting. The resulting filename
may then be altered if runique is on.
5)
For mput commands and put commands with unspecified remote file
2000/2001
local file
csh(1); c.f.
local file
"globbing"
37
Guião
names, the remote filename is the local filename, which may be
altered by a ntrans or nmap setting. The resulting filename may
then be altered by the remote server if sunique is on.
FILE TRANSFER PARAMETERS
The FTP specification specifies many parameters which may affect a file
transfer. The type may be one of "ascii", "image" (binary), "ebcdic",
and "local byte size" (for PDP-10's and PDP-20's mostly). Ftp supports
the ascii and image types of file transfer, plus local byte size 8 for
tenex mode transfers.
Ftp supports only the default values for the remaining file transfer
parameters: mode, form, and struct.
OPTIONS
Options may be specified at the shell command line. Several options can
be enabled or disabled with ftp commands.
The -v (verbose on) option forces ftp to show all responses from the
remote server, as well as report on data transfer statistics.
The -n option restrains ftp from attempting "auto-login" upon initial
connection. If auto-login is enabled, ftp will check the .netrc file
(see below) in the user's home directory for an entry describing an
account on the remote machine. If no entry exists, ftp will prompt for
the remote machine login name (default is the user identity on the local
machine), and, if necessary, prompt for a password and an account with
which to login.
The -i option turns off interactive prompting during multiple file
transfers.
The -d option enables debugging.
The -g option disables file name globbing.
THE .netrc FILE
The .netrc file contains login and initialization information used by the
auto-login process. It resides in the user's home directory. The
following tokens are recognized; they may be separated by spaces, tabs,
or new-lines:
machine name
Identify a remote machine name. The auto-login process searches the
.netrc file for a machine token that matches the remote machine
specified on the ftp command line or as an open command argument.
Once a match is made, the subsequent .netrc tokens are processed,
stopping when the end of file is reached or another machine or a
default token is encountered.
default
This is the same as machine name except that default matches any
name. There can be only one default token, and it must be after all
machine tokens. This is normally used as:
default login anonymous password user@site
thereby giving the user automatic anonymous ftp login to machines
not specified in .netrc. This can be overridden by using the -n flag
to disable auto-login.
login name
Identify a user on the remote machine.
If this token is present,
2000/2001
38
Guião
the auto-login process will initiate a login using the specified
name.
password string
Supply a password. If this token is present, the auto-login process
will supply the specified string if the remote server requires a
password as part of the login process. Note that if this token is
present in the .netrc file for any user other than anonymous, ftp
will abort the auto-login process if the .netrc is accessible by
anyone besides the user (see below for the proper protection mode.)
account string
Supply an additional account password. If this token is present,
the auto-login process will supply the specified string if the
remote server requires an additional account password, or the autologin process will initiate an ACCT command if it does not. Note
that if this token is present in the .netrc file, ftp will abort the
auto-login process if the .netrc is accessible by anyone besides the
user (see below for the proper protection mode.)
macdef name
Define a macro. This token functions like the ftp macdef command
functions. A macro is defined with the specified name; its contents
begin with the next .netrc line and continue until a null line
(consecutive new-line characters) is encountered. If a macro named
init is defined, it is automatically executed as the last step in
the auto-login process.
The error message
Error: .netrc file is readable by others.
means the file is ignored by ftp because the file's password and/or
account information is unprotected. Use
chmod go-rwx .netrc
to protect the file.
SEE ALSO
ftpd(1M)
BUGS
Correct execution of many commands depends upon proper behavior by the
remote server.
An error in the treatment of carriage returns in the 4.2BSD UNIX asciimode transfer code has been corrected. This correction may result in
incorrect transfers of binary files to and from 4.2BSD servers using the
ascii type. Avoid this problem by using the binary image type.
TRACEROUTE
NAME
traceroute - print the route packets take to a network host
SYNOPSIS
/usr/etc/traceroute [ -g addr ] [ -l ] [ -m max_ttl ] [ -n ] [ -p port ]
[ -q nqueries ] [ -r ] [ -s src_addr ] [ -t tos ]
[ -w waittime ] host [ datalen ]
DESCRIPTION
2000/2001
39
Guião
The Internet is a large and complex aggregation of network hardware,
connected by gateways. Tracking the route your packets follow (or
finding the miscreant gateway that's discarding your packets) can be
difficult. traceroute utilizes the IP protocol ‘‘time-to-live'' (TTL)
field and attempts to elicit an ICMP TIME_EXCEEDED response from each
gateway along the path to some host.
The only mandatory parameter is the destination host name or IP address.
The default probe datagram length is 40 bytes, but this may be increased
by specifying the additional length (in bytes) after the destination host
name.
The options are:
-g
Enable the IP LSRR (Loose Source Record Route) option in addition to
the TTL tests. This is useful for asking how somebody else, at
addr, (either an IP address or a hostname) reaches a particular
target.
-l
Print the value of the TTL field in each received packet (this can
be used to help detect asymmetric routing).
-m
Set the maximum time-to-live (maximum number of hops) used in
outgoing probe packets. The default is 30 hops.
-n
Print hop addresses numerically rather than symbolically and
numerically (saves a nameserver address-to-name lookup for each
gateway found on the path).
-p
Set the base UDP port number used in probes (default is 33434).
traceroute hopes that nothing is listening on UDP ports base to
base+nhops-1 at the destination host (so an ICMP PORT_UNREACHABLE
message will be returned to terminate the route tracing). If
something is listening on a port in the default range, this option
can be used to pick an unused port range.
-q
Set the number of probe packets to send. The default is 3 packets.
-r
Bypass the normal routing tables and send directly to a host on an
attached network. If the host is not on a directly attached
network, an error is returned. This option can be used to ping a
local host through an interface that has no route through it (for
example, after the interface was dropped by routed(1M)).
-s
Use the following IP address (which must be given as a number, not a
hostname) as the source address in outgoing probe packets. On hosts
with more than one IP address, this option can be used to force the
source address to be something other than the IP address of the
interface the probe packet is sent on. If the IP address is not one
of this machine's interface addresses, an error is returned and
nothing is sent.
-t
Set the type-of-service (TOS) in probe packets to the following
value (default zero). The value must be a decimal integer in the
range 0 to 255. This option can be used to see if different typesof-service result in different paths. Not all values of TOS are
legal or meaningful: see the IP RFC for definitions. Useful values
are probably -t 16 (low delay) and -t 8 (high throughput).
-v
Verbose output. Received ICMP packets other than TIME_EXCEEDED and
PORT_UNREACHABLEs are listed.
2000/2001
40
-w
Guião
Set the time (in seconds) to wait for a response to a probe (default
is 3 seconds).
This program attempts to trace the route an IP packet would follow to
some Internet host by launching UDP probe packets with a small TTL then,
listening for an ICMP TIME_EXCEEDED reply from a gateway. The probes
begin with a TTL of one and increase by one until an ICMP
PORT_UNREACHABLE message is received, which means we got to ‘‘host'' or
hit the maximum (which defaults to 30 hops but can be changed with the -m
flag). Three probes (changed with -q flag) are sent at each TTL setting
and a line is printed showing the TTL, address of the gateway and round
trip time of each probe. If the probe answers come from different
gateways, the address of each responding system will be printed. If
there is no response within a 3-second timeout interval (changed with the
-w flag), a ‘‘*'' is printed for that probe.
So that the destination host will not process the UDP probe packets, the
destination port is set to an unlikely value. If someone on the
destination is using that value, it can be changed with the -p flag.
A sample use and output might be:
% traceroute nis.nsf.net.
traceroute to nis.nsf.net (35.1.1.48), 30 hops max, 56 byte packet
1 helios.ee.lbl.gov (128.3.112.1) 19 ms 19 ms 0 ms
2 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 39 ms 19 ms
4 ccngw-ner-cc.Berkeley.EDU (128.32.136.23) 39 ms 40 ms 39 ms
5 ccn-nerif22.Berkeley.EDU (128.32.168.22) 39 ms 39 ms 39 ms
6 128.32.197.4 (128.32.197.4) 40 ms 59 ms 59 ms
7 131.119.2.5 (131.119.2.5) 59 ms 59 ms 59 ms
8 129.140.70.13 (129.140.70.13) 99 ms 99 ms 80 ms
9 129.140.71.6 (129.140.71.6) 139 ms 239 ms 319 ms
10 129.140.81.7 (129.140.81.7) 220 ms 199 ms 199 ms
11 nic.merit.edu (35.1.1.48) 239 ms 239 ms 239 ms
Notice that lines 2 and 3 are the same because of a buggy kernel on the
second hop system - lbl-csam.arpa - that forwards packets with a zero TTL
(a bug in the distributed version of 4.3BSD). You have to guess what
path the packets are taking cross-country since the NSFNet (129.140)
doesn't supply address-to-name translations for its NSSes.
A more interesting example is:
% traceroute allspice.lcs.mit.edu.
traceroute to allspice.lcs.mit.edu (18.26.0.115), 30 hops max
6 128.32.197.4 (128.32.197.4) 59 ms 119 ms 39 ms
7 131.119.2.5 (131.119.2.5) 59 ms 59 ms 39 ms
8 129.140.70.13 (129.140.70.13) 80 ms 79 ms 99 ms
9 129.140.71.6 (129.140.71.6) 139 ms 139 ms 159 ms
10 129.140.81.7 (129.140.81.7) 199 ms 180 ms 300 ms
11 129.140.72.17 (129.140.72.17) 300 ms 239 ms 239 ms
12 * * *
13 128.121.54.72 (128.121.54.72) 259 ms 499 ms 279 ms
14 * * *
15 * * *
2000/2001
41
Guião
16 * * *
17 * * *
18 ALLSPICE.LCS.MIT.EDU (18.26.0.115) 339 ms 279 ms 279 ms
Notice that the gateways 12, 14, 15, 16 and 17 hops away either don't
send ICMP TIME_EXCEEDED messages or send them with a TTL too small to
reach us. 14 - 17 are running the MIT C Gateway code that doesn't send
TIME_EXCEEDEDs.
The silent gateway 12 in the above example may be the result of a bug in
the 4.[23]BSD network code (and its derivatives): 4.x (x <= 3) sends an
unreachable message using whatever TTL remains in the original datagram.
Since, for gateways, the remaining TTL is zero, the ICMP TIME_EXCEEDED is
guaranteed to not make it back to us. The behavior of this bug is
slightly more interesting when it appears on the destination system:
% traceroute rip.berkeley.edu
6 csgw.Berkeley.EDU (128.32.133.254) 39 ms 59 ms 39 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 rip.Berkeley.EDU (128.32.131.22) 59 ms ! 39 ms ! 39 ms !
Notice of the 12 ‘‘gateways'' (13 is the final destination), exactly the
half of them are ‘‘missing''. In this example, rip, a Sun-3 running Sun
OS3.5, is using the TTL from the arriving datagram as the TTL in its ICMP
reply. The reply will then time out on the return path, with no notice
sent to anyone since ICMP packets aren't sent for ICMP packets, until we
probe with a TTL that's at least twice the path length - that is, rip is
really only 7 hops away. A reply that returns with a TTL of 1 is a clue
this problem exists. Traceroute prints a ‘‘!'' after the time if the TTL
is <= 1. Since some vendors ship obsolete or nonstandard software,
expect to see this problem frequently and/or take care selecting the target host of your probes.
Other possible annotations after the time are !H, !N, !P (got a host,
network or protocol unreachable, respectively), !S or !F (source route
failed or fragmentation needed - neither of these should ever occur, and
the associated gateway is broken if you see one). If almost all the
probes result in some kind of unreachable, traceroute will give up and
exit.
(ttl=n!) indicates that the TTL value in the ICMP TIME_EXCEEDED packet
that we received was "unexpected". What we expect is that the value will
be (some initial value - the number of routers between us). In other
words, if the path from hop 5 to us is the same as the path from us to
hop 5, we expect to receive a TTL value of (some initial value - 4).
Unfortunately, there are several common "initial value"s for ICMP TTLs.
The most common are 255, 60, 59, 30, 29. (IRIX, 4.3BSD-tahoe and cisco
routers use 255, Proteon routers use either 59 or 29 depending on
software release, several other implementations use 60 and 30.) Traceroute checks against all of these, making it hard to detect some "off
by one" routing asymmetries. If you want to see all the TTL values in
all the packets, use the -l option.
2000/2001
42
Guião
For example,
% traceroute -g 10.3.0.5 128.182.0.0
will show the path from the Cambridge Mailbridge to PSC while
% traceroute -g 192.5.146.4 -g 10.3.0.5 35.0.0.0
shows how the Cambridge Mailbrige reaches Merit, by using PSC to reach
the Mailbridge.
This program is intended for use in network testing, measurement, and
management. It should be used primarily for manual fault isolation. It
is unwise to use traceroute during normal operations or from automated
scripts due to the load it could impose on the network.
AUTHORS
Van Jacobson, Steve Deering, C. Philip Wood, Tim Seaver, and Ken Adelman.
SEE ALSO
netstat(1), ping(1M)
ARP
NAME
arp - address resolution display and control
SYNOPSIS
arp
arp
arp
arp
arp
hostname
-a [ unix ] [ kmem ]
-d hostname
-s hostname ether_addr [ temp ] [ pub ] [ trail ]
-f filename
DESCRIPTION
The arp program displays and modifies the Internet-to-Ethernet address
translation tables used by the address resolution protocol (arp(7P)).
With no flags, the program displays the current ARP entry for hostname.
The host may be specified by name or by number, using Internet dot
notation. With the -a flag, the program displays all of the current ARP
entries by reading the table from the file kmem (default /dev/kmem) based
on the kernel file unix (default /unix).
With the -d flag, a super-user may delete an entry for the host called
hostname.
The -s flag is given to create an ARP entry for the host called hostname
with the Ethernet address ether_addr. The Ethernet address is given as
six hex bytes separated by colons. The entry will be permanent unless
the word temp is given in the command. If the word pub is given, the
entry will be "published"; i.e., this system will act as an ARP server,
responding to requests for hostname even though the host address is not
its own. The word trail indicates that trailer encapsulations may be
sent to this host.
The -f flag causes the file filename to be read and multiple entries to
be set in the ARP tables. Entries in the file should be of the form
hostname ether_addr [ temp ] [ pub ] [ trail ]
with argument meanings as given above.
2000/2001
43
Guião
EXAMPLES
Command lines are followed by the output.
A completed successful entry:
# arp moose
moose (192.26.72.5) at 8:0:69:2:24:3e
A completed successful entry which is marked "permanent" and "published":
# arp rainbow
rainbow (192.26.72.3) at 8:0:69:2:4:94 permanent published
An incomplete entry:
# arp ender
ender (192.26.72.246) at (incomplete)
A non-existent entry:
# arp foobar
foobar (192.26.72.1) -- no entry
SEE ALSO
inet(7P), arp(7P), ifconfig(1M)
ARP is a protocol used to dynamically map between DARPA Internet and
10Mb/s Ethernet addresses. It is used by all the 10Mb/s Ethernet
interface drivers. It is not specific to Internet protocols or to 10Mb/s
Ethernet, but this implementation currently supports only that
combination.
ARP caches Internet-Ethernet address mappings. When an interface
requests a mapping for an address not in the cache, ARP queues the
message which requires the mapping and broadcasts a message on the
associated network requesting the address mapping. If a response is
provided, the new mapping is cached and any pending message is
transmitted. Each address mapping has a timer associated with it and
completed address mappings are aged after 20 minutes. The timer is reset
each time the address mapping is updated by a SIOCSARP ioctl call or by
sending a packet to the Internet address to which the mapping belongs.
This timer value is not configurable. ARP will queue at most one packet
while waiting for a mapping request to be responded to; only the most
recently ‘‘transmitted'' packet is kept.
To facilitate communications with systems which do not use ARP, ioctls
are provided to enter and delete entries in the Internet-to-Ethernet
tables. Usage:
#include <sys/ioctl.h>
#include <sys/socket.h>
#include <net/if.h>
struct arpreq arpreq;
ioctl(s, SIOCSARP, (caddr_t)&arpreq);
ioctl(s, SIOCGARP, (caddr_t)&arpreq);
ioctl(s, SIOCDARP, (caddr_t)&arpreq);
Each ioctl takes the same structure as an argument. SIOCSARP sets an ARP
entry, SIOCGARP gets an ARP entry, and SIOCDARP deletes an ARP entry.
2000/2001
44
Guião
These ioctls may be applied to any socket descriptor s, but only by the
super-user. The arpreq structure contains:
/* ARP ioctl request */
struct arpreq {
struct sockaddr
arp_pa;
/* protocol address */
struct sockaddr
arp_ha;
/* hardware address */
int
arp_flags;
/* flags */
};
/* arp_flags field values */
#define
ATF_COM
0x02
#define
ATF_PERM
0x04
#define
ATF_PUBL
0x08
#define
ATF_USETRAILERS
/* completed entry (arp_ha valid) */
/* permanent entry */
/* publish (respond for other host) */
0x10 /* send trailer packets to host */
The address family for the arp_pa sockaddr must be AF_INET; for the
arp_ha sockaddr it must be AF_UNSPEC. The only flag bits which may be
written are ATF_PERM, ATF_PUBL and ATF_USETRAILERS. ATF_PERM causes the
entry to be permanent if the ioctl call succeeds. The peculiar nature of
the ARP tables may cause the ioctl to fail if more than 8 (permanent)
Internet host addresses hash to the same slot. ATF_PUBL specifies that
the ARP code should respond to ARP requests for the indicated host coming
from other machines. This allows a host to act as an ‘‘ARP server,''
which may be useful in convincing an ARP-only machine to talk to a nonARP machine.
ARP is also used to negotiate the use of trailer IP encapsulations;
trailers are an alternate encapsulation used to allow efficient packet
alignment for large packets despite variable-sized headers. Hosts which
wish to receive trailer encapsulations so indicate by sending gratuitous
ARP translation replies along with replies to IP requests; they are also
sent in reply to IP translation replies. The negotiation is thus fully
symmetrical, in that either or both hosts may request trailers. The
ATF_USETRAILERS flag is used to record the receipt of such a reply, and
enables the transmission of trailer packets to that host.
ARP watches passively for hosts impersonating the local host (i.e. a host
which responds to an ARP mapping request for the local host's address).
DIAGNOSTICS
The following messages can appear on the console:
arp: host with ether address %x:%x:%x:%x:%x:%x is using my IP address
x.x.x.x
ARP has discovered another host on the local network which responds to
mapping requests for its own Internet address.
arp: ether address is broadcast for IP address x.x.x.x
ARP has discovered another host on the local network which maps that
host's IP address onto the ethernet broadcast address.
SEE ALSO
inet(7F), arp(1M), ifconfig(1M), intro(3)
‘‘An Ethernet Address Resolution Protocol,'' RFC826, Dave Plummer,
Network Information Center, SRI.
‘‘Trailer Encapsulations,'' RFC893, S.J. Leffler and M.J. Karels, Network
Information Center, SRI.
BUGS
ARP packets on the Ethernet use only 42 bytes of data; however, the
2000/2001
45
Guião
smallest legal Ethernet packet is 60 bytes (not including CRC).
systems may not enforce the minimum packet size, others will.
Some
NSLOOKUP(1C)
NAME
nslookup - query Internet name servers interactively
SYNOPSIS
nslookup [ -option ... ] [ host-to-find | - [ server ]]
DESCRIPTION
Nslookup is a program to query Internet domain name servers. Nslookup has
two modes: interactive and non-interactive. Interactive mode allows the
user to query name servers for information about various hosts and
domains or to print a list of hosts in a domain. Non-interactive mode is
used to print just the name and requested information for a host or
domain.
ARGUMENTS
Interactive mode is entered in the following cases:
a)
when no arguments are given (the default name server will be used),
b)
when the first argument is a hyphen (-) and the second argument is
the host name or Internet address of a name server.
Non-interactive mode is used when the name or Internet address of the
host to be looked up is given as the first argument. The optional second
argument specifies the host name or address of a name server.
The options listed under the ‘‘set'' command below can be specified in
the .nslookuprc file in the user's home directory if they are listed one
per line. Options can also be specified on the command line if they
precede the arguments and are prefixed with a hyphen. For example, to
change the default query type to host information, and the initial
timeout to 10 seconds, type:
nslookup -query=hinfo -timeout=10
INTERACTIVE COMMANDS
Commands may be interrupted at any time by typing a control-C. To exit,
type a control-D (EOF) or type exit. The command line length must be
less than 256 characters. To treat a built-in command as a host name,
precede it with an escape character (\). N.B. an unrecognized command
will be interpreted as a host name.
host [server]
Look up information for host using the current default server or
using server if specified. If host is an Internet address and the
query type is A or PTR, the name of the host is returned. If host
is a name and does not have a trailing period, the default domain
name is appended to the name. (This behavior depends on the state of
the set options domain, srchlist, defname, and search). To look up
a host not in the current domain, append a period to the name.
server domain
lserver domain
Change the default server to domain. Lserver uses the initial server
to look up information about domain while server uses the current
2000/2001
46
Guião
default server. If an authoritative answer can't be found, the names
of servers that might have the answer are returned.
root Changes the default server to the server for the root of the domain
name space. Currently, the host ns.internic.net is used. (This
command is a synonym for lserver ns.internic.net.) The name of the
root server can be changed with the set root command.
finger [name] [> filename]
finger [name] [>> filename]
Connects with the finger server on the current host. The current
host is defined when a previous lookup for a host was successful and
returned address information (see the set querytype=A command).
Name is optional. > and >> can be used to redirect output in the
usual manner.
ls [option] domain [> filename]
ls [option] domain [>> filename]
List the information available for domain, optionally creating or
appending to filename. The default output contains host names and
their Internet addresses. Option can be one of the following:
-t querytype
lists all records of the specified type (see querytype below).
-a
lists aliases of hosts in the domain. synonym for -t
-d
lists all records for the domain.
-h
lists CPU and operating system information for the domain.
synonym for -t HINFO.
-s
lists well-known services of hosts in the domain.
-t WKS.
synonym for -t
CNAME.
ANY.
synonym for
When output is directed to a file, hash marks are printed for every
50 records received from the server.
view filename
Sorts and lists the output of previous ls command(s) with more(1).
help
?
Prints a brief summary of commands.
exit Exits the program.
set keyword[=value]
This command is used to change state information that affects the
lookups. Valid keywords are:
all
Prints the current values of the frequently-used options to
set. Information about the current default server and host is
also printed.
class=value
2000/2001
47
Guião
Change the query class to one of:
IN
the Internet class.
CHAOS
the Chaos class.
HESIOD
the MIT Athena Hesiod class.
ANY
wildcard (any of the above).
The class specifies the protocol group of the information.
(Default = IN, abbreviation = cl)
[no]debug
Turn debugging mode on. A lot more information is printed about
the packet sent to the server and the resulting answer.
(Default = nodebug, abbreviation = [no]deb)
[no]d2
Turn exhaustive debugging mode on.
every packet are printed.
(Default = nod2)
Essentially all fields of
domain=name
Change the default domain name to name. The default domain name
is appended to a lookup request depending on the state of the
defname and search options. The domain search list contains
the parents of the default domain if it has at least two
components in its name. For example, if the default domain is
CC.Berkeley.EDU, the search list is CC.Berkeley.EDU and
Berkeley.EDU. Use the set srchlist command to specify a
different list. Use the set all command to display the list.
(Default = value from hostname, /usr/etc/resolv.conf or
LOCALDOMAIN, abbreviation = do)
srchlist=name1/name2/...
Change the default domain name to name1 and the domain search
list to name1, name2, etc. A maximum of 6 names separated by
slashes (/) can be specified. For example,
set srchlist=lcs.MIT.EDU/ai.MIT.EDU/MIT.EDU
sets the domain to lcs.MIT.EDU and the search list to the three
names. This command overrides the default domain name and
search list of the set domain command. Use the set all command
to display the list.
(Default = value based on hostname, /usr/etc/resolv.conf or
LOCALDOMAIN, abbreviation = srchl)
[no]defname
If set, append the default domain name to a single-component
lookup request (i.e., one that does not contain a period).
(Default = defname, abbreviation = [no]def)
[no]search
If the lookup request contains at least one period but doesn't
end with a trailing period, append the domain names in the
domain search list to the request until an answer is received.
(Default = search, abbreviation = [no]sea)
port=value
Change the default TCP/UDP name server port to value.
(Default = 53, abbreviation = po)
2000/2001
48
Guião
querytype=value
type=value
Change the type of information query to one of:
A
the host's Internet address.
CNAME
the canonical name for an alias.
HINFO
the host CPU and operating system type.
MINFO
the mailbox or mail list information.
MX
the mail exchanger.
NS
the name server for the named zone.
PTR
the host name if the query is an Internet address,
otherwise the pointer to other information.
SOA
the domain's ‘‘start-of-authority'' information.
TXT
the text information.
UINFO
the user information.
WKS
the supported well-known services.
Other types (ANY, AXFR, MB, MD, MF, NULL) are described in the
RFC-1035 document.
(Default = A, abbreviations = q, ty)
[no]recurse
Tell the name server to query other servers if it does not have
the information.
(Default = recurse, abbreviation = [no]rec)
retry=number
Set the number of retries to number. When a reply to a request
is not received within a certain amount of time (changed with
set timeout), the timeout period is doubled and the request is
resent. The retry value controls how many times a request is
resent before giving up.
(Default = 4, abbreviation = ret)
root=host
Change the name of the root server to host. This affects the
root command.
(Default = ns.internic.net., abbreviation = ro)
timeout=number
Change the initial timeout interval for waiting for a reply to
number seconds. Each retry doubles the timeout period.
(Default = 5 seconds, abbreviation = ti)
[no]vc
Always use a virtual circuit when sending requests to the
server.
(Default = novc, abbreviation = [no]v)
[no]ignoretc
2000/2001
49
Guião
Ignore packet truncation errors.
(Default = noignoretc, abbreviation = [no]ig)
DIAGNOSTICS
If the lookup request was not successful, an error message is printed.
Possible errors are:
Timed out
The server did not respond to a request after a certain amount of
time (changed with set timeout=value) and a certain number of
retries (changed with set retry=value).
No response from server
No name server is running on the server machine.
No records
The server does not have resource records of the current query type
for the host, although the host name is valid. The query type is
specified with the set querytype command.
Non-existent domain
The host or domain name does not exist.
Connection refused
Network is unreachable
The connection to the name or finger server could not be made at the
current time. This error commonly occurs with ls and finger
requests.
Server failure
The name server found an internal inconsistency in its database and
could not return a valid answer.
Refused
The name server refused to service the request.
Format error
The name server found that the request packet was not in the proper
format. It may indicate an error in nslookup.
FILES
/usr/etc/resolv.conf
$HOME/.nslookuprc
/usr/bsd/nslookup.help
ENVIRONMENT
HOSTALIASES
LOCALDOMAIN
initial domain name and name server addresses.
user's initial options.
summary of commands.
file containing host aliases.
overrides default domain.
SEE ALSO
resolver(3), resolver(4), named(1M),
RFC-1034 ''Domain Names - Concepts and Facilities''
PING
NAME
ping - send ICMP ECHO_REQUEST packets to network hosts
2000/2001
50
Guião
SYNOPSIS
/usr/etc/ping [-dfnqrvRL] [-c count] [-s size] [-l preload]
[-i interval] [-p pattern] [-T ttl] [-I addr] host
DESCRIPTION
Ping is a tool for network testing, measurement and management. It
utilizes the ICMP protocol's ECHO_REQUEST datagram to elicit an ICMP
ECHO_RESPONSE from a host or gateway. ECHO_REQUEST datagrams (‘‘pings'')
have an IP and ICMP header, followed by an 8-byte timestamp, and then an
arbitrary number of ‘‘pad'' bytes used to fill out the packet.
The host can be the name of a host or its Internet address.
are:
The options
-c count
Stop after sending (and receiving) count ECHO_RESPONSE packets.
-d
Set the SO_DEBUG option on the socket being used.
-f
Flood ping. Outputs packets as fast as they come back or one
hundred times per second, whichever is more. (The repetition rate
can be adjusted with the -i option.) For every ECHO_REQUEST sent a
period '.' is printed, while for ever ECHO_REPLY received a
backspace is printed. This provides a rapid display of how many
packets are being dropped. This can be extremely stressful on a
network and should be used with caution.
-i interval
Wait interval seconds between sending each packet. The default is to
wait for one second between each packet, except when the -f option
is used when the default is 0.01 second.
-l preload
Send preload packets as fast as possible before falling into the
normal mode of behavior.
-n
Numeric output only. No attempt will be made to lookup symbolic
names for host addresses. Useful if your name server is flaky or
for hosts not in the database.
-p pattern
You may specify up to 16 ‘‘pad'' bytes to fill out the packet you
send. This is useful for diagnosing data-dependent problems in a
network. For example, ‘‘-p ff'' will cause the sent packet to be
filled with all ones.
-q
Quiet output.
termination.
Nothing is displayed except the summary line on
-r
Bypass the normal routing tables and send directly to a host on an
attached network. If the host is not on a directly-attached
network, an error is returned. This option can be used to ping a
local host through an interface that has no route through it (e.g.,
after the interface was dropped by routed(1M)).
-s size
Send datagrams containing size bytes of data. The default is 56,
which translates into 64 ICMP data bytes when combined with the 8
bytes of ICMP header data. The maximum allowed value is 65468
bytes.
2000/2001
51
-v
Guião
Verbose output. ICMP packets other than ECHO RESPONSE that are
received are listed.
-I interface
Send multicast datagrams on the network interface specified by the
interface's hostname or IP address.
-L
When sending to a multicast destination address, don't loop the
datagram back to ourselves.
-R
Record
packet
the IP
ignore
Route. Includes the RECORD_ROUTE option in the ECHO_REQUEST
and displays the route buffer on returned packets. Note that
header is only large enough for six such routes. Many hosts
or discard this option.
-T ttl
Changes the default time-to-live for datagrams sent to a multicast
address.
Ping should be used primarily for manual fault isolation. Because of the
load it can impose on the network, it is unwise to use ping during normal
operations or from automated scripts. When using ping for fault
isolation, it should first be run on the local host, to verify that the
local network interface is up and running. Then, hosts and gateways
further and further away should be ‘‘pinged''.
Ping continually sends one datagram per second, and prints one line of
output for every ECHO_RESPONSE returned. On a trusted system with IP
Security Options enabled, if the network idiom is not MONO, ping also
prints a second line containing the hexadecimal representation of the IP
security option in the ECHO_RESPONSE. If the -c count option is given,
only that number of requests is sent. No output is produced if there is
no response. Round-trip times and packet loss statistics are computed.
If duplicate packets are received, they are not included in the packet
loss calculation, although the round trip time of these packets is used
in calculating the minimum/average/maximum round-trip time numbers. When
the specified number of packets have been sent (and received) or if the
program is terminated with an interrupt (SIGINT), a brief summary is
displayed. When not using the -f (flood) option, the first interrupt,
usually generated by control-C or DEL, causes ping to wait for its
outstanding requests to return. It will wait no longer than the longest
round trip time encountered by previous, successful pings. The second
interrupt stops ping immediately.
DETAILS
An IP header without options in 20 bytes. An ICMP ECHO_REQUEST packet
contains an additional 8 bytes worth of ICMP header followed by an
arbitrary amount of data. When a packetsize is given, this indicated the
size of this extra piece of data (the default is 56). Thus the amount of
data received inside of an IP packet of type ICMP ECHO_REPLY will always
be 8 bytes more than the requested data space (the ICMP header).
If the data space is at least eight bytes large, ping uses the first
eight bytes of this space to include a timestamp which it uses in the
computation of round trip times. If less than eight bytes of pad are
specified, no round trip times are given.
DUPLICATE AND DAMAGED PACKETS
Ping will report duplicate and damaged packets. Duplicate packets should
never occur, and seem to be caused by inappropriate link-level
2000/2001
52
Guião
retransmissions. Duplicates may occur in many situations and are rarely
(if ever) a good sign, although the presence of low levels of duplicates
may not always be cause for alarm.
Damaged packets are obviously serious cause for alarm and often indicate
broken hardware somewhere in the ping packet's path (in the network or in
the hosts).
TRYING DIFFERENT DATA PATTERNS
The (inter)network layer should never treat packets differently depending
on the data contained in the data portion. Unfortunately, data-dependent
problems have been known to sneak into networks and remain undetected for
long periods of time. In many cases the particular pattern that will
have problems is something that doesn't have sufficient ‘‘transitions'',
such as all ones or all zeros, or a pattern right at the edge, such as
almost all zeros. It isn't necessarily enough to specify a data pattern
of all zeros (for example) on the command line because the pattern that
is of interest is at the data link level, and the relationship between
what you type and what the controllers transmit can be complicated.
This means that if you have a data-dependent problem you will probably
have to do a lot of testing to find it. If you are lucky, you may manage
to find a file that either can't be sent across your network or that
takes much longer to transfer than other similar length files. You can
then examine this file for repeated patterns that you can test using the
-p option of ping.
TTL DETAILS
The TTL value of an IP packet represents the maximum number of IP routers
that the packet can go through before being thrown away. In current
practice you can expect each router in the Internet to decrement the TTL
field by exactly one.
The TCP/IP specification says that the TTL field for TCP packets should
be set to 60, but many systems use smaller values (IRIX and 4.3BSD use
30, 4.2BSD used 15).
The maximum possible value of this field is 255, and most Unix systems
set the TTL field of ICMP ECHO_REQUEST packets to 255. This is why you
will find you can ‘‘ping'' some hosts, but not reach them with telnet or
ftp.
In normal operation ping prints the ttl value from the packet it
receives. When a remote system receives a ping packet, it can do one of
three things with the TTL field in its response:
+o Not change it; this is what Berkeley Unix systems did before the
4.3BSD-tahoe release. In this case the TTL value in the received
packet will be 255 minus the number of routers in the round-trip path.
+o Set it to 255; this is what IRIX and current Berkeley Unix systems do.
In this case the TTL value in the received packet will be 255 minus the
number of routers in the path from the remote system to the pinging
host.
+o Set it to some other value. Some machines use the same value for ICMP
packets that they use for TCP packets, for example either 30 or 60.
Others may use completely wild values.
BUGS
Many Hosts and Gateways ignore the RECORD_ROUTE option.
2000/2001
53
Guião
The maximum IP header length is too small for options like RECORD_ROUTE
to be completely useful. There's not much that can be done about this,
however.
Flood pinging is not recommended in general, and flood pinging the
broadcast address should only be done under very controlled conditions.
The record-route option does not work with hosts using network code
derived from 4.3BSD.
SEE ALSO
netstat(1), ifconfig(1M), routed(1M)
NVRAM
NAME
nvram, sgikopt - get or set non-volatile RAM variable(s)
SYNOPSIS
nvram [-v] [name [value]]
sgikopt [name...]
DESCRIPTION
Nvram may be used to set or print the values of non-volatile RAM
variables. If name is specified, nvram prints the corresponding value.
If value is specified and name is defined in non-volatile RAM, nvram
replaces name's definition string with value. The -v option causes nvram
to print a line of the form name=value after getting or setting the named
variable. When invoked with no arguments, all known variables are
displayed in the name=value form.
If invoked as sgikopt, more than one name may be given. Names that do
not match known variables are ignored. The exit status is 1 if any
arguments don't match, and 0 otherwise.
NOTES
Non-volatile RAM contains a small set of well-known strings at fixed
offsets. Nvram may not be used to define new variables.
Only the super-user may set variables.
The term "Non-volatile RAM" is somewhat misleading, because some
variables are placed only in volatile RAM, and will be reset on power-up.
Different models have different mixes of volatile and non-volatile
variables.
DIAGNOSTICS
If an attempt to get or set a variable fails for any reason, nvram prints
an appropriate message on standard error and exits with non-zero status.
Not all machines support the ability to change the contents of nonvolatile memory with the nvram command. To change the contents of nonvolatile memory on those machines you must use the PROM monitor setenv
command.
SEE ALSO
sgikopt(2), syssgi(2), prom(1m)
2000/2001
54
Guião
IFCONFIG
NAME
ifconfig - configure network interface parameters
SYNOPSIS
/usr/etc/ifconfig interface address_family [ address [ dest_address ] ] [
parameters ]
/usr/etc/ifconfig interface [ protocol_family ]
DESCRIPTION
Ifconfig is used to assign an address to a network interface and/or
configure network interface parameters. Ifconfig is invoked at boot time
from /etc/init.d/network to define the network address of each interface
present on a machine; you may also use it once the system is up to
redefine an interface's address or other operating parameters. The
interface parameter is a string of the form ‘‘name unit'', e.g.,
‘‘enp0''. (The -i option to netstat(1) displays the interfaces on the
machine.)
Since an interface may receive transmissions in differing protocols, each
of which may require separate naming schemes, it is necessary to specify
the address_family, which may change the interpretation of the remaining
parameters. Currently, just the ‘‘inet'' address family is supported.
For the Internet family, the address is either an Internet address
expressed in the Internet standard ‘‘dot notation'' (see inet(3N)), or a
host name present in the hosts(4) file, /etc/hosts. (Other hosts
databases, such as named and NIS, are ignored.)
Only the super-user may modify the configuration of a network interface.
The following parameters may be set with ifconfig:
up
Mark an interface ‘‘up''. This may be used to enable an
interface after an ‘‘ifconfig down.'' It happens
automatically when setting the first address on an
interface. If the interface was reset when previously
marked down, the hardware will be re-initialized.
down
Mark an interface ‘‘down''. When an interface is marked
‘‘down'', the system will not attempt to transmit messages
through that interface. If possible, the interface will be
reset to disable reception as well. This action does not
automatically disable routes using the interface.
arp
Enable the use of the Address Resolution Protocol in
mapping between network level addresses and link level
addresses (default). This is currently implemented for
mapping between Internet addresses and 10Mb/s Ethernet
addresses.
-arp
Disable the use of the Address Resolution Protocol.
alias addr
Establish an additional network address for this
interface. This can be useful in permitting a single
physical interface to accept packets addressed to several
different addresses such as when one is changing network
numbers, and one wishes to accept packets addressed to the
old interface. The 'broadcast' and 'netmask' options may
be used in conjunction with the 'alias' option. When using
2000/2001
55
Guião
aliases one may have to change the configuration of routed
especially if aliases are on different networks than the
primary address. Aliases are added as host entries in the
routing tables for routed. See (routed(1m)) for more
information on this.
-alias|delete addr
Deletes a previously added alias.
metric n
Set the routing metric of the
The routing metric is used by
(routed(1m)). Higher metrics
route less favorable; metrics
to the destination network or
interface to n, default 0.
the routing protocol
have the effect of making a
are counted as addition hops
host.
netmask mask
Specify how much of the address to reserve for subdividing
networks into sub-networks. The mask includes the network
part of the local address and the subnet part, which is
taken from the host field of the address. The mask can be
specified as a single hexadecimal number with a leading
0x, with a dot-notation Internet address, or with a
pseudo-network name listed in the network table
networks(4). The mask contains 1's for the bit positions
in the 32-bit address which are to be used for the network
and subnet parts, and 0's for the host part. The mask
should contain at least the standard network portion, and
the subnet field should be contiguous with the network
portion.
broadcast addr Specify the address to use to represent broadcasts to the
network. The default broadcast address is the address
with a host part of all 1's.
dest_addr
Specify the address of the correspondent on the other end
of a point-to-point link.
debug
Enable driver-dependent debugging code; usually, this
turns on extra console error logging.
-debug
Disable driver-dependent debugging code.
Ifconfig displays the current configuration for a network interface when
no optional parameters are supplied. If a protocol family is specified,
ifconfig will report only the details specific to that protocol family.
NOTE
Network interfaces on the IRIS-4D can only receive and not send packets
that use ‘‘trailer'' link-level encapsulation. Therefore, ifconfig does
not accept the trailers parameter.
DIAGNOSTICS
Messages indicating the specified interface does not exist, the requested
address is unknown, or the user is not privileged and tried to alter an
interface's configuration.
FILES
/etc/hosts
host-address database
/etc/config/ifconfig-?.options
site-specific options
(1 file per interface)
2000/2001
56
Guião
SEE ALSO
netstat(1), network(1M)
NETSTAT
NAME
netstat - show network status
SYNOPSIS
netstat
netstat
netstat
netstat
netstat
[ -Aanu ] [ -f address_family ] [ system ] [ core ]
[ -imnqrsM ] [ -f address_family ] [ system ] [ core ]
[ -n ] [ -I interface ] interval [ system ] [ core ]
-C [ -n ] [ interval ] [ system ]
[ -p protocol ] [ system ] [ core ]
DESCRIPTION
The netstat command symbolically displays the contents of various
network-related data structures. There are a number of output formats,
depending on the options for the information presented. The first form
of the command displays a list of active sockets for each protocol. The
second form presents the contents of one of the other network data
structures according to the option selected. Using the third form, with
an interval specified, netstat will continuously display the information
regarding packet traffic on the configured network interfaces. The
fourth form displays statistics about the named protocol.
The options have the following meaning:
-A
With the default display, show the address of any protocol control
blocks associated with sockets; used for debugging.
-a
With the default display, show the state of all sockets; normally
sockets used by server processes are not shown.
-l
With the default display, on systems supporting IP security options,
show the mandatory and discretionary access control attributes
associated with sockets. These consist of a mandatory access
control label, printed at the beginning of each line, and a socket
uid and acl, printed at the end of each line. (For AF_INET sockets
only, a second mandatory access control label, SndLabel, is also
shown. SndLabel is a copy of the label in the u_area.) On systems
not supporting IP security options, -l is silently ignored.
-C
Display the contents of several of the other formats in dynamic
"full-screen" forms. Many of the values can be displayed as simple
totals (r or "reset"), changes during the previous interval (d or
"delta"), or changes since a fix moment (z or "zero").
-i
Show the state of interfaces which have been auto-configured
(interfaces statically configured into a system, but not located at
boot time are not shown). When -a is also present, show all
addresses (unicast, multicast and link-level) associated with each
interface.
-iq
Show the information for -i with the number of packets currently in
the output queue, the queue size, and the number of dropped packets
due to a full queue.
-I interface
Show information only about this interface; used with an interval as
2000/2001
57
Guião
described below.
-m
Show statistics recorded by the memory management routines (the
network manages a private pool of memory buffers).
-n
Show network addresses as numbers (normally netstat interprets
addresses and attempts to display them symbolically). This option
may be used with any of the display formats.
-p protocol
Show statistics about protocol, which is either a well-known name
for a protocol or an alias for it. Some protocol names and aliases
are listed in the file /etc/protocols. A null response typically
means that there are no interesting numbers to report. The program
will complain if protocol is unknown or if there is no statistics
routine for it. (This includes counting packets for the HELO
routing protocol as unknown.)
-s
Show per-protocol statistics.
-r
Show the routing tables.
statistics instead.
-M
Show the kernel multicast routing tables. When -s is also present,
show multicast routing statistics instead.
When -s is also present, show routing
-f address_family
Limit statistics or address control block reports to those of the
specified address family. The following address families are
recognized: inet, for AF_INET, and unix, for AF_UNIX. (ns, for
AF_NS is not currently supported.)
-u
A synonym for -f unix.
The arguments, system and core allow substitutes for the defaults
‘‘/unix'' and ‘‘/dev/kmem''.
The default display, for active sockets, shows the local and remote
addresses, send and receive queue sizes (in bytes), protocol, and the
internal state of the protocol. Address formats are of the form
‘‘host.port'' or ‘‘network.port'' if a socket's address specifies a
network but no specific host address. When known the host and network
addresses are displayed symbolically according to the data bases
/etc/hosts and /etc/networks, respectively. If a symbolic name for an
address is unknown, or if the -n option is specified, the address is
printed numerically, according to the address family. For more
information regarding the Internet ‘‘dot format,'' refer to inet(3N).
Unspecified, or ‘‘wildcard'', addresses and ports appear as ‘‘*''.
The interface display provides a table of cumulative statistics regarding
packets transferred, errors, and collisions. The network addresses of
the interface and the maximum transmission unit (‘‘mtu'') are also
displayed.
The routing table display indicates the available routes and their
status. Each route consists of a destination host or network and a
gateway to use in forwarding packets. The flags field shows the state of
the route (‘‘U'' if ‘‘up''), whether the route is to a gateway (‘‘G'') or
a host (‘‘H''), whether the route was created dynamically by a redirect
(‘‘D''), and whether the route has been modified by a redirect (‘‘M'').
Direct routes are created for each interface attached to the local host;
2000/2001
58
Guião
the gateway field for such entries shows the address of the outgoing
interface. The MTU field shows the MTU value set with the route(1M)
command for that route. The RTT and RTTvar fields show the estimated
round-trip time (RTT) and the variance in RTT for routes with large
amounts of TCP traffic. The RTT and RTTvar values are in seconds with a
resolution of .125 seconds. The use field provides a count of the number
of packets sent using that route. The interface entry indicates the
network interface utilized for the route.
When netstat is invoked with an interval argument, it displays a running
count of statistics related to network interfaces. This display consists
of a column for the primary interface (the first interface found during
autoconfiguration) and a column summarizing information for all
interfaces. The primary interface may be replaced with another interface
with the -I option. The first line of each screen of information
contains a summary since the system was last rebooted. Subsequent lines
of output show values accumulated over the preceding interval.
SEE ALSO
hosts(4), networks(4), nfsstat(1M), protocols(4), services(4), smtstat(1)
BUGS
The notion of errors is ill-defined.
TELNET
NAME
telnet - User interface to the TELNET protocol
SYNOPSIS
telnet [-d] [-n tracefile] [-l user | -a] [-e escape-char] [host [port]]
DESCRIPTION
The telnet command is used to communicate with another host using the
TELNET protocol. If telnet is invoked without the host argument, it
enters command mode, indicated by its prompt (telnet>). In this mode, it
accepts and executes the commands listed below. If it is invoked with
arguments, it performs an open command (see below) with those arguments.
Options:
-d
Sets the initial value of the debug toggle to TRUE.
-n tracefile
Opens tracefile for recording trace information.
tracefile command below.
See the set
-l user When connecting to the remote system, if the remote system
understands the ENVIRON option, then user will be sent to the
remote system as the value for the variable USER. This option
may also be used with the open command.
-a
Auto-login. Same as specifying -l with your user name.
option may also be used with the open command.
This
-e escape-char
Sets the initial telnet escape character to escape-char. If
escape-char is the null character (specified by "" or ''), then
there will be no escape character.
2000/2001
59
Guião
host
Indicates the official name, an alias, or the Internet address of
a remote host.
port
Indicates a port number (address of an application).
is not specified, the default telnet port is used.
If a number
Once a connection has been opened, telnet will attempt to enable the
TELNET LINEMODE option. If this fails, then telnet will revert to one of
two input modes: either "character at a time" or "old line by line"
depending on what the remote system supports.
When LINEMODE is enabled, character processing is done on the local
system, under the control of the remote system. When input editing or
character echoing is to be disabled, the remote system will relay that
information. The remote system will also relay changes to any special
characters that happen on the remote system, so that they can take effect
on the local system.
In "character at a time" mode, most text typed is immediately sent to the
remote host for processing.
In "old line by line" mode, all text is echoed locally, and (normally)
only completed lines are sent to the remote host. The "local echo
character" (initially "^E") may be used to turn off and on the local echo
(this would mostly be used to enter passwords without the password being
echoed).
If the LINEMODE option is enabled, or if the localchars toggle is TRUE
(the default for "old line by line"; see below), the user's quit, intr,
and flush characters are trapped locally, and sent as TELNET protocol
sequences to the remote side. If LINEMODE has ever been enabled, then
the user's susp and eof are also sent as TELNET protocol sequences, and
quit is sent as a TELNET ABORT instead of BREAK. There are options (see
toggle autoflush and toggle autosynch below) which cause this action to
flush subsequent output to the terminal (until the remote host
acknowledges the TELNET sequence) and flush previous terminal input (in
the case of quit and intr).
While connected to a remote host, telnet command mode may be entered by
typing the telnet "escape character" (initially "^]"). When in command
mode, the normal terminal editing conventions are available.
The following telnet commands are available. Only enough of each command
to uniquely identify it need be typed (this is also true for arguments to
the mode, set, toggle, unset, slc, environ, and display commands).
close
Close a TELNET session and return to command mode.
display [ argument... ]
Displays all, or some, of the set and toggle values (see
below).
mode type
Type is one of several options, depending on the state of the
TELNET session. The remote host is asked for permission to go
into the requested mode. If the remote host is capable of
entering that mode, the requested mode will be entered.
character
2000/2001
60
Guião
Disable the TELNET LINEMODE option, or, if the remote side
does not understand the LINEMODE option, then enter
"character at a time" mode.
line
Enable the TELNET LINEMODE option, or, if the remote side
does not understand the LINEMODE option, then attempt to
enter "old-line-by-line" mode.
isig (-isig)
Attempt to enable (disable) the TRAPSIG mode of the
LINEMODE option. This requires that the LINEMODE option
be enabled.
edit (-edit)
Attempt to enable (disable) the EDIT mode of the LINEMODE
option. This requires that the LINEMODE option be
enabled.
softtabs (-softtabs)
Attempt to enable (disable) the SOFT_TAB mode of the
be enabled.
litecho (-litecho)
Attempt to enable (disable) the LIT_ECHO mode of the
be enabled.
?
Prints out help information for the mode command.
open host [ [-l user | -a] [-]port ]
Open a connection to the named host. If no port number is
specified, telnet will attempt to contact a TELNET server at
the default port. The host specification may be either a host
name (see hosts(4)) or an Internet address specified in the
"dot notation" (see inet(3N)). The -l option may be used to
specify the user name to be passed to the remote system via the
ENVIRON option. The -a option sends your user name to the
remote system via the ENVIRON option. When connecting to a
non-standard port, telnet omits any automatic initiation of
TELNET options. When the port number is preceded by a minus
sign, the initial option negotiation is done. After
establishing a connection, the .telnetrc in the user's home
directory is opened. Lines beginning with a # are comment
lines. Blank lines are ignored. Lines that begin without
whitespace are the start of a machine entry. The first thing
on the line is the name of the machine that is being connected
to. The rest of the line, and successive lines that begin with
whitespace are assumed to be telnet commands and are processed
as if they had been typed in manually to the telnet command
prompt.
quit
Close any open TELNET session and exit telnet. An end of file
(in command mode) will also close a session and exit.
send arguments
Sends one or more special character sequences to the remote
host. The following are the arguments which may be specified
2000/2001
61
Guião
(more than one argument may be specified at a time):
abort
Sends the TELNET ABORT (ABORT processes) sequence.
ao
Sends the TELNET AO (Abort Output) sequence, which should
cause the remote system to flush all output from the
remote system to the user's terminal.
ayt
Sends the TELNET AYT (Are You There) sequence, to which
the remote system may or may not choose to respond.
brk
Sends the TELNET BRK (Break) sequence, which may have
significance to the remote system.
ec
Sends the TELNET EC (Erase Character) sequence, which
should cause the remote system to erase the last character
entered.
el
Sends the TELNET EL (Erase Line) sequence, which should
cause the remote system to erase the line currently being
entered.
eof
Sends the TELNET EOF (End Of File) sequence.
eor
Sends the TELNET EOR (End of Record) sequence.
escape
Sends the current telnet escape character (initially
"^]").
ga
Sends the TELNET GA (Go Ahead) sequence, which likely has
no significance to the remote system.
getstatus
If the remote side supports the TELNET STATUS command,
getstatus will send the subnegotiation to request that the
server send its current option status.
ip
Sends the TELNET IP (Interrupt Process) sequence, which
should cause the remote system to abort the currently
running process.
nop
Sends the TELNET NOP (No OPeration) sequence.
susp
Sends the TELNET SUSP (SUSPend process) sequence.
synch
Sends the TELNET SYNCH sequence.
2000/2001
This sequence causes the
62
Guião
remote system to discard all previously typed (but not yet
read) input. This sequence is sent as TCP urgent data
(and may not work if the remote system is a 4.2 BSD system
- if it doesn't work, a lower case "r" may be echoed on
the terminal).
?
Prints out help information for the send command.
set argument value
unset arguments...
The set command will set any one of a number of telnet
variables to a specific value or to TRUE. The special value
off turns off the function associated with the variable, this
is equivalent to using the unset command. The unset command
will disable or set to FALSE any of the specified functions.
The values of variables may be interrogated with the display
command. The variables which may be set or unset, but not
toggled, are listed here. In addition, any of the variables
for the toggle command may be explicitly set or unset using the
set and unset commands.
echo
This is the value (initially "^E") which, when in "line by
line" mode, toggles between doing local echoing of entered
characters (for normal processing), and suppressing
echoing of entered characters (for entering, say, a
password).
eof
If telnet is operating in LINEMODE or "old line by line"
mode, entering this character as the first character on a
line will cause this character to be sent to the remote
system. The initial value of the eof character is taken
to be the terminal's eof character.
erase
If telnet is in localchars mode (see toggle localchars
below), and if telnet is operating in "character at a
time" mode, then when this character is typed, a TELNET EC
sequence (see send ec above) is sent to the remote system.
The initial value for the erase character is taken to be
the terminal's erase character.
escape
This is the telnet escape character (initially "^[") which
causes entry into telnet command mode (when connected to a
remote system).
flushoutput
below) and the flushoutput character is typed, a TELNET AO
sequence (see send ao above) is sent to the remote host.
The initial value for the flush character is taken to be
the terminal's flush character.
interrupt
below) and the interrupt character is typed, a TELNET IP
2000/2001
63
Guião
sequence (see send ip above) is sent to the remote host.
The initial value for the interrupt character is taken to
be the terminal's intr character.
kill
below), and if telnet is operating in "character at a
time" mode, then when this character is typed, a TELNET EL
sequence (see send el above) is sent to the remote system.
The initial value for the kill character is taken to be
the terminal's kill character.
lnext
mode, then this character is taken to be the terminal's
lnext character. The initial value for the lnext
character is taken to be the terminal's lnext character.
quit
below) and the quit character is typed, a TELNET BRK
sequence (see send brk above) is sent to the remote host.
The initial value for the quit character is taken to be
the terminal's quit character.
reprint
reprint character. The initial value for the reprint
character is taken to be the terminal's reprint character.
start
If the TELNET TOGGLE-FLOW-CONTROL option has been enabled,
then this character is taken to be the terminal's start
character. The initial value for the kill character is
taken to be the terminal's start character.
stop
If the TELNET TOGGLE-FLOW-CONTROL option has been enabled,
then this character is taken to be the terminal's stop
character. The initial value for the kill character is
taken to be the terminal's stop character.
susp
If telnet is in localchars mode, or LINEMODE is enabled,
and the suspend character is typed, a TELNET SUSP sequence
(see send susp above) is sent to the remote host. The
initial value for the suspend character is taken to be the
terminal's suspend character.
tracefile
This is the file to which the output, caused by netdata or
option tracing being TRUE, will be written. If it is set
to '-', then tracing information will be written to
standard output (the default).
worderase
worderase character. The initial value for the worderase
character is taken to be the terminal's worderase
2000/2001
64
Guião
character.
slc state
The slc command (Set Local Characters) is used to set or
change the state of the special characters when the TELNET
LINEMODE option has been enabled. Special characters are
characters that get mapped to TELNET commands sequences
(like ip or quit) or line editing characters (like erase
and kill). By default, the local special characters are
exported.
export
Switch to the local defaults for the special
characters. The local default characters are those
of the local terminal at the time when telnet was
started.
import
Switch to the remote defaults for the special
characters. The remote default characters are those
of the remote system at the time when the TELNET
connection was established.
check
Verify the current settings for the current special
characters. The remote side is requested to send all
the current special character settings, and if there
are any discrepancies with the local side, the local
side will switch to the remote value.
?
Prints out help information for the slc command.
environ arguments...
The environ command is used to manipulate the variables
that my be sent through the ENVIRON option. The initial
set of variables is taken from the user's environment with
only the DISPLAY and PRINTER variables being exported by
default.
Valid arguments for the environ command are:
define variable value
Define the variable variable to have a value of
value. Any variables defined by this command are
automatically exported. The value may be enclosed in
single or double quotes so that tabs and spaces may
be included.
undefine variable
Remove variable from the list of environment
variables.
export variable
Mark the variable variable to be exported to the
remote side.
unexport variable
Mark the variable variable to not be exported unless
explicitly asked for by the remote side.
2000/2001
65
Guião
send variable
Send the variable variable to the remote side.
list
List the current set of environment variables. Those
marked with a **** will be sent automatically, other
variables will only be sent if explicitly requested.
?
Prints out help information for the environ command.
?
Displays the legal set (unset) commands.
toggle arguments...
Toggle (between TRUE and FALSE) various flags that control how
telnet responds to events. These flags may be set explicitly
to TRUE or FALSE using the set and unset commands listed above.
More than one argument may be specified. The state of these
flags may be interrogated with the display command. Valid
arguments are:
autoflush
If autoflush and localchars are both TRUE, then when the
ao, intr, or quit characters are recognized (and
transformed into TELNET sequences; see set above for
details), telnet refuses to display any data on the user's
terminal until the remote system acknowledges (via a
TELNET TIMING MARK option) that it has processed those
TELNET sequences. The initial value for this toggle is
TRUE if the terminal user had not done an "stty noflsh",
otherwise FALSE (see stty(1)).
autosynch
If autosynch and localchars are both TRUE, then when
either the intr or quit characters is typed (see set above
for descriptions of the intr and quit characters), the
resulting TELNET sequence sent is followed by the TELNET
SYNCH sequence. This procedure should cause the remote
system to begin throwing away all previously typed input
until both of the TELNET sequences have been read and
acted upon. The initial value of this toggle is FALSE.
binary
Enable or disable the TELNET BINARY option on both input
and output.
inbinary
Enable or disable the TELNET BINARY option on input.
outbinary
Enable or disable the TELNET BINARY option on output.
crlf
If this is TRUE, then carriage returns will be sent as
<CR><LF>. If this is FALSE, then carriage returns will be
send as <CR><NUL>. The initial value for this toggle is
FALSE.
crmod
2000/2001
66
Guião
Toggle carriage return mode. When this mode is enabled,
most carriage return characters received from the remote
host will be mapped into a carriage return followed by a
line feed. This mode does not affect those characters
typed by the user, only those received from the remote
host. This mode is not very useful unless the remote host
only sends carriage return, but never line feed. The
initial value for this toggle is FALSE.
debug
Toggles socket level debugging (useful only to the
superuser). The initial value for this toggle is FALSE.
localchars
If this is TRUE, then the flush, interrupt, quit, erase,
and kill characters (see set above) are recognized
locally, and transformed into (hopefully) appropriate
TELNET control sequences (respectively ao, ip, brk, ec,
and el; see send above). The initial value for this
toggle is TRUE in "old line by line" mode, and FALSE in
"character at a time" mode. When the LINEMODE option is
enabled, the value of localchars is ignored, and assumed
to always be TRUE. If LINEMODE has ever been enabled,
then quit is sent as abort, and eofand suspend are sent as
eofand susp, see send above).
netdata
Toggles the display of all network data (in hexadecimal
format). The initial value for this toggle is FALSE.
options
Toggles the display of some internal telnet protocol
processing (having to do with TELNET options). The
initial value for this toggle is FALSE.
prettydump
When the netdata toggle is enabled, if prettydump is
enabled the output from the netdata command will be
formatted in a more user readable format. Spaces are put
between each character in the output, and the beginning of
any TELNET escape sequence is preceded by a '*' to aid in
locating them.
?
Displays the legal toggle commands.
z
Suspend telnet.
the csh(1).
This command only works when the user is using
! [ command ]
Execute a single command in a subshell on the local system. If
command is omitted, then an interactive subshell is invoked.
status
Show the current status of telnet. This includes the peer one
is connected to, as well as the current mode.
? [ command ]
Get help. With no arguments, telnet prints a help summary. If
a command is specified, telnet will print the help information
for just that command.
2000/2001
67
Guião
ENVIRONMENT
Telnet uses at least the HOME, SHELL, USER, DISPLAY, and TERM environment
variables. Other environment variables may be propagated to the other
side via the TELNET ENVIRON option.
FILES
~/.telnetrc
user customized telnet startup values
NOTES
On some remote systems, echo has to be turned off manually when in "old
line by line" mode.
In "old line by line" mode or LINEMODE the terminal's eof character is
only recognized (and sent to the remote system) when it is the first
character on a line.
2000/2001
68
Guião
ANEXO III
2000/2001
69
Guião
Destination specified is invalid.
Pinging students.students.iscte.pt [10.10.10.1] with 32 bytes of data:
Reply from 10.10.10.1: bytes=32 time<10ms TTL=63
Pinging socrates.students.iscte.pt [10.10.10.2] with 32 bytes of data:
Pinging
Request
Request
Request
Request
10.10.10.3 with 32 bytes of data:
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
www.students.iscte.pt [10.10.10.6] with 32 bytes of data:
timed out.
timed out.
timed out.
timed out.
Pinging lp.students.iscte.pt [10.10.10.7]
with 32 bytes of data:
TTL=128
TTL=128
TTL=128
TTL=128
Pinging work.students.iscte.pt [10.10.10.8] with 32 bytes of data:
Pinging software.students.iscte.pt [10.10.10.9] with 32 bytes of data:
Pinging areas.students.iscte.pt [10.10.10.10] with 32 bytes of data:
2000/2001
70
Reply
Reply
Reply
Reply
from
from
from
from
Pinging
data:
Request
Request
Request
Request
10.10.10.10:
10.10.10.10:
10.10.10.10:
10.10.10.10:
bytes=32
bytes=32
bytes=32
bytes=32
Guião
time<10ms
time<10ms
time<10ms
time<10ms
TTL=128
TTL=128
TTL=128
TTL=128
alunosbdc.students.iscte.pt [10.10.10.11] with 32 bytes of
timed
timed
timed
timed
out.
out.
out.
out.
Pinging alunospdc.students.iscte.pt [10.10.10.12] with 32 bytes of
data:
Pinging bd.students.iscte.pt [10.10.10.13]
TTL=128
TTL=128
TTL=128
TTL=128
Pinging
Request
Request
Request
Request
anubis.students.iscte.pt [10.10.10.14] with 32 bytes of data:
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
osiris.students.iscte.pt [10.10.10.15] with 32 bytes of data:
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
baco.students.iscte.pt [10.10.10.16] with 32 bytes of data:
timed out.
timed out.
timed out.
timed out.
Pinging eti-lab-01.students.iscte.pt [10.10.10.17] with 32 bytes of
data:
Pinging
Request
Request
Request
Request
sql.students.iscte.pt [10.10.10.18] with 32 bytes of data:
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
2000/2001
71
Guião
Pinging
data:
Request
Request
Request
Request
nb-compac.students.iscte.pt [10.10.10.20] with 32 bytes of
Pinging
data:
Request
Request
Request
Request
axis-alunos.students.iscte.pt [10.10.10.21] with 32 bytes of
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
timed
timed
timed
timed
timed
timed
timed
timed
out.
out.
out.
out.
out.
out.
out.
out.
Pinging net-TALLY.students.iscte.pt [10.10.10.23] with 32 bytes of
data:
Pinging mercurio.students.iscte.pt [10.10.10.24] with 32 bytes of
data:
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
I0E08-1.students.iscte.pt [10.10.10.26] with 32 bytes of data:
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Request timed out.
2000/2001
72
Guião
Request timed out.
Request timed out.
Request timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging rede33.students.iscte.pt
Reply from 10.10.10.33: bytes=32
[10.10.10.33] with 32 bytes of data:
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging
Request
Request
Request
Request
rede37.students.iscte.pt [10.10.10.37] with 32 bytes of data:
timed out.
timed out.
timed out.
timed out.
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging rede39.students.iscte.pt [10.10.10.39] with 32 bytes of data:
2000/2001
73
Guião
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
2000/2001
74
Guião
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
2000/2001
75
Guião
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
timed out.
timed out.
timed out.
timed out.
2000/2001
76
Pinging
Request
Request
Request
Request
Guião
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
timed out.
timed out.
timed out.
timed out.
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
2000/2001
77
Reply
Reply
Reply
Reply
from
from
from
from
10.10.10.80:
10.10.10.80:
10.10.10.80:
10.10.10.80:
bytes=32
bytes=32
bytes=32
bytes=32
Guião
time<10ms
time<10ms
time<10ms
time<10ms
TTL=128
TTL=128
TTL=128
TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
2000/2001
78
Guião
Request timed out.
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
2000/2001
79
Pinging
Request
Request
Request
Request
Guião
timed out.
timed out.
timed out.
timed out.
Pinging ETI-LAB-04 [10.10.10.101]
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging ETI-LAB-05 [10.10.10.102]
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging I1SE1-16 [10.10.10.103] with 32 bytes of data:
Pinging ETI-LAB-03 [10.10.10.104]
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging ETI-LAB-07 [10.10.10.105]
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging ETI-LAB-08 [10.10.10.106]
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging I1S19-13 [10.10.10.107] with 32 bytes of data:
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
2000/2001
80
Guião
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging ETI-LAB-10 [10.10.10.115]
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging IS19-03 [10.10.10.118] with 32 bytes of data:
2000/2001
81
Request
Request
Request
Request
timed
timed
timed
timed
Guião
out.
out.
out.
out.
Pinging I1E14-16 [10.10.10.121] with 32 bytes of data:
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging IE14-12 [10.10.10.126] with 32 bytes of data:
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
2000/2001
82
Guião
Pinging I2ES-07 [10.10.10.131] with 32 bytes of data:
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Request timed out.
Request timed out.
2000/2001
83
Guião
Request timed out.
Request timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
2000/2001
84
Reply
Reply
Reply
Reply
from
from
from
from
10.10.10.150:
10.10.10.150:
10.10.10.150:
10.10.10.150:
Guião
bytes=32
bytes=32
bytes=32
bytes=32
time<10ms
time<10ms
time<10ms
time<10ms
TTL=128
TTL=128
TTL=128
TTL=128
Pinging I0S07-11B [10.10.10.156] with 32 bytes of data:
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
2000/2001
85
Guião
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
2000/2001
86
Guião
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging INSTALA [10.10.10.180] with 32 bytes of data:
2000/2001
87
Guião
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging SONORA [10.10.10.182] with 32 bytes
of data:
TTL=32
TTL=32
TTL=32
TTL=32
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
2000/2001
88
Guião
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Reply from 10.10.10.194: bytes=32 time=10ms TTL=128
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
2000/2001
89
Guião
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging ETI-LAB-09 [10.10.10.211] with 32 bytes of data:
2000/2001
90
Reply
Reply
Reply
Reply
from
from
from
from
10.10.10.211:
10.10.10.211:
10.10.10.211:
10.10.10.211:
Guião
bytes=32
bytes=32
bytes=32
bytes=32
time<10ms
time<10ms
time<10ms
time<10ms
TTL=128
TTL=128
TTL=128
TTL=128
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging ETI-LAB-06 [10.10.10.215]
Pinging
Request
Request
Request
Request
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
time<10ms TTL=128
timed out.
timed out.
timed out.
timed out.
2000/2001
91
Guião
2000/2001
92
Guião
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
2000/2001
93
Guião
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
Reply from 10.10.10.247: bytes=32 time=10ms
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
TTL=255
Pinging
Request
Request
Request
Request
timed out.
timed out.
timed out.
timed out.
2000/2001
94
Guião
Pinging
data:
Request
Request
Request
Request
swalunos.students.iscte.pt [10.10.10.252] with 32 bytes of
timed
timed
timed
timed
out.
out.
out.
out.
Pinging fw.students.iscte.pt [10.10.10.253]
Reply from 10.10.10.253: bytes=32 time=10ms
TTL=255
TTL=255
TTL=255
TTL=255
Pinging fwi.students.iscte.pt [10.10.10.254] with 32 bytes of data:
Interface: 10.10.10.112 on Interface 2
Internet Address
Physical Address
10.10.10.1
00-00-e8-67-7c-d2
10.10.10.2
00-03-47-08-c7-d9
10.10.10.7
00-4f-4e-06-5b-86
10.10.10.8
00-80-5f-0d-2d-e0
10.10.10.9
00-80-5f-bb-8d-88
10.10.10.10
00-d0-b7-d3-60-0b
10.10.10.12
00-80-5f-bb-68-f4
10.10.10.13
00-4f-4e-01-ad-9a
10.10.10.17
00-4f-4e-06-3a-85
10.10.10.23
00-04-00-34-00-af
10.10.10.24
00-4f-4e-04-35-76
10.10.10.33
00-00-e8-22-7c-fc
10.10.10.34
00-00-e8-22-a3-7d
10.10.10.35
00-00-e8-18-9d-98
10.10.10.36
00-00-e8-4e-c2-fc
10.10.10.37
00-00-e8-22-bd-ac
10.10.10.38
00-00-e8-22-77-a6
10.10.10.39
00-00-e8-22-7c-cc
10.10.10.40
00-00-e8-22-74-dd
10.10.10.41
00-60-97-c2-42-37
10.10.10.42
00-00-e8-4e-c1-8b
10.10.10.43
00-60-97-c2-47-29
10.10.10.44
00-4f-4e-03-13-f0
10.10.10.45
00-00-e8-22-74-85
10.10.10.46
00-60-97-c2-45-a0
10.10.10.47
00-4f-4e-06-3a-d2
10.10.10.48
00-4f-4e-05-7e-cf
10.10.10.50
00-4f-4e-07-56-2b
10.10.10.51
00-4f-4e-08-5e-7b
10.10.10.52
00-4f-4e-08-5e-75
10.10.10.53
00-4f-4e-08-5e-7f
10.10.10.54
00-4f-4e-08-5e-7d
10.10.10.55
00-4f-4e-08-5e-77
10.10.10.56
00-4f-4e-06-ff-fc
10.10.10.57
00-4f-4e-07-03-f3
10.10.10.58
00-4f-4e-07-51-1c
10.10.10.59
00-4f-4e-00-0c-97
Type
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
2000/2001
95
10.10.10.60
10.10.10.61
10.10.10.62
10.10.10.63
10.10.10.65
10.10.10.66
10.10.10.67
10.10.10.68
10.10.10.70
10.10.10.72
10.10.10.73
10.10.10.75
10.10.10.76
10.10.10.79
10.10.10.80
10.10.10.81
10.10.10.82
10.10.10.83
10.10.10.84
10.10.10.85
10.10.10.86
10.10.10.87
10.10.10.88
10.10.10.89
10.10.10.90
10.10.10.92
10.10.10.93
10.10.10.94
10.10.10.95
10.10.10.96
10.10.10.97
10.10.10.98
10.10.10.102
10.10.10.103
10.10.10.104
10.10.10.106
10.10.10.107
10.10.10.108
10.10.10.109
10.10.10.110
10.10.10.111
10.10.10.112
10.10.10.113
10.10.10.114
10.10.10.116
10.10.10.118
10.10.10.119
10.10.10.120
10.10.10.121
10.10.10.122
10.10.10.124
10.10.10.126
10.10.10.128
10.10.10.129
10.10.10.130
10.10.10.131
10.10.10.132
10.10.10.133
10.10.10.134
10.10.10.135
10.10.10.136
00-4f-4e-08-5e-79
00-4f-4e-08-5e-78
00-00-e8-22-a6-33
00-4f-4e-07-56-0d
00-00-e8-22-72-12
00-4f-4e-07-0f-48
00-4f-4e-07-49-69
00-00-e8-a3-1b-79
00-4f-4e-05-81-68
00-00-e8-a4-73-10
00-00-e8-22-a8-57
00-4f-4e-06-fd-e6
00-4f-4e-01-92-1e
00-4f-4e-08-5e-80
00-4f-4e-06-5b-43
00-4f-4e-05-83-b8
00-00-e8-1b-c9-81
00-00-e8-22-c9-00
00-00-e8-a4-5a-f3
00-00-e8-a4-5d-c4
00-00-e8-22-a4-d7
00-4f-4e-07-43-4d
00-4f-4e-07-56-28
00-00-e8-22-a4-31
00-00-e8-1a-86-f5
00-4f-4e-07-47-b9
00-4f-4e-01-26-b0
00-4f-4e-05-81-62
00-4f-4e-08-27-e5
00-4f-4e-04-51-bd
00-00-e8-22-d4-e2
00-00-e8-3d-88-f0
00-4f-4e-06-43-f3
00-00-e8-22-bd-6b
00-4f-4e-06-3b-3c
00-4f-4e-06-47-73
00-00-e8-18-95-5f
00-4f-4e-02-e6-1a
00-4f-4e-03-04-10
00-00-e8-4e-d9-7f
00-00-e8-4e-c2-d2
00-4f-4e-00-0c-92
00-4f-4e-06-50-f8
00-00-e8-22-a5-dc
00-4f-4e-02-89-9d
00-00-e8-22-7c-fa
00-4f-4e-08-5e-7a
00-00-e8-e3-02-9c
00-00-e8-4e-bc-b0
00-4f-4e-03-0a-c8
00-4f-4e-05-86-8f
00-00-e8-13-3e-86
00-4f-4e-05-8a-00
00-00-e8-4e-be-45
00-00-e8-28-d6-7e
00-4f-4e-00-0c-98
00-00-e8-4e-be-44
00-4f-4e-06-59-d1
00-4f-4e-08-5e-76
00-4f-4e-0a-86-f9
00-4f-4e-02-9d-8a
Guião
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
2000/2001
96
10.10.10.138
10.10.10.141
10.10.10.142
10.10.10.143
10.10.10.144
10.10.10.145
10.10.10.147
10.10.10.148
10.10.10.149
10.10.10.150
10.10.10.152
10.10.10.153
10.10.10.154
10.10.10.155
10.10.10.156
10.10.10.157
10.10.10.158
10.10.10.159
10.10.10.160
10.10.10.161
10.10.10.162
10.10.10.163
10.10.10.164
10.10.10.165
10.10.10.167
10.10.10.168
10.10.10.169
10.10.10.170
10.10.10.171
10.10.10.172
10.10.10.173
10.10.10.174
10.10.10.175
10.10.10.176
10.10.10.177
10.10.10.178
10.10.10.179
10.10.10.180
10.10.10.181
10.10.10.182
10.10.10.183
10.10.10.185
10.10.10.186
10.10.10.187
10.10.10.188
10.10.10.192
10.10.10.193
10.10.10.194
10.10.10.196
10.10.10.197
10.10.10.199
10.10.10.201
10.10.10.202
10.10.10.203
10.10.10.204
10.10.10.206
10.10.10.208
10.10.10.209
10.10.10.211
10.10.10.212
10.10.10.213
00-4f-49-01-81-dc
00-00-e8-13-28-cd
00-4f-49-09-3f-e3
00-00-e8-13-44-18
00-4f-4e-05-88-55
00-00-e8-4e-cf-2c
00-4f-4e-00-0c-8b
00-00-e8-4e-db-2b
00-00-e8-22-b9-82
00-00-e8-22-bd-06
00-4f-4e-01-97-0a
00-4f-4e-0a-7d-8b
00-4f-4e-0a-7f-2a
00-00-e8-4e-cf-45
00-4f-4e-0a-86-b4
00-4f-4e-0a-7e-cf
00-4f-4e-0a-8b-cd
00-4f-4e-0a-66-a5
00-4f-4e-0a-85-28
00-4f-4e-06-3e-a8
00-4f-4e-0a-7c-b5
00-4f-4e-02-9d-81
00-4f-4e-08-5e-7e
00-00-e8-1b-c8-5d
00-4f-4e-0a-7a-7e
00-00-e8-22-7c-32
00-00-e8-22-ba-79
00-4f-4e-0a-ac-18
00-4f-4e-01-9f-fb
00-00-e8-4e-dc-a5
00-00-e8-22-74-9a
00-4f-4e-0a-85-08
00-4f-4e-06-bf-9e
00-4f-49-09-46-06
00-00-e8-22-7c-c3
00-4f-4e-05-7c-d4
00-00-e8-4e-c0-b0
00-00-e8-22-7c-cb
00-4f-4e-03-04-08
00-60-97-c2-44-2e
00-00-e8-13-29-93
00-4f-4e-06-67-9b
00-00-e8-4e-ca-e5
00-4f-4e-06-4d-f3
00-00-e8-a6-c7-a1
00-4f-4e-05-85-ba
00-4f-4e-0a-65-6f
00-00-e8-4e-d0-a0
00-4f-4e-0a-63-14
00-00-e8-2d-2c-e6
00-00-e8-4e-bb-fc
00-00-e8-4e-e5-84
00-4f-4e-0a-ac-cf
00-00-e8-4e-cf-51
00-4f-4e-06-5c-97
00-4f-4e-05-87-7e
00-4f-4e-00-3c-aa
00-4f-4e-06-58-42
00-4f-4e-0a-b3-9e
00-00-e8-4e-bf-cb
00-00-e8-4e-cd-36
Guião
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
2000/2001
97
10.10.10.215
10.10.10.217
10.10.10.221
10.10.10.222
10.10.10.223
10.10.10.224
10.10.10.225
10.10.10.227
10.10.10.228
10.10.10.230
10.10.10.231
10.10.10.232
10.10.10.233
10.10.10.234
10.10.10.237
10.10.10.239
10.10.10.240
10.10.10.241
10.10.10.242
10.10.10.243
10.10.10.244
10.10.10.245
10.10.10.246
10.10.10.247
10.10.10.248
10.10.10.249
10.10.10.251
10.10.10.253
10.10.10.254
00-4f-4e-0a-b8-ca
00-00-e8-4e-bf-be
00-00-e8-18-91-f3
00-4f-4e-05-c9-af
00-4f-4e-05-7e-92
00-4f-4e-03-17-35
00-00-e8-13-2a-3a
00-00-e8-4e-bf-12
00-00-e8-4e-c0-13
00-4f-4e-05-82-31
00-00-e8-22-ae-19
00-00-e8-22-77-08
00-4f-4e-06-47-ee
00-00-e8-22-7a-ee
00-00-e8-22-77-0d
00-00-e8-18-99-26
00-4f-4e-0a-96-ba
00-4f-4e-0a-af-f8
00-4f-4e-05-82-27
00-00-e8-1b-cf-50
08-00-4e-2b-40-ef
00-90-04-0f-ca-78
00-90-04-12-57-b8
08-00-4e-09-0f-41
08-00-4e-c9-60-b8
00-90-04-09-92-f8
00-90-04-11-f7-78
08-00-4e-10-5e-e8
00-4f-4e-06-a9-d7
Guião
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
dynamic
2000/2001
98
Guião
ANEXO IV
2000/2001
99
Guião
PING 193.136.190.30 (193.136.190.30): 56 data bytes
----193.136.190.30 PING Statistics---1 packets transmitted, 0 packets received, 100% packet loss
Address: 193.136.188.1
PING 193.136.190.31 (193.136.190.31): 56 data bytes
Address: 193.136.188.1
PING 193.136.190.32 (193.136.190.32): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=2 ms
round-trip min/avg/max = 2/2/2 ms
Address: 193.136.188.1
PING 193.136.190.33 (193.136.190.33): 56 data bytes
Address: 193.136.188.1
Name: indigoxz.adetti.iscte.pt
Address: 193.136.190.33
PING 193.136.190.34 (193.136.190.34): 56 data bytes
Address: 193.136.188.1
Name: indy1.adetti.iscte.pt
Address: 193.136.190.34
PING 193.136.190.35 (193.136.190.35): 56 data bytes
Address: 193.136.188.1
Name: o2video.adetti.iscte.pt
Address: 193.136.190.35
PING 193.136.190.36 (193.136.190.36): 56 data bytes
2000/2001
100
Guião
Address: 193.136.188.1
Name: lablin1.adetti.iscte.pt
Address: 193.136.190.36
PING 193.136.190.37 (193.136.190.37): 56 data bytes
Address: 193.136.188.1
Name: labmult1.adetti.iscte.pt
Address: 193.136.190.37
PING 193.136.190.38 (193.136.190.38): 56 data bytes
Address: 193.136.188.1
Address: 193.136.190.38
PING 193.136.190.39 (193.136.190.39): 56 data bytes
Address: 193.136.188.1
Address: 193.136.190.39
PING 193.136.190.40 (193.136.190.40): 56 data bytes
Address: 193.136.188.1
Address: 193.136.190.40
PING 193.136.190.41 (193.136.190.41): 56 data bytes
2000/2001
101
Guião
Address: 193.136.188.1
Address: 193.136.190.41
PING 193.136.190.42 (193.136.190.42): 56 data bytes
Address: 193.136.188.1
Name: superlab.adetti.iscte.pt
Address: 193.136.190.42
PING 193.136.190.43 (193.136.190.43): 56 data bytes
Address: 193.136.188.1
Name: dhl.adetti.iscte.pt
Address: 193.136.190.43
PING 193.136.190.44 (193.136.190.44): 56 data bytes
Address: 193.136.188.1
Address: 193.136.190.44
PING 193.136.190.45 (193.136.190.45): 56 data bytes
Address: 193.136.188.1
Address: 193.136.190.45
PING 193.136.190.46 (193.136.190.46): 56 data bytes
2000/2001
102
Guião
Address: 193.136.188.1
Address: 193.136.190.46
PING 193.136.190.47 (193.136.190.47): 56 data bytes
Address: 193.136.188.1
Address: 193.136.190.47
PING 193.136.190.48 (193.136.190.48): 56 data bytes
Address: 193.136.188.1
Name: telemed.adetti.iscte.pt
Address: 193.136.190.48
PING 193.136.190.49 (193.136.190.49): 56 data bytes
Address: 193.136.188.1
Name: labserver.adetti.iscte.pt
Address: 193.136.190.49
PING 193.136.190.50 (193.136.190.50): 56 data bytes
Address: 193.136.188.1
Name: web1.adetti.iscte.pt
Address: 193.136.190.50
PING 193.136.190.51 (193.136.190.51): 56 data bytes
Address: 193.136.188.1
Name: lablin2.adetti.iscte.pt
Address: 193.136.190.51
2000/2001
103
Guião
PING 193.136.190.52 (193.136.190.52): 56 data bytes
Address: 193.136.188.1
Address: 193.136.190.52
PING 193.136.190.53 (193.136.190.53): 56 data bytes
Address: 193.136.188.1
Address: 193.136.190.53
PING 193.136.190.54 (193.136.190.54): 56 data bytes
Address: 193.136.188.1
Address: 193.136.190.54
PING 193.136.190.55 (193.136.190.55): 56 data bytes
Address: 193.136.188.1
Name: www.aitear.com
Address: 193.136.190.55
PING 193.136.190.56 (193.136.190.56): 56 data bytes
Address: 193.136.188.1
Name: toshiba2.adetti.iscte.pt
Address: 193.136.190.56
PING 193.136.190.57 (193.136.190.57): 56 data bytes
Address: 193.136.188.1
2000/2001
104
Guião
PING 193.136.190.58 (193.136.190.58): 56 data bytes
Address: 193.136.188.1
Name: pl75.adetti.iscte.pt
Address: 193.136.190.58
PING 193.136.190.59 (193.136.190.59): 56 data bytes
Address: 193.136.188.1
Name: gtadetti.adetti.iscte.pt
Address: 193.136.190.59
PING 193.136.190.60 (193.136.190.60): 56 data bytes
Address: 193.136.188.1
Name: iris.adetti.iscte.pt
Address: 193.136.190.60
PING 193.136.190.61 (193.136.190.61): 56 data bytes
Address: 193.136.188.1
Name: indy2.adetti.iscte.pt
Address: 193.136.190.61
PING 193.136.190.62 (193.136.190.62): 56 data bytes
Address: 193.136.188.1
Name: fore-switch-eth.adetti.iscte.pt
Address: 193.136.190.62
PING 193.136.190.63 (193.136.190.63): 56 data bytes
2000/2001
105
Guião
Address: 193.136.188.1
PING 193.136.190.64 (193.136.190.64): 56 data bytes
Address: 193.136.188.1
PING 193.136.190.65 (193.136.190.65): 56 data bytes
Address: 193.136.188.1
Name: gtrsi.adetti.iscte.pt
Address: 193.136.190.65
PING 193.136.190.66 (193.136.190.66): 56 data bytes
Address: 193.136.188.1
PING 193.136.190.67 (193.136.190.67): 56 data bytes
Address: 193.136.188.1
PING 193.136.190.68 (193.136.190.68): 56 data bytes
Address: 193.136.188.1
PING 193.136.190.69 (193.136.190.69): 56 data bytes
Address: 193.136.188.1
labmult1.adetti.iscte.pt (193.136.190.37) at 0:50:da:c6:48:24
labmult2.adetti.iscte.pt (193.136.190.38) at 0:50:da:c6:48:34
labmult3.adetti.iscte.pt (193.136.190.39) at 0:0:e8:49:86:c8
2000/2001
106
Guião
labmult5.adetti.iscte.pt (193.136.190.40) at 0:4f:49:1:42:5c
superlab.adetti.iscte.pt (193.136.190.42) at 0:4f:4e:a:af:e7
labmult6.adetti.iscte.pt (193.136.190.44) at 0:60:97:b2:79:1
labmult7.adetti.iscte.pt (193.136.190.45) at 0:50:da:c6:46:d4
labmult8.adetti.iscte.pt (193.136.190.46) at 0:50:4:f7:b5:38
labmult9.adetti.iscte.pt (193.136.190.47) at 0:0:86:1a:a8:86
labmult11.adetti.iscte.pt (193.136.190.53) at (incomplete)
labmult12.adetti.iscte.pt (193.136.190.54) at (incomplete)
www.aitear.com (193.136.190.55) at (incomplete)
toshiba2.adetti.iscte.pt (193.136.190.56) at (incomplete)
? (193.136.190.57) at 0:c0:7b:7b:d2:63
pl75.adetti.iscte.pt (193.136.190.58) at (incomplete)
iris.adetti.iscte.pt (193.136.190.60) at 0:40:8c:44:ab:59
indy2.adetti.iscte.pt (193.136.190.61) at 8:0:69:6:eb:ca
2000/2001
107
Guião
ANEXO V
2000/2001
108
ROUTER14.ATM0-0-0.3.Lisboa.rccn.net
193.136.1.190
193.136.5.254
lcatrt1.telepac.net
213.13.135.105
194.65.12.157
Internet
ROUTER16.ATM3-0.3.Lisboa.rccn.net
193.136.1.1
PIX.telepac.pt
193.136.250.30
gtiscte.iscte.pt
193.136.188.254
213.13.135.70
gtadetti.adetti.iscte.pt
193.136.190.59
fwe.iscte.pt
193.136.191.9
gtalunos.iscte.pt
193.136.191.10
iscte.iscte.pt
193.136.188.1
fwi.students.iscte.pt
10.10.10.254
00-4f-4e-06-a9-d7
o2video.adetti.iscte.pt
193.136.190.35
8:0:69:5:bb:7a
255.255.255.224
indy1.adetti.iscte.pt
193.136.190.34
08:00:69:08:27:b2
255.255.255.224
IDC
socrates.students.iscte.pt
10.10.10.2
00-03-47-08-c7-d9
indigoxz.adetti.iscte.pt
193.136.190.33
8:0:69:7:67:2b
255.255.255.224
HUB Passivo
rede33.students.iscte.pt
10.10.10.33
00-00-e8-22-7c-fc
10.10.10.34
00-00-e8-22-a3-7d
10.10.10.39
00-00-e8-22-7c-cc
10.10.10.40
00-00-e8-22-74-dd
10.10.10.41
00-60-97-c2-42-37
10.10.10.35
00-00-e8-18-9d-98
10.10.10.36
00-00-e8-4e-c2-fc
10.10.10.42
00-00-e8-4e-c1-8b
10.10.10.43
00-60-97-c2-47-29
10.10.10.44
00-4f-4e-03-13-f0
10.10.10.37
00-00-e8-22-bd-ac
10.10.10.38
00-00-e8-22-77-a6
i0s05-14.students.iscte.pt
10.10.10.112
00-4F-4E-00-0C-92
255.255.255.0
10.10.10.45
00-00-e8-22-74-85
10.10.10.46
00-60-97-c2-45-a0

Levantamento Parcial da Rede Informática do ISCTE

Transcrição

Documentos relacionados

Insper Institute of Education and Research

Release 6.1.4.8. May 2015

Press Release PT/ENG

layout-newsletter-waiver(ED.09) EN

S25FL032A

a eficiência nas caixas de crédito agrícola mútuo - dinâmia`cet-iul

Programa preliminar

`Creative Cities` to `Urban Creativity` - dinâmia`cet-iul - iscte-iul

sorted by most viewed (includes insight post +

Todos os códigos de erros SMTP - Mail Delivery System