On Saturday 18 July 2015 17:39:48 David Wright wrote:
> And ip's -o switch makes it even easier
> because each item is all on one line.
For some, possibly idiosyncratic, meanings of the word "easier". ;-)
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
On Sat, 18 Jul 2015, Dan Ritter wrote:
I find that a bizarre attitude.
I'm so sorry. I hope the experience was not too
uncomfortable for you. Please forgive me. I have many
personal shortcomings, and frequent descents into
bizarro-world figures prominently in any comprehensive
list of them
Quoting bri...@aracnet.com (bri...@aracnet.com):
> On Fri, 17 Jul 2015 19:25:45 -0500
> David Wright wrote:
>
> > Quoting John J. Boyer (john.bo...@abilitiessoft.org):
> > > Thanks for all of your answers. The problem was that ifconfig is in sbin
> > > not bin.
> >
> > I think you're better off
Patrick Wiseman writes:
> On Fri, Jul 17, 2015 at 2:25 PM, John J. Boyer
> wrote:
>> I have net-tools. ifconfig works only for root. WHY? On other distros
>> ordinary users can use it.
>
> You haven't been listening to what others have been telling you.
> ifconfig resides in sbin, which is in ro
"John J. Boyer" writes:
> Why isn't ifconfig available on Jessie? There id no package. The
> command produces an error message that it has not been found.
>
> John
>
> On Fri, Jul 17, 2015 at 01:44:35PM -0400, Miles Fidelman wrote:
>> John J. Boyer wrote:
>> >I have Jessie set up for CLI only. T
"John J. Boyer" writes:
> None of these solutions work. ifconfig is not available on Jessie. ip
> seems to be inapropriate. dig produces nothing. I have used ifconfig on
> other distros.
>
> John
>
> On Fri, Jul 17, 2015 at 05:41:27PM +0200, Elimar Riesebieter wrote:
>> * John J. Boyer [2015-0
bri...@aracnet.com a écrit :
>
> the output of ip is a bit of a mess.
>
> valid_lft forever preferred_lft forever
>
> what the hell ? i have no idea what tha means.
It is specific to IPv6 addresses. When an interface gets IPv6 addresses
assigned by stateless address autoconfiguration (SLAAC)
On 18/07/15 15:25, bri...@aracnet.com wrote:
the output of ip is a bit of a mess.
valid_lft forever preferred_lft forever
what the hell ? i have no idea what tha means. i know i'll do man ip, it's
probably
got an explanation. no. it doesn't.
It's saying that the valid and preferred remai
On Fri, 17 Jul 2015 19:25:45 -0500
David Wright wrote:
> Quoting John J. Boyer (john.bo...@abilitiessoft.org):
> > Thanks for all of your answers. The problem was that ifconfig is in sbin
> > not bin.
>
> I think you're better off forgetting about ifconfig and using ip in
> its place; that's th
On Fri, Jul 17, 2015 at 09:27:04PM -0400, Bob Bernstein wrote:
> On Fri, 17 Jul 2015, Martin G. McCormick wrote:
>
> >Yes but depending on how your path is set it may not simply work.
>
> NO.
>
> There ought to be no monkeying EVA with the default PATHs (for root
> and other users) created by th
Quoting Bob Bernstein (poo...@ruptured-duck.com):
> On Fri, 17 Jul 2015, David Wright wrote:
>
> >I think you're better off forgetting about ifconfig and using ip
> >in its place;
>
> Ach du Lieber Himmel! You will have to pry ifconfig out of my cold
> dead fingers!
>
> >that's the direction thi
On Fri, 17 Jul 2015, Martin G. McCormick wrote:
Yes but depending on how your path is set it may not
simply work.
NO.
There ought to be no monkeying EVA with the default
PATHs (for root and other users) created by the
authors of Linux and Unix. Period. (Which is why the
wheel group ought t
On Fri, 17 Jul 2015, Hans wrote:
If you know a little bit about the range of the
network (i.e. if you know at least , it is
192.168.), then you might try to scan the IP with a
direct connection to the network card.
Try nmap (either from a separate computer with a
crossover cable) on the c
On Fri, 17 Jul 2015, David Wright wrote:
I think you're better off forgetting about ifconfig
and using ip in its place;
Ach du Lieber Himmel! You will have to pry ifconfig
out of my cold dead fingers!
that's the direction things are heading.
Of course David I am no one to gainsay your ty
Quoting John J. Boyer (john.bo...@abilitiessoft.org):
> Thanks for all of your answers. The problem was that ifconfig is in sbin
> not bin.
I think you're better off forgetting about ifconfig and using ip in
its place; that's the direction things are heading. From Packages:
Package: iproute2
...
Miles Fidelman writes:
> ifconfig -a
> is always a good one
Yes but depending on how your path is set it may not simply work.
Martin McCormick
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive
On Friday 17 July 2015 18:49:59 John J. Boyer wrote:
> ip
> seems to be inapropriate.
Why is
$ip addr
inappropriate for finding out the IP address of an interface?
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas.
On Fri 17 Jul 2015 at 14:47:09 -0400, Cindy-Sue Causey wrote:
> On 7/17/15, Jape Person wrote:
> >
> > I think ifconfig isn't a package.
> >
> > By default on my Jessie systems it's under /sbin.
> >
> > If
> >
> > $ ifconfig -a
> >
> > doesn't work, then
> >
> > $ /sbin/ifconfig -a
> >
> > probab
On 7/17/15, Jape Person wrote:
>
> I think ifconfig isn't a package.
>
> By default on my Jessie systems it's under /sbin.
>
> If
>
> $ ifconfig -a
>
> doesn't work, then
>
> $ /sbin/ifconfig -a
>
> probably will.
Ah-HA! I usually remember to try going that route if something
suggested here does
On Fri 17 Jul 2015 at 13:25:35 -0500, John J. Boyer wrote:
> I have net-tools. ifconfig works only for root. WHY? On other distros
> ordinary users can use it.
That's a change of tack! It started with "I cannot find a file but on
other distros users are more capable" and has now become "ifconfig
On Fri, Jul 17, 2015 at 2:25 PM, John J. Boyer
wrote:
> I have net-tools. ifconfig works only for root. WHY? On other distros
> ordinary users can use it.
You haven't been listening to what others have been telling you.
ifconfig resides in sbin, which is in root's but not the ordinary
user's path
> I have Jessie set up for CLI only. […]
> What command will tell me what ip address it is using?
ip address works fine:
ip address show scope global | sed -r -n 's|^ *inet6? ([^ /]*).*$|\1|p'
--
Gabriel
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of
I have net-tools. ifconfig works only for root. WHY? On other distros
ordinary users can use it.
John
On Fri, Jul 17, 2015 at 08:01:29PM +0200, Simon Brandmair wrote:
> Hi,
>
> On 07/17/2015 07:50 PM, John J. Boyer wrote:
> > None of these solutions work. ifconfig is not available on Jessie. ip
> Am 17.07.2015 um 19:57 schrieb "John J. Boyer" :
>
> Why isn't ifconfig available on Jessie? There id no package. The
> command produces an error message that it has not been found.
>
> John
>
>> On Fri, Jul 17, 2015 at 01:44:35PM -0400, Miles Fidelman wrote:
>> John J. Boyer wrote:
>>> I ha
On Fri 17 Jul 2015 at 12:57:37 -0500, John J. Boyer wrote:
> Why isn't ifconfig available on Jessie? There id no package. The
> command produces an error message that it has not been found.
brian@desktop:~$ dpkg -S ifconfig
net-tools: /usr/share/man/pt_BR/man8/ifconfig.8.gz
net-tools: /usr/share
On 07/17/2015 01:49 PM, John J. Boyer wrote:
None of these solutions work. ifconfig is not available on Jessie. ip
seems to be inapropriate. dig produces nothing. I have used ifconfig on
other distros.
John
I think ifconfig isn't a package.
By default on my Jessie systems it's under /sbin.
I
Hi,
On 07/17/2015 07:50 PM, John J. Boyer wrote:
> None of these solutions work. ifconfig is not available on Jessie. ip
> seems to be inapropriate. dig produces nothing. I have used ifconfig on
> other distros.
ifconfig is available if you install net-tools.
And what do you mean with "ip seems
On 17/07/15 18:49, John J. Boyer wrote:
None of these solutions work. ifconfig is not available on Jessie. ip
seems to be inapropriate. dig produces nothing. I have used ifconfig on
other distros.
I'm using DHCP at home, and it appears to me that the answer Lisi Reisz
kindly provided you with
Am Freitag, 17. Juli 2015, 12:49:59 schrieb John J. Boyer:
> None of these solutions work. ifconfig is not available on Jessie. ip
> seems to be inapropriate. dig produces nothing. I have used ifconfig on
> other distros.
>
> John
Hi John,
just an idea.
If you know a little bit about the range
Why isn't ifconfig available on Jessie? There id no package. The
command produces an error message that it has not been found.
John
On Fri, Jul 17, 2015 at 01:44:35PM -0400, Miles Fidelman wrote:
> John J. Boyer wrote:
> >I have Jessie set up for CLI only. The machine is on a local network
> >us
Le 17/07/2015 19:49, John J. Boyer a écrit :
> None of these solutions work. ifconfig is not available on Jessie. ip
> seems to be inapropriate. dig produces nothing. I have used ifconfig on
> other distros.
>
> John
>
> On Fri, Jul 17, 2015 at 05:41:27PM +0200, Elimar Riesebieter wrote:
>> * Joh
None of these solutions work. ifconfig is not available on Jessie. ip
seems to be inapropriate. dig produces nothing. I have used ifconfig on
other distros.
John
On Fri, Jul 17, 2015 at 05:41:27PM +0200, Elimar Riesebieter wrote:
> * John J. Boyer [2015-07-17 08:32 -0500]:
>
> > I have Jessie
John J. Boyer wrote:
I have Jessie set up for CLI only. The machine is on a local network
using dhcp. What command will tell me what ip address it is using?
Thanks,
John
ifconfig -a
is always a good one
--
In theory, there is no difference between theory and practice.
In practice, there is.
On Jul 17, 2015 11:53 AM, "Elimar Riesebieter" wrote:
>
> * John J. Boyer [2015-07-17 08:32 -0500]:
>
> > I have Jessie set up for CLI only. The machine is on a local network
> > using dhcp. What command will tell me what ip address it is using?
>
> $ dig +short `hostname -f`
>
Won't always wor
* John J. Boyer [2015-07-17 08:32 -0500]:
> I have Jessie set up for CLI only. The machine is on a local network
> using dhcp. What command will tell me what ip address it is using?
$ dig +short `hostname -f`
Elimar
--
The path to source is always uphill!
-un
John J. Boyer writes:
I have Jessie set up for CLI only. The machine is on a local
network using dhcp. What command will tell me what ip address
it is using?
$ ip addr
Alexis.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
On Fri 17 Jul 2015 at 08:32:59 -0500, John J. Boyer wrote:
> I have Jessie set up for CLI only. The machine is on a local network
> using dhcp. What command will tell me what ip address it is using?
ifconfig -a
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject o
On Friday 17 July 2015 14:32:59 John J. Boyer wrote:
> I have Jessie set up for CLI only. The machine is on a local network
> using dhcp. What command will tell me what ip address it is using?
$ ip addr
HTH
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject o
Hi,
On 07/17/2015 03:32 PM, John J. Boyer wrote:
> I have Jessie set up for CLI only. The machine is on a local network
> using dhcp. What command will tell me what ip address it is using?
ifconfig ?
Kind regards,
--
“One original thought is worth a thousand mindless quotings.”
“Le vrai n'est
Darac Marjal wrote:
> The problem that I have is that the ip address that the workstation
> gets at boot has a finite "valid_lft" (as seen in `ip a`). When this
> lifetime runs out, the IP is removed from the interface. Now, I
> think DHCP does try to pick up at that point, but the root file
> syst
On 7/17/14, rajiv chavan wrote:
> Thu, 17 Jul 2014 13:21:19 +0530
>
> Mett:
>
> Modem has ports 23,80,5431. Ssh may not be an option.
>
>
>
> On 7/15/14, mett wrote:
>> On Mon, 14 Jul 2014 22:33:11 +0530
>> rajiv chavan wrote:
>>
>>> On Mon, 14 Jul 2014 07:53:06 +0530
>>> - Hide quoted text -
>>
Thu, 17 Jul 2014 13:21:19 +0530
Mett:
Modem has ports 23,80,5431. Ssh may not be an option.
On 7/15/14, mett wrote:
> On Mon, 14 Jul 2014 22:33:11 +0530
> rajiv chavan wrote:
>
>> On Mon, 14 Jul 2014 07:53:06 +0530
>> - Hide quoted text -
>> rajiv chavan wrote:
>>
>> > Mon, 14 Jul 2014 07:2
On Mon, 14 Jul 2014 22:33:11 +0530
rajiv chavan wrote:
> On Mon, 14 Jul 2014 07:53:06 +0530
> - Hide quoted text -
> rajiv chavan wrote:
>
> > Mon, 14 Jul 2014 07:26:20 +0530
> >
> > Thank you Mett.
> > Traceroute packets from another host dropped by ISP netwoek at
> > 218.248.0.0
> >
> > >nets
On Mon, 14 Jul 2014 07:53:06 +0530
rajiv chavan wrote:
> Mon, 14 Jul 2014 07:26:20 +0530
>
> Thank you Mett.
> Traceroute packets from another host dropped by ISP netwoek at
> 218.248.0.0
>
> >netstat -rn
>
> Destination Gateway Genmask Flags MSS Window
> irtt Iface 0.0.0
On Mon, 14 Jul 2014 00:31:43 +0530
rajiv chavan wrote:
> Sun, 13 Jul 2014 23:34:41 +0530
>
> ip a output on an adsl+ (pppoe) client:
> =snip=
> 2: eth0: mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
> inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0
> 3: ppp0: mtu 1
On 06/10/11 20:30, Ireneusz Szcześniak wrote:
Student bring their laptops and get the ethernet cable from the lab
computers. They do it frantically a few times, and the desktop interface
gets this address.
Personally, I would set up a wireless interface for student's laptops.
Then, LART any s
Ireneusz Szcześniak wrote:
> Thank you, Chris, for the idea. The IP addresses would be randomly
> distributed, while I would like to keep them in a contiguous range.
That's fine; I suspect the earlier suggestion would suit you better.
Chris
--
To UNSUBSCRIBE, email to debian-user-requ...@lis
On 2011-10-06, Ireneusz Szcześniak wrote:
> On 06.10.2011 00:08, Liam O'Toole wrote:
>> Yet another option is to configure clients to send their hostname in the
>> DHCP request. The hostnames will register with dnsmasq's DNS resolver,
>> so you can connect to the clients by hostname rather than IP
On Thu, Oct 06, 2011 at 07:30:00PM BST, Ireneusz Szcześniak wrote:
> On 06.10.2011 08:56, Raf Czlonka wrote:
> > What do you mean by "falls back to a random IP address"?
>
> The interface is assigned an address in the range 169.254.0.0/16.
Remove the package which assigns those IP addresses, e.g.
On 06.10.2011 08:56, Raf Czlonka wrote:
> What do you mean by "falls back to a random IP address"?
The interface is assigned an address in the range 169.254.0.0/16.
> What purpose unplugging the PC from the network has?
> Is it part of the lab?
Student bring their laptops and get the ethernet
On Thu, Oct 06, 2011 at 06:13:04AM BST, Ireneusz Szcześniak wrote:
> This is what I have already done, but the static lease doesn't
> protect me from the "unplugging problem" and the behaviour of
> dhclient. I haven't looked into the config of dhclient yet, but
> reconfiguring it so that it keeps
On 06.10.2011 00:08, Liam O'Toole wrote:
On 2011-10-05, Raf Czlonka wrote:
On Wed, Oct 05, 2011 at 08:59:08PM BST, Ireneusz Szcześniak wrote:
The computers are in a university laboratory, where students often
unplug the lan cable. Then they plug the cable again after some
time, and unplug aga
On 05.10.2011 23:15, Raf Czlonka wrote:
On Wed, Oct 05, 2011 at 08:59:08PM BST, Ireneusz Szcześniak wrote:
The computers are in a university laboratory, where students often
unplug the lan cable. Then they plug the cable again after some
time, and unplug again.
The problem with this plugging a
On 2011-10-05, Raf Czlonka wrote:
> On Wed, Oct 05, 2011 at 08:59:08PM BST, Ireneusz Szcześniak wrote:
>> The computers are in a university laboratory, where students often
>> unplug the lan cable. Then they plug the cable again after some
>> time, and unplug again.
>>
>> The problem with this p
On Wed, Oct 05, 2011 at 08:59:08PM BST, Ireneusz Szcześniak wrote:
> The computers are in a university laboratory, where students often
> unplug the lan cable. Then they plug the cable again after some
> time, and unplug again.
>
> The problem with this plugging and unplugging is that when the
>
Thank you, Chris, for the idea. The IP addresses would be randomly
distributed, while I would like to keep them in a contiguous range.
On 03.10.2011 18:52, Chris Davies wrote:
Javier Barroso wrote:
If you know which macs you will have, you can make an init script
which generate /etc/network/
On 03.10.2011 12:38, Darac Marjal wrote:
I'm not sure about hostname but there IS a way to assign a static IP
address to an interface based on it's MAC address. It's called StateLess
Address Autoconfiguration (SLAAC). Basically, you take the 48-bit mac
address, modify it a little (mainly adding
On 03.10.2011 09:43, Scott Ferguson wrote:
If you have a large number of identical hardware machines to image - a
multicast solution that allows defining build rules (ie static network
addresses, hostname, /etc/host, passwords, usernames, network shares and
logons etc)
might save time and make m
On 03.10.2011 01:36, Liam O'Toole wrote:
Could you elaborate on why you can't use a DHCP server? I ask this
because you can set up dnsmasq to assign a fixed IP address to a client
based on its hostname or MAC address, and to give clients an infinite
lease. Therefore it offers a convenient way to
On 02.10.2011 22:37, Raf Czlonka wrote:
I was about to suggest preseeding as well - works great if you combine
it with pxelinux, even if you need to set up a DHCP server on a small
subnet only for that purpose. But if it doesn't, your option is a
script - try some scripts/rules from ifupdown* pa
On 02.10.2011 21:19, Camaleón wrote:
True, I wasn't clear enough. Ideally, I would like to have a config
file that would list MAC addresses and IP addresses that these NICs
should have.
Hum... if I understood you correctly, you want to "dump" a previously
generated ISO image into a set of com
Javier Barroso wrote:
> If you know which macs you will have, you can make an init script
> which generate /etc/network/interface and /etc/hostname and /etc/hosts
> the first boot and then remove itself.
You don't even need to know in advance the MACs as long as enough of
the address is unique.
On Sun, Oct 02, 2011 at 06:31:59PM +0200, Ireneusz Szcześniak wrote:
> Hi,
>
> I'm planning to install an image of Debian to a number of computers.
> Each of these computers will have the same configuration except the
> hostname and the IP address. The IP configuration has to be static.
> I can't
On 03/10/11 03:31, Ireneusz Szcześniak wrote:
> Hi,
>
> I'm planning to install an image of Debian to a number of computers.
> Each of these computers will have the same configuration except the
> hostname and the IP address. The IP configuration has to be static.
> I can't use a DHCP server.
>
On Sunday 02 October 2011 19:08:26 Ireneusz Szcześniak wrote:
> As I mentioned before, I
> can't use a DHCP server.
Ah, sorry. I missed that. Ignore the noise from me!
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm
On Sunday 02 October 2011 17:31:59 Ireneusz Szcześniak wrote:
> QUESTION; Is there a way to assign a hostname and a static IP address
> at boot time depending on the MAC address of the computer's network
> interface card?
I can do this via my router if I wish, and set the computer up with dhcp. I
On 2011-10-02, Ireneusz Szcześniak wrote:
> Dnsmasq is a DHCP and DNS server combined. As I mentioned before, I
> can't use a DHCP server.
>
> On 02.10.2011 20:02, H.S. wrote:
>> On 02/10/11 12:31 PM, Ireneusz Szcześniak wrote:
>>> Hi,
>>>
>>> I'm planning to install an image of Debian to a numb
On 02/10/11 02:08 PM, Ireneusz Szcześniak wrote:
> Dnsmasq is a DHCP and DNS server combined. As I mentioned before, I
> can't use a DHCP server.
>
> On 02.10.2011 20:02, H.S. wrote:
>> On 02/10/11 12:31 PM, Ireneusz Szcześniak wrote:
>>> Hi,
>>>
>>> I'm planning to install an image of Debian to
On Sun, Oct 02, 2011 at 05:31:59PM BST, Ireneusz Szcześniak wrote:
> I'm planning to install an image of Debian to a number of computers.
> Each of these computers will have the same configuration except the
> hostname and the IP address. The IP configuration has to be static.
> I can't use a DHCP
On Sun, 02 Oct 2011 20:06:45 +0200, Ireneusz Szcześniak wrote:
> On 02.10.2011 19:31, Camaleón wrote:
>
>> On Sun, 02 Oct 2011 18:31:59 +0200, Ireneusz Szcześniak wrote:
>>
>>> I'm planning to install an image of Debian to a number of computers.
>>> Each of these computers will have the same conf
Javier, thank you for your input. It seems that your solution should
work. The file /etc/network/interfaces should only be modified early
enough. I will give it a try!
Thank you again!
On 02.10.2011 20:52, Javier Barroso wrote:
Hello,
2011/10/2 Ireneusz Szcześniak:
Hi,
I'm planning to i
Hello,
2011/10/2 Ireneusz Szcześniak :
> Hi,
>
> I'm planning to install an image of Debian to a number of computers. Each of
> these computers will have the same configuration except the hostname and the
> IP address. The IP configuration has to be static. I can't use a DHCP
> server.
>
> QUESTI
On 02/10/11 12:31 PM, Ireneusz Szcześniak wrote:
> The IP configuration has to be static. I can't use a DHCP server.
H.S. wrote at 2011-10-02 13:02 -0500:
> I use dnsmasq for exactly this purpose (my home lan is quite small
> though). Works quite well.
dnsmasq is a DHCP server, which the original
Dnsmasq is a DHCP and DNS server combined. As I mentioned before, I
can't use a DHCP server.
On 02.10.2011 20:02, H.S. wrote:
On 02/10/11 12:31 PM, Ireneusz Szcześniak wrote:
Hi,
I'm planning to install an image of Debian to a number of computers.
Each of these computers will have the same c
Camaleón, thank you for your input. However, I don't want to install
the system from scratch, but to clone a previously prepared image.
True, I wasn't clear enough. Ideally, I would like to have a config
file that would list MAC addresses and IP addresses that these NICs
should have.
On 02.
On 02/10/11 12:31 PM, Ireneusz Szcześniak wrote:
> Hi,
>
> I'm planning to install an image of Debian to a number of computers.
> Each of these computers will have the same configuration except the
> hostname and the IP address. The IP configuration has to be static. I
> can't use a DHCP server.
On Sun, 02 Oct 2011 18:31:59 +0200, Ireneusz Szcześniak wrote:
> I'm planning to install an image of Debian to a number of computers.
> Each of these computers will have the same configuration except the
> hostname and the IP address. The IP configuration has to be static. I
> can't use a DHCP se
On Jo, 29 iul 10, 15:54:12, Jozsi Vadkan wrote:
> TEST-A.txt: list of ip address ranges [AS/isp's in a country]
> TEST-B.txt: list of ip addresses
>
> I just need to know, if an ip in the TEST-B.txt is in a range of
> TEST-A.txt
>
> cat "TEST-A.txt"
> 63.31.63.0/24;9007;44536
> 64.65.0.0/19;9000;
On Sat, 2007-01-13 at 00:29 +, Alan Chandler wrote:
> On Friday 12 January 2007 18:00, Greg Folkert wrote:
> > On Fri, 2007-01-12 at 09:44 +0200, Justin Hartman wrote:
> > [...snip...]
> >
> > > Without making a single change to the interfaces file I issued a
> > > /etc/init.d/networking restar
On Friday 12 January 2007 18:00, Greg Folkert wrote:
> On Fri, 2007-01-12 at 09:44 +0200, Justin Hartman wrote:
> [...snip...]
>
> > Without making a single change to the interfaces file I issued a
> > /etc/init.d/networking restart command and low and behold my
> > network just went down again wit
On Fri, 2007-01-12 at 09:44 +0200, Justin Hartman wrote:
[...snip...]
> Without making a single change to the interfaces file I issued a
> /etc/init.d/networking restart command and low and behold my network
> just went down again with no access to the server so now I'm wondering
> if this has to d
On 1/12/07, Alan Chandler wrote:
I don't think that is an issue. My /etc/network/interfaces file
follows. Essentially this machine is my router connecting via eth0 to
the internet (and using dhcp from my ISP to get me an IP address - and
prerunning the firewall as it comes up) on the lan side a
On Friday 12 January 2007 02:00, Andrew Sackville-West wrote:
> On Fri, Jan 12, 2007 at 03:04:08AM +0200, Justin Hartman wrote:
> > On 1/12/07, Michael Bellears
> >
> > <[EMAIL PROTECTED]> wrote:
> > >Bahfat fingers! Try auto eth0:0
> >
> > The problem with auto eth0:0 is that last time I did t
On 1/12/07, Andrew Sackville-West wrote:
I believe that when you brought this up before you were told that eth0
and eth0.0 are the same thing and that was the problem. you need
either eth0 and eth0.1 or eth0.0 and eth0.1. If it wasn't you,
sorry. :)
Yes this was me who originally brought this u
On Fri, Jan 12, 2007 at 03:04:08AM +0200, Justin Hartman wrote:
> On 1/12/07, Michael Bellears
> <[EMAIL PROTECTED]> wrote:
> >Bahfat fingers! Try auto eth0:0
>
> The problem with auto eth0:0 is that last time I did this and I ran a
> networking restart I completely shut down my server from ex
On 1/12/07, Michael Bellears
<[EMAIL PROTECTED]> wrote:
Bahfat fingers! Try auto eth0:0
The problem with auto eth0:0 is that last time I did this and I ran a
networking restart I completely shut down my server from external
access. I had to get the datacenter to remove the auto and then I
c
>
> Yes - Add:
>
> auto eth0:1
Bahfat fingers! Try auto eth0:0
> Ok this setup in the /etc/network/interfaces file is working great.
> One problem however is if I restart the machine the eth0:0
> doesn't load at runtime and i have to manually run ifup
> eth0:0 before the interface loads.
>
> Is there any way to ensure that the eth0:0 loads at boot time?
Ye
On 1/4/07, Larry Irwin <[EMAIL PROTECTED]> wrote:
Forget my last email... too quick on the keyboard...
The "auto" declaration is for physical interfaces only...
It should have looked like this when you were done:
#Physical interface
auto eth0
#Base address
iface eth0 inet static
address 7
Forget my last email... too quick on the keyboard...
The "auto" declaration is for physical interfaces only...
It should have looked like this when you were done:
#Physical interface
auto eth0
#Base address
iface eth0 inet static
address 70.87.206.50
netmask 255.255.255.0
gatewa
On Thursday, January 04, 2007 Justin Hartman wrote:
Currently my /etc/network/interfaces is configured as:
auto eth0
iface eth0 inet static
address 70.87.206.50
netmask 255.255.255.0
gateway 70.87.206.49
I thought that adding the following would allow me to assign and use
the
Quoting Stephen Cormier <[EMAIL PROTECTED]>:
It is working, thanks.
I remark out the "auto eth0" in the Primary network interface thinking it had
to do with the dhcp settings for the nic.
Thanks again.
Fernando
On October 14, 2005 02:00 am, [EMAIL PROTECTED] wrote:
Use this.
# The loopback ne
On October 14, 2005 02:00 am, [EMAIL PROTECTED] wrote:
Use this.
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
# Iface eth0 inet dhcp
iface eth0 inet static
address 192.168.0.110
netmask 255.255.255.0
gateway 192.168.0
[EMAIL PROTECTED] wrote:
> Quoting Kent West <[EMAIL PROTECTED]>:
> I already did these steps, I rebooted the computer and run ifconfig, but
> nothing, I didn't get the information for the nic. What is wrong?
> thanks again
Please post the output of "ifconfig" and the contents of your
"/etc/netwo
[EMAIL PROTECTED] wrote:
>Hi,
>I just installed Debian Sarge, and by mistake I configured the NIC to DHCP. I
>don't want DHCP, how can I change the ip address from DHCP to a permanent
>static ip address? I tried already ifconfig eth0 ipaddress, it works, but the
>change is just temporary. When I r
On Fri, 10 Jun 2005 19:20:10 +0200, Phil Dyer wrote:
> The other way would be to edit /etc/dhclient.conf and tell it to prepend
> to the list of dns servers
>
> prepend domain-name-servers x.x.x.x;
Or there's the supersede option in dhclient.conf which makes
resolv.conf only contain whatever you p
Paul Johnson writes:
> But they're not modems, they're bridges or routers.
They contain DSL modems in addition to bridges and/or routers. Look up how
DSL works.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Friday June 10 2005 8:52 am, David Nicholls wrote:
> gpgkeys: key EB6AF9F2ED602A59 not found on keyserver
> Hi,
>
> I've got a few Debian (sarge) boxes connected to isp's via either
> ADSL modems (dlink dsl-300t's) or with a internal pci adsl modems.
That's nice. But they're not modems, they'r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Nicholls said:
> I've been having a few problems with dns lookups and have been given a
> new set up dns servers and not the same ones placed into resolv.conf by
> dhcp.
>
> Obviously if I make a change to resolv.conf, it will be soon-after be
>
Harland Christofferson wrote:
I am slowly working toward a vpn between the office and home. I now
have to change my lan at work so as not to conflict w/ the lan at
home.
at work, i reconfigured my eth1 interface:
eth1 192.168.2.1 255.255.254.0
eth1:0 192.168.1.1 255.255.255.0
the
1 - 100 of 114 matches
Mail list logo
