Linux-Networking Digest #564, Volume #11 Thu, 17 Jun 99 03:13:50 EDT
Contents:
Re: horde and IMP (Jonathan Guthrie)
Re: SNMP tools (Frederic Pont)
Re: Could Microsoft Cheat On The New Mindcraft Benchmark? (was: Mindcraft Retest
News (Paul D. Smith)
Re: new house wiring ([EMAIL PROTECTED])
ifconfig, route hate CIDR netmasks? ([EMAIL PROTECTED])
Re: Can't ping anything. (Stewart Honsberger)
Realtek NIC HELP??????? ("Kyle Hittle")
Re: Network (Atomic) Time (James Youngman)
USR ISA 28.8 ("joe")
Re: PPP Scripting... Help? ([EMAIL PROTECTED])
ipfwadm ("Stephan M. Ott // OKDesign oHG")
Re: diald still dials every time (Gilford Wimbley)
Re: PPP and looped back serial line (Spudly)
Re: Could Microsoft Cheat On The New Mindcraft Benchmark? (was: Mindcraft Retest
News (Paul D. Smith)
Re: Diald keeps dialing... (Gilford Wimbley)
Where can I get the 'linux-sna' code ? ("MinSoon Park")
Re: real newbie needs help on domain name registration
Re: cable modem or ASDL (Gilford Wimbley)
----------------------------------------------------------------------------
From: Jonathan Guthrie <[EMAIL PROTECTED]>
Subject: Re: horde and IMP
Date: 17 Jun 1999 04:58:12 GMT
Lee A. Perry <[EMAIL PROTECTED]> wrote:
> Anybody using IMP? I wanted to use Netscape Messaging server but they only
> like Solaris now? Are there any other web based email severs out there?
I use imp and I like it. You'll need a PHP3 capable Web server, but you
should be running one of those, anyway.
--
Jonathan Guthrie ([EMAIL PROTECTED])
Brokersys +281-895-8101 http://www.brokersys.com/
12703 Veterans Memorial #106, Houston, TX 77014, USA
------------------------------
From: Frederic Pont <[EMAIL PROTECTED]>
Subject: Re: SNMP tools
Date: Thu, 17 Jun 1999 04:17:40 GMT
this should be a good startpoint :
http://ucd-snmp.ucdavis.edu/
In article <[EMAIL PROTECTED]>,
"Witman Peng" <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> Is there any SNMP tools with source code out there? I plan to develop
a SNMP
> & RMON based network management tool. Any input would be appreciated.
> Thanks.
>
> BR,
> Witman Peng
>
>
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: [EMAIL PROTECTED] (Paul D. Smith)
Crossposted-To:
omp.os.ms-windows.nt.advocacy,comp.os.linux.advocacy,comp.infosystems.www.servers.unix,comp.os.linux.misc
Subject: Re: Could Microsoft Cheat On The New Mindcraft Benchmark? (was: Mindcraft
Retest News
Date: 17 Jun 1999 01:20:20 -0400
Reply-To: [EMAIL PROTECTED]
%% "Chad Mulligan" <[EMAIL PROTECTED]> writes:
cm> Paul D. Smith wrote in message ...
>> %% "Chad Mulligan" <[EMAIL PROTECTED]> writes:
>>
>> >> IE ? who cares. THe Solaris version is a POS.
cm> Couldn't be worse that Netscape.
>> Hah hah hah! You _obviously_ have never tried it. I have. Trust me,
>> no matter how bad you think Netscape is, IE for Solaris is much, much
>> worse.
cm> Correct, I was drawing a logical conclusion from my bad
cm> experiences with Netscape on every platform.
No logical conclusion can be drawn when extrapolating from a sample base
of 1 (the number of platforms you've used IE on).
>> IMO, Netscape on UNIX isn't too bad. It's big and kinda slow, and
>> until very recently would die on me much more than I expect from a
>> UNIX tool, but since I started using Navigator 4.08 it's been
>> pretty stable. (I tried 4.5 for a while, but the bookmark
>> drag-n-drop is busted so I went back to 4.08).
cm> I don't know about that, I've got a Dell OptiPlex 250 sitting next
cm> to a Sparc Ultra 10, and Netscape on the Ultra doesnt load as fast
cm> as IE on 98.
(a) That's the advantage of having the browser embedded in the OS ;)
(b) I didn't say anything about startup speed, or compare speeds at all:
in fact I said Netscape is "kinda slow". I said it "isn't too bad",
and "it's been pretty stable".
(c) Who cares about startup speed? I start the thing when I login, and
it just stays up for weeks until I logout again.
Oh yah, you're coming from a Windows environment, where startup
speed matters much more ;).
Actually, Netscape is more stable on my Win98 box than IE 4. Maybe I
have an old or buggy version of IE, but my wife brings down Win98, hard,
regularly while using IE (maybe that's the _disadvantage_ of having the
browser in the OS?).
--
===============================================================================
Paul D. Smith <[EMAIL PROTECTED]> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
===============================================================================
These are my opinions---Nortel Networks takes no responsibility for them.
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: new house wiring
Date: Thu, 17 Jun 1999 03:44:56 GMT
Well, ok, a little conduit here and there to future proof is a good
idea. But the house still needs to be wired in the first place. So
the hard part is making the right decisions, with today's understanding.
It is clear to me that one should try to do the job today to minimize
the likelihood that it will need to be re-done again anytime soon.
At the very least, 4-pair unshielded twisted pair cable should be
installed from a central point of administration to each RJ-45 style
jack in the walls. The hardware selected at the central point of
administration should allow any incoming phone line to be cross-
connected to any jack in the house. As an option, a handful of jacks
in the house can be cross-connected to a 10Base-T Ethernet hub to form
a LAN.
If there is a home office, I would put four jacks in the room, and
perhaps a few more on another wall, for flexibility in the placement of
furniture and equipment. Not every jack has to be live at any one time.
The scheme here follows a structured, standardized (TIA/EIA-568A)
approach that has been developed for commercial office space over the
past ten years.
75 Ohm coax is also an important part of a structured cabling solution
for a home.
Additional information can be found at
http://www.home-cabling.com/solution/shopping-guide_concise.html
Regards,
Bill Baxter
In article <7k3bv0$tgv$[EMAIL PROTECTED]>,
Frederick Haab <[EMAIL PROTECTED]> wrote:
> In article <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED] wrote:
>
> > another suggestion: think about where you might want access on each
> floor
> > and run PVC pipe at least between floors, and perhaps between
certain
> rooms.
> > Later, you can snake whatever you want easily....
>
> I just wanted to chime in and agree, here. Run conduit...whatever you
> run today will be old-hat in the future, so instead of having to
settle
> on one technology you just pull new wires whenever necessary.
>
> Cheers,
> Fred
>
> --
> ---
> - Frederick Haab - Turner Studios -
>
> 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: ifconfig, route hate CIDR netmasks?
Date: Thu, 17 Jun 1999 04:04:57 GMT
Roadrunner in the Northern Virginia area seems to be using CIDR IP
addressing. i.e., the netmask their DHCP server wants my Debian 2.1 box
to use is 25.255.252.0.
Feeding a netmask like this into both ifconfig and route causes them to
complain bitterly. I think this is also the reason why the DHCP clients
(dhcpcd and dhclient) that I've tried to use die silently and without a
trace except for their /var/run/*.pid files.
Strangely enough, the dhcpxd client available at freshmeat.net seems to
be able to cope with the CIDR netmask--it actually manages to set up the
interface and routes. The netmasks it sets up are wrong
though -- 255.0.0.0 and not 25.255.252.0. Despite this, I can use the
cable modem.
Could someome tell me if the dhcpcd and dhclients are bombing out
because of the wierd netmask, and if the netmask is in fact an indicator
of CIDR? If so, what should I do to live with CIDR?
Thanks!
...Edmund.
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: [EMAIL PROTECTED] (Stewart Honsberger)
Subject: Re: Can't ping anything.
Reply-To: [EMAIL PROTECTED]
Date: Thu, 17 Jun 1999 03:52:29 GMT
On Thu, 17 Jun 1999 01:25:42 GMT, [EMAIL PROTECTED] wrote:
>I've got problems trying to get my network card working under linux.
Could your netmask be off? I've seen 255.255.255.0 more often than
255.255.255.255.
What about cabling? There have been a couple of times where I've found
my cable come loose from the back of my NIC. Or a terminator? (Are you
using Cat-5 or coax? If coax, a faulty hub?).
Can you ping that machine FROM your gateway?
--
Stewart Honsberger (AKA Blackdeath) @ http://sprk.com/blackdeath/
[EMAIL PROTECTED] (Remove 'thirteen' to reply privately)
Humming along under SuSE Linux 6.0 / OS/2 Warp 4
------------------------------
From: "Kyle Hittle" <[EMAIL PROTECTED]>
Subject: Realtek NIC HELP???????
Date: Thu, 17 Jun 1999 13:40:24 -0400
i have a reltek pci 10/100 nic model number RTL8131A
is this device supported by linux, please help me anyone, i need to config
this nic so that i can hook up my T1
thanx
kyle
------------------------------
From: James Youngman <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux
Subject: Re: Network (Atomic) Time
Date: 15 Jun 1999 22:12:43 +0100
Walt Shekrota <[EMAIL PROTECTED]> writes:
> Also try 'man rtime'
> Some dists have it, some don't.
You mean "rdate".
--
ACTUALLY reachable as @free-lunch.demon.(whitehouse)co.uk:james+actually
------------------------------
From: "joe" <[EMAIL PROTECTED]>
Subject: USR ISA 28.8
Date: Thu, 17 Jun 1999 01:17:47 -0400
Hey,
I seem to be having trouble getting my modem to work (I bet none of you
have /ever/ heard of that problem before.). What I have is a USR 28.8k ISA
modem (this is /not/ a winmodem.)
When I try KPPP (I am running Mandrake 5.2, with KDE.) it reports that
"the modem is not ready." The modem is using ttyS0 irq 4 port 0x3f8 uart
16550A. I have set the /etc/rc.d/rc.serial to "setserial ttyS0 irq4 port
0x3f8 uart 16550A." When I boot and setserial runs, it reports that ttyS0
does not exist, but it ( and cua0) /are/ listed in the /dev. Frankly, I'm
at a loss.
Thanks in advance for any help.
Joe Green
------------------------------
Crossposted-To:
alt.os.linux.dial-up,alt.uu.comp.os.linux.questions,comp.os.linux.help,comp.os.linux.setup
From: [EMAIL PROTECTED]
Subject: Re: PPP Scripting... Help?
Date: Thu, 17 Jun 1999 04:06:01 GMT
In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] says...
> I used a nice little program called "pppconfig", which is in Debian Linux
> 2.1. Nice little graphical interface, very easy to configure. You should be
> able to get it from ftp.debian.org.
>
> Sam
>
> "Troy C. Newman" wrote:
>
> > I finally got my modem working and am currently trying to configure my
> > dial-up connection... I've played a little with the commands and have
> > dialed the isp but then nothing... is there a way to find out what the
> > script should say/do to establish and maintain the connection or is it a
> > matter of trial and error for different isp's.
> >
> > any help would be greatly appreciated...tcn.
>
>
A very good document on setting up PPP on Linux can be found at
http://axion.physics.ubc.ca/ppp-linux.html
------------------------------
From: "Stephan M. Ott // OKDesign oHG" <[EMAIL PROTECTED]>
Subject: ipfwadm
Date: Thu, 17 Jun 1999 08:04:40 +0200
Hi folks,
can anyone point me to a URL with good Infos about the usage of ipfwadm ?
Thank you in advance
--- Stephan
------------------------------
From: [EMAIL PROTECTED] (Gilford Wimbley)
Subject: Re: diald still dials every time
Date: Thu, 17 Jun 1999 06:08:11 GMT
On Wed, 16 Jun 1999 16:22:24 GMT, Paulo Garcia <[EMAIL PROTECTED]>
wrote:
>
>
>> I don't think diald automatically tells you exactly why it is bringing
>> itself up. On my machine, it does send a message to
>> "/var/log/messages" every time it comes up. But that message doesn't
>> specify which rule was responsible for bringing the link up.
>>
>> On my installation of diald, there is a file called "standard.filter"
>> in the directory "/etc". This file, which came with the distribution
>> of diald, controls what packets bring the link up and keep it up. It
>> has many explanatory comments.
>>
>> I do not fully understand everything in the file myself, but if you
>> can find this file on your machine somewhere, you can play with it.
>> Also, you can post portions of it with questions and people can answer
>> them.
>>
>> let me know if you want me to email my "standard.conf" to you.
>>
>> regards, GW
>> [snip]
>>
>I look this standard.conf and to my knowlegement it 's very dificult to
>understand, but I'll research a little more.
>
>If you can send me your standard.conf I accept. May be looking your
>file I can do something...
>
>
>Thanks!
>--
>===========================
>[]'s
>Paulo Garcia
>[EMAIL PROTECTED]
>Digivoice Eletronica
>
>
>Sent via Deja.com http://www.deja.com/
>Share what you know. Learn what you don't.
Actually, my file is basically the standard file. It is hard to
understand, but basically, you should try ignoring all packets that
have anything to do with netbios. Like I said, this never was
entirely successful for me. But you can save the original in a safe
place, then make modifications and restart diald. Then see if you get
an improvement. I went through this myself, and I was never
successful. But hey, it was fun. The problem, if I recall, is that
since the packets are directed at the name server, and so they cannot
be filtered without stopping name service altogether. This is not
desireable.
Here is the standard.filter:
# This is a pretty complicated set of filter rules.
# (These are the rules I use myself.)
#
# I've divided the rules up into four sections.
# TCP packets, UDP packets, ICMP packets and a general catch all rule
# at the end.
#------------------------------------------------------------------------------
# Rules for TCP packets.
#------------------------------------------------------------------------------
# General comments on the rule set:
#
# In general we would like to treat only data on a TCP link as
signficant
# for timeouts. Therefore, we try to ignore packets with no data.
# Since the shortest possible set of headers in a TCP/IP packet is 40
bytes.
# Any packet with length 40 must have no data riding in it.
# We may miss some empty packets this way (optional routing
information
# and other extras may be present in the IP header), but we should get
# most of them. Note that we don't want to filter out packets with
# tcp.live clear, since we use them later to speedup disconnects
# on some TCP links.
#
# We also want to make sure WWW packets live even if the TCP socket
# is shut down. We do this because WWW doesn't keep connections open
# once the data has been transfered, and it would be annoying to have
the link
# keep bouncing up and down every time you get a document.
#
# Outside of WWW the most common use of TCP is for long lived
connections,
# that once they are gone mean we no longer need the network
connection.
# We don't neccessarily want to wait 10 minutes for the connection
# to go down when we don't have any telnet's or rlogin's running,
# so we want to speed up the timeout on TCP connections that have
# shutdown. We do this by catching packets that do not have the live
flag set.
# --- start of rule set proper ---
# When initiating a connection we only give the link 15 seconds
initially.
# The idea here is to deal with possibility that the network on the
opposite
# end of the connection is unreachable. In this case you don't really
# want to give the link 10 minutes up time. With the rule below
# we only give the link 15 seconds initially. If the network is
reachable
# then we will normally get a response that actually contains some
# data within 15 seconds. If this causes problems because you have a
slow
# response time at some site you want to regularly access, you can
either
# increase the timeout or remove this rule.
accept tcp 15 tcp.syn
# Keep named xfers from holding the link up
ignore tcp tcp.dest=tcp.domain
ignore tcp tcp.source=tcp.domain
# (Ack! SCO telnet starts by sending empty SYNs and only opens the
# connection if it gets a response. Sheesh..)
accept tcp 5 ip.tot_len=40,tcp.syn
# keep empty packets from holding the link up (other than empty SYN
packets)
ignore tcp ip.tot_len=40,tcp.live
# make sure http transfers hold the link for 2 minutes, even after
they end.
# NOTE: Your /etc/services may not define the tcp service www, in
which
# case you should comment out the following two lines or get a more
# up to date /etc/services file. See the FAQ for information on
obtaining
# a new /etc/services file.
accept tcp 120 tcp.dest=tcp.www
accept tcp 120 tcp.source=tcp.www
# Once the link is no longer live, we try to shut down the connection
# quickly. Note that if the link is already down, a state change
# will not bring it back up.
keepup tcp 5 !tcp.live
ignore tcp !tcp.live
# an ftp-data or ftp connection can be expected to show reasonably
frequent
# traffic.
accept tcp 120 tcp.dest=tcp.ftp
accept tcp 120 tcp.source=tcp.ftp
#NOTE: ftp-data is not defined in the /etc/services file provided with
# the latest versions of NETKIT, so I've got this commented out here.
# If you want to define it add the following line to your
/etc/services:
# ftp-data 20/tcp
# and uncomment the following two rules.
#accept tcp 120 tcp.dest=tcp.ftp-data
#accept tcp 120 tcp.source=tcp.ftp-data
# If we don't catch it above, give the link 10 minutes up time.
accept tcp 600 any
# Rules for UDP packets
#
# We time out domain requests right away, we just want them to bring
# the link up, not keep it around for very long.
# This is because the network will usually come up on a call
# from the resolver library (unless you have all your commonly
# used addresses in /etc/hosts, in which case you will discover
# other problems.)
# Note that you should not make the timeout shorter than the time you
# might expect your DNS server to take to respond. Otherwise
# when the initial link gets established there might be a delay
# greater than this between the initial series of packets before
# any packets that keep the link up longer pass over the link.
# Don't bring the link up for rwho.
ignore udp udp.dest=udp.who
ignore udp udp.source=udp.who
# Don't bring the link up for RIP.
ignore udp udp.dest=udp.route
ignore udp udp.source=udp.route
# Don't bring the link up for NTP or timed.
ignore udp udp.dest=udp.ntp
ignore udp udp.source=udp.ntp
ignore udp udp.dest=udp.timed
ignore udp udp.source=udp.timed
# Don't bring up on domain name requests between two running nameds.
ignore udp udp.dest=udp.domain,udp.source=udp.domain
# Bring up the network whenever we make a domain request from
someplace
# other than named.
accept udp 30 udp.dest=udp.domain
accept udp 30 udp.source=udp.domain
# Do the same for netbios-ns broadcasts
# NOTE: your /etc/services file may not define the netbios-ns service
# in which case you should comment out the next three lines.
ignore udp udp.source=udp.netbios-ns,udp.dest=udp.netbios-ns
accept udp 30 udp.dest=udp.netbios-ns
accept udp 30 udp.source=udp.netbios-ns
# keep routed and gated transfers from holding the link up
ignore udp tcp.dest=udp.route
ignore udp tcp.source=udp.route
# Anything else gest 2 minutes.
accept udp 120 any
# Catch any packets that we didn't catch above and give the connection
# 30 seconds of live time.
accept any 30 any
#-=-=-=-=-=----end of file
good luck.
------------------------------
From: Spudly <[EMAIL PROTECTED]>
Subject: Re: PPP and looped back serial line
Date: Thu, 17 Jun 1999 15:35:42 +1000
Clifford Kite wrote:
> It's likely that the chat expect/send script is ending prematurely.
> If the expect/sends are arguments to chat then I'd look for a carriage
> return that is not `\' escaped at the some expect/send line (except
> the last of course). A space or TAB immediately following the `\'
> would do it.
Yeah, the chat script was dodgey - I don't really know why, but I copy and
pasted it again from another script I knew worked - and hey presto! :)
Thanks for your help, it is much appreciated. And thanks to the rest of
you...."there's a lotta love in this room." (guess the movie...)
-Spud.
------------------------------
From: [EMAIL PROTECTED] (Paul D. Smith)
Crossposted-To:
omp.os.ms-windows.nt.advocacy,comp.os.linux.advocacy,comp.infosystems.www.servers.unix,comp.os.linux.misc
Subject: Re: Could Microsoft Cheat On The New Mindcraft Benchmark? (was: Mindcraft
Retest News
Date: 17 Jun 1999 01:22:44 -0400
Reply-To: [EMAIL PROTECTED]
%% [EMAIL PROTECTED] (I R A Aggie) writes:
+ I only do because, even without all that crap, it's _still_ much bigger
+ than Netscape Communicator.
iraa> Surely you jest?
Nope. Well, Communicator 4.0x, whatever was out last summer.
+ The mind boggles.
iraa> Indeed. Hmmm...incompetent programmers or staticly-linked
iraa> libraries or both?
Probably both... plus maybe some kind of emulation library for their
Windows code so they didn't have to write a native X version? Dunno.
Don't wanna know. Deleted it.
--
===============================================================================
Paul D. Smith <[EMAIL PROTECTED]> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
===============================================================================
These are my opinions---Nortel Networks takes no responsibility for them.
------------------------------
From: [EMAIL PROTECTED] (Gilford Wimbley)
Subject: Re: Diald keeps dialing...
Date: Thu, 17 Jun 1999 06:21:29 GMT
On Wed, 16 Jun 1999 12:16:47 GMT, [EMAIL PROTECTED] (Frank Hahn)
wrote:
[snip]
>Well I can testify to the fact that Samba and diald can both be
>running at the same time with no problems. I have a three computer
>network. One is a Windows 95 machine, one is a 486 running Linux,
>and one is a Sun Sparc machine running Solaris.
>
Oh, yeah, I never meant to imply that they were incompatible, only
that I couldn't figure out how to stop the link from coming up every
fifteen minutes. Are you saying that yours definitely doesn't?
That's great.
At the time I was messing with it, I think I had only tcp/ip
installed, too. Now I certainly have only tcp/ip installed, and I
checked (using tcpdump) to see if the packets still come, and they do.
As I said before, I don't really care now that I have DSL, but for
everyone's benefit, maybe you could do this:
1) explain your configuration. How is name service provided on your
intranet? Do you have a caching name server? How have you configured
the name service relavant options in smb.conf?
2) especially if you don't have a caching name server on the lan,
could you post your standard.filter file? Also, if it wouldn't
compromise your security could you post any firewall rules that might
be helping to squelch windows95's errant packets.
>
>The Linux and Solaris machines are both running Samba and the Linux
>machine has diald running on it. I'm not positive, but, I think the
>solution is to just use TCP/IP networking on the Windows machine.
>At least with me, that is the only one installed.
>
>
>[Snipped]
>
>>what does fwiw stand for?
>>
>fwiw = "for what it's worth" (I believe)
>
thank you.
>--
>Frank Hahn
>
>Consultants are mystical people who ask a company for a number and then
>give it back to them.
regards,
GW
------------------------------
From: "MinSoon Park" <[EMAIL PROTECTED]>
Subject: Where can I get the 'linux-sna' code ?
Date: Thu, 17 Jun 1999 06:21:37 GMT
I cannot find 'linux-sna' code to evaluate.
Only I can find was '*.diff.gz' files. They called it 'patch'.
But I cannot find full code of 'linux-sna' anywhere.
How can I get that ?
If any one can give me the code, please email it to me right now.
[EMAIL PROTECTED]
Thanks
MinSoon Park
------------------------------
From: [EMAIL PROTECTED] ()
Subject: Re: real newbie needs help on domain name registration
Date: 17 Jun 1999 06:33:58 GMT
Reply-To: [EMAIL PROTECTED]
On Wed, 16 Jun 1999 11:37:11 GMT, [EMAIL PROTECTED] muttered:
>I want to setup a webpage on my own computer, i am using cable with static
>ip
>address. And I have some problems in filling out the Name Server
>Information which
>requires "Primary & Secondary Server Hostname:", "Primary & SecondaryServer
>Netaddress:"
>
>Below is the example figure that my isp provides for my computer able to
>connect to the net:
>
>Host Name: xxxxxxxx.yyyyy.eee.com
>DNS Servers: 123.123.123.1
> 123.123.123.2
> 123.123.123.3
>
>My IP address: 222.222.222.2
>
>Can anyone help me what thing should I put into "Primary & Secondary Server
>Hostname:", "Primary & SecondaryServer Netaddress:"??
>
>Thank you very much~~
>
>Mic
>
>
The Primary & Secondary Server Netaddresses are the IPs of your
nameservers:
Primary: 123.123.123.2
Secondary: 123.123.123.3
You'll have to contact your service provider to get the names of those
servers-- they are the Primary and Secondary Server hostnames.
Then, you'll need to contact your service provider and make sure they add
your new domain & hostnames to their DNS records using your IP address, so
your new domain name resolves to your IP address. Not all ISPs do this
without getting some kind of hosting account, so check with them.
Something else to think about, if your ISP assigns you a different IP
address each time you connect (known as DHCP), then this probably won't
work. If your IP address is static (if it stays 222.222.222.2 each time
you connect), then the above should work fine.
--
-] Michael Proto [-
-] MCP [-
-] Happy Linux user since 1997 [-
ERROR: REALITY.SYS Corrupted! Reboot universe? (Y/n)
------------------------------
From: [EMAIL PROTECTED] (Gilford Wimbley)
Subject: Re: cable modem or ASDL
Date: Thu, 17 Jun 1999 06:39:41 GMT
On Wed, 16 Jun 1999 22:53:52 -0500, Doug Bryant
<[EMAIL PROTECTED]> wrote:
>hello,
>
>I am fortunate enough to be moving into an area that provides both cable
>modem and ASDL access.
>
>
>Could anyone give advice about which is better/more reliable The cable
>modem access would be through @Home and the ASDL would be through
>Bellsouth.net.
>
>What I am looking for is speed and ability to access my linux box from
>work or on trips. I am able to do this now by emailing my IP# to my
>work email address over a dial up account.
>
This is anecdotal, and in unresolved, but...
I have ADSL with pacific bell on the west coast of the US. It is
fast, I routinely get speeds at or somewhat over the minimum
guaranteed speed of 384kbps. pacbell's news server has been sketchy,
but they claim they just upgraded it and are working out the bugs.
All other systems have been solid. Today, from work, I tried pinging
my machine and it worked fine. I tried telneting in and it didn't
work. I haven't checked the logs yet, but I am kind of afraid that
they are somehow screening packets. I have a single user type setup,
and maybe they filter packets on it. They also have business-oriented
setups that are not that much more expensive, and which would really
have to let all packets in.
>Is a similar senario possible with one or the other.
>
>
You will most likely get a permanent email address with dsl. You
won't have to mail it.
>I am not expecting either company to jump at the chance to support linux
>so that is not really an issue. I have heard Bellsouth ASDL is
>anti-linux going so far as to not provide access to linux boxes even if
>you set it up yourself. (see slashdot.org and do a search on Bellsouth)
Heh. As far as I'm concerned, data wire is almost like plumbing. The
utilities bring the pipes (data lines) in, the type of faucet you use
is your business.
>
>Thanks for any pointers
>
>Doug Bryant
>[EMAIL PROTECTED]
>
------------------------------
** 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
******************************
