Linux-Networking Digest #44, Volume #11 Wed, 5 May 99 02:14:19 EDT
Contents:
Re: PCI Network Card that definetly work in Linux and Window 98 (Kevin Colquitt)
Re: newbie networking problem (Kevin Colquitt)
Re: newbie networking problem (Luca Filipozzi)
Re: Redhat 6.0... the good, the bad, and the ugly (Michael Balderas)
How to control ip-up execution depending on whether I dial out to ISP or in to my
own box? (Thomas Porter)
Use 8 IP as a subnet to the whole 16 ip network (Mark Lo)
Proxy server ("John Smith")
Re: Linux < -- > Windows NT network (Amir Malik)
Re: Virus Warining - Just came in (=?iso-8859-1?Q?Bj=F8rn?= Ruberg)
Re: New radius server ("Michael George III")
2 NIC in RH, 2 subnet required? ("Jeffrey Yu")
Re: Redhat 6.0... the good, the bad, and the ugly (J. Peterson)
Re: NDS logins on Linux? (L J Bayuk)
Re: NFS mount trouble: RPC not registered? ("James Gillespie")
Re: Tickling diald? ("K.A. Steensma")
Re: Redhat 6.0... the good, the bad, and the ugly (William Taylor)
Trying to get my new linux system to talk to @home ("Derek Smith")
Re: viewing Linux Xserver Xfree86 on NT ? (Robin Jackson)
Re: IP masquerading - blocking remote telnet (Luca Filipozzi)
VERY slow modem (Jason Bond)
FTP Login to red hat running FWTK (Dennis)
----------------------------------------------------------------------------
From: Kevin Colquitt <[EMAIL PROTECTED]>
Subject: Re: PCI Network Card that definetly work in Linux and Window 98
Date: Wed, 05 May 1999 03:59:14 GMT
I think the Intel EtherExpress Pro 10/100 is the best, at least for me :),
instead of re-compiling... you could load its module at bootup "eepro100.o"
Kevin
On Wed, 5 May 1999 [EMAIL PROTECTED] wrote:
> Can anybody suggest a reliable but inexpensive PCI 10/100 Ethernet card that
> will definetly work in Linux (without re-compiling the kernel) and Windows 98?
>
> Regards,
> Brian
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>
>
------------------------------
From: Kevin Colquitt <[EMAIL PROTECTED]>
Subject: Re: newbie networking problem
Date: Wed, 05 May 1999 03:52:50 GMT
Do you load the drivers for your 3c589c as a module or is it compiled in?
If I were you... I would load it as a module then run dmesg to see if the
kernel had a problem with it. also you might wanna run something like
procinfo to make sure you don't have something else taking up irq 10.
good luck :)
Kevin
On Tue, 4 May 1999, Jim Thompson wrote:
> I'm running redhat 5.2 on my laptop. I'm trying to get the laptop
> talking to my network. I have a 3c589c pcmcia card. I've successfully
> setup the network card, I can ping the loopback, but I'm unable to ping
> anything on the network. If I use ifconfig to see if the adapter is
> active I get the following:
>
> 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:24 errors:0 dropped:0 overruns:0 frame:0
> TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
>
> eth0 Link encap:Ethernet HWaddr 00:a0:24:A8:D8:D6
> inet addr:192.168.0.4 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 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
> Interrupt:3 Base address:0x300
>
> I thought the problem might be the interrupt being set to 3. I
> downloaded a setup program for the pcmcia card and set the irq to 10. I
> rebooted and did another ifconfig and received the same settings. The
> card is still set to irq 10. Anyone know what the problem is here?
>
> Jim
>
>
>
>
>
------------------------------
From: [EMAIL PROTECTED] (Luca Filipozzi)
Subject: Re: newbie networking problem
Date: Tue, 4 May 1999 21:02:20 -0700
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] says...
> I'm running redhat 5.2 on my laptop. I'm trying to get the laptop
> talking to my network. I have a 3c589c pcmcia card. I've successfully
> setup the network card, I can ping the loopback, but I'm unable to ping
> anything on the network. If I use ifconfig to see if the adapter is
> active I get the following:
>
> 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:24 errors:0 dropped:0 overruns:0 frame:0
> TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
>
> eth0 Link encap:Ethernet HWaddr 00:a0:24:A8:D8:D6
> inet addr:192.168.0.4 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 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
> Interrupt:3 Base address:0x300
>
> I thought the problem might be the interrupt being set to 3. I
> downloaded a setup program for the pcmcia card and set the irq to 10. I
> rebooted and did another ifconfig and received the same settings. The
> card is still set to irq 10. Anyone know what the problem is here?
>
> Jim
>
>
>
>
Please post the output of "route -n".
Try typing "route add -net 192.168.0.0 netmask 255.255.255.0".
--
Luca Filipozzi <[EMAIL PROTECTED]>
------------------------------
From: mike*no*spam*@yourhelpdesk.com (Michael Balderas)
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 04:00:09 GMT
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.
>>
>>
>>
>
------------------------------
From: [EMAIL PROTECTED] (Thomas Porter)
Subject: How to control ip-up execution depending on whether I dial out to ISP or in
to my own box?
Date: 5 May 1999 02:38:53 GMT
Reply-To: [EMAIL PROTECTED]
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?
--
Tom Porter [EMAIL PROTECTED]
========================================================================
"On two occasions I have been asked [by members of Parliament],
'Pray, Mr. Babbage, if you put into the machine wrong figures, will
the right answers come out?' I am not able rightly to apprehend the
kind of confusion of ideas that could provoke such a question."
------------------------------
From: Mark Lo <[EMAIL PROTECTED]>
Subject: Use 8 IP as a subnet to the whole 16 ip network
Date: Wed, 05 May 1999 11:20:42 +0800
Is it possible to use 8 ip from 16 to subnet for Firewall to Webserver?
After I read "Proxy ARP Subnet mini-HOWTO", I wonder to setup as
follows.
[ Router ]-----------[ FireWall ]--------------[ www ]
10.20.30.1 10.20.30.2 10.20.30.9 10.20.30.10
255.255.255.240 .240 .248 .248
So, from Router to firewall to webserver, it is the same network.
>From firewall to webserver, it is a subnet.
But I wonder it may not good firewall to protect the webserver. As I
will use ipfwadm, this setup will pass through the firewall rules.
Any comment are appreciated,
Mark
------------------------------
From: "John Smith" <[EMAIL PROTECTED]>
Subject: Proxy server
Date: Tue, 4 May 1999 22:08:04 -0700
is there a proxy server that is not SQUID? I'm getting an error with squid,
when i run it -z it tells me it cannot create the directories? anyone has
any idea?
------------------------------
From: Amir Malik <[EMAIL PROTECTED]>
Subject: Re: Linux < -- > Windows NT network
Date: 5 May 1999 04:32:35 GMT
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.
Thanks,
Amir
Luca Filipozzi wrote:
>
> In article <7glinf$cqp$[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> says...
> > I have a 3-port + 1 uplink port Asante NetExtender hub.
> Hub basics: an uplink port has an internal cross-over. This allows you
to
> use a standard 10BaseT cable to connect this hub's uplink port to the
> normal port of another hub or switch. In this way, you only have to have
> one cable hanging around... the straight through kind. Otherwise, if you
> have both on hand (straight through and cross-over) and you don't do a
> good job of labelling, you always waste time figuring out whether you
> have the right cable.
>
> > Which port should
> > I connect the 10BaseT cable to?
> From computer to hub: to the normal ports with a "normal" straight-thu
> cable.
>
> > If I connect it to any of the three normal
> > hub ports, they light up,
> Which is good. Leave it in the normal port.
>
> > but if I connect it to the uplink port, the
> > light doesn't light up.
> Which is good. Don't plug your computer into the uplink port.
>
> > When I try to do: route add -net 192.168.0.0
> > ...it says:
> > SIOCADDRT: Network is unreachable
> This means that your interface (eth0 or whatever) doesn't have an ip
> address in the 192.168.0.0 network. Please post the output of the
> following commands:
> # ifconfig
> # route -n
> This will help us to diagnose.
>
> > ...but when I do: route add -net 192.168.0.2 (the ip for the NT box)
> > ... it says:
> > SIOCADDRT: Invalid argument
> You can't do this. You're trying to make use a host address
(192.168.0.2)
> as a network address (192.168.0.0).
>
> > How can I set up the approptiate routing?
> > NOTE: This is my Kernel IP routing table:
> You should type
> # route add -net 192.168.0.0 netmask 255.255.255.0
>
> Note that the mask argument is important here since you have chosen
> 192.168.0 as your network. All bits 0 (integer 0) or all bits 1 (integer
> 255) are special values in terms of networking numbers. All bits 0 is
> usually the network address while all bits one is usually netmask.
>
> Therefore, I recommend you use 192.168.1.0 as your subnet rather than
> 192.168.0.0.
>
> Please post the output with hostname resolution disabled. From this
> routing table, we can't see what pc404hp's ip address is. You can do
this
> by typing:
> # route -n
>
> > Destination Gateway Genmask Flags Metric Ref Use Iface
> > pc404hp * 255.255.255.255 UH 0 0 1 1 eth0
> > 127.0.0.0 * 255.0.0.0 U 0 0 1 1 lo
> > default pc404hp 0.0.0.0 UG 0 0 1 0 eth0
>
> --
> Luca Filipozzi <[EMAIL PROTECTED]>
================== Posted via SearchLinux ==================
http://www.searchlinux.com
------------------------------
From: =?iso-8859-1?Q?Bj=F8rn?= Ruberg <[EMAIL PROTECTED]>
Subject: Re: Virus Warining - Just came in
Date: Thu, 29 Apr 1999 09:14:51 +0200
Mikey wrote:
>
> If you receive an email titled "It Takes Guts to Say 'Jesus' DO NOT
> OPEN
> IT.
[ blah blah blah ]
Unless this actually happened to you: Please check the major anti-virus
websites before you post anything like this. This is just a re-write of
the other "Good times"- and "returned or unable to deliver"-warnings.
Neither DataFellows, McAfee nor Symantec had this listed, except for in
the "Hoax"-section on the Symantec site
(http://www.symantec.com/avcenter/hoax.html).
Ask someone who has a clue before you post stupid messages as this one
on news.
--
Bj�rn Ruberg / http://traktor.nlh.no/beorn
Remove the .no_spam for my email address
"The more you scream the less you hear" * f i s h *
------------------------------
From: "Michael George III" <[EMAIL PROTECTED]>
Crossposted-To: comp.unix.solaris
Subject: Re: New radius server
Date: Wed, 5 May 1999 00:12:56 -0400
Kerry J. Cox <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Currently we are running the Livingston radius server. I am
> entertaining the possibility of moving to another radius server or
> reconfiguring the existing one. What we really need is to set it up so
> that we can determine who we want to be able to log in multiple times
> and who we don't want to allow on more than one at a time.
Been there, migrated, from livingston, to ascend, and finally ended up here
http://www.merit.edu/aaa/
Works great! Note: If you are running Solaris 2.7, it will not compile
properly. You need to rewrite a small section of code due to a duplicate
name collision between Solaris and Radius. Other than that, it rocks and
has features, features, features...
Also, check out my radius page...
http://mike.wnol.net/projects/radius
Peace!
-Michael
------------------------------
From: "Jeffrey Yu" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: 2 NIC in RH, 2 subnet required?
Date: Tue, 4 May 1999 20:11:30 -0400
Hi, I am trying to configure two NIC in my Linux box (RH5.2).
I assigned two ip for both, ie, 191.191.191.1, 191.191.191.2.
Now the problem is I can only ping the 2nd NIC (eth1). It
seems this is a network routing issue. What should I do to
configure the routing table right? Are these two NC required
to be from two different subnet, ie, 191.2.0.0 and 191.5.0.0?
Please help!!
--Jeffrey
------------------------------
From: [EMAIL PROTECTED] (J. Peterson)
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 01:05:11 GMT
Was there any problem with your hard drive being greater than 8.4MB?
>All my hardware (with the exception of my Hauppauge tuner card) works
>flawlessly. Ensonique sound, Riva128 video, 13G seagate drive and ne2000
>network included.
------------------------------
From: [EMAIL PROTECTED] (L J Bayuk)
Subject: Re: NDS logins on Linux?
Date: 5 May 1999 00:35:45 GMT
[EMAIL PROTECTED] wrote:
>Hi, I'm clueless about Netware so please forgive me if I don't use the right
>terminology here. Anyway, I'm running RedHat 5.2 (kernel 2.0.36) with ncpfs
>2.2.0. I'm trying to login to a Netware 4.11 server that does logins with
>NDS. I've read conflicting stuff on whether ncpfs 2.2.0 supports NDS logins.
>Does it? If yes, how would I go about logging in? If no, is there another
>software package that will let me do an NDS login with my current setup?
I think looking at the source distribution will clear up confusion.
ncpfs 2.2.0 does come with NDS support, but it is normally left out
when building, because of a patent restriction on the RSA encryption
used by NDS. See the README.NDS file in the source tree.
The question you need to ask your Netware admin is, do they have
bindery emulation on or off? If on, you will be able to log in
with ncpfs 2.2.0 without its NDS support. If off, you will need
to either build ncpfs with NDS support, or use Caldera's NDS client.
------------------------------
From: "James Gillespie" <[EMAIL PROTECTED]>
Subject: Re: NFS mount trouble: RPC not registered?
Date: Tue, 4 May 1999 21:15:22 -0400
<[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]...
> I am trying to get a two node home LAN to mount directories and I'm
> stuck. I've checked all the HOWTOs - but I can seem to find this one.
> I have two nodes (upstairs - server, and downstairs). They can ping one
> another, rlogin, export displays etc., but the NFS mounting is hosed.
> It won't mount during bootup and when I do it manually
>
> [root@naughton /etc]# mount downstairs:/net
> mount: RPC: Program not registered
[SNIP]
Have you checked to see if the nfsd daemon is running, and have you shared
the filesystem that you want to share? I have not done too much with nfs
under linux, but in Solaris the file /etc/dfs/dfstab is where you share
files, and on boot if there are entries in this file then the nfsd daemon
will start automatically. Running /etc/init.d/nfs.server manually will start
the daemon manually if you share the filesystem manually.
Hope this helps,
Jim Gillespie
------------------------------
From: "K.A. Steensma" <[EMAIL PROTECTED]>
Subject: Re: Tickling diald?
Date: Wed, 05 May 1999 01:11:26 GMT
An un-resolved IP address from the DNS server triggers diald to call up
your IPS. The author (of diald) suggests that you NOT run a DNS server.
It is far easier to 'just' have a /etc/hosts file to perform look-up's.
KAS
Braxton Burrsaddle wrote:
> When I first loaded SuSE 6.0 on my gateway box, diald worked
> perfectly. Then I set up DNS, which works fine, but now diald doesn't
> automatically dial. It appears to "work", but links don't stay up.
> My intent is that diald will dial to my ISP when packets need to be
> sent. dctrl works just fine when it is commanded to force the link
> up, it starts pppd and the link works, but it seems that nothing is
> tickling diald to stay awake, and it times out. Everything that wants
> to send or receive packets works as long as the link stays up, but
> that appears to be strictly constrained by a timeout. Starting an
> application does not stimulate diald to start a link.
>
> It looks like setting up DNS (and making the change to "nameserver"
> that defines the gateway as the local nameserver) broke diald. Am I
> interpreting this right? What is it that should stimulate diald to
> keep my ppp link up, and how do I route packets to ensure that diald
> gets tickled?
>
> Aside - next stop is masquerading. I got the lx_suse.rpm kernel 2.2.5
> update, and it appears not to have included ipchains. Anyone know
> whether this is an oversight?
>
> TIA -
>
> Greg
>
> [EMAIL PROTECTED] reply-to bogus, remove z's to construct email
> address.
------------------------------
From: William Taylor <[EMAIL PROTECTED]>
Reply-To: [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 05:29:13 GMT
I didn't see any. RH6 installed fine on a clean 18GB WD drive. I did notice
that fdisk did not get the correct LBA translation for the drive but instead
used the "real" values. I changed this manually to the LBA values. On a drive
with a pre-existing FAT partition it got the values correctly.
I got m SB PCI128 working with no problems. And so far no issues with KDE or
GNOME.
"J. Peterson" wrote:
> Was there any problem with your hard drive being greater than 8.4MB?
>
> >All my hardware (with the exception of my Hauppauge tuner card) works
> >flawlessly. Ensonique sound, Riva128 video, 13G seagate drive and ne2000
> >network included.
------------------------------
From: "Derek Smith" <[EMAIL PROTECTED]>
Subject: Trying to get my new linux system to talk to @home
Date: Wed, 05 May 1999 00:59:28 GMT
I just got done setting up a linux system and am having problems getting it
to talk to thecox@home network. (static IP address) Linux is talking to the
network card correctly, but won't resolve DNS or anything from the network.
Is there anyone who has their system up and connected to the @home network
that could give me some pointers? I'm using Red Hat 5.2. It's like the
system works perfectly until I try to access something outside the machine.
Thanks
Derek Smith
Sound Technology Consultants
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Robin Jackson)
Crossposted-To: comp.os.linux.misc,comp.os.linux.x
Subject: Re: viewing Linux Xserver Xfree86 on NT ?
Date: Wed, 05 May 1999 05:39:38 +0000
In article <[EMAIL PROTECTED]>,
gus <[EMAIL PROTECTED]> wrote:
>Robin, I post this for two reasons, the first is that I think I know the
>answer, and the second is that, if I do, then it helps you, if not, then
>I learn something new ...
>
>... so, verify I am correct before trusting this as accurate.
>
>startx will always start an X window manager on the Linux machine.
>Remember, the X server *always* operates on the *client* machine. So, if
>you want an X window session on an NT box, then the X server must run on
>the NT box. The Application server is the Linux box. MI/X *is* the X
>server. If you are at the Linux console, then Xfree is the X server. The
>trick is that you can tell any X aware app which server to display
>itself on. So, the DISPLAY environment variable indicates to the
>application which X server to communicate with. It will default to the
>linux machine, but this can be changed by setting the DISPLAY variable.
>
>So, From your NT box, start MIX. Then telnet to the Linux box and log
>in. Set the DISPLAY variable to "export DISPLAY=<NT-IPAddress>:0.0
>
>Then, do something like "xterm &".
>
>At no point have you said "startx". There is no need.
>
>My only concern is that IIRC, MIX does not support the "qt" libraries or
>something, so KDE does not run correctly.
Hi
All the above work son my Mac (not NT).
The problem is I don't just want an xterm I want the same type of desktop,
startbar, control panel that I see on my Linux box.
I have it partially sorted by doing an exec fvmw2 (or something like that)
but it is not working perfectly.
Robin
------------------------------
From: [EMAIL PROTECTED] (Luca Filipozzi)
Subject: Re: IP masquerading - blocking remote telnet
Date: Tue, 4 May 1999 22:43:40 -0700
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] says...
> Here in comp.os.linux.networking, Wonkoo Kim <[EMAIL PROTECTED]>
> spake unto us, saying:
>
> >Disabling telnetd is definitely not an option for me, because
> >I have to telnet to the Linux box from other PCs in my home LAN.
> >(The Linux box has no monitor!)
>
> I just bought a cute little 9" mono VGA monitor for US$10 at a local
> computer fair for my firewall box. :-)
>
>
Yikes. Use SSH instead!! Get rid of telnetd on your firewall.
--
Luca Filipozzi <[EMAIL PROTECTED]>
------------------------------
From: Jason Bond <[EMAIL PROTECTED]>
Subject: VERY slow modem
Date: Tue, 04 May 1999 22:49:49 -0700
For some reason, transmission rates from my ISP
are unbearably slow with I am running in Linux.
When I am running in Win 95, they are much much
faster (seriously, like 100 times faster). I actually have 2 modems,
one is a 56k win modem (which windows obviously uses) and the other is a
33.6k modem which Linux uses. The discrepancy in speeds is NOT due to
56k vs 33.6k. I know it is quite hard to diagnose the problem from such
a limited description, but does anyone have any ideas as to why this
might be? Thanks greatly in advance.
Jason
------------------------------
From: [EMAIL PROTECTED] (Dennis)
Subject: FTP Login to red hat running FWTK
Date: Wed, 05 May 1999 01:55:55 GMT
Is it possible to ftp to my firewall running FWTK?
THanks
Dennis
------------------------------
** 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
******************************
