On Tuesday 16 April 2002 13:30, Curtis L. Olson wrote:
> Alasdair Campbell writes:
> > For several days now, I have been unable to access the FlightGear-source
> > and Simgear repositories.
> >
> > [root@birnie FlightGear]# cvs update -dP
> > cvs [update aborted]: recv() from server cvs.flightgear.org: Connection
> > reset by peer
> > [root@birnie FlightGear]# cvs --version
> >
> > Concurrent Versions System (CVS) 1.11 (client/server)
> >
> > The FlightGear-base and plib repositories are OK.
> > Has there been a change I've missed?
> >
> > Logging in again does the same:
> >
> > cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.7 login
> > CVS password: (guest)
> > cvs [login aborted]: recv() from server cvs.flightgear.org: Connection
> > reset by peer
>
> If you send me more detailed information about when you tried to
> access the cvs repository, I can dig in the logs and see if there is
> anything useful.
>
> However, I'm going to guess that something about your machine's
> name/ip address is not registered in dns properly. Given the location
> of the flightgear server (i.e. it's plugged into the internet) I need
> to be at least a little bit concerned about security. The server is
> configured to reject hosts who's name/ip address (both forward and
> reverse lookups) is not properly entered in dns. This hopefully
> catches at least some of the more obvious ip spoofing. FWIW, we do
> take a fair bit of port scanning and probes so security is actually a
> real issue. I try my best to keep up with all the latest security
> patches for this machine and not leave too many wide open gaping
> holes.
>
> Regards,
>
> Curt.
Oh gosh, this sounds complicated.
OK, just tried accessing cvs.flightgear.org at 14:30 BST (13:30 GMT) today
16 Apr 2002.
My IPA is dynamically allocated (I think) from btinternet.com
At the time I tried the access it was 213.122.182.44
.....
[root@birnie /root]# ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:38:00:01:BE
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:285 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:11 Base address:0xe800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:74 errors:0 dropped:0 overruns:0 frame:0
TX packets:74 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
ppp0 Link encap:Point-to-Point Protocol
inet addr:213.122.182.44 P-t-P:213.120.208.167
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:576 Metric:1
RX packets:85 errors:0 dropped:0 overruns:0 frame:0
TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
I had no problems up until about a week ago. My current fgfs is unflyable.. it
has the "land of the midday moon" syndrome, and horrible response times.
Hope this will help you help.
TIA
--
Kind Regards,
Alasdair Campbell
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
