Re: Networking problem on Shuttle XS35GTV2

On Wed, 29 Feb 2012 12:32:44 +, Camaleón wrote: > On Tue, 28 Feb 2012 20:32:07 +, Ramon Hofer wrote: > >> On Tue, 28 Feb 2012 16:44:05 +, Camaleón wrote: > >>> Mmm, if your problem is a missing kernel module (jme.ko), the file is >>> located here: >>> >>> /lib/modules/2.6.32-5-686/k

Re: Networking problem on Shuttle XS35GTV2

On Wed, Feb 29, 2012 at 12:32:44PM +, Camaleón wrote: > > Okay, it is important to use the right syntax for the CD to be properly > recognized. You should never try and manually enter the CDROM into your sources.list, always use apt-cdrom. Although, the installer usually handles that for you

Re: Networking problem on Shuttle XS35GTV2

On Tue, 28 Feb 2012 20:32:07 +, Ramon Hofer wrote: > On Tue, 28 Feb 2012 16:44:05 +, Camaleón wrote: >> Mmm, if your problem is a missing kernel module (jme.ko), the file is >> located here: >> >> /lib/modules/2.6.32-5-686/kernel/drivers/net/jme.ko >> >> Which is available in the first

Re: Networking problem on Shuttle XS35GTV2

Pascal Hambourg wrote: > Keith McKenzie a écrit : > > Ramon Hofer wrote: > >> What am I doing wrong? Personally I would install a different network card for the installation and then get through the install part. Then after the system is running I would install the new drivers when the onboard ne

Re: Networking problem on Shuttle XS35GTV2

On Tue, 28 Feb 2012 16:44:05 +, Camaleón wrote: > On Tue, 28 Feb 2012 15:34:44 +, Ramon Hofer wrote: > >> I have described my problem a while ago and now I got a solution to my >> Ubuntu bug report: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316 See posts 5 >> and 6 >>

Re: Networking problem on Shuttle XS35GTV2

On Tue, 28 Feb 2012 18:31:19 +, Keith McKenzie wrote: > On 28/02/12 15:34, Ramon Hofer wrote: >> So I tried to do the way post 6 describes. I have installed >> debian-6.0.4- i386-CD-1.iso after putting it on a usb stick with >> unetbootin. Then I tried to install gcc but it can't find the >> i

Re: Networking problem on Shuttle XS35GTV2

On Tue, 28 Feb 2012 18:28:18 +, Keith McKenzie wrote: > On 28/02/12 15:34, Ramon Hofer wrote: >> Hi all >> >> I have described my problem a while ago and now I got a solution to my >> Ubuntu bug report: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316 See posts 5 >> and 6 >> >

Re: Networking problem on Shuttle XS35GTV2

Hello, Keith McKenzie a écrit : > On 28/02/12 16:03, Ramon Hofer wrote: >> >> http://kernel-handbook.alioth.debian.org/ch-initrd.html >> >> Chapter 6.4 Examining the initrd contents tells me to: >> mount -t cramfs /boot/initrd.img-2.6.12-1-686 /mnt/initrd -o loop >> >> So I took my gunzipped file

Re: Networking problem on Shuttle XS35GTV2

On 28/02/12 16:03, Ramon Hofer wrote: I was looking for the initrd.gz in the installation medium. I found two: /install.386/gtk/initrd.gz and /install.386/initrd.gz They aren't the same. Why are there two versions of them? Is it ok to take this one: /install.386/initrd.gz? /install.386/g

Re: Networking problem on Shuttle XS35GTV2

On 28/02/12 15:34, Ramon Hofer wrote: So I tried to do the way post 6 describes. I have installed debian-6.0.4- i386-CD-1.iso after putting it on a usb stick with unetbootin. Then I tried to install gcc but it can't find the installation medium anymore. So I mounted the created usb stick to /medi

Re: Networking problem on Shuttle XS35GTV2

On 28/02/12 15:34, Ramon Hofer wrote: Hi all I have described my problem a while ago and now I got a solution to my Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316 See posts 5 and 6 Post 5 sounds great but I can't find how to unpack the initrd.gz. Can you help me

Re: Networking problem on Shuttle XS35GTV2

On Tue, 28 Feb 2012 15:34:44 +, Ramon Hofer wrote: > I have described my problem a while ago and now I got a solution to my > Ubuntu bug report: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316 See posts 5 > and 6 > > Post 5 sounds great but I can't find how to unpack the init

Re: Networking problem on Shuttle XS35GTV2

On Tue, 28 Feb 2012 16:40:46 +0100, Hans-J. Ullrich wrote: > Am Dienstag, 28. Februar 2012 schrieb Ramon Hofer: >> I have described my problem a while ago and now I got a solution to my >> Ubuntu bug report: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316 See posts 5 >> and 6 >>

Re: Networking problem on Shuttle XS35GTV2

Am Dienstag, 28. Februar 2012 schrieb Ramon Hofer: > Hi all > > I have described my problem a while ago and now I got a solution to my > Ubuntu bug report: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/880316 > See posts 5 and 6 > > Post 5 sounds great but I can't find how to unpack t

Re: Networking problem

On Thu, Dec 10, 2009 at 09:22:17PM +0700, freeburn wrote: > Now we want to use a machine which will be connected with the smpp > server and also connected with the office network for accessing our > remote content server(where our website is hosted). I have tried to use > two ethernate cards. but

Re: Networking problem

Am 10.12.2009 um 15:22:17 schrieb freeburn: > I'm describing the scenario. plz help me with this. > > In our office we have set up a private network. a central dhcp server > assigns private Ip's to all the Desktops. Now recently we are developing > an automated sms application. so we have made a

Re: Networking problem (SOLVED)

On Sat, 2007-08-25 at 16:40 -0700, Dr. Jennifer Nussbaum wrote: > Im sorry, i looked closely at the packages and i see > now that theres a new version of the driver package to > go with the new kernel. I would have expected that > there would be some kind of automatic update, or some > way of letti

Re: Networking problem (SOLVED)

>>What is your Wi-Fi chip? Maybe you don't have the >>driver module >>installed for the newer kernel version. > >Its an Intel PRO/Wireless 3945ABG. From my dmesg in >the 2.6.18-4 kernel: > >--- >ipw3945: Intel(R) PRO/Wireless 3945 Network Connection >driver for Linux, 1.1.2dmpr >ipw3945: Copyright(

Re: networking problem

L.V.Gandhi wrote: My laptop is served by dhcp router. my hostname lvgdell600m. lvgdell600m:~# cat /etc/hostname lvgdell600m my /etc/hosts is lvgdell600m:~# cat /etc/hosts 127.0.0.1 localhost.localdomain localhost lvgdell600m 192.168.1.51mohan 192.168.1.52lvgdell600m 192.168

Re: Networking Problem - yup

On Mon, 2 Aug 2004, Jonathan Barnes wrote: > > Thanks for the reply, I was wondering what a good way of subnetting my networks > would be.. What would be be advisable for someone with a DMZ and a LAN, and > another LAN inside the first LAN "better" or "good way" will depend on who you ask i

Re: Networking Problem - yup

On Mon, 2 Aug 2004, Jonathan Barnes wrote: > Matt Perry wrote: > > > On Mon, 2 Aug 2004, Jonathan Barnes wrote: > > > > > >>eth1 Link encap:Ethernet HWaddr 00:05:1C:13:5C:8D > >> inet addr:10.1.1.1 Bcast:10.1.1.255 Mask:255.255.255.0 > >> UP BROADCAST MULTICAST MTU:1

Re: Networking Problem - yup

Jonathan Barnes wrote: Alvin Oga wrote: yup ... your mask 255.255.255.0 says use only the last octet .. 10.0.0.x is NOT in the same network as 10.1.1.x it's doing what you told it ... maybe not what you want if you want to use 10.0.0.2 ... don't... "0" is best used for network name use 10.1.

Re: Networking Problem - yup

Alvin Oga wrote: yup ... your mask 255.255.255.0 says use only the last octet .. 10.0.0.x is NOT in the same network as 10.1.1.x it's doing what you told it ... maybe not what you want if you want to use 10.0.0.2 ... don't... "0" is best used for network name use 10.1.1.2 and your trouble

Re: Networking Problem

Matt Perry wrote: On Mon, 2 Aug 2004, Jonathan Barnes wrote: eth1 Link encap:Ethernet HWaddr 00:05:1C:13:5C:8D inet addr:10.1.1.1 Bcast:10.1.1.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 That's odd. The line above should contain "RUNNING" but it do

Re: Networking Problem

On Mon, 2 Aug 2004, Jonathan Barnes wrote: > eth1 Link encap:Ethernet HWaddr 00:05:1C:13:5C:8D > inet addr:10.1.1.1 Bcast:10.1.1.255 Mask:255.255.255.0 > UP BROADCAST MULTICAST MTU:1500 Metric:1 That's odd. The line above should contain "RUNNING" but it doesn't. Ca

Re: Networking Problem

Matt Perry wrote: On Sun, 1 Aug 2004, Jonathan Barnes wrote: Destination Gateway Genmask Flags Metric RefUse Iface 10.0.0.00.0.0.0 255.255.255.0 U 0 00 eth0 10.0.0.00.0.0.0 255.255.255.0 U 0 00 eth1 0.0.0

Re: Networking Problem

On Sun, 1 Aug 2004, Jonathan Barnes wrote: > >>>Destination Gateway Genmask Flags Metric RefUse Iface > >>>10.0.0.00.0.0.0 255.255.255.0 U 0 00 eth0 > >>>10.0.0.00.0.0.0 255.255.255.0 U 0 00 eth1 > >>>0.0

Re: Networking Problem

Jonathan Barnes wrote: Matt Perry wrote: On Sun, 1 Aug 2004, Jonathan Barnes wrote: I cant see anything wrong with my routing table either: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.00.0.0.0 255.255.255.0 U 0

Re: Networking Problem

Matt Perry wrote: On Sun, 1 Aug 2004, Jonathan Barnes wrote: I cant see anything wrong with my routing table either: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 10.0.0.00.0.0.0 255.255.255.0 U 0 00 eth0 10

Re: Networking Problem

Paul Gear wrote: Jonathan Barnes wrote: John Summerfield wrote: I _thought_ you might be Australian. Yes I am :) We're everywhere! (It's Sunday arvo - time to break my Linux box for this week.) Nah. Your both bananabenders. Not that we don't bend a few. _I_ have a few spares

Re: Networking Problem

Jonathan Barnes wrote: > John Summerfield wrote: > >> I _thought_ you might be Australian. > > > Yes I am :) We're everywhere! (It's Sunday arvo - time to break my Linux box for this week.) -- Paul -- Every gun that is made, every warship launched, every rocket fi

Re: Networking Problem

John Summerfield wrote: I _thought_ you might be Australian. Yes I am :) I don't know just that your tools are on Windows: boot Linux (Knoppix is fine) if you can. From there, traceroute x.com ping -R -c4 x.org and see where routing breaks. Also, on Debbie (the Debian box) sysctl -a | grep ip_ H

Re: Networking Problem

Jonathan Barnes wrote: Hi, I'm having a very strange networking problem that has my linux buddies and I stumped. I'll draw a basic mud map because it makes it ALOT easier to understand my situation as I have two gateways due to shared housing. I _thought_ you might be Australian. [Bridged ADSL Mod

Re: Networking Problem

On Sun, 1 Aug 2004, Jonathan Barnes wrote: > I cant see anything wrong with my routing table either: > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric RefUse Iface > > 10.0.0.00.0.0.0 255.255.255.0 U 0 00 eth0 > > 10

Re: Networking Problem

Matt Perry wrote: On Sun, 1 Aug 2004, Jonathan Barnes wrote: my Debian Box. eg: The Firewall can ping my Debian Box, but my Debian Box can't ping the firewall. It's sounds like IP forwarding isn't working. Take down the interface that uses 10.1.1.1 and then try to ping the firewall. What happen

Re: Networking Problem

On Sun, 1 Aug 2004, Jonathan Barnes wrote: > my Debian Box. eg: The Firewall can ping my Debian Box, but my Debian > Box can't ping the firewall. It's sounds like IP forwarding isn't working. Take down the interface that uses 10.1.1.1 and then try to ping the firewall. What happens? What is th

Re: networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel]

on Mon, 12 Apr 2004 09:53:38PM -0400, Derrick 'dman' Hudson insinuated: > On Mon, Apr 12, 2004 at 06:26:33PM -0400, Nori Heikkinen wrote: > | on Mon, 12 Apr 2004 03:08:28PM -0400, Derrick 'dman' Hudson insinuated: > | > What version of the dhcp-client package do you have installed? > | > | 2.0pl5-

Re: networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel]

On Mon, Apr 12, 2004 at 06:26:33PM -0400, Nori Heikkinen wrote: | on Mon, 12 Apr 2004 03:08:28PM -0400, Derrick 'dman' Hudson insinuated: | > On Mon, Apr 12, 2004 at 12:19:06PM -0400, Nori Heikkinen wrote: | > | on Fri, 09 Apr 2004 03:42:06PM -0400, Derrick 'dman' Hudson insinuated: | > [...] | >

Re: networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel]

Derrick 'dman' Hudson wrote: > On Mon, Apr 12, 2004 at 02:11:24PM -0400, Nori Heikkinen wrote: > | on Mon, 12 Apr 2004 02:02:06PM -0400, J F insinuated: > | > I don't have a specific answer to your problem, > | > but using aptitude seems to ease upgrade problems. > | > Also, having testing, unstab

Re: networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel]

on Mon, 12 Apr 2004 03:08:28PM -0400, Derrick 'dman' Hudson insinuated: > On Mon, Apr 12, 2004 at 12:19:06PM -0400, Nori Heikkinen wrote: > | on Fri, 09 Apr 2004 03:42:06PM -0400, Derrick 'dman' Hudson insinuated: > [...] > | > I haven't noticed any changes in networking, but that might be > | > d

using apt/aptitude (was: Re: networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel])

On Mon, Apr 12, 2004 at 02:11:24PM -0400, Nori Heikkinen wrote: | [back on-list] | | on Mon, 12 Apr 2004 02:02:06PM -0400, J F insinuated: | > I don't have a specific answer to your problem, | > but using aptitude seems to ease upgrade problems. | > Also, having testing, unstable, and stable all i

Re: networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel]

On Mon, Apr 12, 2004 at 12:19:06PM -0400, Nori Heikkinen wrote: | on Fri, 09 Apr 2004 03:42:06PM -0400, Derrick 'dman' Hudson insinuated: [...] | > I haven't noticed any changes in networking, but that might be | > dependent on the hardware and what modules I already had configured | > to be loade

Re: networking problem with 2.6.4 kernel [was: Re: 2.6.4 kernel install wants to remove current kernel]

[back on-list] on Mon, 12 Apr 2004 02:02:06PM -0400, J F insinuated: > I don't have a specific answer to your problem, > but using aptitude seems to ease upgrade problems. > Also, having testing, unstable, and stable all in > /etc/apt/sources.list seems to get aptitude > to converge on a working s

Re: networking problem encountered while installing "Woody"

--- Aurélien_Campéas <[EMAIL PROTECTED]> wrote: > You have a problem with dhcp here. Are you sure you want it ? It > seems > like the dhcp client doesn't find a dhcp server... > I mean, why not pick up some private ip adress (like 192.168.0.2) and > rewrite your eth0 entry in /etc/network/interfa

Re: networking problem encountered while installing "Woody"

Le lun 22/03/2004 à 09:22, Renhao Zhang a écrit : > Aurlien, > Thank you for your prompt and insightful reply. I'll > get a move on learning to compiling my own kernel. Wait a minute... ! > # The first network card - this entry was created > during the Debian installation > # (network, broadc

Re: networking problem encountered while installing "Woody"

Aurélien, Thank you for your prompt and insightful reply. I'll get a move on learning to compiling my own kernel. Hopefully, that'll get the networking functioning. In the mean time, I'd still like to learn exactly how my setup isn't working and what I am fixing. The following is the info you a

Re: networking problem (perhaps with Autonegotiate?)

I haven't had the dubious pleasure of having any association with an ME Network. However, if other versions of Windows are anything to go by my recollection is that Connection Sharing sets up the gateway as 192.168.0.1 with the other machines usually getting their IP from the gateway via dhcp.

Re: networking problem (perhaps with Autonegotiate?)

> all i'm doing to try to connect is putting the DNS in > the /etc/resolv.conf and then typing: > > ifconfig eth0 192.168.10.90 netmask 255.255.255.0 > (actually every time i type this two more lines like Seems like you forgot to create a default route. If you do a plain 'ifconfig' you wil see th

Re: networking problem and philosophy

On Mon, 2003-03-03 at 13:25, David Z Maze wrote: > Hmm. Is there anything informative in /etc/network/interfaces (the > "normal" place for network settings under Debian)? You also might try > running your DHCP client by hand, and seeing if that works. Also, > check that your kernel configuratio

Re: networking problem and philosophy

On Mon, 2003-03-03 at 13:25, David Z Maze wrote: > > Bret Comstock Waldow <[EMAIL PROTECTED]> writes: > > > I'm trying to get Debian going on my Thinkpad T21, and synchronize with > > my Sony Clie PDA. > > (This works fine for me, but I always build my own kernel. I've had > better luck using

Re: networking problem and philosophy

Bret Comstock Waldow <[EMAIL PROTECTED]> writes: > I'm trying to get Debian going on my Thinkpad T21, and synchronize with > my Sony Clie PDA. (This works fine for me, but I always build my own kernel. I've had better luck using coldsync than pilot-link, and the first sync always fails.) > I'm

Re: networking problem during install

on Thu, Aug 30, 2001 at 06:39:44PM -0700, Bob Galloway ([EMAIL PROTECTED]) wrote: > Well, I finally got the box to network. As god as my witness, I have > no idea why this worked, but it worked: I swapped the NetGear card out > of the box, replaced it with the LinkSys card, and tried one more ti

Re: networking problem during install

Well, I finally got the box to network. As god as my witness, I have no idea why this worked, but it worked: I swapped the NetGear card out of the box, replaced it with the LinkSys card, and tried one more time. Funny, it works now. I'm still scratching my head wondering why it didn't work th

Re: networking problem during install

on Thu, Aug 30, 2001 at 12:56:22AM -0700, Bob Galloway ([EMAIL PROTECTED]) wrote: > On Wed, Aug 29, 2001 at 04:55:15PM -0700, Brandon High wrote: > > On Wed, Aug 29, 2001 at 01:04:51PM -0700, Karsten M. Self wrote: > > > Another thought: PCI bus problems? > > > > > > Have you tried an alternate

Re: networking problem during install

On Wed, Aug 29, 2001 at 04:55:15PM -0700, Brandon High wrote: > On Wed, Aug 29, 2001 at 01:04:51PM -0700, Karsten M. Self wrote: > > Another thought: PCI bus problems? > > > > Have you tried an alternate card in the box? If everthing outside the > > box works, the card(s) work, and the CPU isn't

Re: networking problem during install

On Wed, Aug 29, 2001 at 01:04:51PM -0700, Karsten M. Self wrote: > Another thought: PCI bus problems? > > Have you tried an alternate card in the box? If everthing outside the > box works, the card(s) work, and the CPU isn't misbehaving, I'd suspect > a mobo/bus problem. No idea how to diagnose

Re: networking problem during install

on Tue, Aug 28, 2001 at 09:33:06PM -0700, Bob Galloway ([EMAIL PROTECTED]) wrote: > Howdy, deb folk! > > I'm trying to turn an old AT&T Globalyst P90 box into a firewall > running Debian. Installation via NFS would be much easier if I could > get networking to work! Too bad I can't seem to get

Re: networking problem during install

On Wed, Aug 29, 2001 at 08:51:21AM -0400, James D Strandboge wrote: > Forgive me I this is redundant, but is your ethernet card set to auto > negotiate > its speed? Sometimes this can be a problem if you are on a 10BaseT network > and > the card goes to 100Baset. I'm using 10BaseT. When I swap

Re: networking problem during install

On Wed, Aug 29, 2001 at 12:10:21AM -0700 or thereabouts, Bob Galloway wrote: Forgive me I this is redundant, but is your ethernet card set to auto negotiate its speed? Sometimes this can be a problem if you are on a 10BaseT network and the card goes to 100Baset. Jamie Strandboge -- "The goal o

Re: networking problem during install

On Tue, Aug 28, 2001 at 11:33:04PM -0700, Karsten M. Self wrote: > > Okay. I just tried again with potato install disks, from the 'compact' > > series. Same problems as with slink. Great sadness and woe. > > > > A recap: > > - ifconfig reports TX packets, but no RX packets. > > - networ

Re: networking problem during install

on Tue, Aug 28, 2001 at 11:08:22PM -0700, Bob Galloway ([EMAIL PROTECTED]) wrote: > On Tue, Aug 28, 2001 at 10:01:51PM -0700, Bob Galloway wrote: > > > Do you have the installation stuff on the NFS export? It may be > > > easier to download rescue and root floppies from the potato installers > >

Re: networking problem during install

On Tue, Aug 28, 2001 at 10:01:51PM -0700, Bob Galloway wrote: > > Do you have the installation stuff on the NFS export? It may be > > easier to download rescue and root floppies from the potato installers > > and do a network install. You'd be using a 2.2 kernel then. > > I considered doing that

Re: networking problem during install

On Wed, Aug 29, 2001 at 12:51:20AM -0400, dman wrote: > tulip driver ... I've heard stories from some people that older tulip > drivers don't work with certain newer cards. What NIC are you using? > Personally I've never had any problems with the tulip driver starting > with version 0.90 and a Lin

Re: networking problem during install

On Tue, Aug 28, 2001 at 09:33:06PM -0700, Bob Galloway wrote: | Howdy, deb folk! | | I'm trying to turn an old AT&T Globalyst P90 box into a firewall | running Debian. Installation via NFS would be much easier if I could | get networking to work! Too bad I can't seem to get the box to notice | i

Re: Networking problem (SAMBA???)

> "aparra" == aparra <[EMAIL PROTECTED]> writes: aparra> But the problem is that some times the win98 machines stops aparra> viewing the network, put I still have IP conexion. And if I aparra> try to make, from any win machine. a telnet to any linux, it aparra> takes years to get the prompt.

Re: Networking problem (SAMBA???)

On Tue, Jun 12, 2001 at 04:06:09PM +0200, aparra wrote: > Hello!! > > > I have a GenuineIntel, Pentium 100. I use this machine as server, with > Samba, to serve printer, and files. I have also an other machine > (identical) as router and www server. But the problem is that some times > the

Re: networking problem

Try changing your netmasks to 255.255.0.0 -Jason *** REPLY SEPARATOR *** On 18/03/00 at 4:54 PM Thomas Braun wrote: >hello group, > > >i have two nic's in one debian computer, >and i want to reach both networks over a router and from the subnet. > >the first nic has the 192.16

Re: networking problem

Nope. irq conflict with sound card. Mike McNally wrote: > > route add -host 127.0.0.1 lo > success (but isn't this supposed to be done by a bootup script ifup?) > > ifconfig eth0 192.168.1.1 netmask 255.255.255.0 up > SIOCSIFFLAGS: Resource temporarily unavailable > SIOCSIFFLAGS: Resource tempor

Re: networking problem

More problems which will hopefully present a clue kernel: registered device ppp0 pppd[432]: pppd 2.3.11 started by root, uid 0 pppd[432]: Using interface ppp8 pppd[432]: Connect : ppp8 <--> /dev/ttyS1 pppd[432]: tcflush failed: input/output error pppd[432]: Exit ls /var/log/lock nothing tree /et

Re: networking problem

Trying Sven's ifup -a SIOCSIFFLAGS: Resource temporarily unavailable SIOCSIFFLAGS: Resource temporarily unavailable I think I goofed up the kernel compile. I remember being unsure of questions regarding pty unix98 dmesg | pty pty: 256 Unix98 ptys configured but I kind of recall not adding all

Re: networking problem

On Sun, Sep 03, 2000 at 02:28:30PM -0500, Mike McNally wrote: > route add -host 127.0.0.1 lo > success (but isn't this supposed to be done by a bootup script ifup?) Sorry to butt into the middle of this thread like this, but I shouldn't the default route be re-set by "ifup -a"? If I set the defa

Re: networking problem

route add -host 127.0.0.1 lo success (but isn't this supposed to be done by a bootup script ifup?) ifconfig eth0 192.168.1.1 netmask 255.255.255.0 up SIOCSIFFLAGS: Resource temporarily unavailable SIOCSIFFLAGS: Resource temporarily unavailable failure Maybe pty/kernel_config problem? mike Mike

Re: networking problem with 2.1.x

Ben Jorgensen <[EMAIL PROTECTED]> writes: > When booting with 2.1.128 I can't remove the net entry in the routing > table. > > route del > > I get SIOCDERT: no such process > > What's wrong? With 2.0.35 it works fine! 2.1.x drastically changed the way routing works. Usually it looks the sam