Linux-Networking Digest #135, Volume #10 Sun, 7 Feb 99 03:14:06 EST
Contents:
PCI + ISA NE2000 Cards ([EMAIL PROTECTED])
Re: Ping OK, can't FTP/Telnet/Samba (Marc Remijn)
Re: Intel EtherExpress 10/100B ISA need help (Zot O'Connor)
Re: Network Setup Problems (Ed Jones)
Re: FTPd, TELNETd Problems (Ed Jones)
Re: one ip address ("Nick Short")
Flags in if.h (Vladimir Peric)
Re: IP masquerading (jamie)
Re: Help: RoadRunner Akron and Linux (jamie)
Re: Any Help for my network ! (Luca Filipozzi)
backorfice client ([EMAIL PROTECTED])
Re: newbie: ping ok --no telnet ftp ("Sean Connolly")
Re: printing problem with Netatalk 1.42b (BrimStone)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Subject: PCI + ISA NE2000 Cards
Date: Sun, 07 Feb 1999 06:37:44 GMT
Reply-To: [EMAIL PROTECTED]
I have a pc that has two ethernet cards (NE2000). The first is an ISA that
has been set as jumperless at io=0x300 irq=10, and the other is a ne2k_pci.
Anyways, I thought I'd try the 2.2 kernels, but my set up didn't work (DHCP
bombs, delaying eth initialization). My own damn fault for not reading the
documentation. Anyways I took out the pci card to test something, and now
when I put the pci card back in it jumps on eth0 at irq=10 and DHCP fails and
my networking isn't set up properly. eth0 is supposed to DHCP my internet
address and as the default route, while eth1 is my local ethernet. I'm using
a greatly modified redhat 5.1 setup. How can I get my NE2000 to sit on
irq=10 and dhcp, while my eth1 grabs whatever is available?
Any assistance would be greatly appreciated.
Thanks,
Brian Seppanen
[EMAIL PROTECTED]
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: Marc Remijn <[EMAIL PROTECTED]>
Subject: Re: Ping OK, can't FTP/Telnet/Samba
Date: Sun, 07 Feb 1999 01:50:12 +0100
jim wrote:
> David Kirkpatrick wrote in message <[EMAIL PROTECTED]>...
> > What is the result of nbtstat -n on windows and does it match
> >the domain on linux?
> Here it is...
> #------------- Cut Here ----------------------------------------
> Node IpAddress: [192.168.1.2] Scope Id: []
> NetBIOS Local Name Table
> Name Type Status
> ---------------------------------------------
> DADDYS <00> UNIQUE Registered
> HOUSEHOLD <00> GROUP Registered
> DADDYS <03> UNIQUE Registered
> DADDYS <20> UNIQUE Registered
> HOUSEHOLD <1E> GROUP Registered
> JIM <03> UNIQUE Registered
> HOUSEHOLD <1D> UNIQUE Registered
> ..__MSBROWSE__.<01> GROUP Registered
> #------------- Cut Here ----------------------------------------
hmmm PENGUIN should be there somewhere... ... oh sorry that's with -c
option which shows the cache. First open network neighbourhood otherwise
there won't be anyting in the cache.
You might try nbtstat -A <ip address of penguin>
> >Are you using a non root login to login to Linux or are you
> >getting that far? When you say you can't telnet or ftp what
> >error messages are you getting?
> I've tried various logins... Usually non-root... Most often as 'jim' (as
> in nbtstat example above).
> FTP gives "connect: connection timed out" after :20-:30 seconds, then the
> ftp prompt with no connection. Telnet gives message box with "connect
> failed!" in the title bar and no other info except for an "OK" button.
> By the way, both FTP and Telnet first try to fire up the modem to make a
> dial-up connection. I hit a "cancel" button on the dial-up message box and
> the modem hangs up; then there's a flurry of flashing lights on the ethernet
> hub (mostly on the Win95 port, but at least one flash on the Linux port). I
> would like to know how to make Win95 try the Ethernet first; but that seems
> lower priority right now. I know that when my LAN worked a week or so ago
> that I had to cancel the dialup first and then FTP would connect over the
> Ethernet.
In the internet explorer settings check connection tab and set to
connect to the internet using LAN instead of using a phone line. Then
DUN won't fire up first. Yes even though it is in iexplorer this setting
is global and effects all programms using TCP/IP.
Maybe your LAN problems have the following cause. The other machines on
your network have autosensing 10/100 mbps cards, your old card and your
unix were 10 mbps, so the other cards switched to 10 mbps. Now the new
card in your windows is also 10/100. So when you switch on you win
machines first the speed will switch to 100 mbps which will give
problems with cards that can only do 10. But then you should probably
see the collision leds lighting on your hub and NIC's.
Because it worked before you changed the network card in your windows
machine it is probably some lower level protocol that is going wrong. So
SAMBA settings aren't the obvious things to look at first.
First things like ping, telnet and ftp should work fine and then it's
time to start looking at Samba settings.
> (The TCP/IP properties box for the NIC has an 'advanced' tab which has a
> check box named "Set this protocol to be the default protocol." It doesn't
> seem to make Win 95 try the NIC any earlier...)
> > Why is workgroup=HOUSEHOLD rather than bogusdomain?
> My reading of the Win95 resource kit is that a workgroup isn't the same as
> a domain... So that a company with one domain could use more than one
> workgroup (i.e. 'SALES', 'PAYROLL', 'TECHSUPPORT', etc.). I'll have to
> fiddle with this some more...
This is rather vague. If you have used windows NT and 95 machines in one
network you will know that in some cases the two are interchangeable,
but not allways.
A Windows (NT) domain is a workgroup with a shared userbase. So in a
domain the users are managed by one machine (a domain controller),
sometimes aided by one or more secondary dc's.
> >What are the complete names in lmhosts?
> The complete names are things like "penguin.bogusdomain.bogus". (As I
lmhosts file map NETBIOS names to IP adresses. The NETBIOS name of your
windows machine is the name you have entered in the.... (starting my
windows box)... 'identification' tab of network config. It's the
'computer name' entry.
Normally you only need this file if you want to access netbios smb
shares which are not on the same network.
On the same network machines announce their services via broadcasts. I
don't have any entry in my lmhosts file and can access my linux samba
server.
> just re-read my original message at the start of this thread I see that my
> lmhosts file has each computer defined with and without the domain name;
> that doesn't seem right. The Windows resource kit is a little dense here,
> but by my reading the Windows lmhosts should NOT have domain names, and the
> Linux version SHOULD. (?))
Again it's not needed. You might want to include you linux machine to
your \windows\hosts file to be able to ftp, telnet to it referring to
it's name.
If you really want to use a lmhosts entry to your linux machine than use
it's netbios name. Samba uses the host name for this. So don't add a
domain. Just penguin or even PENGUIN, but case doesn't seem very
important for NETBIOS /SMB.
> >> None of the config files have changed since the time it worked with the
> >> old NIC. Since this network is so small and unlikely to change, I was
> doing
> >> all my name resolving with the hosts & lmhosts files. (i.e., no DNS or
> >> WINS). As I said, this worked once... And it still works for Ping.
> >> My hosts file (for all three computers... the Linux box is named
> penguin):
> >> #------------- Cut Here ----------------------------------------
> >> 127.0.0.1 localhost
> >> 192.168.1.1 penguin
> >> 192.168.1.2 daddys
> >> 192.168.1.3 mommys
> >> #------------- Cut Here ----------------------------------------
> >> My lmhosts file (for all three computers):
> >> #------------- Cut Here ----------------------------------------
> >> 192.168.1.1 penguin
> >> 192.168.1.2 daddys
> >> 192.168.1.3 mommys
> >> 192.168.1.1 penguin.bogusdomain.bogus
> >> 192.168.1.2 daddys.bogusdomain.bogus
> >> 192.168.1.3 mommys.bogusdomain.bogus
Not necessary as all computers on the same network, but if you have to,
then only use the NETBIOS names certainly not FQDN's. But still this
won't be the cause of your problem because a) it has worked before and
b) computers on the same network (in your case 192.168.1.0) use
broadcasts for NETBIOS /SMB services.
> >> # workgroup = NT-Domain-Name or Workgroup-Name
> >> workgroup = HOUSEHOLD
OK.
> >> # server string is the equivalent of the NT Description field
> >> server string = Samba Jan 14 16:30
> >> # Cause this host to announce itself to local subnets here
> >> remote announce = 192.168.1.255
This is the broadcast I was writing about above.
> >> Test 3. 'smbclient -L penguin' -- Gives the following results:
> >> #------------- Cut Here ----------------------------------------
> >> Added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0
> >> Server time is Sun Jan 31 17:48:48 1999
> >> Timezone is UTC-8.0
> >> Domain=[HOUSEHOLD] OS=[Unix] Server=[Samba 1.9.18p10]
> >> security=share
> >> Server=[PENGUIN] User=[root] Workgroup=[HOUSEHOLD] Domain=[HOUSEHOLD]
> >> Sharename Type Comment
> >> --------- ---- -------
> >> IPC$ IPC IPC Service (Samba Jan 14 16:30)
> >> root Disk Home Directories
> >> tmp Disk Temporary file space
> >> This machine has a browse list:
> >> Server Comment
> >> --------- -------
> >> DADDYS Daddy's Dell XPS233
> >> PENGUIN Samba Jan 14 16:30
> >> This machine has a workgroup list:
> >> Workgroup Master
> >> --------- -------
> >> HOUSEHOLD DADDYS
> >> #------------- Cut Here ----------------------------------------
> >> This all seems great.
Yep, is fine!
> The Dell XPS233 comment had to have come across
> the
> >> net. (Mommy's computer was off when these diagnostics were run.) The
> >> 'HOUSEHOLD" workgroup is correct, and is set on all three computers.
> >> Test 4. 'nmblookup -B penguin __SAMBA__' -- gives good results:
> >> #------------- Cut Here ----------------------------------------
> >> Sending queries to 192.168.1.1
> >> 192.168.1.1 __SAMBA__<00>
> >> #------------- Cut Here ----------------------------------------
> >> Test 5. 'nmblookup -B daddys' -- Also seems good:
> >> #------------- Cut Here ----------------------------------------
> >> Sending queries to 192.168.1.2
> >> 192.168.1.2 *<00>
> >> #------------- Cut Here ----------------------------------------
> >> Test 6. 'nmblookup -d 2 '*' ' -- Still good...
> >> #------------- Cut Here ----------------------------------------
> >> Added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0
> >> Sending queries to 192.168.1.255
> >> Got a positive name query response from 192.168.1.2 ( 192.168.1.2 )
> >> Got a positive name query response from 192.168.1.1 ( 192.168.1.1 )
> >> 192.168.1.2 *<00>
> >> 192.168.1.1 *<00>
> >> #------------- Cut Here ----------------------------------------
> >> Test 7. 'smbclient \\\\penguin\\tmp' -- No problems yet.
> >> #------------- Cut Here ----------------------------------------
> >> Added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0
> >> Server time is Sun Jan 31 17:59:35 1999
> >> Timezone is UTC-8.0
> >> Domain=[HOUSEHOLD] OS=[Unix] Server=[Samba 1.9.18p10]
> >> security=share
> >> smb: \>
> >> #------------- Cut Here ----------------------------------------
> >> That was the last test that worked. Test 8 failed, which I'll cover in
> a
> >> moment. First, I ran what I'll call Test 7.5 on the Win95 box:
> >> Test 7.5. 'net view' -- gives:
> >> #------------- Cut Here ----------------------------------------
> >> Servers available in workgroup HOUSEHOLD.
> >> Server name Remark
> >> -------------------------------------------------------------------------
> >> -----------------
> >> \\DADDYS Daddy's Dell XPS233
> >> \\PENGUIN Samba Jan 14 16:30
> >> The command was completed successfully.
> >> #------------- Cut Here ----------------------------------------
> >> Again, the "Samba Jan 14 16:30" came across the net from my smb.conf
> file.
> >> Now test 8:
Since ping works and ftp and telnet don't work either, it looks like
only small bits of information pass through the LAN unscathed. Only when
larger amounts of information have to pass things go fishy. Somehow I
suspect a hardware or transport level problem, maybe along the lines of
the speed I wrote about above. Try putting your cards at 10 mbps fixed
instead of autosensing. Check cables. Maybe you touched the cable
between the hub and your unix when changing the NIC in the windows
machine.
Marc
------------------------------
From: Zot O'Connor <[EMAIL PROTECTED]>
Subject: Re: Intel EtherExpress 10/100B ISA need help
Date: Sat, 06 Feb 1999 23:16:20 -0800
I believe there is no support for the 100B (ISA) cards.
If this is not true, cool I have a stack of them.
I think Donald Becker (author of the 100/PCI driver) felt that it was a
hassle and why do you want to attempt to run 100 Mhz on an 12 Mhz ISA
slot.
I'd be happy to get 10Mhz working on them, they are free to me (since
they are just sitting here).
Hope to be proved wrong!
"Felix A. Hernandez" wrote:
>
> I have Linux Redhat 5.1 and I can not get my Intel EtherExpress 10/100B ISA
> to work. If I type:
>
--
Zot O'Connor
www.ZotConsulting.com
www.WhiteKnightHackers.com
------------------------------
From: Ed Jones <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Network Setup Problems
Date: Sun, 07 Feb 1999 06:35:56 +0000
Jay Bonk wrote:
> Everything seemed to be working correctly except the Network.
>
> During the Install I selected the 3c509 (My NIC is the 509B -- but the 3COM
> Manual specifies the same settings)
>
Yes, the 3C509B ISA Card is listed in the Hardware-HOWTO with the
3c509.. so this should be o.k. Issue the command "lsmod" and you should
see 3c509 listed as one of the modules. I use this card myself.
Jay sounds like something is foul here.
1. Issue the "ifconfig" command and verify that eth0 is listed with you
ip.
2. Check /etc/hosts to verify that it contains this line:
127.0.0.1 localhost localhost.localdomain
3. Check /etc/sysconfig/network and verify that is looks something like
this:
NETWORKING=yes
FORWARD_IPV4="yes"
HOSTNAME=your.host.name
GATEWAY="xxx.xxx.xxx.xxx"
GATEWAYDEV="eth0"
where xxx.xxx.xxx.xxx is your gateway machine.
4. Check /etc/resolv.conf and verify that it looks something like this:
search your.domain
nameserver xxx.xxx.xxx.xxx
nameserver yyy.yyy.yyy.yyy
Here your domain would be something like network.com and the xxx, yyy
ips are you dns servers.
5. Issue the command "netstat -nr" you should see your routing. There
are two critical lines in here
one: 127.0.0.0 0.0.0.0 255.0.0.0 U etc.
two: 0.0.0.0 xxx.xxx.xxx.xxx 0.0.0.0 UG etc.
where xxx.xxx.xxx.xxx is your gateway's IP
I believe if this checks your you are in business. If the "eth0" device
does not show up in the ifconfig command, there is a problem with the
kernel recognizing your ethernet card, which would be weird for a
3c509B. But it can happen if there is an IRQ conflict (maybe you have
an internal modem or another network card on board?)
If the card is recognized as eth0, then its just a matter of getting the
above files in place. Also, when you installed RedHat, did you select
the "custom," "host" or "workstation" install? If you selected
"workstation" the networking may not be turned on. I've only installed
the other two versions.
good luck
p.s. Compared to the NT servers you should see a nice speed improvement
with your linux box and the network. I do ;-)
------------------------------
From: Ed Jones <[EMAIL PROTECTED]>
Subject: Re: FTPd, TELNETd Problems
Date: Sun, 07 Feb 1999 06:48:08 +0000
mike wrote:
>
> I'm trying to telnet and ftp into my machine. It is not being used as a
> server except for the need to telnet or ftp into occasionally from
> work. Now, I don't understand what files are involved, so if I can get
> a list of those, and what commands, at command prompt, not X programs,
> are necessary to set these options up, I would appreciate it.
>
> Otherwise my networking works quite well.
>
> Thanks
>
> Mike
MIke since I don't know which linux version you are working with, I'm
not sure this will help. And you may have already done this, but what
I'd suggest is:
1. Check the file /etc/inetd.conf and ensure that the in.ftpd and
in.telnetd lines are uncommented.
2. Issue the command "ps -ax" to see which daemons are running. Look
for "inetd". If you don't see it then you need to start it at boot..
that's the daemon that runs the various network services, including ftp
and telnet.
3. If your machine is on a public network (internet for example), watch
your machines security (read security-HOWTO). In particular, I'd
suggest that, in addition to the usual password security, you modify
these files:
a. the file /etc/hosts.deny contain the line ALL: ALL
b. the file /etc/hosts.allow contain lines like:
in.ftpd: xxx.xxx.xxx.xxx
in.telnetd: xxx.xxx.xxx.xxx
where xxx.xxx.xxx.xxx are the ip's of the machine you want to have
telnet/ftp access to your machine. Of course if you have multiple
machines they can each be listed, or if you want a subnet to have
access, you can change those lines to something like
in.ftpd: xxx.xxx.xxx.0/24 or in.ftpd: xxx.xxx.0.0/16
depending upon what type of subnet you are talking about. With this
arrangement, only designated machines would have telnet and ftp access
to your box.. of course if you want anonymous ftp access then use
something like:
in.ftpd: ALL
Good luck
------------------------------
From: "Nick Short" <[EMAIL PROTECTED]>
Subject: Re: one ip address
Date: Sun, 07 Feb 1999 07:07:08 GMT
V2hhdCB5b3UnbGwgbmVlZCB0byBjb25jZW50cmF0ZSBvbiBpcyB0aGUgZmFjdCB0aGF0IHlvdSds
bCBuZWVkIHR3byBuZXR3b3Jrcy4gT25lIG5ldHdvcmsgdG8gc3VwcG9ydCB0aGUgc3RhdGljIElQ
IGFkZHJlc3MgZm9yIHlvdXIgaW50ZXJuZXQgY29ubmVjdGlvbiBhbmQgYW5vdGhlciBuZXR3b3Jr
IHRvIGhhbmRsZSB5b3VyICJsb2NhbCIgbWFjaGluZXMuICBUaGUgbWFjaGluZSB0aGF0IHlvdSB1
c2UgZm9yIHRoZSBzdGF0aWMgSVAgd2lsbCBuZWVkIHR3byBOSUMncyAodW5sZXNzIHdlIHdhbnQg
dG8gZ2V0IGludm9sdmVkIGluICJ2aXJ0dWFsIiBzdHVmZiwgd2hpY2ggSSBkb24ndCBhbmQgSSdt
IG5vdCBzdXJlIExpbnV4IGV2ZW4gc3VwcG9ydHMgdGhlIGNvbmNlcHQgdW5saWtlIFNvbGFyaXMp
LiBTdWZmaWNlIGl0IHNheSwgdHdvIHBoeXNpY2FsIG5ldHdvcmsgY2FyZHMgd2l0aCB0d28gcGh5
c2ljYWwgbmV0d29ya3MgaXMgbXVjaCBzYW5lciB0byBzZXQgdXAgYW5kIHVuZGVyc3RhbmQuDQoN
ClRoZSBIT1dUTydzIG91dCB0aGVyZSB3aWxsIGhlbHAgeW91IGFsb25nLCBtb3N0IHRvZGF5IGFy
ZSB3cml0dGVuIGluIHVuZGVyc3RhbmRhYmxlIHRlcm1zIGFuZCBwcm92aWRlIHBsZW50eSBvZiBl
eGFtcGxlcyB1bmxpa2UgdGhvc2Ugd3JpdHRlbiBhIG51bWJlciBvZiB5ZWFycyBhZ28gYnkgcGVv
cGxlIHdobyBqdXN0IGFzc3VtZWQgdGhhdCB0aGUgcGVvcGxlIHJlYWRpbmcgaXQga25ldyB0aGUg
b3RoZXIgMy80J3Mgb2YgdGhlIHRleHQgdGhleSBkaWRuJ3QgYm90aGVyIHRvIHdyaXRlLg0KDQpJ
IGNvdWxkIHdyaXRlIGEgYm9vayBoZXJlIGFuZCBnaXZlIHlvdSBzdGVwIGJ5IHN0ZXBzIGJ1dCB0
aGUgZmFjdCBvZiB0aGUgbWF0dGVyIGlzLCAqeW91KiByZWFsbHkgc2hvdWxkIGtub3cgdGhlIHN0
ZXBzIGFuZCB1bmRlcnN0YW5kIHdoYXQgeW91J3JlIGRvaW5nLiBJdCBpcyBhIGJpdCBvZiBhIGxl
YXJuaW5nIGN1cnZlIGJ1dCBub3RoaW5nIGZvciBzb21lb25lIHdobyBldmVuIGJvdGhlcnMgdG8g
c2V0IHVwIGEgTGludXggYm94Lg0KDQpNYWF0IHdyb3RlIGluIG1lc3NhZ2UgPDM2QkM5RTI3LkJB
Rjc0MUY2QGNoZXcuZGVtb24ubmw+Li4uDQo+aGVsbG8sDQo+DQo+SSBoYXZlIG15IG93biAobGl0
dGxlKSBuZXR3b3JrIGF0IGhvbWUsIGEgZnRwIHNlcnZlciBhbmQgYSB3ZWJzZXJ2ZXIgYnV0DQo+
SSBoYXZlIG9yZGluYXJ5IGludGVybmV0IGFjY291bnQgYW5kIG9ubHkgb25lIChzdGF0aWMpIGlw
IGFkZHJlc3MuIEJ1dA0KPmlmIEkgd2FudCB0byBjb25uZWN0IGJvdGggbWFjaGluZXMgY29ubmVj
dGVkIHRvIHRoZSBpbnRlcm5ldCB0aGV5IG11c3QNCj5oYXZlIGRpZmZlcmVudCBpcCBhZGRyZXNz
ZXMgYmVjYXVzZSB0aGV5IGhhdmUgZGlmZmVyZW50IGhvc3RuYW1lcy4gQ2FuIEkNCj5oYXZlIHR3
byBpcCBhZGRyZXNzZXMgb24gb25lIGxpbmUgYW5kIGhvdz8gQW5kIGlmIG5vdCwgaXMgdGhlcmUg
YW5vdGhlcg0KPnNvbHV0aW9uPw0KPg0KPlRoYW5rcyENCj4NCj5jaGVlcnMsDQo+DQo+Sm9oYW5u
ZXMsIGh0dHA6Ly93d3cuY2hldy5kZW1vbi5ubA0KPg0K
------------------------------
From: Vladimir Peric <[EMAIL PROTECTED]>
Subject: Flags in if.h
Date: Mon, 01 Feb 1999 11:05:22 +0100
Reply-To: [EMAIL PROTECTED]
Inlude file linux/if.h
/* Standard interface flags. */
#define IFF_UP 0x1 /* interface is up
*/
#define IFF_BROADCAST 0x2 /* broadcast address valid
*/
#define IFF_DEBUG 0x4 /* turn on debugging
*/
#define IFF_LOOPBACK 0x8 /* is a loopback net
*/
#define IFF_POINTOPOINT 0x10 /* interface is has p-p link
*/
#define IFF_NOTRAILERS 0x20 /* avoid use of trailers
*/
#define IFF_RUNNING 0x40 /* resources allocated
*/
#define IFF_NOARP 0x80 /* no ARP protocol
*/
#define IFF_PROMISC 0x100 /* receive all packets
*/
/* Not supported */
#define IFF_ALLMULTI 0x200 /* receive all multicast
packets*/
#define IFF_MASTER 0x400 /* master of a load balancer
*/
#define IFF_SLAVE 0x800 /* slave of a load balancer
*/
#define IFF_MULTICAST 0x1000 /* Supports multicast
*/
What flag or flags combination are condition to determine NIC (ethX
device) ?
Thanks.
--
Vladimir Peric, B.Sc.E.E mailto:[EMAIL PROTECTED]
Resume: http://pentix.imp.bg.ac.yu/vperic/rezime.html
Institute "Mihajlo Pupin" - Belgrade, Yugoslavia
Address: Volgina 15, 11050 Belgrade
------------------------------
From: [EMAIL PROTECTED] (jamie)
Subject: Re: IP masquerading
Reply-To: [EMAIL PROTECTED]
Date: Sun, 07 Feb 1999 00:20:16 -0600
Nightmare <[EMAIL PROTECTED]> wrote:
>
>ipfwadm -F -p deny
>ipfwadm -F -a m -S 192.168.2.2/22 -D 0.0.0.0/0
Perhaps it's me that's confused, as I'm just getting up to
speed on subnet nomenclature and ipfwadm, but it appears
as though you put in the gateway IP instead of the network
address.
--
jamie ([EMAIL PROTECTED])
"There's a seeker born every minute."
------------------------------
From: [EMAIL PROTECTED] (jamie)
Subject: Re: Help: RoadRunner Akron and Linux
Reply-To: [EMAIL PROTECTED]
Date: Sun, 07 Feb 1999 00:08:34 -0600
Ram Rajadhyaksha <[EMAIL PROTECTED]> wrote:
>Hi all, we have a Linux box which we're using with RoadRunner in the
>Akron, OH area. We are currently using rrlogind 1.3 on a RedHat 5.2 box
>to authenticate to the login server.
>
>Everything seems to work ok after we login...until the next day. I'm
>guessing that the authentication server logs us off after x amount of
>time and we need to re-authenticate.
I didn't have any luck with rrlogind on Austin RR. I'm using the rrlogin
perl script, with a cron job to call the rrlogin script every hour
(I think here timeout is set to about 90 minutes)
--
jamie ([EMAIL PROTECTED])
"There's a seeker born every minute."
------------------------------
From: [EMAIL PROTECTED] (Luca Filipozzi)
Subject: Re: Any Help for my network !
Date: Sat, 6 Feb 1999 23:45:09 -0800
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] says...
> Hi there :)
>
> I have a small network at home ( 7 computers) , I'm running
> Linux (RedHat 5.2 kernel = 2.0.36) as server with two network-adapter
> one connecting to my cable modem and the other one to a hub .
> the 6 other computers are running windoze and have also there
> network-adapter. They are connected to a hub as well.
> i'm using ip-masq ....everything is working fine i can get to the
> internet from
> any computer .....no problem , but i was wondering how can i contacte
> any
> of the 6 computers that's run windoze from outside
>
> here is some information about my local IP
>
> My Linux server IP (eth0 at dhcp, eth1 at 192.168.10.1)
>
> windoze 1 at 192.168.10.2
> windoze 2 at 192.168.10.3
> ;
> ;
> ;
> windoze 6 at 192.168.10.7
>
>
> Any help ? ..e-mail me : [EMAIL PROTECTED]
>
>
> Thanks :)
>
>
It depends on what you want to do.
You CAN NOT ping those machines directly, since they are hidden by the
masquerading firewall.
You CAN set up the masquerading firewall to "port forward" packets
received on certain ports to certain machines. So, say you you have a
mail server running on one of the windoze boxes, then you could port
forward smtp and pop packets to that windoze box. You can do the same
thing with a proxy server.
In other words, you select which types of connections to permit to a
given box inside your network. But that's a far cry from having full
access to the machine.
--
Luca Filipozzi <[EMAIL PROTECTED]>
------------------------------
From: [EMAIL PROTECTED]
Subject: backorfice client
Date: Sun, 07 Feb 1999 01:24:26 GMT
I see a backorfice-unix-client rpm on RedHat mirror sites -- what does it
do?
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: "Sean Connolly" <[EMAIL PROTECTED]>
Subject: Re: newbie: ping ok --no telnet ftp
Date: Sun, 7 Feb 1999 02:56:02 -0500
Check your hosts.deny and hosts.allow in your /etc directory. Make sure
there's nothing there intefering.
As for SAMBA, I've never had good luck with it, so I just run everything
TCP/IP straight up. I like it better that way anyway. :-)
Sean
>I am running Red Hat 5.1 in a small home lan with some windows machines (98
&
>NT4). TCP/IP seems to be working fine, since I can ping all the way around,
>my problem is that in trying to telnet or FTP from a win machine to linux
my
>login is refused. After reading some other posts I tried to telnet to
>localhost, and had the same result. In all cases I tried logging in as both
>root, and another user, neither worked. Additionally (or probably because
>of) I can't get SAMBA to work right. the command smbclient -L larry will
>list the C drive as an available resource, but smbclient \\larry\c comes
>back with a menu- type list. I also am not seeing my linux box (curley) in
a
>network neighborhood window. Please Help!!! It' must be something simple,
>but I'm just not seeing it.
------------------------------
From: [EMAIL PROTECTED] (BrimStone)
Subject: Re: printing problem with Netatalk 1.42b
Date: 07 Feb 1999 00:11:05 PST
I already have the correct PPD on the client machines, is it necessary
to have it on the server too?
On 7 Feb 1999 00:12:39 GMT, [EMAIL PROTECTED] (Miguel Cruz)
wrote:
>BrimStone <[EMAIL PROTECTED]> wrote:
>> I'm running Netatalk 1.42b on RH 5.2 and am having a small problem
>> printing to my shared HP LaserJet IIID. I am able to print OK, but
>> everything prints oriented portrait even when you try to print in
>> landscape mode (on both MacOS 7.6.1 and OS 8). I have this same printer
>> shared to PC clients with Samba and they are able to print landscape with
>> no problems. Anyone have any ideas on what may be going on?
>
>Have you installed the correct PPD file on the server?
>
>miguel
------------------------------
** 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
******************************
