https://www.isc.org/software/dhcp/
xu...@epri.sgcc.com.cn
On 2011-08-08 08:12:07 +0300, Volkan YAZICI wrote:
> On Sat, 06 Aug 2011 15:29:04 -0400, "Robert Blair Mason Jr." writes:
> > 1. Why do I have to call iwconfig twice?
>
> Because wicd overwrites it somehow?
No, wicd (the daemon) is stopped at that time.
> > 2. Is wicd at fault in this case? I
On 2011-08-06 15:29:04 -0400, Robert Blair Mason Jr. wrote:
> Thanks for your help! I was finally able to get it to work with the
> following, which I put into a script:
>
> /etc/init.d/wicd stop
> ifconfig $IFACE down
> iwconfig $IFACE essid $ESSID mode Ad-Hoc channel $CHANNEL
> ifconfig $IFACE
On Sat, 06 Aug 2011 15:29:04 -0400, "Robert Blair Mason Jr." writes:
> 1. Why do I have to call iwconfig twice?
Because wicd overwrites it somehow?
> 2. Is wicd at fault in this case? If so, should I file a bug report?
If you can do it manually and wicd cannot by default, then, yes, you
shoul
On Sat, 06 Aug 2011 21:10:53 +0200
Vincent Lefevre wrote:
> On 2011-08-05 09:42:11 -0400, Robert Blair Mason Jr. wrote:
> > I am unable to connect to adhoc networks on debian sid using wicd.
> > Whenever I try to connect to an adhoc network (in this case the one
> > broadcast by barnacle on my ph
On 2011-08-05 09:42:11 -0400, Robert Blair Mason Jr. wrote:
> I am unable to connect to adhoc networks on debian sid using wicd.
> Whenever I try to connect to an adhoc network (in this case the one
> broadcast by barnacle on my phone, but the problem is reproducible on
> any adhoc network), wicd a
Hi everyone,
I am unable to connect to adhoc networks on debian sid using wicd.
Whenever I try to connect to an adhoc network (in this case the one
broadcast by barnacle on my phone, but the problem is reproducible on
any adhoc network), wicd appears to go through all of the steps to
connect succe
:55 corn named[24777]: too many timeouts resolving
'36.106.70.75.in-addr.arpa/PTR' (in '75.in-addr.arpa'?): reducing the
advertised EDNS UDP packet size to 512 octets
Feb 14 10:43:10 corn named[24777]: network unreachable resolving
'3.55.255.193.in-addr.arpa/PTR/IN': 2001
I'm not sure what the routing tables are... I'll try man route and see what I
can glean.
Both machines are on the same hub.
Oh, and a new development, I tried it while I was writing this email. I can
ssh to both of these machines but from home, which is a completely different
network than the
Captain's Log, stardate Fri, 17 Dec 2004 11:41:37 +0100, from the fingers of
Alexandru Cabuz came the words:
> Hi,
>
> I got two computers in my office, both using Debian Sarge. One
> 2.6.9, the other 2.6.7.
>
> They both can ping the outside world (like google.com), but they
> can't ping each oth
On Fri, 17 Dec 2004 11:05:48 -0500, Adam Aube <[EMAIL PROTECTED]> wrote:
> Alexandru Cabuz wrote:
>
> > When I try to ping B from A I get
> > connect: Network is unreachable
>
> > When I try to ping A from B I get
> > From [IP of machine B] icmp_seq=1 Destination Host Unreachable
> > From [IP of
Alexandru Cabuz wrote:
> When I try to ping B from A I get
> connect: Network is unreachable
> When I try to ping A from B I get
> From [IP of machine B] icmp_seq=1 Destination Host Unreachable
> From [IP of machine B] icmp_seq=2 Destination Host Unreachable
> From [IP of machine B] icmp_seq=3 De
Hi,
I got two computers in my office, both using Debian Sarge. One 2.6.9, the
other 2.6.7.
They both can ping the outside world (like google.com), but they can't ping
each other.
Let's call them machine A and machine B.
When I try to ping B from A I get
connect: Network is unreachable
When
On 02/11/2003, at 3:21 PM, Jeffrey Barish wrote:
At that point, ping worked. So it seems as if dhcp is not working.
Is there something in the kernel configuration that is required to
make dhcp work?
You need CONFIG_FILTER enabled in your kernel. It is in networking
options in menuconfig.
Che
On Sun, 2003-11-02 at 09:50, Jeffrey Barish wrote:
> Marshal Wong wrote:
> > On Sat, 2003-11-01 at 20:21, Jeffrey Barish wrote:
> >
> >>When I use the kernel that I built from the source for 2.4.18-686, I get
> >>the message:
> >>
> >>sendto: Network is unreachable
> >>
> >>when I try to ping ano
On Sun, 2003-11-02 at 03:20, Ron Johnson wrote:
> On Sun, 2003-11-02 at 05:03, Marshal Wong wrote:
> > On Sun, 2003-11-02 at 01:41, Ron Johnson wrote:
> > > On Sun, 2003-11-02 at 03:28, Marshal Wong wrote:
> > > > On Sat, 2003-11-01 at 20:21, Jeffrey Barish wrote:
> > > > > When I use the kernel th
Marshal Wong wrote:
On Sat, 2003-11-01 at 20:21, Jeffrey Barish wrote:
When I use the kernel that I built from the source for 2.4.18-686, I get
the message:
sendto: Network is unreachable
when I try to ping another machine on my network. Using ifconfig, I
noticed that eth0 had no IP address a
On Sun, 2003-11-02 at 05:03, Marshal Wong wrote:
> On Sun, 2003-11-02 at 01:41, Ron Johnson wrote:
> > On Sun, 2003-11-02 at 03:28, Marshal Wong wrote:
> > > On Sat, 2003-11-01 at 20:21, Jeffrey Barish wrote:
> > > > When I use the kernel that I built from the source for 2.4.18-686, I get
> > > >
On Sun, 2003-11-02 at 01:41, Ron Johnson wrote:
> On Sun, 2003-11-02 at 03:28, Marshal Wong wrote:
> > On Sat, 2003-11-01 at 20:21, Jeffrey Barish wrote:
> > > When I use the kernel that I built from the source for 2.4.18-686, I get
> > > the message:
> > >
> > > sendto: Network is unreachable
>
On Sun, 2003-11-02 at 03:28, Marshal Wong wrote:
> On Sat, 2003-11-01 at 20:21, Jeffrey Barish wrote:
> > When I use the kernel that I built from the source for 2.4.18-686, I get
> > the message:
> >
> > sendto: Network is unreachable
> >
> > when I try to ping another machine on my network. Us
On Sat, 2003-11-01 at 20:21, Jeffrey Barish wrote:
> When I use the kernel that I built from the source for 2.4.18-686, I get
> the message:
>
> sendto: Network is unreachable
>
> when I try to ping another machine on my network. Using ifconfig, I
> noticed that eth0 had no IP address assigned
On Sat, 2003-11-01 at 22:21, Jeffrey Barish wrote:
> When I use the kernel that I built from the source for 2.4.18-686, I get
> the message:
>
> sendto: Network is unreachable
>
> when I try to ping another machine on my network. Using ifconfig, I
> noticed that eth0 had no IP address assigned
When I use the kernel that I built from the source for 2.4.18-686, I get
the message:
sendto: Network is unreachable
when I try to ping another machine on my network. Using ifconfig, I
noticed that eth0 had no IP address assigned. So I did
ifconfig eth0 down
and then
ifconfig eth0 192.168.
On 4 Jun 2003 "Rolf Erling Robberstad" <[EMAIL PROTECTED]> wrote:
>I installed woody over the internet, configured by the
>local DHCP-server. I then downloaded (from debian)
>kernel 2.4.20 from http://www.kernel.org and compiled
>it to get X working (as part of a i810/i815 howto).
>
>The 3c59x-dr
Rolf Erling Robberstad declaimed:
> I installed woody over the internet, configured by the
> local DHCP-server. I then downloaded (from debian)
> kernel 2.4.20 from http://www.kernel.org and compiled
> it to get X working (as part of a i810/i815 howto).
>
> The 3c59x-driver was compiled directly
On Wed, 04 Jun 2003 18:05:13 +0200
"Rolf Erling Robberstad" <[EMAIL PROTECTED]> wrote:
> I installed woody over the internet, configured by the
> local DHCP-server. I then downloaded (from debian)
> kernel 2.4.20 from http://www.kernel.org and compiled
> it to get X working (as part of a i810/i81
> > # dhclient eth0
> > -didn't help (it is, however present on the machine)
>
> What did it do? Generally dhclient has output.
A blank line for about a second while the computer
was working, then back to an ordinary line:
[EMAIL PROTECTED] dhclient eth0
(small pause)
[EMAIL PROTECTED] _
Tryed
On Wed, 4 Jun 2003, Rolf Erling Robberstad wrote:
> It did work before I got the new kernel (downloaded
> the kernel as an ordinary user).
>
> # dhclient eth0
> -didn't help (it is, however present on the machine)
What did it do? Generally dhclient has output.
--
To UNSUBSCRIBE, email to [EMAI
> If you do have dhclient installed, I would check your
> /etc/network/interfaces file to see if the card is configured to get an IP
> address through DHCP. It should look something like this:
>
> auto eth0
> iface eth0 inet dhcp
I'm afraid that's the way it looked...
> If that isn't the proble
Greetings,
> -Original Message-
> From: Andrew Perrin [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 04, 2003 1:55 PM
> To: Rolf Erling Robberstad
> Cc: [EMAIL PROTECTED]
> Subject: Re: 3c920 in 2.4.20; "network unreachable"
>
>
> On Wed, 4 J
T)
To: Rolf Erling Robberstad <[EMAIL PROTECTED]>
Subject: Re: 3c920 in 2.4.20; "network unreachable"
> AFAIK, compiling it into the kernel isn't enough - you need a user-space
> client to do the actual work. What happens when you do:
>
> dhclient eth0
>
On Wed, 4 Jun 2003, Rolf Erling Robberstad wrote:
> I installed woody over the internet, configured by the
> local DHCP-server. I then downloaded (from debian)
> kernel 2.4.20 from http://www.kernel.org and compiled
> it to get X working (as part of a i810/i815 howto).
>
> The 3c59x-driver was co
I installed woody over the internet, configured by the
local DHCP-server. I then downloaded (from debian)
kernel 2.4.20 from http://www.kernel.org and compiled
it to get X working (as part of a i810/i815 howto).
The 3c59x-driver was compiled directly into the
kernel along with the other needed su
"prover" <[EMAIL PROTECTED]> writes:
> I'M NOT MEMER OF YOUR MAILING LISTS. MY MAIL IS : [EMAIL PROTECTED]
> ([EMAIL PROTECTED] IS ONLY FORWARD FROM [EMAIL PROTECTED]).
>
> WHY THIS MAILS COME TO ME?
> EVERY DAY COME TO ME 200 MAILS FROM YOUR MAILING LISTS.
>
> CAN YOU DO SOMETHING WITH IT?
>
>
From: "DvB" <[EMAIL PROTECTED]>
To: "Debian-User"
Sent: Tuesday, June 04, 2002 4:32 PM
Subject: Re: [SOLVED!] Re: lost route (network unreachable)
> Andy Saxena <[EMAIL PROTECTED]> writes:
>
> > On Mon, Jun 03, 2002 at 09:42:54AM -0500, DvB wrote
From: "Andy Saxena" <[EMAIL PROTECTED]>
To: "Debian-User"
Sent: Tuesday, June 04, 2002 7:05 AM
Subject: Re: [SOLVED!] Re: lost route (network unreachable)
> On Mon, Jun 03, 2002 at 09:42:54AM -0500, DvB wrote:
> > Michel Verdier <[EMAIL PROTECTED]> wri
Andy Saxena <[EMAIL PROTECTED]> writes:
> On Mon, Jun 03, 2002 at 09:42:54AM -0500, DvB wrote:
> > Michel Verdier <[EMAIL PROTECTED]> writes:
> >
> > > DvB <[EMAIL PROTECTED]> a écrit :
> > >
> > > > I tried running route add -host hostname.mydomain.com (though I have no
> > > > idea if that's s
On Mon, Jun 03, 2002 at 09:42:54AM -0500, DvB wrote:
> Michel Verdier <[EMAIL PROTECTED]> writes:
>
> > DvB <[EMAIL PROTECTED]> a écrit :
> >
> > > I tried running route add -host hostname.mydomain.com (though I have no
> > > idea if that's supposed to work or not) and get the following:
> > >
>
Michel Verdier <[EMAIL PROTECTED]> writes:
> DvB <[EMAIL PROTECTED]> a écrit :
>
> > I tried running route add -host hostname.mydomain.com (though I have no
> > idea if that's supposed to work or not) and get the following:
> >
> > SIOCADDRT: No such device
>
> Did you indicate interface name l
DvB <[EMAIL PROTECTED]> a écrit :
> I tried running route add -host hostname.mydomain.com (though I have no
> idea if that's supposed to work or not) and get the following:
>
> SIOCADDRT: No such device
Did you indicate interface name like this :
route add -host hostname.mydomain.com eth0
--
u ping any machine? "Network is unreachable" is usually an
> > indication that your machine is unable to establish contact with the
> > "outside." IIRC it is the same as your machine being unplugged from the
> > network.
> >
>
> That's the s
from the
> network.
>
That's the strange thing. I can reach our production server and the
devel and production servers of the other group I'm doing coding for,
but I can't reach our devel server or a handful of other hosts on the
(internal) network with the "network unreachab
On Wed, May 29, 2002 at 10:42:39AM -0500, DvB wrote:
> On Fri, May 24, 2002 at 09:04:03AM -0500, DvB wrote:
>
> > The "H" flag indicates that the route is to a specific host. Obviously,
> > 255.255.255.255 is not a valid host address.
Interesting reply line. Stop the blatant plagiarism! :-}
>
>
On Fri, May 24, 2002 at 09:04:03AM -0500, DvB wrote:
> The "H" flag indicates that the route is to a specific host. Obviously,
> 255.255.255.255 is not a valid host address.
The field with the 255.255.255.255 is labeled as "Genmask," whatever
that is. Interestingly, the field with "-" is labeled
On Fri, May 24, 2002 at 09:04:03AM -0500, DvB wrote:
> For a few days now, I haven't been able to reach a few of the servers on
> my network. Every time I try to connect to one, I get an error that
> includes the message "network is unreachable."
> When I run netstat -r, all the hosts that I can't
For a few days now, I haven't been able to reach a few of the servers on
my network. Every time I try to connect to one, I get an error that
includes the message "network is unreachable."
When I run netstat -r, all the hosts that I can't reach appear as
follows:
hostname.mydomain.com 255.255.255
> First, try 'ifconfig eth0'. If you get something then the
> device is at least present.
'eth0: error fetching interface information: Device not found'
> If you don't get anything, then next step is
> to check that
> you have the correct modules loaded. Try a 'lsmod' command and see if
> anyth
pparent reason. I realised I couldn't FTP to i, so I tried to ping the
> gateway. This resulted in 'network unreachable', so I looked at ifconfig -
> loopback (127.0.0.1) was there, but no eth0.
>
> I checked /etc/network/interfaces which showed eth0 to be correctly setup.
Unfortunately, the
> network has failed for no apparent reason. I realised I couldn't FTP
> to i, so I tried to ping the gateway. This resulted in 'network
> unreachable', so I looked at ifconfig - loopback (127.0.0.1) was
> there, but no eth0.
>
> I checked
type lspci on command prompt
it will give u r networkcard name
modprbe
update-modules
/etc/passwd
at end of line
+::/bin/bash
later
do networking restart
s kosher there. If none of this works,
read someone else's reply.
HTH,
Brooks
> -Original Message-
> From: Andy Laurence [mailto:[EMAIL PROTECTED]
> Sent: Monday, 10 September, 2001 09:52 AM
> To: debian-user@lists.debian.org
> Subject: Network unreachable
&
well. Unfortunately, the network has failed for
no apparent reason. I realised I couldn't FTP to i, so I tried to ping the
gateway. This resulted in 'network unreachable', so I looked at ifconfig -
loopback (127.0.0.1) was there, but no eth0.
I checked /etc/network/interfaces which showed
ed to ping the
gateway. This resulted in 'network unreachable', so I looked at ifconfig -
loopback (127.0.0.1) was there, but no eth0.
I checked /etc/network/interfaces which showed eth0 to be correctly setup.
I then ran ifdown followed by ifup. Again, no change. I tried a reboot in
va
> gives me 'command not found'. Is there a way to look at man pages with
> another system (Windows) running a browser?
Yes, you can find a collection of man pages here:
http://linux.ctyme.com/
You should be able to find most of the man pages there.
Good luck!
Zonker
--
Joe 'Zonker' Brockmeie
>
>Thanks for the note. I'll try setting the gateway. I think I have the
>syntax written down somewhere.
>
>>Check the man pages. <
>
>Unfortunately, Linux is only partially installed because I can't get my
>http/ftp isn't working to bring in the rest of it, so I don't think I have
>man pages y
> man ifconfig
Just go to google.com and put ifconfig(8) you will find the page in the
web..
for example here:
http://btr0xw.rz.uni-bayreuth.de/cgi-bin/manpages/ifconfig/8
Regards
Roberto
Roberto Diaz <[EMAIL PROTECTED]>
Thanks for the note. I'll try setting the gateway. I think I have the
syntax written down somewhere.
>Check the man pages. <
Unfortunately, Linux is only partially installed because I can't get my
http/ftp isn't working to bring in the rest of it, so I don't think I have
man pages yet. Typing
the command line I do a 'ifconfig eth0 up', and it
> accepts this ok, and if I type 'ifconfig', it lists it there and all looks
> ok.
>
> But I still cannot ping anything but localhost without getting 'Network
> unreachable' errors.
>
> I looked
and if I type 'ifconfig', it lists it there and all looks
ok.
But I still cannot ping anything but localhost without getting 'Network
unreachable' errors.
I looked at /var/log/messages, and didn't see anything bad in there,
except for a message at the very end like:
d
Mark Brown wrote:
>
> On Sat, Dec 09, 2000 at 01:03:01AM -0800, Erik Steffl wrote:
>
> > I can ping crick, I can also telnet (using default telnet port)
> > without problems but when I do telnet crick.fmed.uniba.sk 25 from
> > command line I get the same message (network is unreachable, but onl
On Sat, Dec 09, 2000 at 01:03:01AM -0800, Erik Steffl wrote:
> I can ping crick, I can also telnet (using default telnet port)
> without problems but when I do telnet crick.fmed.uniba.sk 25 from
> command line I get the same message (network is unreachable, but only
> when using port 25).
> n
I am running debian unbstable, kernel 2.2.17 and I just installed
postfix using the 'internet with smarthost' config option.
when I try to send an e-mail to non-local address it says that the
network is unreachable, here's relevant part from syslog:
-- syslog -
On Mon, Sep 25, 2000 at 02:40:51PM +0100, Bob wrote:
> I have a problem with a debian GNU / Linux 2.2 (potato). I tells me that
> network is unreachable, whatever I do.
> When I installed debian, I could not load the ne module (on io=0x280 irq=5).
Can you do it now?
> I only have lo interface
Hello, hope you are well!
I have a problem with a debian GNU / Linux 2.2 (potato). I tells me that
network is unreachable, whatever I do.
When I installed debian, I could not load the ne module (on io=0x280 irq=5).
I only have lo interface loaded, so I follow these steps:
modprobe ne io=0x28
On Sat, Feb 05, 2000 at 15:36, Fam. Engelen wrote:
> '~$echo hallo | lpr' gives a message similar to 'network unreachable, could
> not reach [EMAIL PROTECTED]'
Enable "Networking support" and "TCP/IP networking" in the kernel.
That's it for t
Hi,
I use Debian on an old 486. I removed a lot of packages (especially
networking) for speed. Now when I decided to install a printer, I installed
the 'lprng' package.
'~#echo hallo > /dev/lp1' works as expected (staircase, but it works)
'~$echo hallo | lpr' gi
Hi Chris,
I'm glad that my idea worked for you.
To be honest, everything you described suggested that you had a "problem"
with the firewall. Also, you wrote that the were some "paranoia" messages
during bootup... check tcplogd daemon about that.
There is a "paranoia" option in the firewalls (used
Hi csani,
You're a genius! the ipfwadm -Mf command was rejected, but the
others worked and now I'm back on the net! Can you please explain a
little what was going on and why my config defaulted to
allow_no_network_traffic_mode?
What's the best way to permanently set the correct options?
Many
I am having the same problem here,
I am actullay using RedHat 5.2, on a Tecra 520 but most of the erorrs people
are getting are exactly the same as I am getting.
to check if the PCMCIA card is installed do a cat /proc/interrupts it should
show you if the 3c589_cs is there or not.
tha
Brant & others. getting desperate here, please help!
To answer your question, I'm not sure *EXACTLY* how to check if the
PCMCIA packages are installed, but I believe the answer is yes.
If I look at top, I can see cardmgr running. If I insert/remove the
3c589 I hear the tell-tale hot-swap
I had (maybe) the same problem yesterday:
edit /etc/pcmcia/network.opts and put IP-Address, Network, Gateway,
Broadcast addresses there (without " " quotes around).
Remo
| Dr. Remo Badii | Paul Scherrer Institute |
| Nonlinear
Hi,
I am using 3com 3c905tx with RedHat and although the network card seems to
be "recognized" during installation, the network is unreachable...even the
local network with winNT server.
For example, the response to
ping 204.60.134.10
is "network unreachable"
and the re
Ok, I'm sure we can work through this...
Your /etc/nsswitch.conf file probably needs to have something like this
(this is from the hamm distribution but I believe that bo is similar):
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# Information about this f
[EMAIL PROTECTED] writes:
> I can't get anywhere, I've check the routing tables they appear to be
> set up fine according to the documentation I found on them. I can
> ping my isp and the DNS but nothing else. ifconfig appears to display
> the correct info again according to the documentation I
connected (network unreachable)
> Date: Wednesday, 11 March 1998 12:28
>
>
>
> Well thanks to all your help I'm connected, but (OF COURSE)
> I can't get anywhere, I've check the routing tables they appear to be
> set up fine according to the documentation I found
Well thanks to all your help I'm connected, but (OF COURSE)
I can't get anywhere, I've check the routing tables they appear to be
set up fine according to the documentation I found on them. I can
ping my isp and the DNS but nothing else. ifconfig appears to display
the correct info again accor
Brian Hutchinson wrote:
>
> I have a simple socket program. I've compiled it with gcc on
> Debian 1.1 (kernel 2.0.29) and Red Had (Biltmore 2.0.30) and I keep
> getting Network is unreachable.
>
> Running gdb reveals the connect call is not working.
> After stepping over the connect, errno = 101
er 12, 1997 8:53 AM
To: debian-user@lists.debian.org
Cc: The recipient's address is unknown.
Subject:Socket question? Network unreachable
I have a simple socket program. I've compiled it with gcc on
Debian 1.1 (kernel 2.0.29) and Red Had (Biltmore 2.0.30) and I keep
get
I have a simple socket program. I've compiled it with gcc on
Debian 1.1 (kernel 2.0.29) and Red Had (Biltmore 2.0.30) and I keep
getting Network is unreachable.
Running gdb reveals the connect call is not working.
After stepping over the connect, errno = 101. "Network is unreachable" is
displaye
Carey Evans wrote:
>"Jason Bauer" <[EMAIL PROTECTED]> writes:
>
>> Today my linux started doing something screwy... I boot up and i get the
>> following error
>>
>> SIOCADDR: NETWORK UNREACHABLE
>
>Run "dmesg" and get the messages
"Jason Bauer" <[EMAIL PROTECTED]> writes:
> Today my linux started doing something screwy... I boot up and i get the
> following error
>
> SIOCADDR: NETWORK UNREACHABLE
Run "dmesg" and get the messages applying to your card. Does "lsmod"
show
Today my linux started doing something screwy... I boot up and i get the
following error
SIOCADDR: NETWORK UNREACHABLE
As far as I know i haven't done anything to my network settings.. i have
been playing with the sound module of the kernel but that shouldn't have
anything to do w
82 matches
Mail list logo
