-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Aug 05, 2017 at 10:37:42AM -0400, Gene Heskett wrote:
> On Saturday 05 August 2017 04:13:24 to...@tuxteam.de wrote:
>
> > On Sat, Aug 05, 2017 at 12:11:28AM +1000, Zenaan Harkness wrote:
> > > On Fri, Aug 04, 2017 at 10:14:20AM +0200, to...@tu
On Saturday 05 August 2017 04:13:24 to...@tuxteam.de wrote:
> On Sat, Aug 05, 2017 at 12:11:28AM +1000, Zenaan Harkness wrote:
> > On Fri, Aug 04, 2017 at 10:14:20AM +0200, to...@tuxteam.de wrote:
>
> [chattr]
>
> > Another command that could be add to /e/n/i :)
>
> you nasty ;-)
>
> cheers
> -- t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Aug 05, 2017 at 12:11:28AM +1000, Zenaan Harkness wrote:
> On Fri, Aug 04, 2017 at 10:14:20AM +0200, to...@tuxteam.de wrote:
[chattr]
> Another command that could be add to /e/n/i :)
you nasty ;-)
cheers
- -- t
-BEGIN PGP SIGNATURE-
On Fri, Aug 04, 2017 at 09:01:32AM +0100, Joe wrote:
> On Fri, 4 Aug 2017 10:59:13 +1000
> Zenaan Harkness wrote:
> > Given the uniqueness of how you seem to want to do your networking,
> > perhaps that's the best option to make it less abnormal - looks like
> > it to me.
>
> I don't think it's r
On Fri, Aug 04, 2017 at 10:14:20AM +0200, to...@tuxteam.de wrote:
> On Thu, Aug 03, 2017 at 08:49:05PM +0200, Pascal Hambourg wrote:
> > Le 03/08/2017 à 15:52, Zenaan Harkness a écrit :
> > >On Thu, Aug 03, 2017 at 08:53:27AM -0400, Greg Wooledge wrote:
> > >>But the problem is, various Unix DHCP c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Aug 03, 2017 at 08:49:05PM +0200, Pascal Hambourg wrote:
> Le 03/08/2017 à 15:52, Zenaan Harkness a écrit :
> >On Thu, Aug 03, 2017 at 08:53:27AM -0400, Greg Wooledge wrote:
> >>But the problem is, various Unix DHCP client daemons do *too much*
On Fri, 4 Aug 2017 10:59:13 +1000
Zenaan Harkness wrote:
>
> Given the uniqueness of how you seem to want to do your networking,
> perhaps that's the best option to make it less abnormal - looks like
> it to me.
>
I don't think it's really all that unique, or unreasonable, for a
computer user
On Thu, Aug 03, 2017 at 08:49:05PM +0200, Pascal Hambourg wrote:
> Le 03/08/2017 à 15:52, Zenaan Harkness a écrit :
> > On Thu, Aug 03, 2017 at 08:53:27AM -0400, Greg Wooledge wrote:
> > > But the problem is, various Unix DHCP client daemons do *too much*.
> > > All I want them to do is set the IP
On Thu, Aug 03, 2017 at 08:53:06PM +0200, Pascal Hambourg wrote:
> Le 03/08/2017 à 17:20, Joshua Schaeffer a écrit :
> >
> > Configuration in /etc/network/interfaces only works when NetworkManager
> > isn't installed,
>
> Wrong. The default NetworkManager behaviour is not to manage interfaces
>
Le 03/08/2017 à 17:20, Joshua Schaeffer a écrit :
Configuration in /etc/network/interfaces only works when NetworkManager isn't
installed,
Wrong. The default NetworkManager behaviour is not to manage interfaces
defined in /etc/network/interfaces.
Le 03/08/2017 à 15:52, Zenaan Harkness a écrit :
On Thu, Aug 03, 2017 at 08:53:27AM -0400, Greg Wooledge wrote:
But the problem is, various Unix DHCP client daemons do *too much*.
All I want them to do is set the IP address, netmask, and gateway.
I *don't* want them to change the system hostname
On 08/02/2017 06:56 PM, Zenaan Harkness wrote:
>
> I've preferred a static networking config for years, and resolvconf
> works well in this situation - but once resolvconf is configured,
> I've always put the dns setting in /etc/networks/interfaces
I agree with this as well. If you want to use st
On Thu, Aug 03, 2017 at 08:53:27AM -0400, Greg Wooledge wrote:
> But the problem is, various Unix DHCP client daemons do *too much*.
> All I want them to do is set the IP address, netmask, and gateway.
> I *don't* want them to change the system hostname, or the system
> resolv.conf (in which I have
On Thu, Aug 03, 2017 at 11:09:48AM +1000, Zenaan Harkness wrote:
> Perhaps in certain scenarios, yes - the world's full of wierd
> networks :)
Concrete examples? OK.
Work system: the Information Technology Division (ITD) runs the DHCP
servers, which are basically built around the assumption that
On Wed, Aug 02, 2017 at 02:55:50PM -0400, Greg Wooledge wrote:
> On Wed, Aug 02, 2017 at 08:10:23PM +0200, Pascal Hambourg wrote:
> > Le 02/08/2017 à 16:19, Greg Wooledge a écrit :
> > >
> > > 1) Make sure the Debian "resolvconf" package is *not* installed.
> >
> > You should reconsider this advi
On Wed, Aug 02, 2017 at 05:44:50PM +0400, ruslan axundov wrote:
> Hi
>
> I have a problem with debian 9 as static nameserver .
> So that I used before ubuntu 16.04 and I have configure satatic ip and dns
> and it worked perfectly but today I tried to use debian 9 and when I
> enter static dns s
On Wed, Aug 02, 2017 at 08:10:23PM +0200, Pascal Hambourg wrote:
> Le 02/08/2017 à 16:19, Greg Wooledge a écrit :
> >
> > 1) Make sure the Debian "resolvconf" package is *not* installed.
>
> You should reconsider this advice. resolvconf may be your best ally to
> handle such a situation.
OK, I'v
Le 02/08/2017 à 16:19, Greg Wooledge a écrit :
1) Make sure the Debian "resolvconf" package is *not* installed.
You should reconsider this advice. resolvconf may be your best ally to
handle such a situation.
3) I have utterly no idea how Network-Manager works
Me neither, but I know one t
On Wed, Aug 02, 2017 at 05:44:50PM +0400, ruslan axundov wrote:
> I tried to use debian 9 and when I
> enter static dns server for debian in resolve.conf then after reboot
> debian all dns ip removed from resolv.conf file. I tried multiple method to
> prevent this feature but nothing happen. what
On Thu, 2003-06-05 at 08:20, steve downes wrote:
> On Wed, 2003-06-04 at 23:35, Frank Gevaerts wrote:
> > On Wed, Jun 04, 2003 at 11:10:37PM +0100, steve downes wrote:
> > > On Wed, 2003-06-04 at 15:40, Kevin McKinley wrote:
> > > > On 04 Jun 2003 14:30:50 +0100
> > > > steve downes <[EMAIL PROTECT
On Wed, 2003-06-04 at 23:35, Frank Gevaerts wrote:
> On Wed, Jun 04, 2003 at 11:10:37PM +0100, steve downes wrote:
> > On Wed, 2003-06-04 at 15:40, Kevin McKinley wrote:
> > > On 04 Jun 2003 14:30:50 +0100
> > > steve downes <[EMAIL PROTECTED]> wrote:
> > >
> > > > Anyone know how to get the kerne
On Wed, Jun 04, 2003 at 11:10:37PM +0100, steve downes wrote:
> On Wed, 2003-06-04 at 15:40, Kevin McKinley wrote:
> > On 04 Jun 2003 14:30:50 +0100
> > steve downes <[EMAIL PROTECTED]> wrote:
> >
> > > Anyone know how to get the kernel to see the right irq & io for a 3c509b
> > > card with the ab
On Wed, Jun 04, 2003 at 11:10:37PM +0100, steve downes wrote:
> On Wed, 2003-06-04 at 15:40, Kevin McKinley wrote:
> > On 04 Jun 2003 14:30:50 +0100
> > steve downes <[EMAIL PROTECTED]> wrote:
> >
> > > Anyone know how to get the kernel to see the right irq & io for a 3c509b
> > > card with the ab
On Wed, 2003-06-04 at 15:40, Kevin McKinley wrote:
> On 04 Jun 2003 14:30:50 +0100
> steve downes <[EMAIL PROTECTED]> wrote:
>
> > Anyone know how to get the kernel to see the right irq & io for a 3c509b
> > card with the above kernel. Windows, 2.2 kernel & ltsp all get it right
> > 2.4 gets somet
On 04 Jun 2003 14:30:50 +0100
steve downes <[EMAIL PROTECTED]> wrote:
> Anyone know how to get the kernel to see the right irq & io for a 3c509b
> card with the above kernel. Windows, 2.2 kernel & ltsp all get it right
> 2.4 gets something completely different
>
> Steve
You can specify the IRQ a
On Wed, 5 Mar 2003 at 9:00pm, [EMAIL PROTECTED] wrote:
:Setting up the loopback and pingin it works fine, pinging into the
:machine also works fine (tried from an old win95 machine). But
:pinging out of the machine dosn't work, I'm getting the error message
:"Unable to connect to remote host: N
Barry deFreese
NTS Technology Services Manager
Nike Team Sports
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 05, 2003 1:16 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Network config help needed
>
>
>
> Yep,
Yep, read Net-HOWTO, but still I can't get it to work. ...
Setting up the loopback and pingin it works fine, pinging into the
machine also works fine (tried from an old win95 machine). But
pinging out of the machine dosn't work, I'm getting the error message
"Unable to connect to remote host:
[EMAIL PROTECTED] wrote:
Please help me
I'm trying to connect two pc's, but I allways get the message
"unable to connect to remote host: No route to host". What am I
missing?
My config for pc1 looks like this:
ifconfig eth0 192.168.0.1 netmask 255.255.255.0 up
rout add -host 192.168.0.2 eth0
"
Am Son, 2003-03-02 um 13.15 schrieb [EMAIL PROTECTED]:
> Please help me
> I'm trying to connect two pc's, but I allways get the message
> "unable to connect to remote host: No route to host". What am I
> missing?
>
> My config for pc1 looks like this:
> ifconfig eth0 192.168.0.1 netmask 255.255
-BEGIN PGP SIGNED MESSAGE-
you dont have a lo in ur route: loopback interface.
check whether you can ping to yourself (lo) 127.0.0.1 on each pc.
then configure pc1 as 192.168.0.1. repeat the two steps with pc2,
only changing the ip address.
the initial sections of Net-HOWTO must help.
so
On Monday 10 December 2001 19:39, Mark Ferlatte wrote:
> > Reading again /etc/init.d/dhcp I see the following:
> >
> > # Add all interfaces you want dhcpd to handle here
>
> Change the lines in /etc/init.d/dhcp that look like
>
> start-stop-daemon --start --quiet --pidfile $DHCPDPID
On Mon, Dec 10, 2001 at 05:46:56PM -0300, Daniel Toffetti wrote (1.00):
> Reading again /etc/init.d/dhcp I see the following:
>
> # Add all interfaces you want dhcpd to handle here
Change the lines in /etc/init.d/dhcp that look like
start-stop-daemon --start --quiet --pidfile $DH
On Monday 10 December 2001 16:23, Daniel Toffetti wrote:
> But now (and this is why I say PART-SOLVED) the internal hosts are
> not assigned a valid internal IP from the proxy via pump. I even
> copied the file dhcpd.conf from my old proxy to the new, tried
> changing from pump to dhcpcd in the int
On Sunday 09 December 2001 16:24, Michael Heldebrant wrote:
> > It's strange to me that 'pump -i eth1 --status' shows correctly the
> > gateway (10.7.2.1), nameservers, etc. So I tried to add the two
> > missing entries, and it failed.
> >
> > root:> route add default gw 10.7.2.1 dev eth1
> > SIOCA
On Sun, 2001-12-09 at 12:50, Daniel Toffetti wrote:
> On Sunday 09 December 2001 02:53, Michael Heldebrant wrote:
> > You want:
> > auto ethWHATEVER
> > iface inet dhcp ethWHATEVER
> > instead of "static dhcp" which, I'm not even sure how it would be
> > parsed by ifup. ifconfig should tell you if
On Sunday 09 December 2001 02:53, Michael Heldebrant wrote:
> You want:
> auto ethWHATEVER
> iface inet dhcp ethWHATEVER
> instead of "static dhcp" which, I'm not even sure how it would be
> parsed by ifup. ifconfig should tell you if your interface iseven
> being brought up.
My fault here, sorry
On Sat, 2001-12-08 at 23:14, Daniel Toffetti wrote:
> On Saturday 08 December 2001 16:58, ben wrote:
> > > Right now I get the external interface be assigned the valid IP
> > > address as before, configuring it as 'static dhcp - hostname pump'
> > > in /etc/interfaces. But when I try _any_ ping (an
On Saturday 08 December 2001 16:58, ben wrote:
> > Right now I get the external interface be assigned the valid IP
> > address as before, configuring it as 'static dhcp - hostname pump'
> > in /etc/interfaces. But when I try _any_ ping (any but my own
> > address and localhost, of course), it fails
On Saturday 08 December 2001 10:41 am, Daniel Toffetti wrote:
> Hi all !
>
> I've a small diskless proxy booting from a floppy based distro called
> Coyote. Now I've got an old HDD and I'm installing Debian Potato, but
> I'm failing to get the access to the Net working.
> Right now I get the extern
On Tuesday 30 Oct 2001 7:20 pm, D. wrote:
> you need to answer is what is your Hostname? Then it
> will ask you if you want the program to set up your
> network automatically, saying yes will do this and if
> the program is successful it will say congratulations
> your network is set up.
> What
If memory serves me correctly, during the installation
of Potato at the point of inserting/selecting modules,
if your nic card is on the list and you select it,
when you exit that portation of the install it will
ask you if you want to configure your network. Saying
yes will start the process and
www.webmin.com/webmin
On Tuesday 30 October 2001 08:50 am, Will Newton wrote:
> Is there such a thing?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A long time ago, in a galaxy far, far way, someone said...
> Hi all, I'm just curious. why are there so many files that apparently
> hold the same information? I thought the network configuration were
> kept in files hosts, hostname, gateways, route.s
Thank you!
Robin
- Original Message -
From: "Terry Boon" <[EMAIL PROTECTED]>
To:
Sent: Monday, December 25, 2000 2:58 PM
Subject: Re: Network config easy question
> On Mon, Dec 25, 2000 at 02:27:53PM -0800, Robin Rowe wrote:
> > Dumb question, how do I se
:-> "Pierfrancesco" == Pierfrancesco Caci <[EMAIL PROTECTED]> writes:
> the dns host is set up using /proc directly or by using
> /etc/sysctl.conf
duh... I meant dns domain name
the dns serving you is set in /etc/resolv.conf
Pf
--
---
On Mon, Dec 25, 2000 at 02:27:53PM -0800, Robin Rowe wrote:
> Dumb question, how do I set the IP address, netmask, gateway, and dns host
> on Debian? The docs say that I should edit a file named 'network' but I
> don't find any such file.
/etc/network/interfaces is where you may want to look. Her
:-> "Robin" == Robin Rowe <[EMAIL PROTECTED]> writes:
> Dumb question, how do I set the IP address, netmask, gateway, and dns host
> on Debian? The docs say that I should edit a file named 'network' but I
> don't find any such file.
the docs are outdated. check for a file named /etc/
Check "man interfaces"
On Monday 25 December 2000 04:27 pm, Robin Rowe wrote:
> Dumb question, how do I set the IP address, netmask, gateway, and
> dns host on Debian? The docs say that I should edit a file named
> 'network' but I don't find any such file.
>
> Robin
> [EMAIL PROTECTED]
Pascal Hos
Wayne Topa <[EMAIL PROTECTED]> writes:
> > I can't find this option( CONFIG_RTL8139 ) in network device section.Where
> > is it?
You've to say 'yes' to CONFIG_EXPERIMENTAL, which shows you the
"experimantel" drivers, too.
moritz
--
Moritz Schulte <[EMAIL PROTECTED]> http://hp9001.fh-bi
Subject: RE: Network config
Date: Tue, Nov 21, 2000 at 10:59:09AM +0800
In reply to:Gilbert.Li (??)
Quoting Gilbert.Li (??)([EMAIL PROTECTED]):
>
> I can't find this option( CONFIG_RTL8139 ) in network device section.Where
> is it?
> Thanks
>
On Tue, Nov 21, 2000 at 10:59:09AM +0800, Gilbert.Li (??) wrote:
>
>
> > > > So you actually need to compile the tulip-driver as a module, not
> > > > via-rhine. Look for DEC in the section "Network Devices" during
> > > > kernel-configuration.
> > > As I said, I used DFE 530 TX, not DE 530.
> > > So you actually need to compile the tulip-driver as a module, not
> > > via-rhine. Look for DEC in the section "Network Devices" during
> > > kernel-configuration.
> > As I said, I used DFE 530 TX, not DE 530.
> >
> I don't have the whole thread of this anymore, but I vaguely remember
>
On Mon, Nov 20, 2000 at 08:14:03PM +0800, Gilbert.Li (??) wrote:
> >
> > So you actually need to compile the tulip-driver as a module, not
> > via-rhine. Look for DEC in the section "Network Devices" during
> > kernel-configuration.
> As I said, I used DFE 530 TX, not DE 530.
>
I don't have
> > > > $cat /proc/pci
> > >
> > > That does not mean, that the kernel detects your card but the the
> > > PCI-system does.
> > > What do your logfiles report while booting?
> >
> > via-rhine.c:v1.01 2/27/99 Writen by Donald Becker
> >http://cesdis.gsfc.nasa.gov/linux/drivers/via-rhine.htm
On Mon, Nov 20, 2000 at 09:48:49AM +0800, Gilbert.Li (§õ«Â¾§) wrote:
> > > $cat /proc/pci
> >
> > That does not mean, that the kernel detects your card but the the
> > PCI-system does.
> > What do your logfiles report while booting?
>
> via-rhine.c:v1.01 2/27/99 Writen by Donald Becker
>ht
> 1. I am reading te list so there is no need to send me a private mail
> too.
> 2. Please start to write at the beginning of a line. Your mails are
> very hard to read.
I aologize.
>
> Ok, sure there is a driver in the kernel-tree but you should under all
> circumstances try to compile the d
On Sun, Nov 19, 2000 at 11:11:02AM +0800, Gilbert.Li (§õ«Â¾§) wrote:
1. I am reading te list so there is no need to send me a private mail
too.
2. Please start to write at the beginning of a line. Your mails are
very hard to read.
> > What do you mean? Are you talking about a driver, which is no
>
> > > Yes you need to have the module loaded for your network card
> > > before you can actually use the eth0 interface w/
> ifconfig and such.
> > > Silver
> >
> >if I don't have a built-in network driver, how do I
> configure the driver.
>
> What do you mean? Are you talking about a
On Sat, Nov 18, 2000 at 02:20:35PM +0800, Gilbert.Li (§õ«Â¾§) wrote:
> > Yes you need to have the module loaded for your network card
> > before you can actually use the eth0 interface w/ ifconfig and such.
> > Silver
>
>if I don't have a built-in network driver, how do I configure the drive
> Yes you need to have the module loaded for your network card
> before you can actually use the eth0 interface w/ ifconfig and such.
> Silver
if I don't have a built-in network driver, how do I configure the driver.
Thanks.
> > >
> > > On Tuesday 14 November 2000 10:49, Knud S鷨ensen wro
Knud Sørensen <[EMAIL PROTECTED]> writes:
> Where do debain put gateway info.
Network interfaces get configured via /etc/network/interfaces, see
'man interfaces'. Then you can start/stop these interfaces with
ifup/ifdown. It's just a very nice frontend to configure network
interfaces (it uses ifc
Virginie wrote:
>
> On Tue, Nov 14, 2000 at 05:04:06PM +0100, Knud S?rensen wrote:
> > Thanks, this was the problem.
>
> You're welcome, I'm happy to learn it :)
>
> >
> > When make config ask if I wanted experimental module I say no.
> > And my net card was a experimental realtech thing.
> >
>
Yes you need to have the module loaded for your network card
before you can actually use the eth0 interface w/ ifconfig and such.
Silver
- Original Message -
From: "Knud Sørensen" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, November 14, 2000 12:13 PM
Subject: Re: Network conf
On Tue, Nov 14, 2000 at 11:49:24AM +0100, Knud S?rensen wrote:
> Hi
>
> I am a new debian user.
> I have some problems getting my network to work.
>
> What is the best way to config the network in debian 2.2 ?
>
> It seems that there is a problem finding the eth0 interface.
I personally succee
"Maurizio Boriani (by way of Maurizio Boriani )" wrote:
>
> On Tuesday 14 November 2000 10:49, Knud Sørensen wrote:
> > Hi
> >
> > I am a new debian user.
> > I have some problems getting my network to work.
> >
> > What is the best way to config the network in debian 2.2 ?
> >
> > It seems that t
On Tuesday 14 November 2000 10:49, Knud Sørensen wrote:
> Hi
>
> I am a new debian user.
> I have some problems getting my network to work.
>
> What is the best way to config the network in debian 2.2 ?
>
> It seems that there is a problem finding the eth0 interface.
>
> Can anybody help me ?
>
>
Ethan Benson wrote:
> yup dhcp sucks, for potato configure your interfaces in
> /etc/network/interfaces
>
Does this relate to the current deb2.2 distribution?
Robert
On Mon, Oct 23, 2000 at 09:16:57AM -0400, Michael P. Soulier wrote:
>
> Hmm. I just looked in /etc/init.d, and there's a network script that sets
> up the loopback connection:
>
> #! /bin/sh
> ifconfig lo 127.0.0.1
> route add -net 127.0.0.0
>
> I see an entry in /etc/network/interfaces
On Sun, Oct 22, 2000 at 08:12:33PM -0800, Ethan Benson wrote:
>
> yup dhcp sucks, for potato configure your interfaces in
> /etc/network/interfaces
>
> something like this:
>
> iface eth0 inet static
> address 192.168.0.1
> netmask 255.255.255.0
> network 192.168.0.0
>
On Sun, Oct 22, 2000 at 08:12:33PM -0800, Ethan Benson wrote:
> yup dhcp sucks, for potato configure your interfaces in
> /etc/network/interfaces
>
> something like this:
>
> iface eth0 inet static
> address 192.168.0.1
> netmask 255.255.255.0
> network 192.168.0.0
>
On Sun, Oct 22, 2000 at 11:26:42PM -0400, Michael P. Soulier wrote:
> Ok, Rogers' dhcp servers suck, and I'm tired of it. I just manually set up
> my ip and routing table with ifconfig and route. So, if I want this done on
> every boot instead of dhcp, where is the appropriate place to put the
Quoting John Gould ([EMAIL PROTECTED]):
> Could someone please tell me if there is a tool in Debian to
> configure the permanent network parameters other than changing them
> temporarily with ifconfig or hacking /etc/init.d/network? Slackware has
> 'netconfig', is there a similar tool
sday, February 16, 2000 9:36 PM
Subject: Re: Network config and domain name ?
>Second question: Use modconf
>
>First question: I actually don't know (I always just edit
>/etc/init.d/network) but you could start the installation again and only
>configure the network and skip
Second question: Use modconf
First question: I actually don't know (I always just edit
/etc/init.d/network) but you could start the installation again and only
configure the network and skip the rest, there might be a easier but...
Ron
On Wed, 16 Feb 2000, John Gould wrote:
> Hi everyone,
>
On Wed, Oct 27, 1999 at 02:23:16PM +0200, Stephan Hachinger wrote:
> Hello!
>
> I've finally solved it!
Great, now you should have a look at your MUA and MTA,
because you posted the same mail 5 times!
JY
--
Jean-Yves F. Barbier <[EMAIL PROTECTED]>
It is easier to change the specification to fi
Hello!
I've finally solved it!
- The error messages by commenting some entries in the network script,
- The card problem by changing the BIOS! Yeah, I can't believe it myself,
but I simply had not remembered that a non-pnp card was using IRQ9 and I had
not told that to the bios which also gave I
Hello!
I've finally solved it!
- The error messages by commenting some entries in the network script,
- The card problem by changing the BIOS! Yeah, I can't believe it myself,
but I simply had not remembered that a non-pnp card was using IRQ9 and I had
not told that to the bios which also gave I
Hello!
I've finally solved it!
- The error messages by commenting some entries in the network script,
- The card problem by changing the BIOS! Yeah, I can't believe it myself,
but I simply had not remembered that a non-pnp card was using IRQ9 and I had
not told that to the bios which also gave I
Hello!
I've finally solved it!
- The error messages by commenting some entries in the network script,
- The card problem by changing the BIOS! Yeah, I can't believe it myself,
but I simply had not remembered that a non-pnp card was using IRQ9 and I had
not told that to the bios which also gave I
Hello!
I've finally solved it!
- The error messages by commenting some entries in the network script,
- The card problem by changing the BIOS! Yeah, I can't believe it myself,
but I simply had not remembered that a non-pnp card was using IRQ9 and I had
not told that to the bios which also gave I
looks like the driver for the card isnt loaded.
nate
[mailto:[EMAIL PROTECTED] ]--
Linux System Administrator http://www.firetrail.com/
Firetrail Internet Services Limited http://www.aphroland.org/
Everett, WA 425-348-7336
-BEGIN PGP SIGNED MESSAGE-
On Sun, 24 Oct 1999, Harlan Crystal wrote:
> I believe this results from when you upgrade your
> kernel from the older series to the 2.2.x series.
> The older kernels had a "Route" command which is used
> in various startup scripts, but the newer series
> i
I believe this results from when you upgrade your
kernel from the older series to the 2.2.x series.
The older kernels had a "Route" command which is used
in various startup scripts, but the newer series
is "smarter" and no longer requires the route command
so it doesn't exist. These error me
I had this problem and it turned out the card was trying to use an IRQ of 0.
Fixed it by cd-ing into the modules directory and loading each module in
turn 'til I found one that worked.
Daniel Martin writes:
> Really? My pppd man page covers this [/etc/ppp/options.ttySX]...
Mine doesn't.
> My ppp is from bo, version 2.2.0f-23
My pppd is pppd version 2.2 patch level 0, on a 1.3.1 system recently
upgraded with a Cheap Bytes CD. On the pppd man page source I find
'pppd.8,v 1.1.1.
[EMAIL PROTECTED] (Robert D. Hilliard) writes:
> The pppd man page mentions the option as requiring
> pppd to make a ppp connection using the specified device, but does not
> mention that pppd will then read the file /etc/ppp. README.linux and
> the comments in the file /etc/ppp/options.tty
Robert D. Hilliard writes:
> The pppd man page mentions the option as requiring pppd to
> make a ppp connection using the specified device, but does not mention
> that pppd will then read the file /etc/ppp. README.linux and the
> comments in the file /etc/ppp/options.ttyXX included with the
> dis
Lindsay writes:
> One small point. You can get compression from a modem but it is very
> difficult to get compression over a piece of wire. :-)
'bsdcomp 15,15' works just fine over a piece of wire. Better, in fact,
than over a modem since the modem should already be doing hardware
compression.
(My original post, requesting assistance configuring slip over a
null modem, and the responses recommending ppp instead are omitted to
save bandwidth.)
Thanks again to all. My link is now working perfectly.
The pppd man page mentions the option as requiring
pppd to make a ppp con
Lindsay Allen <[EMAIL PROTECTED]> writes:
> One small point. You can get compression from a modem but it is very
> difficult to get compression over a piece of wire. :-)
I believe compression from a modem is actually software compression
implemented by the modem's ROM, while BSD compressio
Bob,
One small point. You can get compression from a modem but it is very
difficult to get compression over a piece of wire. :-)
I fell for the same thing myself.
But do go for 115200.
Lindsay
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lindsay Allen <[EMAIL PR
Thanks very much for your responses. All responders recommended
using ppp instead of slip. I will try a ppp setup tonight.
I started trying to use slip because the NET-3-HOWTO recommends
it in this situation. Is that advice now obsolete?
John says: "If this works I suggest upp
I needed the same thing recently and someone on this list
kindly posted this solution. Put this on both machines in
/etc/ppp/options.ttyS0 and then type pppd ttyS0 on both
sides. I'm assuming that you are using the first serial
port (ttyS0) on both computers here. 'bobspc' will then
have two ppp
94 matches
Mail list logo
