Linux-Networking Digest #49, Volume #11           Wed, 5 May 99 13:13:44 EDT

Contents:
  Routing / NAT problems ("Thomas")
  Re: Problem connecting under Linux (Clifford Kite)
  Re: 2 NIC in RH, 2 subnet required? (brian moore)
  Re: How to control ip-up execution depending on whether I dial out to ISP or in to 
my own box? (Dale Pontius)
  How to set-up auto-login in Linux (Khairul Effendy)
  Re: Squid Setup (Flippie Spies)
  ANNOUNCE: SNMP Sniffer v1.0 (Nuno Leitao)
  Re: Linux < -- > Windows NT network (mist)
  Re: serieller Remotezugriff auf DOS-Rechner? (Ingo Ciechowski)
  ssh + squid + scotty ("Dominik")
  URGENT: NIS and RH 5.9.7 problem login... (Andre Couture)
  Re: IP Aliasing problems (Matthew Kirkwood)
  Re: pppd: 244000 not supported ("Clifton T. Sharp Jr.")
  Re: NT faster than Linux? (Richard Corfield)
  Re: RedHat 5.2 and Linksys Combo Cards (John Newhall)
  Re: Linux < -- > Windows NT network (Luca Filipozzi)
  Re: Redhat 6.0... the good, the bad, and the ugly ([EMAIL PROTECTED])

----------------------------------------------------------------------------

From: "Thomas" <[EMAIL PROTECTED]>
Subject: Routing / NAT problems
Date: Wed, 5 May 1999 17:12:14 +0200

  Hello,

I have a problem concerning ipchains (I believe).
The setup is like this:

Internet <-> Linux router <-> Class C network (192.168.x.x)

I have used ipchains with MASQ so the clients on the C network
can access the internet, that works fine... but I have problems
when I want to access individual computers sitting on the C network
from the outside (from the internet). Something like generic NAT.
I understand that I can't use the 192. addresses, so I need to map
real IP's to correspond with the computers on the 192. net, but how?
The ipchains REDIRECT only seems to work with certain ports on
the localhost, not a full redirect to another IP.

The actual real-world problem is logging on with Win98 clients that
come in off the internet, to a protected NT domain that sits
behind a linux (RH 6.0) router/firewall. The Win98 clients can have
static IP's.

Sincerely,
  Andreas






------------------------------

From: kite@NoSpam.%inetport.com (Clifford Kite)
Subject: Re: Problem connecting under Linux
Date: 4 May 1999 20:53:41 -0500

[EMAIL PROTECTED] wrote:

: I've written the following script (of course replacing stuff between <> by my
: own ones ):

: pppd connect 'chat -v "" ATD<YOUR_NUMBER> CONNECT "" ogin:<YOUR_LOGIN>
: word:<YOUR_PASSWORD>' /dev/modem <YOUR_MODEM_SPEED> -detach debug crtscts
: modem defaultroute &

: The modem lightens as if the connection is working. However, after a moment
: the light turns as if the connection was off. I aslo tried the same script
: replacing /dev/modem with /dev/cua1 unsuccessfully.

: When I check the ifconfig file, nothing has been added while I try connecting
: with the script. Here what it contains:

: lo  link encap:Local loopback
:     inet addr:127.0.0.1 Bcast:127.255.255.255 Mask 255.0.0.0
:     UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
:     RX packets:0 errors:0 dropped:0 overruns:0
:     TX packets:0 errors:0 dropped:0 overruns:0

There's no ppp interface which means pppd never got started or wasn't
able to bring it up.  You need to find the chat messages in whatever
file RH sends them.  Look in /etc/syslog.conf and note the files on the
right side of the configuration. The messages should be in one of them
and give clues about why the chat script fail, which is what most likely
happened.  There are lots of things that can cause chat to fail.  Here's
one to try right away:  Replace the chat expect/send   CONNECT ''  with
CONNECT "\d\c"  where the meanings of \d and \c can be found in "man chat."

The file to which the pppd link negotiation messages generated by the
debug option are sent should also be given in one of the syslog.conf
configuration lines.  These are important after the ppp interface is up
when pppd fails to negotiate a link protocol.

At a minimum you'll need to post the chat -v messages found in the log
file for us to be able to offer an opinion about the problem.

--
Clifford Kite <kite@inet%port.com>                       Not a guru. (tm)
/* The wealth of a nation is created by the productive labor of its
 * citizens. */

------------------------------

From: [EMAIL PROTECTED] (brian moore)
Crossposted-To: comp.os.linux.misc
Subject: Re: 2 NIC in RH, 2 subnet required?
Date: 5 May 1999 15:13:56 GMT

On 5 May 1999 05:02:57 GMT, 
 Mark Hahn <[EMAIL PROTECTED]> wrote:
> 
> > They will need to be on different subnets if you expect to route, yes.
> 
> nah.

Will be unless you plan on doing host routing, which raises the
complexity of a network greatly (and makes it a major pain in the butt
to do anything).

-- 
Brian Moore                       | "The Zen nature of a spammer resembles
      Sysadmin, C/Perl Hacker     |  a cockroach, except that the cockroach
      Usenet Vandal               |  is higher up on the evolutionary chain."
      Netscum, Bane of Elves.                 Peter Olson, Delphi Postmaster

------------------------------

From: [EMAIL PROTECTED] (Dale Pontius)
Subject: Re: How to control ip-up execution depending on whether I dial out to ISP or 
in to my own box?
Date: 5 May 1999 15:53:15 GMT

In article <[EMAIL PROTECTED]>,
        [EMAIL PROTECTED] (Thomas Porter) writes:
>
> I have a standalone Linux box at home that I have set up to do dialout to my
> ISP.  I use ppp-on and ppp-off scripts as documented in the PPP How-to.  I also
> have scripts to dial out to a RAS where I work.  These scripts run different
> chat scripts and select different ppp options, since these can easily be
> configured in the scripts.
>
> I also use mgetty with Auto-PPP compiled in to enable dial in to my box and
> again point to a different set of ppp options for this.  No problems so far.
>
> BUT, ip-up, ip-down, and ip-up.local are run everytime pppd starts, and I have
> certain things I want to happen when I connect up to my ISP and RAS, and very
> differrent things to happen when I dial _into_ my box.
>
> Is there anyway to specify what ip-up scripts to run, or do I have to make a
> general ip-up script smart enough to figure out how it has been called?  I
> realize that ip-up is passed 5 parameters (or 6 if ipparam is set in the ppp
> options file), but I have not figured out how to use any of those parameters to
> help me determine if the ppp connection was caused by a dialout or a dialin,
> considering I use just one modem, and this is an either/or situation and not
> one where ppp0 is always for dialout and ppp1 is for dialin, for example.
>
> Any ideas?  For example can I force the ppp device to be used, like ppp0 or
> ppp1?
>
Two of the parms passed to ip-up and ip-down are the local and
remote IP addresses. I currently dial out to two different places,
and at one point was dialing th three. Look at the address passed
in - I believe I've used the remote, and just parse based on IP
number. Since I get a new IP each time I dial in, I just use the
first one or two elements instead of all four - the level of detail
is sufficient to discriminate. Then based on who I'm connected to
I do different things.

As for a dial in, don't you have absolute control over at least the
local address? That should be a piece of cake to parse and detect.

Try man pppd to get the specifics on the parameters of ip-up.

Dale Pontius
(NOT speaking for IBM)

------------------------------

From: Khairul Effendy <[EMAIL PROTECTED]>
Subject: How to set-up auto-login in Linux
Date: Wed, 05 May 1999 18:03:50 +0800

How do we set-up auto login (by-passing login session ) when booting a
Linux box?
Anybody can give a clue?

Khairul
new user
RedHat 5.2


------------------------------

From: Flippie Spies <[EMAIL PROTECTED]>
Subject: Re: Squid Setup
Date: Wed, 05 May 1999 10:33:28 +0000

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Chris Blaszczyk wrote:
<blockquote TYPE=CITE>Sorry for this question. I am new at Linux and am
getting the following
<br>error after running&nbsp; /usr/local/squid/bin/squid -z
<br>FATAL: Failed to make swap directory /usr/local/squid/cache/00: (13)
<br>Permission denied
<p>I am logged in as root. Any information would be appreciated.</blockquote>
See if there is a /usr/local/squid/cache/00</html>


------------------------------

From: Nuno Leitao <[EMAIL PROTECTED]>
Crossposted-To: 
comp.dcom.sys.cisco,comp.dcom.net-management,comp.protocols.snmp,comp.os.linux.networking,comp.protocols.tcp-ip
Subject: ANNOUNCE: SNMP Sniffer v1.0
Date: Wed, 05 May 1999 15:41:54 +0100


  Announcing SNMP Sniffer version 1.0, a promiscuous SNMP packet decoder for
Linux and Solaris (potentially runs in any *NIX system supporting libpcap and
CMU-SNMP).
  This is the first version without the "Beta" tag.

  More information and source code in 

        http://users.linuxbox.com/~nunol/snmpsniff/

  Cheers.

-- Nuno Leitao ([EMAIL PROTECTED])
Development Engineer, UUNET - An MCI WorldCom Company,
Internet House, 332 Science Park, Milton Road, Cambridge, CB4 4BZ
Tel +44 1223 250100
Fax +44 1223 250358     http://www.uk.uu.net/

------------------------------

From: mist <[EMAIL PROTECTED]>
Subject: Re: Linux < -- > Windows NT network
Date: Wed, 5 May 1999 11:04:40 +0100
Reply-To: mist <new$[EMAIL PROTECTED]>

Amir Malik <[EMAIL PROTECTED]> scribed to us that -
>The output of ifconfig:
>
>lo        Link encap:Local Loopback
>          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
>          UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
>          RX packets:4 errors:0 dropped:0 overruns:0
>          TX packets:4 errors:0 dropped:0 overruns:0
>
>eth0      Link encap:Ethernet  HWaddr 00:00:1B:4C:02:47
>          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0
>          TX packets:3 errors:0 dropped:0 overruns:0
>          Interrupt:3 Base address:0x300
>

They both look fine.  Assuming you're trying to give the linux box an IP
address of 192.168.0.1


>The output of route -n:
>
>Kernel IP routing table
>Destination   Gateway       Genmask         Flags Metric Ref    Use Iface
>192.168.0.2   0.0.0.0       255.255.255.255 UH    0      0        1 eth0
>192.168.0.1   192.168.0.2   255.255.255.255 UGH   0      0        0 eth0
>127.0.0.0     0.0.0.0       255.0.0.0       U     0      0        1 lo
>

That looks strange.  Why are you trying to route packets for yourself
via the machine .2?  (Though I think that that "use 0" indicates that
the route is not normally used..)  What I would expect to see there is
just one entry, something like

192.168.0.0    0.0.0.0       255.255.255.255 blah blah blah blah eth0


Which you should be able to generate with 


route add -net 192.168.0.0

If you actually want to route all your packets for *other places* (eg
the Internet) via the .2 machine, you'll also need something like

route add default gw 192.168.0.2

Perhaps with an eth0 in there somewhere, I forget.

Try doing the above route commands after 

ifconfig eth0 down
ifconfig eth0 up 

Which should scrub the existing routes.   (Check that the interface
comes back up properly first though.)

<snip>
-- 
Mist.

------------------------------

From: [EMAIL PROTECTED] (Ingo Ciechowski)
Crossposted-To: de.comp.os.msdos,de.comm.software.misc,de.comp.os.unix.networking
Subject: Re: serieller Remotezugriff auf DOS-Rechner?
Date: Wed, 05 May 1999 13:39:45 +0200

In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] () wrote:

> Zugriff auf den DOS-Rechner bekommst Du, wenn Du die Ein- und Ausgabe von 
> COMMAND �ber die Schittstelle f�hrst. (COMMAND /? hilft Dir)
> Da DOS kein Multitasking kann, kannst Du aber keine anderen Programme mehr
> auf dem Rechner ausf�hren. (Auch kann man mit der Tastatur und dem 
> Bildschirm nichts mehr anfangen) Eine M�glichkeit w�re da ein Multitasking
> Aufsatz, wie er z.B. bei Caldera OpenDOS dabei ist. 
> 
> Andreas 


Hm, ich habe das mit der Umleitung der Console mal probiert; nur leider
ohne Erfolg.
Obwohl die serielle Schnittstelle einwandfrei arbeitet, bekomme ich beim
Aufruf von COMMAND COM1: die Fehlermeldung:

  Angegebenes COMMAND-Verzeichnis fehlerhaft

Mit ctty com1: erziele ich leider auch nur:

  Schreibst�rung beim Schreiben auf Ger�t COM1


Die Umlenkung der Console w�re eine hinreichende L�sung, da ich das
Frontentprogramm der TK-Anlage beenden und mir die Logdatei mittels type
abrufen k�nnte - nur funktionieren m��te das schon...

------------------------------

From: "Dominik" <[EMAIL PROTECTED]>
Subject: ssh + squid + scotty
Date: Wed, 5 May 1999 14:52:20 +0200

Hi linuxer.

Some maybe simple questions.

1.
I installed ssh 1.2.26. After them I checked my system with nessus and he
said, i must "update" my ssh on 1.2.25 or use the 2.0 protocol. Do you know
what this mean.

2.
Squid: Do you know, where I can forbite ports? I only want Port for ftp and
http.

3.
scotty: I installed it but how can I start the X-version? Only "#" are
prompted if I start it.

Thank you very much...





------------------------------

From: Andre Couture <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: URGENT: NIS and RH 5.9.7 problem login...
Date: Wed, 05 May 1999 12:17:22 -0400


Hi everyone,

I've upgraded one machine on my private net to RH 5.9.7.
Since then, i cannot login to that machine from any user account that
are defined on my NIS server on RH5.2.

That used to work fine with RH5.2 before.

I can do 'ypcat passwd' or any other yp commands.

If I login as root, I can do 'su - xxx' and it works, it properly mount
the home directory (using autofs) and set everything correctly.
But if I do the following it does not work
$ telnet localhost
...
can't login...

What is it that I'm missing, I've also tried to add a user called
'+::::::' and a group called '+:::' and still nothing.

Is there a problem using RH5.9.7 (RH6.0) nis to a older RH 5.2???

Thanks
Andre


--

  ------------------------------------------------------------------------
Andre Couture
938934 Ontario Inc.
mailto:[EMAIL PROTECTED]





mailto:[EMAIL PROTECTED]




------------------------------

From: Matthew Kirkwood <[EMAIL PROTECTED]>
Crossposted-To: ox.os.linux
Subject: Re: IP Aliasing problems
Date: Wed, 5 May 1999 12:43:12 +0100
Reply-To: Matthew Kirkwood <[EMAIL PROTECTED]>

On 5 May 1999, Nick Williams wrote:

> ifconfig eth0:0 100.0.0.1        

> 100.0.0.0       0.0.0.0    255.0.0.0    U         0 0         0 eth0

> Any ideas what is going on here?

Currently, packets never arrive on an alias, nor are they sent through
them, I believe.  Think of aliases as symlinks, rather than duplicates
and this makes some sense.

Your traceroute problems are likely to be bugs in traceroute itself, as
it does much of the work the would usually be done inside the kernel.

The TCP failures are more interesting - can the other boxes get in?
tcpdumps of this might help.

Matthew.


------------------------------

From: "Clifton T. Sharp Jr." <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: pppd: 244000 not supported
Date: Wed, 05 May 1999 11:20:15 -0500

Clifford Kite wrote:
> Thanks for the clarification, I can see that buffering the decompressed
> data in the modem would be the right thing to do - now that you point
> it out.  I'd assumed that "input buffer" referred to compressed data
> buffering, which wasn't very bright of me.  So the UART doesn't get
> flooded, and there is no problem provided the compression algorithms
> are designed so that no single decompression operation can expand
> a compressed data chunk and overflow the buffer.

Right. And, of course, provided the stuff is coded right. :-) I'm pretty
sure they work in my Zoom, as I've seen 10-11K downloads for long periods
on highly compressible text, pretty slick for a 45333 DCE speed.

Figured you already knew the mechanics of the FIFO queueing, too, but I
was having trouble articulating the explanation (it showed :-) so I figured
it was best if I just "walked the process" so I didn't put my foot in it.

-- 
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|   Cliff Sharp   |  "Speech isn't free when it comes postage-due."           |
|      WA9PDM     |   -- Jim Nitchals, founder, FREE                          |
+-+-+-+-+-+-+-+-+-+- http://www.spamfree.org/ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

------------------------------

From: Richard Corfield <[EMAIL PROTECTED]>
Crossposted-To: uk.comp.os.linux
Subject: Re: NT faster than Linux?
Date: 4 May 1999 21:13:25 +0100

In article <[EMAIL PROTECTED]>,
Anthony W. Youngman <[EMAIL PROTECTED]> wrote:
>
>Rumour? says that M$-basic was basically DEC-basic or somesuch that he
>came across while on work experience at college ...

Way back then BBC Basic was the thing - especialy Version 5 with what were
(for BASIC) advanced features such as switch and while and procedures
with local variables and hence recursion. It was hardly OO but not bad.

 - Richard.

-- 
   _/_/_/  _/_/_/  _/_/_/ Richard Corfield <[EMAIL PROTECTED]>
  _/  _/    _/    _/      Web Page:       http://www.littondale.freeserve.co.uk
 _/_/      _/    _/       Dance (Ballroom, RnR), Hiking, SJA, Linux, ... [ENfP]
_/  _/  _/_/    _/_/_/    PGP2.6 Key ID: 0x0FB084B1     PGP5 Key ID: 0xFA139DA7

------------------------------

From: [EMAIL PROTECTED] (John Newhall)
Subject: Re: RedHat 5.2 and Linksys Combo Cards
Date: Wed, 05 May 1999 13:02:26 GMT

that sounds about right,  is there and way i can find out what
arguments there are and the ones i need to use?

John


On Wed, 05 May 1999 12:27:48 GMT, [EMAIL PROTECTED] wrote:

>In article <[EMAIL PROTECTED]>,
>  [EMAIL PROTECTED] (TheMerk) wrote:
>>
>> i have 2 linksys combo cards,  one is a pci and the other is a pcmcia,
>> i cant seem to find a way to get linux rh 5.2 that is to use the bnc
>> connector and not the 10BaseT,  my main goal it to do a network
>> install on to my notebook that has a small hard drive,  but I would
>> like to get them both back up on my network,  the network is a peer to
>> peer based lan using 2 pc's, a couple of T-connectors and some coax.
>> lan works great in 98 and Nt.
>>
>>
>Those cards are ne2000 compatable. Try those drivers (ne200 & Compat.) I don't
>know if they will autoprobe though. Might have to pass some arguments.
>
>-----------== Posted via Deja News, The Discussion Network ==----------
>http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own    


------------------------------

From: [EMAIL PROTECTED] (Luca Filipozzi)
Subject: Re: Linux < -- > Windows NT network
Date: Wed, 5 May 1999 10:07:17 -0700

In article <7gohl3$7rl$[EMAIL PROTECTED]>, [EMAIL PROTECTED] 
says...
> The output of ifconfig:
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
>           UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
>           RX packets:4 errors:0 dropped:0 overruns:0
>           TX packets:4 errors:0 dropped:0 overruns:0
> 
> eth0      Link encap:Ethernet  HWaddr 00:00:1B:4C:02:47
>           inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0
>           TX packets:3 errors:0 dropped:0 overruns:0
>           Interrupt:3 Base address:0x300
> 
> The output of route -n:
> 
> Kernel IP routing table
> Destination   Gateway       Genmask         Flags Metric Ref    Use Iface
> 192.168.0.2   0.0.0.0       255.255.255.255 UH    0      0        1 eth0
> 192.168.0.1   192.168.0.2   255.255.255.255 UGH   0      0        0 eth0
> 127.0.0.0     0.0.0.0       255.0.0.0       U     0      0        1 lo
> 
> I still can't ping 192.168.0.2.

Your routing table is wrong. It should look something like:
Kernel IP routing table
Destination   Gateway       Genmask         Flags Metric Ref    Use Iface
192.168.0.0   0.0.0.0       255.255.255.0   U     0      0        0 eth0
127.0.0.0     0.0.0.0       255.0.0.0       U     0      0        1 lo
0.0.0.0       <gateway ip>  0.0.0.0         UG    0      0        0 eht0

You should be able to achieve this with
 route add -net 192.168.0.0 netmask 255.255.255.0
 route add -net 127.0.0.0 netmask 255.0.0.0
 route add default gw <gateway ip>

Also, to see if stuff is packets are actually being transmitted on your 
network, use tcpdump. Check out the man page. Try
To dump all packets
 tcpdump -i eth0
To dump packets originating from 192.168.0.1
 tcpdump -i src host 192.168.0.1
To dump packets from and to 192.168.0.1
 tcpdump -i eth0 src host 192.168.0.1 and dst host 192.168.0.1

Try running tcpdump while you ping... you should see some icmp-request 
(and, hopefully, some icmp-reply) traffic.

Hope this helps,

Luca
-- 
Luca Filipozzi <[EMAIL PROTECTED]>

------------------------------

From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.hardware,comp.os.linux.setup
Subject: Re: Redhat 6.0... the good, the bad, and the ugly
Date: Wed, 05 May 1999 15:35:18 GMT

Hi,where to find the ftp mirror? In article
<[EMAIL PROTECTED]
>,  mike*no*spam*@yourhelpdesk.com (Michael Balderas) wrote:

> FTP installs only so far...:)
>
> Mike
>
> On Wed, 5 May 1999 10:53:41 +1000, "Robert Brown" <[EMAIL PROTECTED]>
> wrote:
>
> >Where is everyone getting RH6.0? I thought it wasn't available until the
> >10th May....
> >
> >RB
> >
> >Jeff Volckaert <[EMAIL PROTECTED]> wrote in message
> >news:7gmu2o$[EMAIL PROTECTED]...
> >> Hello Everybody,
> >>
> >> I just did two Redhat 6.0 installs over the weekend and thought some
> >people
> >> might like to read some comments.  Overall I'm really impressed.  Every
> >> Redhat version since 3.0.3 has raised my expectations of Linux and not let
> >> me down.
> >>
> >>
> >> The good:
> >>
> >> The single disk ftp install is great.  It's also nice to test the X setup
> >> during install.
> >>
> >> The bootup process is nicer since they added green OKs (Red faileds) and
> >> changed the X login screen to a much more stylish graphic.
> >>
> >> I LOVE the login option to select Gnome, KDE, etc on login.  Great job
> >> Redhat!
> >>
> >> The desktops keep getting better all the time, this is no exception.  This
> >> is my first experience using Gnome and I love it.  Just need better
> >> installed themes now.  Can't they work a deal with www.themes.org or
> >> something?
> >>
> >> All my hardware (with the exception of my Hauppauge tuner card) works
> >> flawlessly.  Ensonique sound, Riva128 video, 13G seagate drive and ne2000
> >> network included.
> >>
> >>
> >> The Bad:
> >>
> >> I've had a few hard locks.  Ouch!  Some of my first with Linux (which i've
> >> been using for over 3 years).  Not a good trend to start.
> >>
> >> LICQ segment faults now... could be LICQ though.
> >>
> >> Still haven't got XawTV working with my Hauppauge tuner card.  I'll have
> >to
> >> mess around with hand loading modules like I had to do with Redhat
> >> 5.2+2.2.5.  Just hoping I wouldn't have to.
> >>
> >>
> >> The Ugly:
> >>
> >> The Ultima Online client will not run under Gnome but will under
> >WindowMaker
> >> (without sound though, but that's Origin's prob).
> >>
> >> DHCP will not work with my Cable modem.  My workstations DHCP fine to my
> >> Linux DHCP server though.  This one really hurts and prevents me from
> >> upgrading my firewall until it's fixed.  I'm told that Redhat now uses a
> >> program called pump instead of dhcpcd.
> >>
> >>
> >>
> >
>
>

============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own    

------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.networking) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Networking Digest
******************************

Reply via email to