Linux-Networking Digest #943, Volume #11 Mon, 19 Jul 99 19:13:41 EDT
Contents:
Re: SQUID and multible In-Out-IPs ("Holger van Koll")
Re: How to connect dumb terminals via Lan and more? (Glenn)
Re: MARS-NWE paper waste. ([EMAIL PROTECTED])
VPN, IP TUNNEL, SSH Question. ([EMAIL PROTECTED])
pppd:Device can not be overridden (Manfred Plagmann)
Re: Periodic multicast traffic - why? ([EMAIL PROTECTED])
Re: Eicon DIVA under Linux? (Christophe Lambin)
Re: Samba causing broadcast storms?? ([EMAIL PROTECTED])
Re: Periodic multicast traffic - why? (Greg Leblanc)
Re: Periodic multicast traffic - why? ([EMAIL PROTECTED])
Re: TCP Error: No Route to Host (Joe Haberthier)
Re: DNS server problems! (Rob Calfee)
Re: Need "named" DNS daemon ("Joe Kattner")
----------------------------------------------------------------------------
From: "Holger van Koll" <[EMAIL PROTECTED]>
Subject: Re: SQUID and multible In-Out-IPs
Date: Mon, 19 Jul 1999 21:16:00 +0200
Dietrich von der Groeben schrieb in Nachricht <[EMAIL PROTECTED]>...
>Hi all,
>
>I have a big big problem with squid,
>is it possible to run squid in the following configuration:
>
> ____
>LAN1------| |
> | | Internet-IP for LAN1
> | |----------------------
> | | Internet-IP for LAN2
>LAN2------|____|
>
>
>So, if a request comes from LAN1 (customer1) squid uses the official
>IP-Adress for LAN1 and if the request comes from LAN2 (customer2) it
>uses the second official IP-Adress.
>A possible solution would be to run two different squid-daemons, but in
>this case they wouldn't use the same cache.
Why dont you make the first daemon the parent for the other?
Should solve all your problems...
------------------------------
Subject: Re: How to connect dumb terminals via Lan and more?
From: [EMAIL PROTECTED] (Glenn)
Date: Mon, 19 Jul 1999 20:25:18 GMT
In article <7melog$m7t$[EMAIL PROTECTED]>,
{$graham$}@microphoneDOT.prestel.co.uk says...
>
>On Mon, 12 Jul 1999 18:37:39 GMT, [EMAIL PROTECTED] (Glenn) wrote:
>
>>1. How does one physically connect and then cause a login prompt to be
>>generated on a dumb terminal via a Lan connection (Serial to Twisted
>>pair on a 10baseT hub)?
>
>You would need a tcp/ip terminal server, a hardware device that would likely
>cost more than the linux box and terminal combined.
>
>Or, you could just plug the terminal into a serial port on the linux box...
>
>
Thank you Graham for the reply. However, I eventually want to hook up 5-10
terminals so perhaps I'll have to get a multiport serial card/connection setup
after all. I was hoping to just be able to do this through the hub.
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: MARS-NWE paper waste.
Date: Mon, 19 Jul 1999 21:02:51 GMT
It sounds to me like some of your Novell clients may have Form Feed
enabled - a lot of the Client32 versions have this enabled by default.
Go to the Default Capture tab of the Novell Client and uncheck Form
Feed.
Hope this helps,
Bobby
In article <7ml7ri$mt2$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> I have mars-nwe-0.99pl10 running under RH5.2 on a 486DX2/66. I am
using
> it exclusively as a print server for a HP LaserJet 4. Everything
prints
> fine and all is well EXCEPT it wastes a ton of paper. Whenever a user
> prints out of a Win95 DOS screen or app., or when certain users print
> anything from Win95, a blank page, and sometimes two, follow the print
> job. However, from another workstation (Win95 and LINUX), all prints
> fine (except DOS). I have tried disabling "Send EOF" in the print
> filter set up using printtool on the Linux box running Mars, but every
> time I go back, it's enabled again. Anybody have any clues how to
stop
> the senseless murder of trees? I've looked through the mars docs and
> the printing docs I could find, but to no avail.
>
> If this is the wrong forum for this question, please forgive me.
>
> TIA.
>
> Mark
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
>
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: [EMAIL PROTECTED]
Subject: VPN, IP TUNNEL, SSH Question.
Date: Mon, 19 Jul 1999 20:54:06 GMT
Well after perusing the HOWTO's, it's time to ask for some expert
advice.
I have a small lan connected through ADSL and a linux box. (Redhat 6, IP
Masq, IP chains for firewall). I can easily connect from work to home
using SSH which is great to pickup files I need from home.
Here's what I REALLY want to do.
I would like to SSH from home (either from the firewall box or another
linux box on the lan) and get into my linux box here at work. (I am
writing code that works on specific hardware that is inconvienient to
bring home and it would be nice if I could work from home.)
There are some problems with this, though. I work for a large
corporation and do not have access to the firewall. Now, it lets me SSH
out to my home linux box, but I can't SSH back in. Plus, the IP address
for my work box is for our intranet only.
Here's what I would like to do.
1. Run some command that would cause my work machine to connect to my
local machine in say 20 minutes (the time it takes me to get home).
2. When I get home be able to compile and edit files that are in my
work computer (linux).
3. End the connection from home.
Now, I have looked at VPN, but am not sure if this is overkill for what
I want to do. I'm looking for an easy but very secure solution as I do
have both my and my employer's LANs to secure.
Simple answers like...use VPN, but with IPsec and setup a cron job to
connect...are fine.
Thanks for you help in advance.
Sven
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: Manfred Plagmann <[EMAIL PROTECTED]>
Subject: pppd:Device can not be overridden
Date: Tue, 20 Jul 1999 18:05:20 +1200
Hi,
I have set up my ppp ISP connection and all works fine -- being root.
I'll get the error message pppd[]:Device can not be overridden when I
try to connect as a normal user. pppd is set to suid and the scripts are
readable and executable by all.
Any ideas?
Thanks
Manfred
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Periodic multicast traffic - why?
Date: Mon, 19 Jul 1999 20:38:35 GMT
In article <ZlKk3.9$[EMAIL PROTECTED]>,
"Cliff" <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] wrote in message
<7mvgup$vej$[EMAIL PROTECTED]>...
> >Good day!
> >
> >My ipchains-based firewall is receiving a multicast packet
> >every 10 minutes or so (it varies) which I'm currently
> >rejecting. I'm a TCI@Home cable modem user and the address
> >of the incoming packet looks like it's either an @Home machine
> >or another @Home users' machine.
> >
> >The packet log looks like this:
> >
> >Jul 19 08:25:06 <hostname> kernel: Packet log: input REJECT eth0
> >PROTO=24.7.204.1:9 224.0.0.1:0 L=68 S=0x00 I=47382 F=0x0000 T=255
(#19)
> >
> [snip]
>
> A Windows 98 system will broadcast to that IP upon boot up. I
never
> could figure out what M$ was up to with that. There doesn't seem to
be any
> way to keep the Windoze machine from doing it either. I don't think
it will
> cause any harm, at least it hasn't on my LAN yet, but you probably
want to
> block it just in case.
Would a Windows 98 system respond to the packet I'm seeing? If I
read the packet log correctly (unlikely) it's coming from the 24.7.x.x
domain on port 9, asking for a reply to 124.0.0.1 port 0. I can't
imagine why having my machine respond on that port would be a good
thing unless @Home is looking for non-Windows boxes that aren't
configured correctly. If a Windows 98 machine responds, maybe my
firewall should be responding in a similar manner...
Any thoughts?
Regards,
- Leo Butler
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: Christophe Lambin <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Re: Eicon DIVA under Linux?
Date: Mon, 19 Jul 1999 22:49:25 +0200
> can u pls explain how it worked for u??
To get the 2.01 PCI to work, you need isdn4linux kernel code, dated 1
July 1999 or later. The 2.01 has a different interface than the 2.0, for
which support was added only recently in isdn4linux.
ftp://ftp.suse.com/pub/isdn4linux/
Regards,
Christophe
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Samba causing broadcast storms??
Date: Mon, 19 Jul 1999 21:06:50 GMT
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Vidar Andresen) wrote:
> In article <7mngec$h4l$[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote:
> >Hi all,
> >
> >I am running COL 2.2 on a switched lan as a test box. The lan is used
>
> COL 2.2 ?
>
Sorry, COL 2.2 = Caldera Open Linux 2.2
Thanks for the pointers, I will do some digging and post the results!
Tony
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: Greg Leblanc <[EMAIL PROTECTED]>
Subject: Re: Periodic multicast traffic - why?
Date: Mon, 19 Jul 1999 20:47:37 GMT
Is this a multicast packet, or a broadcast packet? We have some cisco
2500 routers on our network, and I can see the broad cast packets that
they send on our firewall logs, but I tend to just ignore them since
they aren't something that should be going through. If it IS a
broadcast (from a router or otherwise), there isn't any reason I can
think of to let it through, although somebody else might know more. If
it's a multicast packet, and it's destined for a machine on your network
it should probably be getting through. You might do a packet capture,
and look at the multicast header of the packet to see where it's
addressed (if you're REALLY adventureous).
Greg
In article <7mvgup$vej$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> Good day!
>
> My ipchains-based firewall is receiving a multicast packet
> every 10 minutes or so (it varies) which I'm currently
> rejecting. I'm a TCI@Home cable modem user and the address
> of the incoming packet looks like it's either an @Home machine
> or another @Home users' machine.
>
> The packet log looks like this:
>
> Jul 19 08:25:06 <hostname> kernel: Packet log: input REJECT eth0
> PROTO=24.7.204.1:9 224.0.0.1:0 L=68 S=0x00 I=47382 F=0x0000 T=255
(#19)
>
> The reason I'm pretty sure the originating machine is part of
> or at least inside @Home is the 24.7.x.x address; @Home users
> and servers seem to be on 24.1.x.x thru 24.7.x.x from what I've
> seen so far of other @Home users IP addresses. But I can't get
> any information out of nslookup, it says it's a non-existent
> host/domain.
>
> Can anyone tell me if I should be allowing these packets, and if
> I do, what I should be doing with them? And more importantly,
> does anyone know why @Home might send out multicast packets so
> regularly? I don't know how on earth my Windows machine where
> the modem was originally configured could do anything with these
> packets.
>
> Thanks,
>
> - Leo Butler
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
>
--
It's pronounced "sexy" not "scuzzy"!
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Periodic multicast traffic - why?
Date: Mon, 19 Jul 1999 21:35:49 GMT
In article <7n02t4$7kg$[EMAIL PROTECTED]>,
Greg Leblanc <[EMAIL PROTECTED]> wrote:
> Is this a multicast packet, or a broadcast packet? We have some cisco
> 2500 routers on our network, and I can see the broad cast packets that
> they send on our firewall logs, but I tend to just ignore them since
> they aren't something that should be going through. If it IS a
> broadcast (from a router or otherwise), there isn't any reason I can
> think of to let it through, although somebody else might know more.
If
> it's a multicast packet, and it's destined for a machine on your
network
> it should probably be getting through. You might do a packet capture,
> and look at the multicast header of the packet to see where it's
> addressed (if you're REALLY adventureous).
Good point, I should be careful with my descriptions! I think it
is a broadcast packet, so I'm not particularly worried about it.
But I wonder why @Home (or anyone else) would broadcast the packet
and give it a destination of port 9 -- no services there that I
know of. What would my Windows 95/98 box do if it received this
packet -- could it respond? Is @Home looking for poorly configured
non-Windows boxes on their subnets? I really want to understand
this packet more than anything else; everything is running just
fine on the firewall and behind it. As far as I know, anyway.
(knock wood)
Regards,
- Leo Butler
> In article <7mvgup$vej$[EMAIL PROTECTED]>,
> [EMAIL PROTECTED] wrote:
> > Good day!
> >
> > My ipchains-based firewall is receiving a multicast packet
> > every 10 minutes or so (it varies) which I'm currently
> > rejecting. I'm a TCI@Home cable modem user and the address
> > of the incoming packet looks like it's either an @Home machine
> > or another @Home users' machine.
> >
> > The packet log looks like this:
> >
> > Jul 19 08:25:06 <hostname> kernel: Packet log: input REJECT eth0
> > PROTO=24.7.204.1:9 224.0.0.1:0 L=68 S=0x00 I=47382 F=0x0000 T=255
> (#19)
> >
> > The reason I'm pretty sure the originating machine is part of
> > or at least inside @Home is the 24.7.x.x address; @Home users
> > and servers seem to be on 24.1.x.x thru 24.7.x.x from what I've
> > seen so far of other @Home users IP addresses. But I can't get
> > any information out of nslookup, it says it's a non-existent
> > host/domain.
> >
> > Can anyone tell me if I should be allowing these packets, and if
> > I do, what I should be doing with them? And more importantly,
> > does anyone know why @Home might send out multicast packets so
> > regularly? I don't know how on earth my Windows machine where
> > the modem was originally configured could do anything with these
> > packets.
> >
> > Thanks,
> >
> > - Leo Butler
> >
> > Sent via Deja.com http://www.deja.com/
> > Share what you know. Learn what you don't.
> >
>
> --
> It's pronounced "sexy" not "scuzzy"!
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
>
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: [EMAIL PROTECTED] (Joe Haberthier)
Subject: Re: TCP Error: No Route to Host
Date: Mon, 19 Jul 1999 22:00:16 GMT
I got it working, thanks so much.
I knew it was a routing problem.
On Sun, 18 Jul 1999 21:09:55 -0700, Allen Wong <[EMAIL PROTECTED]>
wrote:
>Joe,
>
> I think this is because you have two default gateways.
>
>default 166.102.100.1 0.0.0.0 UG
>ppp0
>default 192.168.1.254 0.0.0.0 UG
>eth0
>
>Try issuing the command:
>
>/sbin/route del default gw 192.168.1.254
>
>and, hopefully, the problem will go away. However, you may have to add
>192.168.1.254 back to the routing table as the default gateway when
>you're finished with PPP. Keeping my fingers crossed.
>
>Allen
>--
>Linux: If you're not careful, you might actually learn something.
------------------------------
From: [EMAIL PROTECTED] (Rob Calfee)
Subject: Re: DNS server problems!
Date: Mon, 19 Jul 1999 21:09:37 GMT
Okay,
We got the nameserver up. Changing the name.conf file corrected the
problem, thanks. The other problem we have is that the actual web
address (www.medsort.com) is not finding our name server. What files
do we have to configure to get the server to recognize the domain name
from internic when the above website is hit? Thanks.
Rob Calfee
On Mon, 19 Jul 1999 11:30:56 -0700, "Andrey Smirnov"
<[EMAIL PROTECTED]> wrote:
>Hello,
>
>I'm not sure what version of named you are running, but you may need to edit
>/etc/named.conf file. Read man named.
>
>Good luck
>
>PS. One more thing, in your zone file you have a record for your domain
>@ IN A 207.199.219.3
>
>and also you have another A record pointed to the same address
>
>ns IN A 207.199.219.3
>
>If you want to use the same machine as your ns1 host, the above record needs
>to be changed to:
>
>ns CNAME webdsp.net.
>
>
>You can only have one A record for IP address, and you need to use aliases
>in order to refer to your machine using number of names (www, ftp, news,
>etc.)
>
>
>Rob Calfee wrote in message <[EMAIL PROTECTED]>...
>>Hi all,
>>
>>My friend is having problems setting up his DNS name server. Below
>>are all the files. The first is the actual error from nslookup.
>>Could someone with more knowlegde of the subject look at these files
>>and try find any errors that may be present. He is trying to setup a
>>prmary nameserver for the Internet. I know he'd appreciate, him being
>>my boss and all. Thanks in advance.
>>
>>Rob Calfee
>>Oracle DBA
>>[EMAIL PROTECTED] (or the at the sig below)
>>
>>
>>
>>
>>IP of Server - 207.199.219.3
>>name of server - ns1.webdsp.net
>>
>>
>>
>>Error being given by nslookup
>>[root@NS1 named]# nslookup
>>*** Can't find server name for address 207.199.219.3: Server failed
>>*** Default servers are not available
>>
>>_____________________________________________________________________
>>;NAMED.BOOT
>>;
>>; a caching only nameserver config
>>;
>>directory /var/named
>>cache . named.ca
>>primary webdsp.com named.hosts
>>primary 219.199.207.in-addr.arpa named.rev
>>______________________________________________________
>>;NAMED.HOSTS
>>;named.hosts file for webdsp.com
>>;
>>@ IN SOA ns1.webdsp.net. jhonken.webdsp.net. (
>>99071901 ; serial number
>>86400 ;refresh 24 hrs
>>300 ; retry 5 minutes
>>2592000 ; expire 30 days
>>86400 ; minium 24 hrs
>>)
>>IN NS ns1.webdsp.net.
>>;
>>; The domain itself
>>;
>>@ IN A 207.199.219.3
>>IN MX 100 mailhost.webdsp.net
>>IN HINFO PC-586 Linux
>>;
>>; The primary Nameserver
>>;
>>ns IN A 207.199.219.3
>>nameserver IN CNAME ns1.webdsp.net.
>>;
>>; Other Hosts
>>;
>>localhost IN A 127.0.0.1
>>
>>_________________________________________________________
>>NAMED.LOCAl
>>@ IN SOA localhost. root.localhost. (
>> 1997022700 ; Serial
>> 28800 ; Refresh
>> 14400 ; Retry
>> 3600000 ; Expire
>> 86400 ) ; Minimum
>> IN NS localhost.
>>
>>1 IN PTR localhost.
>>
>>__________________________________________________________
>>;NAMED.REV
>>;named.rev file for webdsp.com
>>;
>>@ IN SOA ns1.webdsp.net. jhonken.webdsp.net. (
>>99071902 ; serial number
>>86400 ; refresh 24 hrs
>>300 ; retry 5 minutes
>>2592000 ; expire 30 days
>>86400 ; minium 24 hrs
>>)
>>IN NS ns1.webdsp.net.
>>;
>>; Reverse map the IP addresses
>>;
>>3 IN PTR ns1.webdsp.net.
>>___________________________________________________________
>>;NAMED.CA
>>; This file holds the information on root name servers needed to
>>; initialize cache of Internet domain name servers
>>; (e.g. reference this file in the "cache . <file>"
>>; configuration file of BIND domain name servers).
>>;
>>; This file is made available by InterNIC registration services
>>; under anonymous FTP as
>>; file /domain/named.root
>>; on server FTP.RS.INTERNIC.NET
>>; -OR- under Gopher at RS.INTERNIC.NET
>>; under menu InterNIC Registration Services (NSI)
>>; submenu InterNIC Registration Archives
>>; file named.root
>>;
>>; last update: Aug 22, 1997
>>; related version of root zone: 1997082200
>>;
>>;
>>; formerly NS.INTERNIC.NET
>>;
>>. 3600000 IN NS A.ROOT-SERVERS.NET.
>>A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4
>>;
>>; formerly NS1.ISI.EDU
>>;
>>. 3600000 NS B.ROOT-SERVERS.NET.
>>B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107
>>;
>>; formerly C.PSI.NET
>>;
>>. 3600000 NS C.ROOT-SERVERS.NET.
>>C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12
>>;
>>; formerly TERP.UMD.EDU
>>;
>>. 3600000 NS D.ROOT-SERVERS.NET.
>>D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90
>>;
>>; formerly NS.NASA.GOV
>>;
>>. 3600000 NS E.ROOT-SERVERS.NET.
>>E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10
>>;
>>; formerly NS.ISC.ORG
>>;
>>. 3600000 NS F.ROOT-SERVERS.NET.
>>F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241
>>;
>>; formerly NS.NIC.DDN.MIL
>>;
>>. 3600000 NS G.ROOT-SERVERS.NET.
>>G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4
>>;
>>; formerly AOS.ARL.ARMY.MIL
>>;
>>. 3600000 NS H.ROOT-SERVERS.NET.
>>H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53
>>;
>>; formerly NIC.NORDU.NET
>>;
>>. 3600000 NS I.ROOT-SERVERS.NET.
>>I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17
>>;
>>; temporarily housed at NSI (InterNIC)
>>;
>>. 3600000 NS J.ROOT-SERVERS.NET.
>>J.ROOT-SERVERS.NET. 3600000 A 198.41.0.10
>>;
>>; housed in LINX, operated by RIPE NCC
>>;
>>. 3600000 NS K.ROOT-SERVERS.NET.
>>K.ROOT-SERVERS.NET. 3600000 A 193.0.14.129
>>;
>>; temporarily housed at ISI (IANA)
>>;
>>. 3600000 NS L.ROOT-SERVERS.NET.
>>L.ROOT-SERVERS.NET. 3600000 A 198.32.64.12
>>;
>>; housed in Japan, operated by WIDE
>>;
>>. 3600000 NS M.ROOT-SERVERS.NET.
>>M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33
>>; End of File
>>
>>Rob Calfee
>>DBA
>>[EMAIL PROTECTED]
>>Rob Calfee
>>DBA
>>[EMAIL PROTECTED]
>
>
>
Rob Calfee
DBA
[EMAIL PROTECTED]
------------------------------
From: "Joe Kattner" <[EMAIL PROTECTED]>
Crossposted-To: linux.redhat.misc
Subject: Re: Need "named" DNS daemon
Date: Mon, 19 Jul 1999 18:45:25 -0400
You can download BIND DNS from:
www.isc.org
Steve Sorden wrote in message <[EMAIL PROTECTED]>...
>I'm setting up Samba on a home network using Redhat 6.0. I just realized
>that even though my Samba server shows up in the network neighborhood, I
>can't access it because I don't have a local DNS server. (I didn't
>select it when I installed Linux.)
>
>How can I install "named" and get it to run at boot?
>
>Thanks,
>Steve Sorden
>
------------------------------
** 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
******************************
