A. Change the $HOSTTYPE to RISC6000 then you can find those libs.
Try typing:
setenv HOSTTYPE RISC6000
A. First on the local workstation type:
xhost [ Remote Hostname ]Then on the remote workstation type:
setenv DISPLAY [ Local Hostname ]:0.0This will allow you to display the GUI on you local workstation.
A. frag1 and frag5 packets do not get fragmented!!!!
A. In RCS, set your disk allocation to 10 MB. There will be a charge of $0.25 per extra MB per month (normal allocation is 5 MB).
This does not show up in my implementation when
I increase the debug level.
Is this something that I need to implement aswell?
A. You need to uncomment the debug statements in the code template you have.
The code says:
dataoffset, /* offset within app packet for next fragment */
offset_in_datagram; /* fragment offset to be written in new fragment header */A.
/* dataoffset: offset within app packet for next fragment. 16 bits */
dataoffset = 0;
/* frag offset in datagram: consider old fragment offset too. 16 bits. */
offset_in_datagram = (old_fragoff & IP_FRAGOFF) << 3;
To minimize confusion, the above is the correct code for the initialization
of these two variables - to help you get started. Basically dataoffset
refers to a running pointer into the datagram or application packet which
is being fragmented. You have to increment it by the maximum possible fragment
size (calculate this from the MTU size) to get the next chunk of payload
to be packaged into the next fragment.
offset_in_datagram should consider old fragment offset too because you
can fragment an already fragmented datagram further in the middle of the
network. You should not increment it by 1 as you suggest below -- this
variable has the units of "bytes" -- which means that you should increment
it by the appropriate number of bytes you have put into each fragment.
/tmp/ccl11jMa.s: line 3954: Cannot create network_layer.o
make: The error code from the last command is
1.
A. I got this problem as well. My previous executable ran into an infinite loop and was coredumped. Because this file is large you may overshoot your rcs quota. so try removing core and make again
A. use the command
$ ulimit -c 0Core file size will be limited to 0 bytes.
A. Are you using an AIX machine? Remember to login only to the known AIX machines in RCS (The command uname will give you what OS you are on).
A. Use the xv utility.
When the little fish appear click the right mouse button in the window.
Then you will see a button on the bottom named "Grab" click that and follow
the directions. After clicking Grap use the middle mouse button to draw
a rectangle around the area you want to capture.
A. No. we do not want to divide the data into 1/8th the mtu size. We just want it to satisfy the constraint that it should be the highest multiple of 8 (its lower 3 bits should be 0) less than mtu. This can be done for eg. by (mtu-IPMHLEN)&~7
A. You are right - it should be part of the "no reassebly reqd" part.
In general, keep in mind that we have provided comments almost each and every line of the code at its appropriate position. We basically wrote the code + comments and removed the code ... I would recommend that you do not move the graphics code from its current position and simply "fill in the blanks" for the remaining code.
A. No. It is called by a section of code that is transparent to you.
We provided the description for completeness.
A. Yes. The order of source/destination in the argument list differs from strcpy(). A man page exists:
Try:
man bcopy
A. Usually - sometimes it might be transparent to you - like ipftimer. I cant recall another case ...
A. Yes. You might do well to have a C reference book handy.
A. . Try using: input_pdu->u.n_pdu.ip_src
Empty n_pdu
IOT/Abort trap (core dumped)
A. These answers were sugested by students!!
A. Maybe you didn't format some parameters correctly before calling some routines. For example, when formate packet to be handed into application layer, you might make some careless mistake so that inproper packet is handed in and that will cause problem later in some routines you didn't write.
app2: Unknown packet type
A. It might happen when you try assembling incorrect data. Check how you are fragmenting and unfragmenting it.
/* Release resources in fragment table: ordered list, state variables */
FreeOrderedList(iq->ipf_q);
A. I forgot state variable:
iq->ipf_state = IPFF_FREE;
A. Type the following without the < > :
ssh -l <your-id-on-remotemachine> <remote-machine>
or ssh <your-id-on-remotemachine>@<remote-machine>
For example:
ssh -l testid rcs-ibm2.rpi.edu
---
|--------->
This is an 'L' in small letters, not a '1' .
or
ssh testid@rcs-ibm2.rpi.edu
A.
General Info:
http://www.ssh.fi/
(free stuff)
http://www.datafellows.com/
(non free stuff)
Win: (ssh1/2) (Just get the trial version)
http://www.datafellows.com/download-purchase/
choose "F-Secure SSH Tunnerl&Terminal
for Windows" from the first popup
MacOS: (ssh1/2) (Just get the trial version)
http://www.datafellows.com/download-purchase/
choose "F-Secure SSH Tunnerl&Terminal
for Macintosh" from the first popup
the unix ssh client/server also does X11 forwarding (over the active connection) so there is no reason to export a DISPLAY assuming both sides are setup to allow it.
A. I have solved the poor image quality of node2 in the Frag_demo program. I tried several things...
I am working from home (with RoadRunner) using both my Linux machine and my Win98 machine.
I telnet to the Linux machine and use ssh to login to an IBM AIX machine
at RPI. Using eXceed (X-Server for windows) I can bring the display
to the Win98 machine. Using this method the node2 appears as a red wire
mesh of the planet earth. From the console of the Linux machine the planet
earth on node2 appears as a nice blue wire mesh. I rebooted Win98 machine
to Linux. Nice blue wire mesh. I decided to monkey with the
color depth.
Initially it was at 32 bpp yielding blue mesh. Then went down
to 8 bpp yielding a perfect planet earth. It turns out that in Win98 I
was running at 24 bpp.
If you are going to qualitatively assess the performance for each of the fragX.config make sure that your display is set down to 8 bpp.
For on campus this is probably not an issue as 8 bpp is default on most of the UNIX machines.
A. Please do not use ssh version 2.
SSH 1.1 should work
Try to see if you can get an older version of F-Secure's SSH, or at least not ssh2.
A. I have solved the firewall connectivity problem. At least for myself here at IBM Burlington. Hopefully this info may help the other sites with firewalls. I was able run Frag_demo with little trouble.
Solution: encapsulate the X packets with ssh which creates a virtual tunnel for packets between the client and server. It does this by encryping the X packets and returning them allong the same port as the ssh session. it sets DISPLAY=cortez.sss.rpi:3.0 for example. ("proxy Xserver")
1. install ssh client on an internal machine.
(as root)
2. use ssh-keygen to create private/public key
pair. (as user)
3. copy the contents of $HOME/.ssh/identity.pub
(on local acct) to
$HOME/.ssh/authorized_keys in RCS acct (via rftp)
4. ssh -l <RCSuserName> cortez.sss.rpi.edu
(add -v to debug)
A. I got the GUI for Lab 1 working on my PC at IBM Poughkeepsie - perhaps it will be of use to other students as well.
To get X Windows DISPLAY (for Lab 1) from RPI rcs machines onto my PC running Windows95, I did the following things:
1. Download & install SecureCRT (evaluation,
free for 30 days) from www.vandyke.com
2. Download & install Starnet X-Win32v4.1.1
(evaluation, free) from www.starnet.com
3. Set up SecureCRT to connect to port 22
(ssh) of the desired machine (rcs.rpi.edu)
3.1 In the Port Forwarding tab of the Advanced
screen in the Session parameters in SecureCRT, ensure that:
The local and
remote ports are numbered 6000
The remote server
(e.g. rcs AIX machine) IP address (NOT hostname) is specified.
4. Start the X-Win32 package
5. Restart SecureCRT and log into the AIX
machine.
6. Obtain Lab1 as indicated, and start the
GUI.
A. The problem is not which version of UNIX you have, but more of whether your firewall allows you to export display. If it does, then it doesn't matter if your local machine is any flavor of UNIX or any architecture as long as it has X-Windows.
Do you have firewall restrictions to your connection from home? If not, you can ssh to rcs machines and work from there.
IF you do have a firewall from your home connection, so that you can't connect from home either, you will have to get an account on a AIX or Solaris machine at IBM. You can then install the lab in that account and telnet/ssh from your existing machine. There shouldn't be any firewall problems intra-domain and hence you can run the GUI display.
A. This is information on establishing a connection to the Rensselaer Computing System (RCS) that will allow students to use X (graphical) applications from off campus.
In order to use an RCS X application you will need to have a high speed connection. Generally, Internet speeds are required.
If your system has ssh programs, you will be able to establish a connection that will allow you to run X based applications. If you are not sure if you have access to these programs or if you have internet access you will need to check with your local system administrators.
If you have a PC that is running an X emulator such as eXceed or X-Win32. You still need Internet access and eXceed or X-Win32 will allow the X setup.
Using a telephone line and dialing a local ISP will not work.
Your PC needs to be attached directly to a high speed Internet
connection.
If you are using an X capable device here are the instructions for connecting to rcs.rpi.edu.
ssh is a program that maybe installed on your local system. If so, it is designed to automatically handle the configuration.
From your system prompt enter "ssh rcs.rpi.edu" and if should be prompted
for your RCS userid. If the address rcs.rpi.edu does not work. Try rcs-ibm.rpi.edu.
rcs-ibm is one of the servers in the the rcs.rpi.edu group. After logging
in (contact me is you need your RCS userid access) you can run any of the
RCS X applications.
============
Patrick Valiquette, Academic Computing Services
e-mail - valiqp@rpi.edu, voice (518) 276-6723
Check out http://poisson.ecse.rpi.edu/~amit/ip/lab1-rsvp.html