05-08-2013
Found the solution. When configuring eth1 (mapped to the VBox hostonly adapter) I supplied the address of that adapter as the gateway address. Going back through some logs, I saw that when building an OL 5.x system, I was never prompted for or presented with a field for a gateway address when configuring the NICs. I never really gave that a thought when the 6.3 setup did so, so I just filled it in and went on my not so merry way. Rebuilt the machine and deliberately left the gateway field blank, and solved not only the immediate problem (the long delay on login) but also the question of "what is different between this 6.3 setup and my previous 5.6 setups".
Thanks to all for your inputs.
This User Gave Thanks to edstevens For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I stupidly changed the shell of the root user to one that does not exist, and now when I try to lgon it says it cannot find the path to my shell and will not let me proceed any further. Is there any way I can get round this without re-installing the OS?
Thanks for any replies. (8 Replies)
Discussion started by: SRP
8 Replies
2. Shell Programming and Scripting
Hi, I need to run a command remotely, rsh is disabled so I'm trying to do this:
ssh myserver ls -lst /work/jsf
The problem is that this prompts for a password and I want to do it in a shell script. How can I pass the password without user interaction? I tried "echo mypass | ssh_command" and... (1 Reply)
Discussion started by: rocky_triton
1 Replies
3. Shell Programming and Scripting
hi
how can I know abt the details of current user who are logged on and as well as those users who currently have an account but are not logged on?
Thanks (1 Reply)
Discussion started by: nokia1100
1 Replies
4. Solaris
Hi
I am envountring a problem while I login using ssh on a sun box to a remote box.
I use ssh user@server and it takes long time to ask for a password..
does anyone knows the reason behind this? or is there a way that this could be solved
Thanks,
Antony (8 Replies)
Discussion started by: antointoronto
8 Replies
5. Linux
Hi, We currently have a problem on a centos server when i try to ssh to it there is a significant delay in getting a login prompt. What would be the steps in troubleshooting this issue? I have try to narrow down a possible network issue but cannot see anything obviously wrong in the routing table,... (4 Replies)
Discussion started by: borderblaster
4 Replies
6. Solaris
I am trying to configure a 4 second delay between failed login attempts on SSH. (1 Reply)
Discussion started by: LittleLebowski
1 Replies
7. Shell Programming and Scripting
Hi im trying to write a script to logon to list of servers with same userID. I have no option/plan to implement ssh-keygen sharing between the systems, so i have written script creating 2 files,
file1 holds list of hosts
host1
host2
host3
file2 has following script
for i in `cat file1`... (1 Reply)
Discussion started by: dreamaix
1 Replies
8. SCO
We have an OpenServer 5.0.5 system that has worked forever, but I'm hearing complaints of logon delays for users now. Normally they would telnet in and the logon screen would pop up, but now it sometimes takes a minute or more, and the user must hit the enter key to get it to appear. Everything... (11 Replies)
Discussion started by: citygov
11 Replies
9. Solaris
I'm having an issue with SSH on a server that hasn't had any configuration changes made on it in a long time. I SSH to the server and it hangs at "debug1: SSH2_MSG_KEXINIT sent" for exactly 40 seconds then connects fine after that pause. Everything I have found points to DNS, but I use host files... (19 Replies)
Discussion started by: kingdbag
19 Replies
10. Solaris
Hi guys.
You'd have to excuse me a bit, as I'm a noob. I really try to avoid asking questions and do research for whatever linux issues that may arise.
I am experiencing a long wait for the shell to come up when I ssh or telnet into a Sunos 5.10 environment.
It takes 70 seconds to give me... (12 Replies)
Discussion started by: gpenco
12 Replies
LEARN ABOUT FREEBSD
traceroute6
TRACEROUTE6(8) BSD System Manager's Manual TRACEROUTE6(8)
NAME
traceroute6 -- print the route IPv6 packets will take to a network node
SYNOPSIS
traceroute6 [-adIlnNrvU] [-f firsthop] [-g gateway] [-m hoplimit] [-p port] [-q probes] [-s src] [-w waittime] [-A as_server] target
[datalen]
DESCRIPTION
The traceroute6 utility uses the IPv6 protocol hop limit field to elicit an ICMPv6 TIME_EXCEEDED response from each gateway along the path to
some host.
The only mandatory parameter is the destination host name or IPv6 address. The default probe datagram carries 12 bytes of payload, in addi-
tion to the IPv6 header. The size of the payload can be specified by giving a length (in bytes) after the destination host name.
Other options are:
-a Turn on AS# lookups for each hop encountered.
-A as_server
Turn on AS# lookups and use the given server instead of the default.
-d Debug mode.
-f firsthop
Specify how many hops to skip in trace.
-g gateway
Specify intermediate gateway (traceroute6 uses routing header).
-I Use ICMP6 ECHO instead of UDP datagrams.
-l Print both host hostnames and numeric addresses. Normally traceroute6 prints only hostnames if -n is not specified, and only numeric
addresses if -n is specified.
-m hoplimit
Specify maximum hoplimit, up to 255. The default is 30 hops.
-n Do not resolve numeric address to hostname.
-N Use a packet with no upper layer header for the probes, instead of UDP datagrams.
-p port
Set UDP port number to port.
-q probes
Set the number of probe per hop count to probes.
-r Bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly-connected net-
work, an error is returned. This option corresponds to the SO_DONTROUTE socket option; it 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 a routing daemon).
-s src Src specifies the source IPv6 address to be used.
-U Use UDP datagrams for the probes. This is the default.
-v Be verbose.
-w waittime
Specify the delay time between probes.
This program prints the route to the given destination and the round-trip time to each gateway, in the same manner as traceroute.
Here is a list of possible annotations after the round-trip time for each gateway:
!N Destination Unreachable - No Route to Host.
!P Destination Unreachable - Administratively Prohibited.
!S Destination Unreachable - Not a Neighbour.
!A Destination Unreachable - Address Unreachable.
! This is printed if the hop limit is <= 1 on a port unreachable message. This means that the packet got to the destination, but
that the reply had a hop limit that was just large enough to allow it to get back to the source of the traceroute6. This was
more interesting in the IPv4 case, where some IP stack bugs could be identified by this behaviour.
EXIT STATUS
The traceroute6 utility will exit with 0 on success, and non-zero on errors.
SEE ALSO
ping(8), ping6(8), traceroute(8)
HISTORY
The traceroute6 utility first appeared in WIDE hydrangea IPv6 protocol stack kit.
BSD
August 24, 2009 BSD