<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>Wolves Digest, Vol 90, Issue 8</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText77696 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Allo, </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Just noticed a post, Heading "Re; Ubuntu
dialup modem set up" or something like that. I Sent that months ago, and as
far as i know haven't re-sent it to you for any reason
whatever. Maybe a hiccup in the system?</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Mart.</FONT> </DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> wolves-bounces@mailman.lug.org.uk on
behalf of wolves-request@mailman.lug.org.uk<BR><B>Sent:</B> Wed 08/06/2005
12:15<BR><B>To:</B> wolves@mailman.lug.org.uk<BR><B>Subject:</B> Wolves Digest,
Vol 90, Issue 8<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Send Wolves mailing list submissions
to<BR>
wolves@mailman.lug.org.uk<BR><BR>To subscribe or unsubscribe via the World Wide
Web, visit<BR> <A
href="http://mailman.lug.org.uk/mailman/listinfo/wolves">http://mailman.lug.org.uk/mailman/listinfo/wolves</A><BR>or,
via email, send a message with subject or body 'help'
to<BR>
wolves-request@mailman.lug.org.uk<BR><BR>You can reach the person managing the
list at<BR>
wolves-owner@mailman.lug.org.uk<BR><BR>When replying, please edit your Subject
line so it is more specific<BR>than "Re: Contents of Wolves
digest..."<BR><BR><BR>Today's Topics:<BR><BR> 1. New Site (Andrew
Lewis)<BR> 2. Re: New Site (Peter Cannon)<BR> 3. Re: FW:
UKUUG LISA/Winter Conference and Perl 6
Workshop<BR> (David Goodwin)<BR> 4.
typo's (David Morley)<BR> 5. Bizarre network problem (Old
Dan)<BR> 6. RE: Bizarre network problem (David
Morley)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message:
1<BR>Date: Sun, 27 Feb 2005 18:05:15 +0000<BR>From: Andrew Lewis
<andrew@monkeysailor.co.uk><BR>Subject: [Wolves] New Site<BR>To:
undisclosed-recipients:;<BR>Message-ID:
<1109527514.7523.14.camel@localhost.localdomain><BR>Content-Type:
text/plain<BR><BR>Hello People!<BR><BR>I've just finished the basic layout of my
new site. In the future there<BR>will be:<BR><BR>* a big animation resource<BR>*
more linux dohickeys and whumpus<BR>* a literature section<BR>* a 'hack a day'
style article repository<BR><BR>Let me know if you find any typos,
etc.<BR><BR>Andrew<BR>"Yes, It's Working... Oh, Yeah! Woo-hoo... It's
wor-Bugger-hot, ow,<BR>unplug it... ow... open the window... get the
extinguisher!" - A.
Lewis<BR><BR><BR><BR><BR>------------------------------<BR><BR>Message:
2<BR>Date: Wed, 8 Jun 2005 10:05:37 +0100<BR>From: Peter Cannon
<peter@cannon-linux.co.uk><BR>Subject: Re: [Wolves] New Site<BR>To:
Wolverhampton Linux User Group <wolves@mailman.lug.org.uk><BR>Message-ID:
<200506081005.47049.peter@cannon-linux.co.uk><BR>Content-Type: text/plain;
charset="utf-8"<BR><BR>On Sunday 27 February 2005 18:05, Andrew Lewis
wrote:<BR><BR><BR>> Let me know if you find any typos, etc.<BR><BR>How a
about a URL you nugget ;-)<BR><BR><BR>--<BR><BR>Regards,<BR>Peter
Cannon.<BR>peter@cannon-linux.co.uk<BR>Fedora Core 3 & Suse Pro
9.2<BR><BR>"There is every excuse for not knowing<BR>there is no excuse for not
asking"<BR>-------------- next part --------------<BR>A non-text attachment was
scrubbed...<BR>Name: not available<BR>Type: application/pgp-signature<BR>Size:
189 bytes<BR>Desc: not available<BR>Url : <A
href="http://mailman.lug.org.uk/pipermail/wolves/attachments/20050608/7b8e7f8a/attachment-0001.bin">http://mailman.lug.org.uk/pipermail/wolves/attachments/20050608/7b8e7f8a/attachment-0001.bin</A><BR><BR>------------------------------<BR><BR>Message:
3<BR>Date: Wed, 08 Jun 2005 10:11:04 +0100<BR>From: David Goodwin
<dg@clocksoft.com><BR>Subject: Re: [Wolves] FW: UKUUG LISA/Winter
Conference and Perl 6<BR>
Workshop<BR>To: Wolverhampton Linux User Group
<wolves@mailman.lug.org.uk><BR>Message-ID:
<42A6B628.2080007@clocksoft.com><BR>Content-Type: text/plain;
charset=ISO-8859-1; format=flowed<BR><BR>guess this was stuck in a queue for a
_long_ time ?<BR><BR>David.<BR><BR><BR>--<BR>David Goodwin<BR>w: <A
href="http://www.clocksoft.co.uk">http://www.clocksoft.co.uk</A> (New
Site!)<BR>e: david.goodwin@clocksoft.com<BR>t: 0121 313
3850<BR><BR><BR><BR>------------------------------<BR><BR>Message: 4<BR>Date:
Wed, 08 Jun 2005 09:03:54 +0000<BR>From: "David Morley"
<davmor2@hotmail.com><BR>Subject: [Wolves] typo's<BR>To:
Wolves@mailman.lug.org.uk<BR>Message-ID:
<BAY107-F18292952D6FB395A5C608BFEFD0@phx.gbl><BR>Content-Type: text/plain;
format=flowed<BR><BR>andy spell do$ or is it meant to be
do$e<BR><BR><BR><BR><BR><BR>------------------------------<BR><BR>Message:
5<BR>Date: Wed, 8 Jun 2005 10:30:17 +0100<BR>From: Old Dan
<djones9960@gmail.com><BR>Subject: [Wolves] Bizarre network problem<BR>To:
Wolverhampton Linux User Group <wolves@mailman.lug.org.uk><BR>Message-ID:
<8d3f565e050608023045b53f71@mail.gmail.com><BR>Content-Type: text/plain;
charset=ISO-8859-1<BR><BR>Hi all<BR><BR>I'm having a bizarre network problem at
work. The configuration here<BR>is that we have a smoothwall box connected
directly to a debian<BR>domain/web/fileserver, which NATs the internet and acts
a bridge<BR>between the wired and wireless network.<BR><BR>Or it did NAT the
internet. At about 12:30 on monday it stopped doing<BR>that.
Dead. I believe it is trying to but has no access itself,<BR>although it
still gets an IP from the smoothie box and when I connect<BR>clients directly to
the smoothie they can connect to the internet.<BR><BR>So I thought, 'it must
have died', and being someone who frankly still<BR>has mostly a Microsoft
background I thought 'I know, I'll reboot both<BR>boxes' (admittedly this was
after sshing in and looking around and<BR>finding nothing apparently
amiss).<BR><BR>No difference. Although I was able to access the web
interface of<BR>smoothwall throughout all this. Using that interface, I
found out<BR>that the internet was connected and we had an external IP. I
could<BR>log into the smoothie no problem and ssh out from there to my
home<BR>server.<BR><BR>In desperation, I enabled the smoothie proxy.
Aha! Web access<BR>returned! Although then I couldn't access the web
interface any<BR>more.... Switch back to direct connection, I could again,
but no web<BR>access again. I understand not being able to access the web
interface<BR>because of the port number, but I can't understand not being able
to<BR>access the 'net through NAT like I was able to before. I
changed<BR>/nothing/ (that I know of) on the server which could have done
this.<BR><BR>I'm completely
baffled.<BR>--<BR>Dan<BR><BR><BR><BR>------------------------------<BR><BR>Message:
6<BR>Date: Wed, 08 Jun 2005 09:58:54 +0000<BR>From: "David Morley"
<davmor2@hotmail.com><BR>Subject: RE: [Wolves] Bizarre network
problem<BR>To: wolves@mailman.lug.org.uk<BR>Message-ID:
<BAY107-F326D3ED0D9DB8E32401C31FEFD0@phx.gbl><BR>Content-Type: text/plain;
format=flowed<BR><BR>just out of interest are you on cable?<BR><BR>>From: Old
Dan <djones9960@gmail.com><BR>>Reply-To: Wolverhampton Linux User Group
<wolves@mailman.lug.org.uk><BR>>To: Wolverhampton Linux User Group
<wolves@mailman.lug.org.uk><BR>>Subject: [Wolves] Bizarre network
problem<BR>>Date: Wed, 8 Jun 2005 10:30:17 +0100<BR>><BR>>Hi
all<BR>><BR>>I'm having a bizarre network problem at work. The
configuration here<BR>>is that we have a smoothwall box connected directly to
a debian<BR>>domain/web/fileserver, which NATs the internet and acts a
bridge<BR>>between the wired and wireless network.<BR>><BR>>Or it did
NAT the internet. At about 12:30 on monday it stopped
doing<BR>>that. Dead. I believe it is trying to but has no access
itself,<BR>>although it still gets an IP from the smoothie box and when I
connect<BR>>clients directly to the smoothie they can connect to the
internet.<BR>><BR>>So I thought, 'it must have died', and being someone
who frankly still<BR>>has mostly a Microsoft background I thought 'I know,
I'll reboot both<BR>>boxes' (admittedly this was after sshing in and looking
around and<BR>>finding nothing apparently amiss).<BR>><BR>>No
difference. Although I was able to access the web interface
of<BR>>smoothwall throughout all this. Using that interface, I found
out<BR>>that the internet was connected and we had an external IP. I
could<BR>>log into the smoothie no problem and ssh out from there to my
home<BR>>server.<BR>><BR>>In desperation, I enabled the smoothie
proxy. Aha! Web access<BR>>returned! Although then I
couldn't access the web interface any<BR>>more.... Switch back to
direct connection, I could again, but no web<BR>>access again. I
understand not being able to access the web interface<BR>>because of the port
number, but I can't understand not being able to<BR>>access the 'net through
NAT like I was able to before. I changed<BR>>/nothing/ (that I know of)
on the server which could have done this.<BR>><BR>>I'm completely
baffled.<BR>>--<BR>>Dan<BR>><BR>>_______________________________________________<BR>>Wolves
LUG mailing list<BR>>Homepage: <A
href="http://www.wolveslug.org.uk/">http://www.wolveslug.org.uk/</A><BR>>Mailing
list: Wolves@mailman.lug.org.uk<BR>>Mailing list home: <A
href="http://mailman.lug.org.uk/mailman/listinfo/wolves">http://mailman.lug.org.uk/mailman/listinfo/wolves</A><BR><BR><BR><BR><BR><BR>------------------------------<BR><BR>_______________________________________________<BR>Wolves
mailing list<BR>Wolves@mailman.lug.org.uk<BR><A
href="http://mailman.lug.org.uk/mailman/listinfo/wolves">http://mailman.lug.org.uk/mailman/listinfo/wolves</A><BR><BR>End
of Wolves Digest, Vol 90, Issue
8<BR>*************************************<BR></FONT></P></DIV>
</BODY>
</HTML>