<< | Thread Index | >> ]    [ << | Date Index | >> ]

To: "Phil Scarratt" <fil,AT,draxsen,DOT,com>
Subject: Re: Tutorial
From: "Shashank Khanvilkar" <shashank,AT,mia,DOT,ece,DOT,uic,DOT,edu>
Date: Fri, 6 Jun 2003 11:06:50 -0500
Cc: "CIPE" <cipe-l,AT,inka,DOT,de>
References: <005601c32a50$3c5d65d0$0f00000a@bug> <3EDD8D54.9000700@draxsen.com> <06a201c32aae$8e47eba0$c900a8c0@ece.uic.edu> <3EE03B5B.5020300@draxsen.com>

> From a quick glance, it looks great. Here is one correction and a few
> suggestions:
>
> 1. In Step vi, there is a spelling error (serber -> server). I know, a
> bit anal, but you asked....

Done..

> 2. With standard redhat setup, you can put all options from the cipe
> options file except maxerr, arg and key into
>
> /etc/sysconfig/network-scripts/ifcfg-cipcbx
>
> For example:
>
> ########## /etc/sysconfig/network-scripts/ifcfg-cipcb0 ##########
> USERCTL=no
> PEERDNS=no
> TYPE=CIPE
> ONBOOT=yes
> DEVICE=cipcb0
> PTPADDR=192.168.254.200
> IPADDR=192.168.254.201
> ME=131.193.50.165:55555
> PEER=131.193.50.184:55555
> ########## end of /etc/sysconfig/network-scripts/ifcfg-cipcb0 ##########
>
> and
>
> ########## /etc/cipe/options.cipcb0 ##########
> maxerr -1
> key             f0....938dba607caf664bb83444QQee
> arg 192.168.2.0
> ########## end of /etc/cipe/options.cipcb0 ##########
>
> The interface can then be started manually with "ifup cipcb0" and
> brought down manually with "ifconfig cipcb0 down". It also should start
> at bootup. This at least works with RH7.2/3. Haven't tested with RH8.0
> (although I can if needed)

Thats a good idea..However i had one doubt.. In the above case, won't the
ciped-cb use the default options file "/etc/cipe/options"
instead of "/etc/cipe/options.cipcb0 ". Let me know.

> 3. If the "server/client" machines are behind firewalls which use
> iptables, you will need to add the following (regexp's are a bit crude
> but serve the purpose). Someone may like to comment on the rules - are
> they too open?:

I will test this and add it by the end of the day...

>
> ########## /etc/cipe/ip-up.local ##########
--SNIp-- 
> exit 0
> ########## end of /etc/cipe/ip-down.local ##########

> I think I will still produce a tutorial (howto eventually) for linux
> cipe <-> Win32 Cipe connections. Unless of course you have one already.
> I might just refer to yours for the linux end setup???

Nopes, but I guess it shouldn't take much time for me to test cipe<->Win32
connections, since I already have the testbed.
I will try to complete this too.

>
> Fil
>
> Shashank Khanvilkar wrote:
> > I have created one.. Please take a look at
> > http://mia.ece.uic.edu/~papers/volans/cipe.html
> > Let me know if you find mistakes.
> > Shashank
> >
> > ----- Original Message ----- 
> > From: "Phil Scarratt" <fil,AT,draxsen,DOT,com>
> > To: <cipe-l,AT,inka,DOT,de>
> > Sent: Wednesday, June 04, 2003 1:10 AM
> > Subject: Re: Tutorial
> >
> >
> >
> >>I am working on one. i have extremely rough notes at the moment.
> >>
> >>Fil
> >>
> >>Michael Piko wrote:
> >>
> >>>just wondering if there is an easy-to-follow guide for connecting Xp
> >>>machines to a Redhat server through cipe?
> >>>
> >>>
> >>>
> >>>--
> >>>Message sent by the cipe-l,AT,inka,DOT,de mailing list.
> >>>Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
> >>>Other commands available with "help" in body to the same address.
> >>>CIPE info and list archive:
> >>
> > <URL:http://sites.inka.de/~bigred/devel/cipe.html>
> >
> >>
> >>-- 
> >>Phil Scarratt
> >>Draxsen Technologies
> >>IT Contractor/Consultant
> >>0403 53 12 71
> >>
> >>
> >>--
> >>Message sent by the cipe-l,AT,inka,DOT,de mailing list.
> >>Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
> >>Other commands available with "help" in body to the same address.
> >>CIPE info and list archive:
> >
> > <URL:http://sites.inka.de/~bigred/devel/cipe.html>
> >
> >
>
>
> -- 
> Phil Scarratt
> Draxsen Technologies
> IT Contractor/Consultant
> 0403 53 12 71
>


<< | Thread Index | >> ]    [ << | Date Index | >> ]