Re: Network configuration

[john doe]

On 8/6/2018 9:15 PM, Ilyass Kaouam wrote:

# Generated by NetworkManager



Ok -- The app "NetworkManager" is managing your interfaces.

To deal with NetworkManager through the CLI and config files you will 
need to do some reading:


https://developer.gnome.org/NetworkManager/stable/nm-settings-keyfile.html
https://developer.gnome.org/NetworkManager/stable/NetworkManager.conf.html
https://arstechnica.com/civis/viewtopic.php?t=1163023

--
John Doe

Re: Network configuration

[Ilyass Kaouam]

Thank's John :) :)

Le lun. 6 août 2018 à 21:40, john doe  a écrit :

> On 8/6/2018 9:15 PM, Ilyass Kaouam wrote:
> > # Generated by NetworkManager
> >
>
> Ok -- The app "NetworkManager" is managing your interfaces.
>
> To deal with NetworkManager through the CLI and config files you will
> need to do some reading:
>
> https://developer.gnome.org/NetworkManager/stable/nm-settings-keyfile.html
> https://developer.gnome.org/NetworkManager/stable/NetworkManager.conf.html
> https://arstechnica.com/civis/viewtopic.php?t=1163023
>
> --
> John Doe
>
>

-- 
*Ilyass kaouam*
*Systems administrator*
* Mastère européen Manager de Projets Informatiques*

Re: Network configuration

[Ilyass Kaouam]

# Generated by NetworkManager

nameserver 8.8.8.8

Le lun. 6 août 2018 à 14:01, john doe  a écrit :

> On 8/6/2018 12:12 PM, Ilyass Kaouam wrote:
> > I configured my network here (see attached picture please)
> >
> > [image: Capture d’écran 2018-08-06 à 12.12.06.png]
> >
>
> I don't have access to images.
> What is the output of:
>
> $ cat /etc/resolv.conf
>
> --
> John Doe
>
>

-- 
*Ilyass kaouam*
*Systems administrator*
* Mastère européen Manager de Projets Informatiques*

Re: Network configuration

[john doe]

On 8/6/2018 12:12 PM, Ilyass Kaouam wrote:

I configured my network here (see attached picture please)

[image: Capture d’écran 2018-08-06 à 12.12.06.png]



I don't have access to images.
What is the output of:

$ cat /etc/resolv.conf

--
John Doe

Re: Network configuration

[john doe]

On 8/6/2018 11:16 AM, Ilyass Kaouam wrote:

Thank you for all your reply,

I configured the network via the GUI during installation, the network works
perfectly.
I just want to know if I want to change the address or ..., without going
through the GUI, where I can make my changes, knowing that the



To answer that question we/you need to know what app is configuring your 
interfaces.

Then you can reed how to configure that app through CLI/config file.

--
John Doe

Re: Network configuration

[Ilyass Kaouam]

Thank you for all your reply,

I configured the network via the GUI during installation, the network works
perfectly.
I just want to know if I want to change the address or ..., without going
through the GUI, where I can make my changes, knowing that the

/etc/network/interfaces file does not contain my configuration :

# This file describes the network interfaces available on your system

# and how to activate them. For more information, see interfaces(5).


source /etc/network/interfaces.d/*


# The loopback network interface

auto lo

iface lo inet loopback

Le lun. 6 août 2018 à 10:30, Curt  a écrit :

> On 2018-08-06, Joe  wrote:
> > On Mon, 6 Aug 2018 04:01:44 -0400
> > Jude DaShiell  wrote:
> >
> >> If you do a command line install with no graphics, you end up with no
> >> network configuration once installation completes.
> >
> > Not in my experience.
> >
> > At one time, if you did a non-expert install with no network DHCP
> > server, then you got no networking, even after a netinstall. It bit me
> > around the time of etch or lenny. I've no idea if it's still true today.
> >
>
> I think there's only one Brian over there in the UK somewhere, and here's
> what
> he said a year back that pertains (if the bug still kicks) to whatever it
> is we're talking about here (in the interests of precision and clarity):
>
>  netcfg sets up the network during installation and writes a temporary
>  /e/n/i stanza. If a user installs a DE and n-m is installed the stanza
>  is not copied to /target, the assumption being, I suppose, that the user
>  would want n-m to handle the network. This happens when either a wired
>  or wireless connection is used to install.
>
>  If the user uses a cabled connection but does not select a DE the stanza
>  is copied to /target.
>
>  If a user has a wireless connection but does not select a DE the stanza
>  is not copied to /target but rewritten to contain loopback only and then
>  copied over. On first boot there is no external connectivity. Your guess
>  is as good as mine why a wireless installation is treated differently
>  from a cabled one. I have never seen any adequate justification for
>  denying external connectivity in this circumstance.
>
> So it is the experience of wireless people, I guess.
>
> --
> Some years ago, when the images which this world affords first opened upon
> me,
> when I felt the cheering warmth of summer and heard the rustling of the
> leaves
> and the warbling of the birds, and these were all to me, I should have
> wept to
> die; now it is my only consolation. --Mary Shelley, Frankenstein; or, The
> Modern Prometheus
>
>

-- 
*Ilyass kaouam*
*Systems administrator*
* Mastère européen Manager de Projets Informatiques*

Re: Network configuration

[Curt]

On 2018-08-06, Joe  wrote:
> On Mon, 6 Aug 2018 04:01:44 -0400
> Jude DaShiell  wrote:
>
>> If you do a command line install with no graphics, you end up with no
>> network configuration once installation completes.
>
> Not in my experience.
>
> At one time, if you did a non-expert install with no network DHCP
> server, then you got no networking, even after a netinstall. It bit me
> around the time of etch or lenny. I've no idea if it's still true today.
>

I think there's only one Brian over there in the UK somewhere, and here's what
he said a year back that pertains (if the bug still kicks) to whatever it
is we're talking about here (in the interests of precision and clarity):

 netcfg sets up the network during installation and writes a temporary
 /e/n/i stanza. If a user installs a DE and n-m is installed the stanza
 is not copied to /target, the assumption being, I suppose, that the user
 would want n-m to handle the network. This happens when either a wired
 or wireless connection is used to install.

 If the user uses a cabled connection but does not select a DE the stanza
 is copied to /target.

 If a user has a wireless connection but does not select a DE the stanza
 is not copied to /target but rewritten to contain loopback only and then
 copied over. On first boot there is no external connectivity. Your guess
 is as good as mine why a wireless installation is treated differently
 from a cabled one. I have never seen any adequate justification for
 denying external connectivity in this circumstance.

So it is the experience of wireless people, I guess.

-- 
Some years ago, when the images which this world affords first opened upon me,
when I felt the cheering warmth of summer and heard the rustling of the leaves
and the warbling of the birds, and these were all to me, I should have wept to
die; now it is my only consolation. --Mary Shelley, Frankenstein; or, The 
Modern Prometheus

Re: Network configuration

[Joe]

On Mon, 6 Aug 2018 04:01:44 -0400
Jude DaShiell  wrote:

> If you do a command line install with no graphics, you end up with no
> network configuration once installation completes.

Not in my experience.

At one time, if you did a non-expert install with no network DHCP
server, then you got no networking, even after a netinstall. It bit me
around the time of etch or lenny. I've no idea if it's still true today.

-- 
Joe

Re: Network configuration

[Jude DaShiell]

If you do a command line install with no graphics, you end up with no
network configuration once installation completes.I left some writing on
wiki.debian.org for how to configure wifi to work for command line
installs on post-install boot and that uses ifup and ifdown.  I don't
know what happened to the text on that site since I put it up in pure
ascii without any markup editing.  If need be, I think I can find it
among my files here.
On Mon, 6 Aug 2018, john doe wrote:

> Date: Mon, 6 Aug 2018 02:02:52
> From: john doe 
> To: debian-user@lists.debian.org
> Subject: Re: Network configuration
> Resent-Date: Mon,  6 Aug 2018 06:03:15 + (UTC)
> Resent-From: debian-user@lists.debian.org
>
> On 8/6/2018 1:53 AM, Ilyass Kaouam wrote:
> > If I choose to configure the network during installation, where can I
> > configure the network after?
> > on which file, because in /etc/network/interfaces I don't see the ip
> > address, subnetwork ...
> >
>
> It depends which pkg you choose to install during installation.
> If you selected a desktop manager (gnome, mate ...) it is most likely that
> NetworkManager (NM), WICD or or similar apps is installed.
>
> For some hints of what is configuring your interfaces you might look at the
> top of:
>
> /etc/resolv.conf
>
>

-- 

Re: Network configuration

[john doe]

On 8/6/2018 1:53 AM, Ilyass Kaouam wrote:

If I choose to configure the network during installation, where can I
configure the network after?
on which file, because in /etc/network/interfaces I don't see the ip
address, subnetwork ...



It depends which pkg you choose to install during installation.
If you selected a desktop manager (gnome, mate ...) it is most likely 
that NetworkManager (NM), WICD or or similar apps is installed.


For some hints of what is configuring your interfaces you might look at 
the top of:


/etc/resolv.conf

--
John Doe

Re: network configuration

[notoneofmyseeds]

On 06/26/2015 05:13 AM, Bob Proulx wrote:

notoneofmyseeds wrote:

>Bob Proulx wrote:
>
>I must say you have written a book here on this topic, Rob. I've learned a
>lot. I printed it out. To your questions now.

Sometimes people say I write too much.  But the details are important.:-)
And this is a large book again with this message.
Thank you very much. I must say your responses have changed the way I 
attend to reading forum posts. As is common, folks will skim through, 
looking for a solution in a response. With yours, it's been very 
different. I print them and read them away from the computer and all the 
distractions. And as such I walk away more informed, and at times, my 
problem becomes secondary, as I try to read, re-read and look for areas 
to pursue, based on your writings, that will make me learn some more. 
One thing with Linux is that there's so much going on, one needs the 
discipline to focus on specific issues; that could be what one is trying 
to accomplish at the moment, or a find a target interest. I feel like 
both has happened in this thread. To be honest, reading your posts makes 
me feel like, hey, I should invite this guy over for tea on Sunday 
evenings, sit out and just talk; no computers around, just share ideas 
and gain knowledge. Such, also, is the tone of your writing.

>I had a very long and nice response that I lost, as a result of an
>application crash.

LOL!  I have been there many times myself!:-)

I've tried this time to ensure it does not happen again.

I am merging two messages from you so I can answer both here at the
same time.


> >   ip addr show

>2: eth0:  mtu 1500 qdisc mq state UP group 
default qlen 1000
> inet 192.168.1.2/24 brd 192.168.1.255 scope global dynamic eth0
>3: wlan0:  mtu 1500 qdisc mq state UP group 
default qlen 1000
> inet 10.10.10.6/24 brd 10.10.10.255 scope global dynamic wlan0

Gotcha.  Although 192.168.1.2 is an unusual address to get from dhcp.
It would help to see the dhcp range the server issues.

And the other eth0 network is:


>2: eth0:  mtu 1500 qdisc mq state UP group 
default qlen 1000
> inet 172.16.1.0/24 brd 172.16.1.255 scope global dynamic eth0
>3: wlan0:  mtu 1500 qdisc mq state UP group 
default qlen 1000
> inet 10.10.10.5/24 brd 10.10.10.255 scope global wlan0

Again the 172.16.1.0 is an unusual address to get from dhcp.  That is
the network address and I don't think this is correct.  Have you
modified the dhcpd server configuration on that network to include the
entire range?

I think the next thing to start debugging is the dhcp server
configuration on each of those networks.  Change the range to
something in the middle such as from 192.168.1.100-192.168.1.200 and
from 172.16.1.100-172.16.1.200 or some such range that does not
include the .0 network address and does not include the .255 broadcast
address.  Don't assign those as host addresses.
We won't need to debug the dhcp servers on the two routers, as I've set 
them to defaults, with very changes, such as changing the ip range for 
one of them. I will get back to this later. I've changed quite a bit 
around here, starting from scratch with dhcp; all set back to defaults, 
with few modifications, such as ip address change. This, just to hone in 
some more.

> >   ip route show | tac

>172.16.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.2
>169.254.0.0/16 dev wlan0  scope link  metric 1000
>10.10.10.0/24 via 10.0.0.1 dev wlan0  proto static  metric 1
>10.10.10.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.5
>default via 172.16.1.1 dev eth0  proto static  metric 1024

The route table is very telling of the problem.  I think in this state
the wifi was connected first and then the wired network was connected
afterward.  The wired network dhcp replaced the default route with its
own route default default via 172.16.1.1 dev eth0.  That is the only
route listed in the above.  It won't be out your wifi interface.  If
your wifi interface is the only one with a route to the Internet then
obviously the above won't work.
I don't think it's the case that the wifi connects first, because I look 
at the hardware light as the laptop boots and it does not come on until 
much later. So I think the wired gets the default routes, as I presume 
it first to 'get there' and keep that route. The wifi interface is the 
only network with a router to the Internet.

You could probably do a manual repair with:

   ip route replace default via 10.10.10.1 dev wlan0

I will respond to this later...

Aftering bringing up the wired interface, which will break the route,
the above would restore the working route out the wlan0 interface.
This is only a temporary measure.  It is temporary because the
dhclient daemon will renew the dhcp lease and every time it does it
will rewrite the default route and break things again.  But it would
probably assure you that this is exactly the problem and that things
can work with the right configuration.


> >Another question.  Are 

Re: network configuration

[Lisi Reisz]

On Friday 26 June 2015 10:28:08 Proxy One wrote:
> Sometimes people say I write too much.

There is writing too much and writing a lot.  I talk too much.  You write a 
lot.

In Latin too much and very much are the same word.  In case any modern 
language does the same thing, Bob is saying that sometimes people think he 
writes a lot more than is necessary or helpful.  Bob doesn't write too much.  
He writes very much, very lucidly.

I wish that I could be half as lucid or, in fact, half as succinct.

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201506261735.03717.lisi.re...@gmail.com

Re: network configuration

[Proxy One]

On 2015-Jun-26 17:27, Charlie wrote:
> On Thu, 25 Jun 2015 21:13:20 -0600 Bob Proulx sent:
> 
> > Sometimes people say I write too much.  But the details are
> > important.  :-)
> 
> No way Bob. Never too much.
> 
> Personally I read all your posts even if they don't apply to anything I
> need or particularly interest me. Sometimes they generate interest.
> 
> There is much to learn and your posts are extremely informative.
> 
> Keep doing as you have been.
> 
> Thank you,
> Charlie

I have to agree with Charlie, Bob. I also read your posts as they contain
informations you can't get anywhere in that form. You don't just offer
resolution to some problem. You explain it in such a accessible way. You
explain why somethings works the way it does and by doing it you explain
some linux topic. Lots of your posts are marked as important in my
mailbox and copied to a folder with tech documentation.

Thank you!


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150626092807.ga9...@gvozdika.example.net

Re: network configuration

[Charlie]

On Thu, 25 Jun 2015 21:13:20 -0600 Bob Proulx sent:

> Sometimes people say I write too much.  But the details are
> important.  :-)

No way Bob. Never too much.

Personally I read all your posts even if they don't apply to anything I
need or particularly interest me. Sometimes they generate interest.

There is much to learn and your posts are extremely informative.

Keep doing as you have been.

Thank you,
Charlie

-- 
Registered Linux User:- 329524
***

If you argue for your limitations, you get to keep
them. ..Richard Bach

***

Debian GNU/Linux - Magic indeed.

-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150626172701.66b1210c@taogypsy

Re: network configuration

[Bob Proulx]

notoneofmyseeds wrote:
> Bob Proulx wrote:
> 
> I must say you have written a book here on this topic, Rob. I've learned a
> lot. I printed it out. To your questions now.

Sometimes people say I write too much.  But the details are important.  :-)
And this is a large book again with this message.

> I had a very long and nice response that I lost, as a result of an
> application crash.

LOL!  I have been there many times myself! :-)

I am merging two messages from you so I can answer both here at the
same time.

> >   ip addr show

> 2: eth0:  mtu 1500 qdisc mq state UP group 
> default qlen 1000
> inet 192.168.1.2/24 brd 192.168.1.255 scope global dynamic eth0
> 3: wlan0:  mtu 1500 qdisc mq state UP group 
> default qlen 1000
> inet 10.10.10.6/24 brd 10.10.10.255 scope global dynamic wlan0

Gotcha.  Although 192.168.1.2 is an unusual address to get from dhcp.
It would help to see the dhcp range the server issues.

And the other eth0 network is:

> 2: eth0:  mtu 1500 qdisc mq state UP group 
> default qlen 1000
> inet 172.16.1.0/24 brd 172.16.1.255 scope global dynamic eth0
> 3: wlan0:  mtu 1500 qdisc mq state UP group 
> default qlen 1000
> inet 10.10.10.5/24 brd 10.10.10.255 scope global wlan0

Again the 172.16.1.0 is an unusual address to get from dhcp.  That is
the network address and I don't think this is correct.  Have you
modified the dhcpd server configuration on that network to include the
entire range?

I think the next thing to start debugging is the dhcp server
configuration on each of those networks.  Change the range to
something in the middle such as from 192.168.1.100-192.168.1.200 and
from 172.16.1.100-172.16.1.200 or some such range that does not
include the .0 network address and does not include the .255 broadcast
address.  Don't assign those as host addresses.

> >   ip route show | tac

> 172.16.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.2
> 169.254.0.0/16 dev wlan0  scope link  metric 1000
> 10.10.10.0/24 via 10.0.0.1 dev wlan0  proto static  metric 1
> 10.10.10.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.5
> default via 172.16.1.1 dev eth0  proto static  metric 1024

The route table is very telling of the problem.  I think in this state
the wifi was connected first and then the wired network was connected
afterward.  The wired network dhcp replaced the default route with its
own route default default via 172.16.1.1 dev eth0.  That is the only
route listed in the above.  It won't be out your wifi interface.  If
your wifi interface is the only one with a route to the Internet then
obviously the above won't work.

You could probably do a manual repair with:

  ip route replace default via 10.10.10.1 dev wlan0

Aftering bringing up the wired interface, which will break the route,
the above would restore the working route out the wlan0 interface.
This is only a temporary measure.  It is temporary because the
dhclient daemon will renew the dhcp lease and every time it does it
will rewrite the default route and break things again.  But it would
probably assure you that this is exactly the problem and that things
can work with the right configuration.

> >Another question.  Are all of the subnets on each of the networks
> >different?  A subnet is something like 192.168.1.0/24.  For example
> >having different subnets would mean 192.168.1.0/24 on one and
> >192.168.20.0/24 on another and 192.168.42.0/24 on the third.  All
> >different.
>
> They are all different.

Good!  That will make things much easier and simpler.

> >Now that you have learned this I have another question.  Which
> >interface do you wish to keep as the default route?

> I assume the default route is the one that will take me online, in that
> case, the wifi.

Then the wifi will be the main interface and will hold eth0 default
route.  The other interfaces should have the default route disabled.

> And this happens here, when ever the ethernet is connected, the wifi, which
> is the connection to the internet does not work. I remain connected to it,
> but can't go online. This would mean the lan is being used as the default
> route?

I think so.  But unfortunately you missed providing the route data.  :-(

> >I think it likely that you have a default route problem which is why I
> >explained it in as much detail as I could above.

> I think you're right. The question now is who do I set it up. I've tried
> several configurations yesterday, none of which worked. For example, I set
> wlan0 to dhcp and set the ethernet static, providing all the details, ip,
> netmask, etc.

That should work.  In fact I was going to suggest such a configuration
as being easier.  Use dhcp on wlan0 but use a static ip configuration
on eth0.  Could you repeat that test and tell us here what you are
doing?

> I also changed the order, moving the wlan0 from top to bottom
> of the ethernet on the network/interfaces file.

The order the interfaces are listed in the interfaces file is not
significant.  Changing the

Re: network configuration

[Gene Heskett]

On Thursday 25 June 2015 08:46:49 notoneofmyseeds wrote:
> On 06/23/2015 10:22 PM, Bob Proulx wrote:
> > Another question: When you are connected to both as you have done
> > what is the output of these commands so that we can see the (as you
> > say broken) state of things?
> >
> >ip addr show
> >
> >ip route show | tac
>
> I had a very long and nice response that I lost, as a result of an
> application crash.
>
> So, now to the specific point:
>
> 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN
> group default
>  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>  inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
>  inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: eth0:  mtu 1500 qdisc mq state UP
> group default qlen 1000
>  link/ether 00:16:d3:27:29:70 brd ff:ff:ff:ff:ff:ff
>  inet 172.16.1.0/24 brd 172.16.1.255 scope global dynamic eth0
> valid_lft 289sec preferred_lft 289sec
>  inet6 fe80::216:d3ff:fe27:2970/64 scope link
> valid_lft forever preferred_lft forever
> 3: wlan0:  mtu 1500 qdisc mq state UP
> group default qlen 1000
>  link/ether 00:13:02:b8:90:4d brd ff:ff:ff:ff:ff:ff
>  inet 10.10.10.5/24 brd 10.10.10.255 scope global wlan0
> valid_lft forever preferred_lft forever
>  inet6 fe80::213:2ff:feb8:904d/64 scope link
> valid_lft forever preferred_lft forever
>
> And:
> 172.16.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.2
> 169.254.0.0/16 dev wlan0  scope link  metric 1000
> 10.10.10.0/24 via 10.0.0.1 dev wlan0  proto static  metric 1
> 10.10.10.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.5
> default via 172.16.1.1 dev eth0  proto static  metric 1024
>
> And I agree, I think this is a routing problem. And I have tried
> setting static ip on wlan and Ethernet, but no luck. I changed the
> order as they appear in the network/interfaces file, no luck.  Set
> dhcp the wlan and static for the ethernet, and did not include a
> gateway, no luck. I include its gateway associated with that network,
> no luck.
>
>  From all that I've read, this should be very simple and
> straightforward. I've followed the rules, but no luck. All I want to
> do is connect to my local lan and the internet at the same time,
> without having to switch to the ethernet when I want to use the lan
> network, and the wifi when I want to go online. Am I the only one
> wanting to do this?

No, but most folks setup their local network on a local 192.168.xx.yy 
address, and NAT translate it in thier router to go web browsing, which 
allows any machine on your local net full access to the internet.

If your router cannot do that, get one that can. I use anything with 
enough flash and memory to allow dd-wrt to be re-flashed into it.  That 
also allows you to serve your own web page from a machine on the local 
net, in this case, this machine.  The uplink pipe is obviously somewhat 
slow, but it works.

> Thanks a lot.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/201506251020.55470.ghesk...@wdtv.com

Re: network configuration

[notoneofmyseeds]

On 06/23/2015 10:22 PM, Bob Proulx wrote:

Another question: When you are connected to both as you have done what
is the output of these commands so that we can see the (as you say
broken) state of things?

   ip addr show

   ip route show | tac
I had a very long and nice response that I lost, as a result of an 
application crash.


So, now to the specific point:

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
group default

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc mq state UP 
group default qlen 1000

link/ether 00:16:d3:27:29:70 brd ff:ff:ff:ff:ff:ff
inet 172.16.1.0/24 brd 172.16.1.255 scope global dynamic eth0
   valid_lft 289sec preferred_lft 289sec
inet6 fe80::216:d3ff:fe27:2970/64 scope link
   valid_lft forever preferred_lft forever
3: wlan0:  mtu 1500 qdisc mq state UP 
group default qlen 1000

link/ether 00:13:02:b8:90:4d brd ff:ff:ff:ff:ff:ff
inet 10.10.10.5/24 brd 10.10.10.255 scope global wlan0
   valid_lft forever preferred_lft forever
inet6 fe80::213:2ff:feb8:904d/64 scope link
   valid_lft forever preferred_lft forever

And:
172.16.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.2
169.254.0.0/16 dev wlan0  scope link  metric 1000
10.10.10.0/24 via 10.0.0.1 dev wlan0  proto static  metric 1
10.10.10.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.5
default via 172.16.1.1 dev eth0  proto static  metric 1024

And I agree, I think this is a routing problem. And I have tried setting 
static ip on wlan and Ethernet, but no luck. I changed the order as they 
appear in the network/interfaces file, no luck.  Set dhcp the wlan and 
static for the ethernet, and did not include a gateway, no luck. I 
include its gateway associated with that network, no luck.


From all that I've read, this should be very simple and 
straightforward. I've followed the rules, but no luck. All I want to do 
is connect to my local lan and the internet at the same time, without 
having to switch to the ethernet when I want to use the lan network, and 
the wifi when I want to go online. Am I the only one wanting to do this?


Thanks a lot.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/558bf839.9070...@gmx.de

Re: network configuration

[Charles Kroeger]

On Tue, 23 Jun 2015 22:30:02 +0200
Bob Proulx  wrote:

> Perhaps someone else on the mailing list will have additional
> suggestions.  Hopefully they will be better than my poor contributions
> here.

I would suggest getting into the depths of
the /etc/wpa_supplicant/wpa_supplicant.conf  file. You have to marvel at the 
mind
that came up with that but there is a lot of help and examples and creative
ways to use it, on the Internet. 

-- 
CK


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/cv17kvf7lu...@mid.individual.net

Re: network configuration

[Bob Proulx]

notoneofmyseeds wrote:
> "one ethernet interface that you sometimes connect to one wired network and 
> sometimes to a different wired network?"
> For now, this is a laptop that is located in one place.
> All networks are DHCP.

Those are good clarifications.  Let me mention a few problems to be
overcome with it.

DHCP is the Dynamic Host Configuration Protocol that configures a
network interface.  Among the things it configures is the default
gateway router.

  $ ip route show | grep ^default
  default via 93.184.216.34 dev eth0

Normally there will be one interface active at a time configured with
DHCP.  Therefore there will be one default route.  However if you have
several interfaces configured with DHCP all active at the same time
then each interface will configure a default route.  Let me write this
contrived example showing the problem.

  $ ip route show | tac | grep ^default
  default via 93.184.216.34 dev eth0
  default via 93.184.216.34 dev eth1
  default via 93.184.216.34 dev wlan0

Or maybe:

  $ ip route show | tac | grep ^default
  default via 93.184.216.34 dev eth1
  default via 93.184.216.34 dev eth0
  default via 93.184.216.34 dev wlan0

Or maybe:

  $ ip route show | tac | grep ^default
  default via 93.184.216.34 dev wlan0
  default via 93.184.216.34 dev eth1
  default via 93.184.216.34 dev eth0

The order of the default routes is important because the first one
matched is the one used.  The order is set by the last one
configured.  The last interface to have dhcp'd an address will set a
default route and it will be the first one matched.

Also note that until recently the kernel listed routes in top-down
order.  The first route matched as displayed from the top-down was the
one that matched.  This was true of *BSD and SystemV and others.
Newer Linux kernels since some version I forget have unfortunately
reversed this order.  Now the Linux kernel lists routes in bottom-top
priority listing.  I think that is simply a bug but so it is.  I often
pipe the output of ip route show through 'tac' to reverse the order in
order to get a sane top-bottom ordering.  That is why I have tac in
the above.  To make it display in the Right order.

There is an old saying that goes, "... if you have to ask then ..."
which applies here.  If you don't know and have to ask about default
routes then you should only ever have *one* default route on the
system.  There are only some few special cases where it would be
otherwise.  One default route normally makes the most sense.

Another question: When you are connected to both as you have done what
is the output of these commands so that we can see the (as you say
broken) state of things?

  ip addr show

  ip route show | tac



Another question.  Are all of the subnets on each of the networks
different?  A subnet is something like 192.168.1.0/24.  For example
having different subnets would mean 192.168.1.0/24 on one and
192.168.20.0/24 on another and 192.168.42.0/24 on the third.  All
different.

Along with the default route every IP address assigned will create a
route in the route table for that subnet.

  $ ip route show | tac
  192.168.230.0/24 dev eth0  proto kernel  scope link  src 192.168.230.120 
  default via 192.168.230.1 dev eth0 

Routes match top to bottom (in the sane ordering after reversing them
with tac to restore the order to the way other kernels report it) and
therefore addresses on the local subnet are matched before the default
route.  For example in the above an address 192.168.230.27 would match
on the local subnet and would be routed directly using the listed src
address of the host.  Addresses such as 8.8.8.8 would fall through all
of the routes until hitting the default route at the bottom and would
then be routed through the default route to the router and out to the
Internet.

A more complicated routing table could be this example.  Routes are
matched from the top down and the first one matched indicates which
interface the packet is routed through.

  $ ip route show | tac
  216.17.153.56/29 dev eth0  proto kernel  scope link  src 216.17.153.62 
  192.168.240.0/24 dev eth0  proto kernel  scope link  src 192.168.240.1 
  192.168.230.0/24 dev eth1  proto kernel  scope link  src 192.168.230.1 
  192.168.94.0/24 dev eth2  proto kernel  scope link  src 192.168.94.1 
  192.168.93.0/24 dev wlan0  proto kernel  scope link  src 192.168.93.1 
  172.27.61.2 dev tun0  proto kernel  scope link  src 172.27.61.1 
  172.27.61.0/24 via 172.27.61.2 dev tun0 
  default via 216.17.153.57 dev eth0 

Normally it is important to ensure that every interface has a
different subnet so that routing is sane.  A typical problem is that
people don't think about this and then set up the same subnet on
multiple different interfaces.  If that happens the result is order
dependent depending upon the order the interfaces were brought up.
Things usually don't work very well.



Now that you have learned this I have another question.  W

Re: network configuration

[notoneofmyseeds]

On 06/22/2015 10:39 PM, Bob Proulx wrote:

If you have only one wired ethernet and are planning on connecting
back and forth between two wired networks then it is similar but I
would use guessnet to manage the interface so that it can
automatically switch you between the specified network profiles.
...and not to make matters any complicated, would guessnet allow me to 
be connected to the wifi and Ethernet at the same time, without loosing 
access to the Internet? It is the case now that if I connect with both, 
I loose Internet and can only access the local network.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/55887a2c.8000...@gmx.de

Re: network configuration

[notoneofmyseeds]

On 06/22/2015 10:39 PM, Bob Proulx wrote:

You say networks.  Is that the same as ethernet interfaces?  You have
two ethernet interfaces?  Or you have one ethernet interface that you
sometimes connect to one wired network and sometimes to a different
wired network?
Bob, your ever so detailed and kind responses are simply wonderful. 
Sorry for the naming. You explanation as understood is correct: "


"one ethernet interface that you sometimes connect to one wired network and 
sometimes to a different wired network?"



Is this a laptop that is carried mobile to various places?  Or is it a
laptop that always sits in one place and needs to connect to different
networks in that one place?  (I would suggest different things if it
iis three fully specified local networks with static ip addresses
versus if it were carried mobile and must connect to random dhcp
networks too.)

For now, this is a laptop that is located in one place.


On these networks are they DHCP or static IPs?

All networks are DHCP.


For the WiFi network are you needing to select them manually from a
desktop graphically with the mouse?  Or is this from a set of known
networks that you would preconfigure and then not change?  (Such as in
a home network environment but not mobile at airports or elsewhere.)
Home network, just select and go. So for now, I simply disconnect the 
wired when I want to use the wireless and disconnect the wireless when I 
want to use the wifi. I do this with Network manager. And it's a tiring 
business.



>And when I do this, hope to be connected to a respective network based
>on my explicit rules.

Have you looked at the "guessnet" package?  It might help you.

   http://guessnet.alioth.debian.org/

   https://packages.debian.org/jessie/guessnet

There are also "whereami" and other packages in this topic space too.


>I hope this can work. And I hope I have explained a bit more enough.
>Are there rules I must follow to do this properly. As I've tried before
>without success.
>Thanks for your help.

There are still many possibilities.  But if we go through more
questions and answers then it will eventually be communicated.:-)

So far we have the above and your previously written:


>I'm using a laptop and want the wifi to go online, but the ethernet to
>stay on a different lan networks, actually two different networks. And
>I worry how to proceed with such a configuration. Ideas?

Let me assume you want to keep NetworkManager (or better wicd)
managing your wifi interface but manually configure your eth0 and eth1
wired interfaces.  For that you would simply add a static or dhcp
configuration to /etc/network/interfaces for eth0 and eth1 but not
specify wlan0.  (Reboot after doing this so that NM won't grab eth0
and eth1.)  With that configuration you will manually select the WiFi
connection "to the internet" as you say.  As you connect the wired
networks they will use the explicit configuration in
/etc/network/interfaces for them.

If you have only one wired ethernet and are planning on connecting
back and forth between two wired networks then it is similar but I
would use guessnet to manage the interface so that it can
automatically switch you between the specified network profiles.

Would I need to remove network manager to use the guessnet option?


And so forth...

Bob



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/558874f4.7060...@gmx.de

Re: network configuration

[Bob Proulx]

notoneofmy wrote:
> I have three separate networks, ip addresses, etc.
> One wireless and two hard wired, ethernet.
> The wireless must connect to the internet.
> As is necessary, I will need to physically swap the ethernet cables
> between networks.

You say networks.  Is that the same as ethernet interfaces?  You have
two ethernet interfaces?  Or you have one ethernet interface that you
sometimes connect to one wired network and sometimes to a different
wired network?

Is this a laptop that is carried mobile to various places?  Or is it a
laptop that always sits in one place and needs to connect to different
networks in that one place?  (I would suggest different things if it
iis three fully specified local networks with static ip addresses
versus if it were carried mobile and must connect to random dhcp
networks too.)

On these networks are they DHCP or static IPs?

For the WiFi network are you needing to select them manually from a
desktop graphically with the mouse?  Or is this from a set of known
networks that you would preconfigure and then not change?  (Such as in
a home network environment but not mobile at airports or elsewhere.)

> And when I do this, hope to be connected to a respective network based
> on my explicit rules.

Have you looked at the "guessnet" package?  It might help you.

  http://guessnet.alioth.debian.org/

  https://packages.debian.org/jessie/guessnet

There are also "whereami" and other packages in this topic space too.

> I hope this can work. And I hope I have explained a bit more enough.
> Are there rules I must follow to do this properly. As I've tried before
> without success.
> Thanks for your help.

There are still many possibilities.  But if we go through more
questions and answers then it will eventually be communicated. :-)

So far we have the above and your previously written:

> I'm using a laptop and want the wifi to go online, but the ethernet to
> stay on a different lan networks, actually two different networks. And
> I worry how to proceed with such a configuration. Ideas?

Let me assume you want to keep NetworkManager (or better wicd)
managing your wifi interface but manually configure your eth0 and eth1
wired interfaces.  For that you would simply add a static or dhcp
configuration to /etc/network/interfaces for eth0 and eth1 but not
specify wlan0.  (Reboot after doing this so that NM won't grab eth0
and eth1.)  With that configuration you will manually select the WiFi
connection "to the internet" as you say.  As you connect the wired
networks they will use the explicit configuration in
/etc/network/interfaces for them.

If you have only one wired ethernet and are planning on connecting
back and forth between two wired networks then it is similar but I
would use guessnet to manage the interface so that it can
automatically switch you between the specified network profiles.

And so forth...

Bob


signature.asc
Description: Digital signature

Re: network configuration

[notoneofmy]

On 15-06-21 11:52 PM, Bob Proulx wrote:
>> do I need to remove/purge NetworkManager Applet 0.9.10.0 to manually
>> > configure my interfaces?
> It is not necessary.  However I recommend doing so anyway.
>
> It is not necessary because NetworkManager and wicd ignore any
> interface with a configuration in /etc/network/interfaces.  They
> determine that there is no explicit configuration and then assume
> control of the interface.  If you create an explicit configuration
> they will not control it.
>
> However there is a little bit of a chicken-and-egg startup problem.
> Initially they will control the interface and there won't be an
> explicit configuration for it.  You need to shut them down before
> adding an explicit configuration.  Not doing this can cause problems
> where NM is *still* controlling it from before, along with the
> explicit configuration trying to control it.  Of course rebooting
> after setting up an explicit configuration should reset everything.
>
> I still recommend removing NetworkManager because I have too many
> times had NM break the network on upgrades.  Expecially when
> connecting to the system remotely with ssh that is unacceptable to
> have NM break the network connection to it.
>
> For a mobile device and graphical interactive control I use and
> recommend wicd.
Thanks for your recommendation. If what I want to do does not work, I
will install wicd instead.
>> > I'm using a laptop and want the wifi to go online, but the ethernet to stay
>> > on a different lan networks, actually two different networks. And I worry
>> > how to proceed with such a configuration. Ideas?
> This description is ambiguous.  Please say more?
>
> Bob
I have three separate networks, ip addresses, etc.
One wireless and two hard wired, ethernet.
The wireless must connect to the internet.
As is necessary, I will need to physically swap the ethernet cables
between networks.
And when I do this, hope to be connected to a respective network based
on my explicit rules.
I hope this can work. And I hope I have explained a bit more enough.
Are there rules I must follow to do this properly. As I've tried before
without success.
Thanks for your help.

Re: network configuration

[Bob Proulx]

notoneofmyseeds wrote:
> do I need to remove/purge NetworkManager Applet 0.9.10.0 to manually
> configure my interfaces?

It is not necessary.  However I recommend doing so anyway.

It is not necessary because NetworkManager and wicd ignore any
interface with a configuration in /etc/network/interfaces.  They
determine that there is no explicit configuration and then assume
control of the interface.  If you create an explicit configuration
they will not control it.

However there is a little bit of a chicken-and-egg startup problem.
Initially they will control the interface and there won't be an
explicit configuration for it.  You need to shut them down before
adding an explicit configuration.  Not doing this can cause problems
where NM is *still* controlling it from before, along with the
explicit configuration trying to control it.  Of course rebooting
after setting up an explicit configuration should reset everything.

I still recommend removing NetworkManager because I have too many
times had NM break the network on upgrades.  Expecially when
connecting to the system remotely with ssh that is unacceptable to
have NM break the network connection to it.

For a mobile device and graphical interactive control I use and
recommend wicd.

> I'm using a laptop and want the wifi to go online, but the ethernet to stay
> on a different lan networks, actually two different networks. And I worry
> how to proceed with such a configuration. Ideas?

This description is ambiguous.  Please say more?

Bob


signature.asc
Description: Digital signature

Re: network configuration failed during installation

[Tiago Almeida]

I Hope you get you network up and working,

We're here to help.

-- 
Tiago Almeida
tiagov...@gmail.com

Re: network configuration failed during installation

[Alexander Kaphuk]

Thanks a lot for a prompt reply to my email, Tiago!

I'll follow up on the suggestions you've made and let you know how I go.

Cheers.

Alexander Kapshuk.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration failed during installation

[Tiago Almeida]

Alexander,

You probaly should look at:

www.about*debian*.com/*network*.htm

To the automatic network configuration works during installation you must
have cable on (link on network-card) and your network card must be know to
Linux (a.k.a properly modules loaded), may cards have support built-in a few
ones you must get from third-party (manufactor) install or compile.

You can look at /var/log/messages for notices about eth0 or other network
device.

Also, you must have a DHCP on network for automatic config work, sure.

2009/9/10 Alexander Kaphuk 

> G'day,
>
> I have installed Debian Lenny on a HP Comaq Presario CQ61 laptop. However,
> the automatic network configuration failed during installation. I'm fairly
> new to Linux. I'd appreciate somebody referring me to a HOWTO or some other
> resource containing instructions on how to rectify the problem. Is there's a
> log file on the system that could point me in the right direction?
>
> Thanking you all in advance,
>
> Alexander Kapshuk.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a
> subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
>
>


-- 
Tiago Almeida
tiagov...@gmail.com

re: network configuration failed during installation

[Alexander Kaphuk]

G'day,

I have installed Debian Lenny on a HP Comaq Presario CQ61 laptop. 
However, the automatic network configuration failed during installation. 
I'm fairly new to Linux. I'd appreciate somebody referring me to a HOWTO 
or some other resource containing instructions on how to rectify the 
problem. Is there's a log file on the system that could point me in the 
right direction?


Thanking you all in advance,

Alexander Kapshuk.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration for Eth0

[Paul Cartwright]

On Sun May 3 2009, Andrei Popescu wrote:
> > Firestarter might work, but i really wanted to be able to add my own
> > entry to some file somewhere:) command-line junky :)
>
> Sounds like shorewall to me ;)

ahhh, I might have to look at it. thanks!
per the INTRO page:
http://www.shorewall.net/

Shorewall is not a daemon. Once Shorewall has configured the Linux networking 
subsystem, its job is complete and there is no “Shorewall process” left 
running in your system. The /sbin/shorewall program can be used at any time 
to monitor the Netfilter firewall.

this is what I am looking for.

-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration for Eth0

[Paul Cartwright]

On Sat May 2 2009, Andrei Popescu wrote:
> > need to run:
> > iptables -I INPUT -p tcp -m state --state NEW --dport 80 -i eth0 -j
> > ACCEPT iptables -I INPUT -p tcp -m state --state NEW --dport 22 -i eth0
> > -j ACCEPT /sbin/iptables -N ssh-connection
> > /sbin/iptables -A ssh-connection -i eth0 -p tcp --dport 22 -m
> > recent --update --seconds 600 --hitcount 4 --rttl --name SSH -j
> > LOG --log-prefix "SSH_brute_force "
> > /sbin/iptables -A ssh-connection -i eth0 -p tcp --dport 22 -m
> > recent --update --seconds 600 --hitcount 4 --rttl --name SSH -j DROP
> > /sbin/iptables -A ssh-connection -p tcp --dport 22 -m state --state NEW
> > -m recent --set --name SSH -j ACCEPT
>
> Sorry, I'm not familiar with either iptables or firestarter. You might
> want to start a new thread about this.

I'm not familiar with firestarter either, that's why I tried to create a shell 
script.. I'm better when I can work with plain old config files.. and VI :)

-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration for Eth0

[Andrei Popescu]

On Sat,02.May.09, 16:32:44, Paul Cartwright wrote:

> Firestarter might work, but i really wanted to be able to add my own 
> entry to some file somewhere:) command-line junky :)

Sounds like shorewall to me ;)

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: Digital signature

Re: network configuration for Eth0

[Paul Cartwright]

On Sat May 2 2009, Thorny wrote:
> If I understand correctly what you asking:
>
> You will need to option your router to port forward port 80 requests
> from the WAN interface to the static IP Address of the computer on your
> LAN you want them to go to.

I have done that and it works.

>
> If those "laptops" are in your LAN, you will have to option firestarter
> on the computer in question to allow connections on service port 22 from
> your laptops in your LAN IP Address range.

I have also done that, and it works.
 
>
> In case I misunderstood you, I agree with Andrei, this thread has strayed
> far enough from the original topic to be worthy of starting a new thread.
> In any case, I advise you do that to make sure enough people look at it
> for good peer review.

so far, so good. Now I guess I need to start a new thread about IPTABLES.. 
right now I forgot that I had firestart installed, but I just wanted to 
create some rules to port forward to a static IP for HTTP web access. 
Firestarter might work, but i really wanted to be able to add my own entry to 
some file somewhere:) command-line junky :)

thanks!


-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration for Eth0

[Thorny]

On Sat, 02 May 2009 06:15:04 -0400, Paul Cartwright posted:
[...]
> what I want is a rule tht allows http for my web page to port forward from
> my router to my desktop, and also allow me to ssh into my desktop from my
> laptops. 

If I understand correctly what you asking:

You will need to option your router to port forward port 80 requests
from the WAN interface to the static IP Address of the computer on your
LAN you want them to go to.

If those "laptops" are in your LAN, you will have to option firestarter
on the computer in question to allow connections on service port 22 from
your laptops in your LAN IP Address range.

If those "laptops" are on the WAN (Internet), you will have to option the
router to port forward port 22 requests to the static IP Address of the
computer on your LAN you want them to go to.

In case I misunderstood you, I agree with Andrei, this thread has strayed
far enough from the original topic to be worthy of starting a new thread.
In any case, I advise you do that to make sure enough people look at it
for good peer review.

[...]


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration for Eth0

[Andrei Popescu]

On Sat,02.May.09, 06:15:04, Paul Cartwright wrote:
> On Sat May 2 2009, Andrei Popescu wrote:
> > > part of the problem was 2 files I had worked on that did give me
> > > errors, and I removed them. 1 was ipv6,
> >
> > Do yo mean the module? If you don't want it loaded (though I have it and
> > there are no problems) just blacklist it in a file (ex. 00local.conf)
> > under /etc/modprobe.d/ with
> >
> > blacklist ipv6
> 
> actually, I was trying to setup IPv6, but I don't think my router supports 
> it. 
> So it isn't necessary. I'm not sure anything is loaded for ipv6.. how would I 
> check?

You don't need to worry about it. 

> > > the other was an iptables entry. I was trying to add an iptables entry
> > > to allow ssh & http ports. I can get this to work from a shell script,
> >
> > I saw in the (sniped) output above that you also use firestarter. I
> > don't think it's a good idea to mix firewall frontends with custom rules
> > in some script. Pick one and stick to it.
> >
> > If firestarter can't do what you need (or don't know how to configure
> > it) just ask for help, there are many others (personally I prefer
> > shorewall, it's quite easy to setup and very powerful).
> 
> ok, so I have firestarter installed:
> 
> ii  firestarter1.0.3-6gtk program for managing and observing your 
> 
> what I want is a rule tht allows http for my web page to port forward from my 
> router to my desktop, and also allow me to ssh into my desktop from my 
> laptops. Right now I have it setup to use ssh keys for security, and I have 
> to run that script every time i boot, to get my http ports open.
> How do I get that done with iptables automatically at boot?
> right now this is my script, but I'm not at all sure this is exactly what i 
> need to run:
> iptables -I INPUT -p tcp -m state --state NEW --dport 80 -i eth0 -j ACCEPT
> iptables -I INPUT -p tcp -m state --state NEW --dport 22 -i eth0 -j ACCEPT
> /sbin/iptables -N ssh-connection
> /sbin/iptables -A ssh-connection -i eth0 -p tcp --dport 22 -m 
> recent --update --seconds 600 --hitcount 4 --rttl --name SSH -j 
> LOG --log-prefix "SSH_brute_force "
> /sbin/iptables -A ssh-connection -i eth0 -p tcp --dport 22 -m 
> recent --update --seconds 600 --hitcount 4 --rttl --name SSH -j DROP
> /sbin/iptables -A ssh-connection -p tcp --dport 22 -m state --state NEW -m 
> recent --set --name SSH -j ACCEPT

Sorry, I'm not familiar with either iptables or firestarter. You might 
want to start a new thread about this.

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: Digital signature

Re: network configuration for Eth0

[Paul Cartwright]

On Sat May 2 2009, Andrei Popescu wrote:
> > part of the problem was 2 files I had worked on that did give me
> > errors, and I removed them. 1 was ipv6,
>
> Do yo mean the module? If you don't want it loaded (though I have it and
> there are no problems) just blacklist it in a file (ex. 00local.conf)
> under /etc/modprobe.d/ with
>
> blacklist ipv6

actually, I was trying to setup IPv6, but I don't think my router supports it. 
So it isn't necessary. I'm not sure anything is loaded for ipv6.. how would I 
check?

>
> > the other was an iptables entry. I was trying to add an iptables entry
> > to allow ssh & http ports. I can get this to work from a shell script,
>
> I saw in the (sniped) output above that you also use firestarter. I
> don't think it's a good idea to mix firewall frontends with custom rules
> in some script. Pick one and stick to it.
>
> If firestarter can't do what you need (or don't know how to configure
> it) just ask for help, there are many others (personally I prefer
> shorewall, it's quite easy to setup and very powerful).

ok, so I have firestarter installed:

ii  firestarter1.0.3-6gtk program for managing and observing your 

what I want is a rule tht allows http for my web page to port forward from my 
router to my desktop, and also allow me to ssh into my desktop from my 
laptops. Right now I have it setup to use ssh keys for security, and I have 
to run that script every time i boot, to get my http ports open.
How do I get that done with iptables automatically at boot?
right now this is my script, but I'm not at all sure this is exactly what i 
need to run:
iptables -I INPUT -p tcp -m state --state NEW --dport 80 -i eth0 -j ACCEPT
iptables -I INPUT -p tcp -m state --state NEW --dport 22 -i eth0 -j ACCEPT
/sbin/iptables -N ssh-connection
/sbin/iptables -A ssh-connection -i eth0 -p tcp --dport 22 -m 
recent --update --seconds 600 --hitcount 4 --rttl --name SSH -j 
LOG --log-prefix "SSH_brute_force "
/sbin/iptables -A ssh-connection -i eth0 -p tcp --dport 22 -m 
recent --update --seconds 600 --hitcount 4 --rttl --name SSH -j DROP
/sbin/iptables -A ssh-connection -p tcp --dport 22 -m state --state NEW -m 
recent --set --name SSH -j ACCEPT


-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration for Eth0

[Andrei Popescu]

On Sat,02.May.09, 05:38:38, Paul Cartwright wrote:
 
> well, that seems to work.
... 
> part of the problem was 2 files I had worked on that did give me 
> errors, and I removed them. 1 was ipv6,

Do yo mean the module? If you don't want it loaded (though I have it and 
there are no problems) just blacklist it in a file (ex. 00local.conf) 
under /etc/modprobe.d/ with

blacklist ipv6

> the other was an iptables entry. I was trying to add an iptables entry 
> to allow ssh & http ports. I can get this to work from a shell script, 

I saw in the (sniped) output above that you also use firestarter. I 
don't think it's a good idea to mix firewall frontends with custom rules 
in some script. Pick one and stick to it.

If firestarter can't do what you need (or don't know how to configure 
it) just ask for help, there are many others (personally I prefer 
shorewall, it's quite easy to setup and very powerful).

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: Digital signature

Re: network configuration for Eth0

[Paul Cartwright]

On Sat May 2 2009, Andrei Popescu wrote:
> > #static setup
> > #auto eth0
> > #iface eth0 inet static
> > #address 192.168.10.103
> > #netmask 255.255.255.0
> > #broadcast 192.168.10.255
> > here is what I have now:
>
> Please re-enable this part (and comment out the dhcp parts) and post the
> output of 'ifup -v eth0' (if it's complaining that it's already
> configured then do a 'ifdown eth0' first).

# ifup -v eth0
Configuring interface eth0=eth0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/bridge
run-parts: executing /etc/network/if-pre-up.d/iptables
Restoring iptables rules...
run-parts: executing /etc/network/if-pre-up.d/uml-utilities
run-parts: executing /etc/network/if-pre-up.d/vde2

ifconfig eth0 192.168.10.103 netmask 255.255.255.0 broadcast 192.168.10.255 

up
 route add default gw 192.168.10.1  eth0 
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/000resolvconf
run-parts: executing /etc/network/if-up.d/50firestarter
Stopping the Firestarter firewall
Starting the Firestarter firewall
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/bind9
run-parts: executing /etc/network/if-up.d/clamav-freshclam-ifupdown
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/ntp
run-parts: executing /etc/network/if-up.d/ntpdate
run-parts: executing /etc/network/if-up.d/openntpd
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/postfix
run-parts: executing /etc/network/if-up.d/uml-utilities

well, that seems to work.
# ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:16:76:bc:3f:af  
  inet addr:192.168.10.103  Bcast:192.168.10.255  Mask:255.255.255.0
  inet6 addr: fe80::216:76ff:febc:3faf/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:4743323 errors:0 dropped:0 overruns:0 frame:0
  TX packets:4512344 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:100 
  RX bytes:3929836675 (3.6 GiB)  TX bytes:1192756579 (1.1 GiB)
  Memory:dffe-e000 

part of the problem was 2 files I had worked on that did give me errors, and I 
removed them. 1 was ipv6, the other was an iptables entry. I was trying to 
add an iptables entry to allow ssh & http ports. I can get this to work from 
a shell script, but I don't know where to put it to make it start on boot:
iptables -I INPUT -p tcp -m state --state NEW --dport 80 -i eth0 -j ACCEPT
iptables -I INPUT -p tcp -m state --state NEW --dport 22 -i eth0 -j ACCEPT
/sbin/iptables -N ssh-connection
/sbin/iptables -A ssh-connection -i eth0 -p tcp --dport 22 -m 
recent --update --seconds 600 --hitcount 4 --rttl --name SSH -j 
LOG --log-prefix "SSH_brute_force "
/sbin/iptables -A ssh-connection -i eth0 -p tcp --dport 22 -m 
recent --update --seconds 600 --hitcount 4 --rttl --name SSH -j DROP
/sbin/iptables -A ssh-connection -p tcp --dport 22 -m state --state NEW -m 
recent --set --name SSH -j ACCEPT

-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration for Eth0

[Andrei Popescu]

On Fri,01.May.09, 05:36:06, Paul Cartwright wrote:
> I seemed to have a problem with my static setup of eth0 that stopped my 
> debian 
> lenny setup from coming up correctly. I kept getting errors in logs.
> To redo my network config, just eth0, what is the best way to do it. I tried 
> dpkg-reconfigure ifupdown, but that didn't change the interfaces file.
> this is what I had that didn't work:
> #static setup
> #auto eth0
> #iface eth0 inet static
> #address 192.168.10.103
> #netmask 255.255.255.0
> #broadcast 192.168.10.255
> here is what I have now:

Please re-enable this part (and comment out the dhcp parts) and post the 
output of 'ifup -v eth0' (if it's complaining that it's already 
configured then do a 'ifdown eth0' first).

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: Digital signature

Re: network configuration for Eth0

[Paul Cartwright]

On Fri May 1 2009, Bob Cox wrote:
> What I would expect to see is something a bit like this:
>
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet static
> address 192.168.10.103
> netmask 255.255.255.0
> gateway 192.168.10.1
> network 192.168.10.0
> broadcast 192.168.10.255
>
> (assuming you have a router of that IP address of course).
>
> If you *do* have network-manager installed then this could be the cause
> of many of your woes.

rc  network-manager 0.6.5-3 

network management framework daemon
rc  network-manager-gnome   0.6.5-3 

network management framework (GNOME frontend)


-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration for Eth0

[Paul Cartwright]

On Fri May 1 2009, Celejar wrote:
> > this is what I had that didn't work:
> > #static setup
> > #auto eth0
> > #iface eth0 inet static
> > #address 192.168.10.103
> > #netmask 255.255.255.0
> > #broadcast 192.168.10.255
> > here is what I have now:
# The loopback network interface
auto lo 
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

> >
> > what's wrong with it?
>
> Something's missing here; what did you have, and what do you have now?
I hit SEND a bit too fast..


-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration for Eth0

[Paul Cartwright]

On Fri May 1 2009, Andrei Popescu wrote:
> > auto lo
> > iface lo inet loopback
> >
> > auto eth0
> > iface eth0 inet static
> > address 192.168.10.103
> > netmask 255.255.255.0
> > gateway 192.168.10.1
> > network 192.168.10.0
> > broadcast 192.168.10.255
>
> Nitpick: 'network' and 'broadcast' are optional and gateway is necessary
> only if this interface is used to connect to the internet.

yes gateway is my router that my PC is connected to.
router connected to DSL modem.

-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration for Eth0

[Paul Cartwright]

On Fri May 1 2009, Bob Cox wrote:
> > Nitpick: 'network' and 'broadcast' are optional and gateway is necessary
> > only if this interface is used to connect to the internet.
>
> Good points.  I like nitpicking ;-)
>
> As an aside, I use static IPs on everything here with no wireless and
> all manually configured as per my example.  
that is what I am trying to do, take away the DHCP and make them static. I 
have my desktop, a laptop that I connect using a wired connection, and my 
wifes laptop. I also have some other test servers that get turned on every so 
often..
I am using dyndns and port forwarding to my desktop for http..  so I want a 
static IP in my network for my desktop.

>
> The only exception to this is a recently acquired laptop with which I
> wanted to use both wireless and DHCP and be able to control it all from
> a GUI interface; something I have not done before.  I tried and failed
> with the kde front-end to network manager and in the end purged all
> traces of them and installing wicd ("aptitude show wicd" describes it
> well).  It is really excellent and just works, seamlessly restoring
> networking after suspending and so on and allowing easy switching from
> wired to wireless and so on.



-- 
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration for Eth0

[Bob Cox]

On Fri, May 01, 2009 at 19:04:25 +0300, Andrei Popescu 
(andreimpope...@gmail.com) wrote: 

[snip]

> Nitpick: 'network' and 'broadcast' are optional and gateway is necessary 
> only if this interface is used to connect to the internet.

Good points.  I like nitpicking ;-)

As an aside, I use static IPs on everything here with no wireless and
all manually configured as per my example.  

The only exception to this is a recently acquired laptop with which I
wanted to use both wireless and DHCP and be able to control it all from
a GUI interface; something I have not done before.  I tried and failed
with the kde front-end to network manager and in the end purged all
traces of them and installing wicd ("aptitude show wicd" describes it
well).  It is really excellent and just works, seamlessly restoring
networking after suspending and so on and allowing easy switching from
wired to wireless and so on.

-- 
Bob Cox.  Stoke Gifford, near Bristol, UK.
Please reply to the list only.  Do NOT send copies directly to me.
http://bobcox.com/


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration for Eth0

[Andrei Popescu]

On Fri,01.May.09, 15:11:17, Bob Cox wrote:
 
> What I would expect to see is something a bit like this:
> 
> auto lo
> iface lo inet loopback
> 
> auto eth0
> iface eth0 inet static
> address 192.168.10.103
> netmask 255.255.255.0
> gateway 192.168.10.1
> network 192.168.10.0
> broadcast 192.168.10.255

Nitpick: 'network' and 'broadcast' are optional and gateway is necessary 
only if this interface is used to connect to the internet.

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)


signature.asc
Description: Digital signature

Re: network configuration for Eth0

[Bob Cox]

On Fri, May 01, 2009 at 05:36:06 -0400, Paul Cartwright (a...@pcartwright.com) 
wrote: 

> I seemed to have a problem with my static setup of eth0 that stopped my 
> debian 
> lenny setup from coming up correctly. I kept getting errors in logs.
> To redo my network config, just eth0, what is the best way to do it. I tried 
> dpkg-reconfigure ifupdown, but that didn't change the interfaces file.
> this is what I had that didn't work:
> #static setup
> #auto eth0
> #iface eth0 inet static
> #address 192.168.10.103
> #netmask 255.255.255.0
> #broadcast 192.168.10.255
> here is what I have now:
> 
> what's wrong with it?

As others have commented Paul, there's not a lot here to go on.  Your
setup which didn't work is all commented out and the rest is just blank.

What I would expect to see is something a bit like this:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.10.103
netmask 255.255.255.0
gateway 192.168.10.1
network 192.168.10.0
broadcast 192.168.10.255

(assuming you have a router of that IP address of course).

If you *do* have network-manager installed then this could be the cause
of many of your woes.

-- 
Bob Cox.  Stoke Gifford, near Bristol, UK.
Please reply to the list only.  Do NOT send copies directly to me.
http://bobcox.com/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration for Eth0

[Thorny]

On Fri, 01 May 2009 05:36:06 -0400, Paul Cartwright posted:

> I seemed to have a problem with my static setup of eth0 that stopped my
> debian lenny setup from coming up correctly.

This doesn't tell us anything that we could use to troubleshoot. Do you
mean the system doesn't come up or just doesn't come up the way you want
it?

> I kept getting errors in logs.

If you would detail the errors, it might be easier to make a
troubleshooting decision of what to check first.

> To redo my network config, just eth0, what is the best way to do it.
> I tried dpkg-reconfigure ifupdown, but that didn't change the interfaces
> file. this is what I had that didn't work:
> #static setup
> #auto eth0
> #iface eth0 inet static
> #address 192.168.10.103
> #netmask 255.255.255.0
> #broadcast 192.168.10.255
> here is what I have now:
> 
> what's wrong with it?

Do you by any chance have network-manager running on the system?

I agree with Celejar, did you leave part of your description out or do you
mean that it is now blank?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: network configuration for Eth0

[Celejar]

On Fri, 1 May 2009 05:36:06 -0400
Paul Cartwright  wrote:

> I seemed to have a problem with my static setup of eth0 that stopped my 
> debian 
> lenny setup from coming up correctly. I kept getting errors in logs.
> To redo my network config, just eth0, what is the best way to do it. I tried 
> dpkg-reconfigure ifupdown, but that didn't change the interfaces file.
> this is what I had that didn't work:
> #static setup
> #auto eth0
> #iface eth0 inet static
> #address 192.168.10.103
> #netmask 255.255.255.0
> #broadcast 192.168.10.255
> here is what I have now:
> 
> what's wrong with it?

Something's missing here; what did you have, and what do you have now?

Celejar
--
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Network configuration

[Raj Kiran Grandhi]

Dan H wrote:

Hello folks,

I'm trying to control an external instrument via Ethernet. I've installed an 
additional networking card in my Debian box and connected the thing via a 
crossover cable.

NOTE: I've booted Windows on the same machine and was able to talk to the 
instrument using a supplied demo program (LabView). So, physically the 
connection is correct, but when I try tp PING the instrument from within Linux, 
I get no reply.

I don't really know where to start all this, so I'd like to know if at least my 
network settings are correct. I've set the address of the secondary interface 
to 192.168.0.1, the instrument has 192.168.0.2. Does my box automatically know 
to use the other card when I try to connect to an 192.168 address?

Thanks,
--D.

Here's the output of ifconfig. What does "Link encap:UNSPEC" mean? Is that a 
problem?

eth0  Link encap:UNSPEC  HWaddr 00-00-10-DC-00-38-3E-C6-00-00-00-00-00-00-00-00  
  inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0

  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


eth1  Link encap:Ethernet  HWaddr 00:0C:76:54:FE:B1  
 .

 (my "outside" network connection)
 .


Please post your /etc/network/interfaces and the output of "route -n"

Does your outside network share the same network number? I think if you 
define a static route to your device through eth0, you may be able to 
access it. For eg:


# route add 192.168.0.2 dev eth0

--
Raj Kiran Grandhi


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: network configuration issue - iptables

[Andrew Sackville-West]

On Thu, Jun 28, 2007 at 11:07:01PM +0100, Adam Hardy wrote:
> Andrew Sackville-West on 25/06/07 04:27, wrote:
> >On Sat, Jun 23, 2007 at 08:35:09PM +0100, Adam Hardy wrote:
> >>I have set up a network for our house using a gateway server with etch 
> >>and two NICs, eth1 for the internal network and eth2 for the DSL modem.
> >>
> >>I set up iptables with firewall-builder and all seems OK, but I can only 
> >>ever access the web interface on the DSL modem from the gateway server 
> >>directly after downing the internal network on eth1.
> >>
> >>The modem's web interface is on 192.168.1.1 on eth2 and if I don't down 
> >>eth1, the browser won't find it.
> >
> >number your internal lan addresses in a different subnet. Use
> >192.168.2.x for your lan. Then, because the modem is on a different
> >subnet, it should "just work". At least in my lan it works that
> >way. My dsl modem is accessible as 192.168.0.1 while my lan is
> >192.168.1.x.
> >
> >also, you can sometimes (depending on how its all configured) access
> >the modem by browsing to your *public ip* which resolves to your
> >modem, but since you're coming form the inside, it gives you the
> >configuration. 
> 
> That worked! Respect to you. I have only a small grasp of what my iptables 
> config does, but it works.

that wasn't so much an iptables issue as a routing issue. I'm guessing
you had your network configured with the same subnet on two different
interfaces. I'm not really sure how it all works, but with eth1 coming
up first and being attached to the 192.168.1.* subnet, then when the
machine goes looking for 192.168.1.1 (the router) it looks on eth1 and
can't find it because its on the other interface. make sense? 

that's surely a flawed explanation, but it works for me.

A


signature.asc
Description: Digital signature

Re: network configuration issue - iptables

[Adam Hardy]

Andrew Sackville-West on 25/06/07 04:27, wrote:

On Sat, Jun 23, 2007 at 08:35:09PM +0100, Adam Hardy wrote:
I have set up a network for our house using a gateway server with etch and 
two NICs, eth1 for the internal network and eth2 for the DSL modem.


I set up iptables with firewall-builder and all seems OK, but I can only 
ever access the web interface on the DSL modem from the gateway server 
directly after downing the internal network on eth1.


The modem's web interface is on 192.168.1.1 on eth2 and if I don't down 
eth1, the browser won't find it.


number your internal lan addresses in a different subnet. Use
192.168.2.x for your lan. Then, because the modem is on a different
subnet, it should "just work". At least in my lan it works that
way. My dsl modem is accessible as 192.168.0.1 while my lan is
192.168.1.x.

also, you can sometimes (depending on how its all configured) access
the modem by browsing to your *public ip* which resolves to your
modem, but since you're coming form the inside, it gives you the
configuration. 


That worked! Respect to you. I have only a small grasp of what my iptables 
config does, but it works.


Fortunately I recently set up DHCP for my whole LAN so it was just a case of 
changing the internal LAN in two or three files on the server from 192.168.1.* 
to 192.168.0.*


Thanks for the idea.


Adam


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: network configuration issue - iptables

[Andrew Sackville-West]

On Sat, Jun 23, 2007 at 08:35:09PM +0100, Adam Hardy wrote:
> I have set up a network for our house using a gateway server with etch and 
> two NICs, eth1 for the internal network and eth2 for the DSL modem.
> 
> I set up iptables with firewall-builder and all seems OK, but I can only 
> ever access the web interface on the DSL modem from the gateway server 
> directly after downing the internal network on eth1.
> 
> The modem's web interface is on 192.168.1.1 on eth2 and if I don't down 
> eth1, the browser won't find it.

number your internal lan addresses in a different subnet. Use
192.168.2.x for your lan. Then, because the modem is on a different
subnet, it should "just work". At least in my lan it works that
way. My dsl modem is accessible as 192.168.0.1 while my lan is
192.168.1.x.

also, you can sometimes (depending on how its all configured) access
the modem by browsing to your *public ip* which resolves to your
modem, but since you're coming form the inside, it gives you the
configuration. 

hth.

A


signature.asc
Description: Digital signature

Re: network configuration problem

[David Z Maze]

"Ritesh Raj Sarraf" <[EMAIL PROTECTED]> writes:

> 1.  (*) text/plain  ( ) text/html   

(Please post to the list in plain text only.)

> i'm a newbie to Debian. I just shifted from RedHat. I've got two lan
> cards on my debian system. one connected to the internet and the
> other to my local lan. i'm not able to ping my ISP DNS server from
> my debian machine.
>
> Details:
> eth0 (Ethernet connected to ISP)
> IP 192.168.1.43
> DNS 192.168.1.1
> Gateway 192.168.1.1
> Subnet 255.255.255.0

So, to be clear: you're logged in on this machine, you type 'ping
192.168.1.1', and nothing happens?  Is the physical infrastructure
working?  (Are all the cables connected, do you have the right blinky
lights everywhere?)  If that all works, what do 'ifconfig eth0' and
'route -n' say?

> eth1 (Ethernet connected to my LAN)
> IP 10.0.0.1
> DNS 192.168.1.1
> Gateway 192.168.1.43
> Subnet 255.0.0.0

"Gateway" isn't something you want to define on more than one
interface; if you do define it, if needs to be an address on the same
network (so, in this case, a 10.x.x.x address).  How exactly are you
specifying "gateway" and "DNS" here?

It looks like the setup you want is:

-- eth0 is on 192.168.1.43/24
-- eth1 is on 10.0.0.1/8
-- The default route is via 192.168.1.1 (on eth0)
-- The DNS server is 192.168.1.43, which happens to be on eth0's
   network
-- (Optional) ipmasq from eth1 to eth0

And none of the settings you've given so far contradict this.  :-)

-- 
David Maze [EMAIL PROTECTED]  http://people.debian.org/~dmaze/
"Theoretical politics is interesting.  Politicking should be illegal."
-- Abra Mitchell


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: network configuration problem

[Uwe Dippel]

On Thu, 08 Jan 2004 03:30:28 +0530, Ritesh Raj Sarraf wrote:

> hi all,
> i'm a newbie to Debian. I just shifted from RedHat. I've got two lan cards on my 
> debian system. one connected to the internet and the other to my local lan. 
> i'm not able to ping my ISP DNS server from my debian machine.

Also coming from RedHat, this doesn't look like a Debian problem, but
rather like a settings problem. Eventually including route.
Does your ISP actually set you on a private network ? Plus the strange
10.0.0.1 for your Internal Network with a gateway being your outside IP.
Here I'd rather expect no gateway, but a route ... .

Anyway, difficult to say, because we cannot guess the correct settings !


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: network configuration

[Christophe Courtois]

Le Mercredi 27 Août 2003 13:03, James LeClair a déclamé :
>The problem is that I can not get both eth0 and eth1
> working at the same time. eth0: io=0x300 irq=10
> eth1: io=0x240 irq=3

 I've got this on my old P75 (2 ISA cards too), in /etc/modutils/aliases

alias eth0  ne
alias eth1  ne
options ne  io=0x240,0x280 irq=11,10

 And eth0 and eth1 are activated in /etc/modules.

 Hope it helps...

-- 
Christophe Courtois - Ostwald, Alsace, France
http://www.courtois.cc/ - Clé PGP : 0F33E837
--
 If speed scares you, try Microsoft Windows.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: network configuration

[Johan Braennlund]

In article <[EMAIL PROTECTED]> you wrote:
> Hello all. Almost there. Still working on this 486. Hopefully it will be a 
> routing, firewalling box. The 2 nics in this box are dlink 220 isa. I have 
> been able to determine that they both require the "ne" network module. The 
> problem is that I can not get both eth0 and eth1 working at the same time.
> eth0: io=0x300 irq=10
> eth1: io=0x240 irq=3

Googling for 'linux "two nics" "ne module"' turns up

http://www.sunhelp.org/pipermail/rescue/2002-April/053577.html

which suggests that

/sbin/modprobe io=0x300,0x240 ne

should work. If it doesn't, please post the error message.

- Johan


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: network configuration

[Jeff]

Ernesto Marquina, 2002-Nov-27 20:05 +:
> Hi,
> 
> While I was configuring my network on debian woody, the isntaller
> asked me if theres an DHCP server on my network, I answered YES and
> he configured everything for me. Now everytime I start my linux I
> get this netenv window...and I choose the "default" configuration,
> which I think is the one that the installer generated for me when it
> found a DHCP server the last time.
> 
> But now I'm in another network, and when I select the "default"
> profile, it holds there for ages and worst thing that after that, I
> dont have network connection. I checked the server-default file that
> the installer genereated, and I have some environment variables
> which have wrong IP addresses, it has IP address from the last
> network I logged in, but not for the current network I'm in.
>
> Does anybody know why could that be?, or with this "default"
> configuration netenv is not looking for a DHCP server anymore in
> order to assign new addresses?, if so...how can I "force" linux to
> search for a DHCP server?

It looks like you have the package "netenv" installed with allows you
to configure multiple network setups and choose the appropriate one.
Look at "man netenv" to see out to add the other network to the config
so you'll see "default" and "other" on the netenv window.

jc

-- 
Jeff CoppockSystems Engineer
Diggin' Debian  Admin and User


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: network configuration problem

[Peter Whysall]

On Fri, 2002-06-28 at 07:49, Lars Jensen wrote:
> Initially when I first set up my system (potato), I configured the
> network for DHCP. How do I change it to a manual configuration of DNS,
> gateway and permanent IP? Which files do I need to change? Is there a
> tool for this?
> 
> Also, how do I change my host name.

Your hostname is set in /etc/hostname.

DNS is dealt with in /etc/resolv.conf like so:

search 
nameserver 

The "search" line is optional.

To configure the network card itself, you want to look at
/etc/network/interfaces

Here's the relevant stanza from mine:

auto eth0
iface eth0 inet static
address 10.200.1.2
netmask 255.255.0.0
gateway 10.200.1.1
broadcast 10.200.255.255

Hope this helps.

Take care, 

Peter.

-- 
Peter Whysall
[EMAIL PROTECTED]
The TLD in my email address is sdrawkcab.
Debian GNU/Linux 3.0 sid -- kernel 2.4.18


signature.asc
Description: This is a digitally signed message part

Re: network configuration problem

[vanillicat]

On Fri, 2002-06-28 at 02:49, Lars Jensen wrote:
 
> Also, how do I change my host name.


I believe hostname is stored /etc/hostname


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: network configuration??

[Elizabeth Barham]

The name of the program that is being run is netenv; it is there to
aid laptop users who may change their network environment options
regularly (example, one for home, one for the office, another for a
remote location).

You can just disable netenv from being run. Probably the
easiest way is to edit /etc/init.d/netenv

 begin /etc/init.d/netenv 
#!/bin/sh

###
# NEW LINES
RUN_ME=0

if [ "$RUN_ME" = "0" ] ; then
exit 0;
fi
# fin
###

test -x /sbin/netenv || exit 0

case "$1" in
start | restart | force-reload | reload)
/bin/rm -f /etc/netenv/netenv
/sbin/netenv
;;
stop)
;;
*)
echo "Usage: $0 {start|stop|restart|reload|force-reload}"
exit 1
;;
esac
 end /etc/init.d/netenv 

The other method would be to remove the symbolic link in the
/etc/rc[0-9S].d directories. I find simply changing the init script
easier personally.

Make sure your /etc/network/interfaces is set up correctly, though.

Elizabeth


Michael Griffis <[EMAIL PROTECTED]> writes:

> I am new to linux and rather ambitiously installed Woody on my Fujitsu
> laptop with good results.
> 
> However every time I reboot I am asked to choose a network environment
> and the only option is to set a new environment and enter a new IP.  I
> use DHCP so I don't enter an IP and everything seems to work fine.  
> 
> Is this a network configuration problem?  Is there anyway to avoid this
> extra step?
> 
> thanks,
> 
> mg
> 
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: network configuration??

[Sean 'Shaleh' Perry]

On 22-Mar-2002 Michael Griffis wrote:
> I am new to linux and rather ambitiously installed Woody on my Fujitsu
> laptop with good results.
> 
> However every time I reboot I am asked to choose a network environment
> and the only option is to set a new environment and enter a new IP.  I
> use DHCP so I don't enter an IP and everything seems to work fine.  
> 
> Is this a network configuration problem?  Is there anyway to avoid this
> extra step?
> 

you chose 'laptop' during the install, right?  It looks like you have a program
installed which tries to allow you to have multiple hard coded IPs based on
where you turn on your laptop.  I believe it is called 'netenv'.  Try purging
the package.

Re: network configuration??

[Angus D Madden]

Michael Griffis, Fri, Mar 22, 2002 at 10:39:01AM -0700: 
> I am new to linux and rather ambitiously installed Woody on my Fujitsu
> laptop with good results.
> 
> However every time I reboot I am asked to choose a network environment
> and the only option is to set a new environment and enter a new IP.  I
> use DHCP so I don't enter an IP and everything seems to work fine.  
> 
> Is this a network configuration problem?  Is there anyway to avoid this
> extra step?
> 

Does the screen look like this:
http://netenv.sourceforge.net/netenv.gif ?

If so, you have netenv installed on your laptop.  'apt-get remove
netenv' should take care of it.

Make sure your /etc/network/interfaces file is configured for dhcp and
you should be ready to go.

g



-- 
Brought to you by Debian 3.0
Linux took 2.4.16 #1 SMP Sat Jan 5 12:52:24 EST 2002 i686 unknown


pgp9QbkySjP6e.pgp
Description: PGP signature

[jason@whizzird.net: Re: Network configuration]

[Jason Majors]

You don't need an rc.local script.
If you look in /etc/rc2.d/ you'll see lots of S scripts.
These are the scripts that get run when you start the system. The 'S'
is for "Start" (I guess), and there are "K" scripts for "Kill" in other
related directories. The number is the order in which it will run 00 is
first, 99 is last. These files are symbolic links to files in the
/etc/init.d/ directory.
There are two files that would be in your /etc/init.d if you installed
the networking and apache packages (which you should, the package
management is debian's best feature): networking and apache. If they're
not there, make up your own and symlink them to /etc/rc2.d. Or if you
install the packages ifupdown, net-tools, and netbase (which you might
have), you'll have the networking script built for you, and you just
add your settings to the /etc/network/interfaces file.

If you do build your own, it's best to put one set of related startup
commands in one file, so you can bring that daemon up or down, without
interfering with others.

On Thu, Aug 23, 2001 at 05:19:19PM -0700, bob parker scribbled...
> I'm still quite new to this excellent os (Potato r3) 
> and am building a web server. 
> I have made a script - rc.local to configure my 
> network adapter using ifconfig and route. 
> At the moment I'm invoking this by hand after bootup. 
> My question is where do I install this script so that 
> it's automatically run on boot up? 
>  
> I'm also running Apache by hand, having built it from 
> a tarball off a magazine CD. That's what the boss 
> wanted!. Should I start that from inside the rc.local 
> script? 
>  
> Thanks 
> Bob Parker 

Re: Network configuration

[David Nusinow]

Hi Bob,
You can (should) stick your script in /etc/init.d. Then, check what 
runlevel 
you're in. It should be at the top of /etc/inittab. For that runlevel, go in 
to the appropriate /etc/rcX.d folder (X corresponding to your runlevel) and 
put a symlink to the script in /etc/init.d. Pay attention to the prefix on 
the alias name, the S is critical (won't load without it), and the number 
determines what order scripts are executed.
If the script isn't too complex, you may be able to do what you need 
without 
it. Check the manpage for "interfaces", which is the config file for ifup and 
ifdown. It should be able to do the stuff you want without resorting to a 
custom script. interfaces is in /etc/network by the way. Good luck!

- David Nusinow
  [EMAIL PROTECTED]

On Thursday 23 August 2001 05:19 pm, bob parker wrote:
> I'm still quite new to this excellent os (Potato r3)
> and am building a web server.
> I have made a script - rc.local to configure my
> network adapter using ifconfig and route.
> At the moment I'm invoking this by hand after bootup.
> My question is where do I install this script so that
> it's automatically run on boot up?
>
> I'm also running Apache by hand, having built it from
> a tarball off a magazine CD. That's what the boss
> wanted!. Should I start that from inside the rc.local
> script?
>
> Thanks
> Bob Parker

Re: Network Configuration

[Nathan]

First you need to find out what brand of card you have, then setting it
up for a static IP is pretty easy.
once u have found out what card you have and installed it in the kernel
then go to /etc/network and edit interfaces, it should look a little like
this:
auto eth0
iface eth0 inet static
   
address   192.168.0.1   
<<-=- change to you static IP
   
netmask    255.255.255.0  <<-=- the netmask for
your WAN
   
network 192.168.0.0   
<<-=- change to your network address
   
broadcast    192.168.0.255    <<-=-
your getting the picture
   
gateway  192.168.0.10   
<<-=- the IP of the computer that handles the Internet connection
now this may not be what u want but this is sort of the general idea
of how i did it :o)
 
 
 
 
 
 
Raghunathan VS wrote:

Sir/Ma'm, I
have installed Debian on my system. But I have problem in configuring the
internet connection.pppconfig
seem to offer solution for dial-up lines.But
I have a LAN card installed in my system and it is on WAN having an unique
IP address.How do I install
my LAN card and configure the IP for net connectivity ? Expecting
quick answer to proceed furtherThanksRegardsRaghu

Re: Network configuration

[Nate Amsden]

Steve Doerr wrote:
> 
> Hi.  I wonder if anybody has any advice on network configuration,
> because I can't get eth1 to pass any traffic out of my router box.
> 
> I've got box1's eth0 connected to my dsl line through the dsl
> modem/router and it picks up the ip, etc. through dhcpcd.  This card is
> connected to the internet fine.
> 
> I've got box1's eth1 connected to jack 1 of the hub, but the hub doesn't
> show anything connected.  eth1 is a good card, and I can ping it at
> 192.168.1.1, but I've missed something about configuring it to send
> traffic out to my hub and my network.
> 
> eth1 on box1 is configured as follows in /etc/network/interfaces (even
> though I'm using dhcpcd on eth0, the external ip is always the same, so
> I'm using static on eth1):
> 
> iface eth1 inet static
>address 192.168.1.1
>netmask 255.255.255.0
>network 192.168.1.0
>broadcast 192.168.1.255
>gateway 

for one eth1 should have no gateway. i don't know if this would cause the
problem your having but it might. just keep the gateway on eth0 if traffic
is going out there. also be sure ip forwarding is turned on.

if your using kernel 2.2:

echo 1 >/proc/sys/net/ipv4/ip_forward

also if your doing IP MASQ be sure the rules are enabled/configured right.

and be sure that all other machines are using 192.168.1.1 as their gateway
if this machine is the only router/gateway.

nate


-- 
:::
ICQ: 75132336
http://www.aphroland.org/
http://www.linuxpowered.net/
[EMAIL PROTECTED]

Re: network configuration scripts

[Silver]

> the debian way is now to edit /etc/network/interfaces
> this is mine (there are 2 network cards in my box) :
>
> <-- cut here -->
> # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
>
> # The loopback interface
> auto lo
> iface lo inet loopback
>
> # ADSL interface
> auto eth0
> iface eth0 inet static
> address 10.0.0.10
> netmask 255.255.255.0
> network 10.0.0.0
> broadcast 10.0.0.255
> up /etc/network/ipchains.rules
>
> # Local network
> auto eth1
> iface eht1 inet static
> address 192.168.1.1
> netmask 255.255.255.0
> network 192.168.1.0
> broadcast 192.168.1.255
> <-- cut here -->
>
> note that it acts as a firewall and i run the ipchains rules when the
> interface comes up
> this way you can just do 'ifup eth0' and 'ifdown eth0' to raise/shutdown
an
> interface =)
>
> IMHO, there shouldnt be any customization in /etc/init.d, it's just a
place
> for startup and
> shutdown scripts (you can add yours for your particular services if you
> want).
>
> Silver
>
> - Original Message -
> From: "Keegan Prendergast" <[EMAIL PROTECTED]>
> To: 
> Sent: Wednesday, November 15, 2000 10:27 PM
> Subject: network configuration scripts
>
>
> >I have my debian linux box setup as a masqing gateway for the rest of
> > the computers in the house.  The problem is, I did it by hand and have
not
> > rebooted since, because i could not figure out where i should put the
> > commands =).  Should they go in /etc/init.d/networking, or some local
init
> > file. Also has the structure of the network startup changed, because all
> > of the documentation i have found refers to paths or files, that are not
> > the same as the ones i haveAt anyrate if any one knows the source of
> > any detailed/current documentation on the way debian runs startup files,
> > network configuration, or just has an answer to my question please
> > reply...thanks...oh yeah...i am running potato..

Re: network configuration scripts

[will trillich]

On Wed, Nov 15, 2000 at 03:27:14PM -0600, Keegan Prendergast wrote:
>I have my debian linux box setup as a masqing gateway for the rest of
> the computers in the house.  The problem is, I did it by hand and have not
> rebooted since, because i could not figure out where i should put the
> commands =).  Should they go in /etc/init.d/networking, or some local init
> file. Also has the structure of the network startup changed, because all
> of the documentation i have found refers to paths or files, that are not
> the same as the ones i haveAt anyrate if any one knows the source of
> any detailed/current documentation on the way debian runs startup files,
> network configuration, or just has an answer to my question please
> reply...thanks...oh yeah...i am running potato..

/etc/network/interfaces is where you should set up potato
networking parameters, including your internal (192.168.*.*
probably) net card and your external net card; then

apt-get install ipmasq

and you should be done.

for your other computers, specify 192.168.debian.box as
their gateways. there's a bit more to it than this,
and someone's working on it, hot and heavy, over
at eGroups.com/group/newbieDoc...

-- 
There are only two places in the world where time takes
precedence over the job to be done.  School and prison. 
--William Glasser 

[EMAIL PROTECTED]***http://www.dontUthink.com/

volunteer to document your experience for next week's
newbies -- http://www.eGroups.com/messages/newbieDoc

Re: network configuration - after install

[Hugo van der Merwe]

On Wed, Oct 11, 2000 at 01:38:22PM +, Jamil Geor wrote:
> Hi,
>   You could just use modconf to install the network card module that
> you need.
> 
> Jamil

Thanks. It appears, however, that I didn't make the question very clear.
Just installing the module is not going to get the network configured:
/etc/hosts, /etc/resolv.conf, /etc/network/interfaces... these files
have all not been set up as necessary, and I think I may be missing a
couple, which is why I'm looking for something similar to "pcnetconfig"
(which is for pcmcia network cards).

Thanks,
Hugo van der Merwe

> On Mon, 9 Oct 2000, Hugo van der Merwe wrote:
> > pcnetconfig does this job. Is there an easy way to get the networking
> > configured after a base install? (I'm considering going through the

Re: network configuration - after install

[Jamil Geor]

Hi,
You could just use modconf to install the network card module that
you need.

Jamil

On Mon, 9 Oct 2000, Hugo van der Merwe wrote:

> Hello,
> 
> I am doing another debian install, and was uncertain about the network
> card type. I decided to skip that part of the install, hoping to find an
> easy way to do it after the basic system is up and running. On a laptop,
> pcnetconfig does this job. Is there an easy way to get the networking
> configured after a base install? (I'm considering going through the
> installation menu again.)
> 
> Thanks,
> Hugo van der Merwe
> 
> ps. Is /dev/cdrom created when the module is loaded, or some other time
> by some other script?
> 
> 
> -- 
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
> 
> 
> 

Re: Network Configuration

[kmself]

On Tue, Sep 12, 2000 at 02:50:21PM +0800, Saran ([EMAIL PROTECTED]) wrote:
> Hi,
> 
> I thought linuxconf is only available on RedHat ?

[EMAIL PROTECTED]:karsten]$ apt-cache search linuxconf
linuxconf - a powerful Linux administration kit
linuxconf-x - X11 GUI for Linuxconf
linuxconf-dev - Development files for Linuxconf
linuxconf-i18n - international language files for Linuxconf

With very few exceptions (largely proprietary software), software
available for GNU/Linux is available on *all* systems.  RedHat is
committed to releasing all of its software under GPL, this includes
linuxconf.

-- 
Karsten M. Self  http://www.netcom.com/~kmself
 Evangelist, Opensales, Inc.http://www.opensales.org
  What part of "Gestalt" don't you understand?   Debian GNU/Linux rocks!
   http://gestalt-system.sourceforge.net/K5: http://www.kuro5hin.org
GPG fingerprint: F932 8B25 5FDD 2528 D595 DC61 3847 889F 55F2 B9B0


pgpHGlIwqnA83.pgp
Description: PGP signature

RE: Network Configuration

[Saran]

Well, the way my company network is configured is that the RH box acts as
router and gateway and firewall both for internal and external network;
internal here being the 100.100.100.x network and external being
255.255.255.248.
I suppose that the same goes for my colleague's PC as it is configured
exactly as the RH box.  My guess would be that the collisions is due to my
colleague's PC and the RH box acting as router and gateway on the same
network ???

Okay, the reason for my wanting to do the above is to be able to connect to
my Debian PC via the 100.100.100.x internal to the LAN when I am in the
office and also to connect to my Debian PC from an external dialup via the
255.255.255.248 network when outside the office.  Right now, I am unable to
connect directly to my Debian PC by telnetting directly to it.  I have to
telnet to the RH box first and then connect to my Debian PC via the
100.100.100.x address.  Internal LAN has false addresses and the external
network with 255.255.255.248 netmask has real addresses (registered
addresses).

Any ideas ?
Thank you in advance.

Cheers,
Saranjit Singh.


-Original Message-
From: CHEONG, Shu Yang [Patrick] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 12, 2000 3:16 PM
To: 'Saran'
Cc: 'debian-user@lists.debian.org'
Subject: RE: Network Configuration


1.  Linuxconf is a Linux administration/configuration tool...as such any
Linux distribution can run it (see
http://www.solucorp.qc.ca/linuxconf/).

2.  Whoa...2 (I repeat 2) gateways...and 2 routersso which box acts
as gateway for which network..confusing isn't it andit may be the cause
of those collisions you see on the Debian box .I suggest one box be used as
a router and anotherbe used as the gateway (and firewall) to the
external network..


HTH

Regards.

Patrick Cheong
Information Systems Assurance
Measat Broadcast Network Systems
e-mail: mailto:[EMAIL PROTECTED]
Visit us at: http://www.astro.com.my

> -Original Message-
> From: Saran [SMTP:[EMAIL PROTECTED]
> Sent: Tuesday, September 12, 2000 2:50 PM
> To:   CHEONG, Shu Yang [Patrick]; debian-user@lists.debian.org
> Subject:  RE: Network Configuration
>
> Hi,
>
> I thought linuxconf is only available on RedHat ?
>
> Yes, the RH box is acting as the gateway for the network also.
>
> Dunno about the kernel version, but I'll try it later.
>
> As for the collisions, I'm not sure, but there has been no problems.
> Could
> this be the issue ?  Both the RH server and my colleague's RH PC can
> connect
> to the network, but my Debian can't.  When I boot up my PC, there are no
> conflict errors generated.  How do I check whether there are any conflicts
> other than this method ?
>
> Note that I have not included the ifconfig and route info of my Debian PC
> here.  But basically, I configured as the ones below, with the IP address
> being the only difference.
>
> Thanks in advance
> Saranjit Singh.
>
>
> -Original Message-
> From: CHEONG, Shu Yang [Patrick] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 12, 2000 2:41 PM
> To: debian-user@lists.debian.org
> Subject: RE: Network Configuration
>
>
> See below
>
> Patrick Cheong
> Information Systems Assurance
> Measat Broadcast Network Systems
> e-mail: mailto:[EMAIL PROTECTED]
> Visit us at: http://www.astro.com.my
>
> > -Original Message-
> > From:   Saran [SMTP:[EMAIL PROTECTED]
> > Sent:   Tuesday, September 12, 2000 2:05 PM
> > To: debian-user@lists.debian.org
> > Subject:Network Configuration
> > Importance: High
> >
> > Hi Guys,
> >
> > I just subscribed to this list to get more information regarding the
> > Debian
> > Linux, which kind of lacks a lot of information resources.  Most sites
> are
> > about RedHat Linux and as much as Debian is giving me problems, I still
> > like
> > to stick to this distribution instead of moving to RedHat.  I have
> several
> > questions that I'd like to ask namely :
> > 1.  Does Debian have any administrative tools akin to IBM AIX
> > smitty, smit,
> > wsm (Web System Management) whereby it allows me to administer and
> manage
> > the system without having to edit files and typing in complex commands
> > every
> > time ?
>   [CHEONG, Shu Yang (Patrick)]  Have you tried linuxconf?
>
> > 2. This is critical and I am about to start banging my head on the
> > wall,
> > except that I still holding on to the hope that you guys can help me out
> > here.  Well, currently there is a system within my environment which is
> > running RedHat 6.x and it has two ethernet adapter (3Com) installed on
> the
> > system.  This sys

RE: Network Configuration

[CHEONG, Shu Yang \[Patrick\]]

1.  Linuxconf is a Linux administration/configuration tool...as such any
Linux distribution can run it (see
http://www.solucorp.qc.ca/linuxconf/).

2.  Whoa...2 (I repeat 2) gateways...and 2 routersso which box acts
as gateway for which network..confusing isn't it andit may be the cause
of those collisions you see on the Debian box .I suggest one box be used as
a router and anotherbe used as the gateway (and firewall) to the
external network..


HTH

Regards.

Patrick Cheong
Information Systems Assurance
Measat Broadcast Network Systems
e-mail: mailto:[EMAIL PROTECTED]
Visit us at: http://www.astro.com.my

> -Original Message-
> From: Saran [SMTP:[EMAIL PROTECTED]
> Sent: Tuesday, September 12, 2000 2:50 PM
> To:   CHEONG, Shu Yang [Patrick]; debian-user@lists.debian.org
> Subject:  RE: Network Configuration
> 
> Hi,
> 
> I thought linuxconf is only available on RedHat ?
> 
> Yes, the RH box is acting as the gateway for the network also.
> 
> Dunno about the kernel version, but I'll try it later.
> 
> As for the collisions, I'm not sure, but there has been no problems.
> Could
> this be the issue ?  Both the RH server and my colleague's RH PC can
> connect
> to the network, but my Debian can't.  When I boot up my PC, there are no
> conflict errors generated.  How do I check whether there are any conflicts
> other than this method ?
> 
> Note that I have not included the ifconfig and route info of my Debian PC
> here.  But basically, I configured as the ones below, with the IP address
> being the only difference.
> 
> Thanks in advance
> Saranjit Singh.
> 
> 
> -Original Message-
> From: CHEONG, Shu Yang [Patrick] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, September 12, 2000 2:41 PM
> To: debian-user@lists.debian.org
> Subject: RE: Network Configuration
> 
> 
> See below
> 
> Patrick Cheong
> Information Systems Assurance
> Measat Broadcast Network Systems
> e-mail: mailto:[EMAIL PROTECTED]
> Visit us at: http://www.astro.com.my
> 
> > -Original Message-
> > From:   Saran [SMTP:[EMAIL PROTECTED]
> > Sent:   Tuesday, September 12, 2000 2:05 PM
> > To: debian-user@lists.debian.org
> > Subject:Network Configuration
> > Importance: High
> >
> > Hi Guys,
> >
> > I just subscribed to this list to get more information regarding the
> > Debian
> > Linux, which kind of lacks a lot of information resources.  Most sites
> are
> > about RedHat Linux and as much as Debian is giving me problems, I still
> > like
> > to stick to this distribution instead of moving to RedHat.  I have
> several
> > questions that I'd like to ask namely :
> > 1.  Does Debian have any administrative tools akin to IBM AIX
> > smitty, smit,
> > wsm (Web System Management) whereby it allows me to administer and
> manage
> > the system without having to edit files and typing in complex commands
> > every
> > time ?
>   [CHEONG, Shu Yang (Patrick)]  Have you tried linuxconf?
> 
> > 2. This is critical and I am about to start banging my head on the
> > wall,
> > except that I still holding on to the hope that you guys can help me out
> > here.  Well, currently there is a system within my environment which is
> > running RedHat 6.x and it has two ethernet adapter (3Com) installed on
> the
> > system.  This system is running Masquarading (Sp ???), whereby there are
> > two
> > networks, one is running on 100.100.100.x and the other is running on
> > 255.255.255.x.  This system is also acting as the gateway.
>   [CHEONG, Shu Yang (Patrick)]  Is the RH box acting as a gateway,
> too?
> > A colleague of mine also runs his system on Redhat 6.x and is able to
> view
> > two networks on his system also having two ethernet adapters (Generic,
> > dunno
> > what brand they are).
> > What I can't understand and which is giving me pain is that my system
> > configured with Debian 2.1 cannot view the two networks.  I have two
> > ethernet adapters (3Com) installed and if I configure both the cards
> with
> > one pointing to the 100.100.100.x network and the other with the
> > 255.255.255.x network, the system will not be able to ping any host out
> > there (I have already configured the ifconfig and route similar to the
> RH
> > 6.x systems).  But if I disable the 255.255.255.x network, I can ping
> and
> > view the other systems.  If I do it the other way round, the system
> cannot
> > detect any host whatever (Disable 100.100.100.x and enable
> 255.255.255.x).
> >
> > I have checked the connections t

RE: Network Configuration

[Saran]

Hi,

I thought linuxconf is only available on RedHat ?

Yes, the RH box is acting as the gateway for the network also.

Dunno about the kernel version, but I'll try it later.

As for the collisions, I'm not sure, but there has been no problems.  Could
this be the issue ?  Both the RH server and my colleague's RH PC can connect
to the network, but my Debian can't.  When I boot up my PC, there are no
conflict errors generated.  How do I check whether there are any conflicts
other than this method ?

Note that I have not included the ifconfig and route info of my Debian PC
here.  But basically, I configured as the ones below, with the IP address
being the only difference.

Thanks in advance
Saranjit Singh.


-Original Message-
From: CHEONG, Shu Yang [Patrick] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 12, 2000 2:41 PM
To: debian-user@lists.debian.org
Subject: RE: Network Configuration


See below

Patrick Cheong
Information Systems Assurance
Measat Broadcast Network Systems
e-mail: mailto:[EMAIL PROTECTED]
Visit us at: http://www.astro.com.my

> -Original Message-
> From: Saran [SMTP:[EMAIL PROTECTED]
> Sent: Tuesday, September 12, 2000 2:05 PM
> To:   debian-user@lists.debian.org
> Subject:  Network Configuration
> Importance:   High
>
> Hi Guys,
>
> I just subscribed to this list to get more information regarding the
> Debian
> Linux, which kind of lacks a lot of information resources.  Most sites are
> about RedHat Linux and as much as Debian is giving me problems, I still
> like
> to stick to this distribution instead of moving to RedHat.  I have several
> questions that I'd like to ask namely :
>   1.  Does Debian have any administrative tools akin to IBM AIX
> smitty, smit,
> wsm (Web System Management) whereby it allows me to administer and manage
> the system without having to edit files and typing in complex commands
> every
> time ?
[CHEONG, Shu Yang (Patrick)]  Have you tried linuxconf?

>   2. This is critical and I am about to start banging my head on the
> wall,
> except that I still holding on to the hope that you guys can help me out
> here.  Well, currently there is a system within my environment which is
> running RedHat 6.x and it has two ethernet adapter (3Com) installed on the
> system.  This system is running Masquarading (Sp ???), whereby there are
> two
> networks, one is running on 100.100.100.x and the other is running on
> 255.255.255.x.  This system is also acting as the gateway.
[CHEONG, Shu Yang (Patrick)]  Is the RH box acting as a gateway,
too?
> A colleague of mine also runs his system on Redhat 6.x and is able to view
> two networks on his system also having two ethernet adapters (Generic,
> dunno
> what brand they are).
> What I can't understand and which is giving me pain is that my system
> configured with Debian 2.1 cannot view the two networks.  I have two
> ethernet adapters (3Com) installed and if I configure both the cards with
> one pointing to the 100.100.100.x network and the other with the
> 255.255.255.x network, the system will not be able to ping any host out
> there (I have already configured the ifconfig and route similar to the RH
> 6.x systems).  But if I disable the 255.255.255.x network, I can ping and
> view the other systems.  If I do it the other way round, the system cannot
> detect any host whatever (Disable 100.100.100.x and enable 255.255.255.x).
>
> I have checked the connections to the ethernet adapters and they are
> functioning.
>
> I have updated my kernel to the 2.2.16 enabling masquarading but am still
> unable to detect any host when both the ethernet adapters are enabled.
>
[CHEONG, Shu Yang (Patrick)]  I suggest you use the 2.2.17 kernel
instead (even the 2.2.17-preX-X which includes Alan Cox's patches) as IICR,
there were problems with the 2.2.16 kernel. Can't reccall whether the
problem was in relation to security or some other issue.

> What could be the problem here ?
>
> I've included the ifconfig and route info for the gateway system and also
> my
> colleague's system for your info.  My system route and ifconfig
> information
> is as the ones below, but I still can't detect both networks.
>
> $ /sbin/ifconfig
> eth0  Link encap:Ethernet  HWaddr 00:60:97:C4:FB:97
>   inet addr:202.190.130.195  Bcast:202.190.130.199
> Mask:255.255.255.248
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:12722 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:12388 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:1 txqueuelen:100
>   Interrupt:5 Base address:0xe400
>
> eth1  Link encap:Ethernet  HWaddr 00:60:08:91:B1:C5
>   

RE: Network Configuration

[CHEONG, Shu Yang \[Patrick\]]

See below

Patrick Cheong
Information Systems Assurance
Measat Broadcast Network Systems
e-mail: mailto:[EMAIL PROTECTED]
Visit us at: http://www.astro.com.my

> -Original Message-
> From: Saran [SMTP:[EMAIL PROTECTED]
> Sent: Tuesday, September 12, 2000 2:05 PM
> To:   debian-user@lists.debian.org
> Subject:  Network Configuration
> Importance:   High
> 
> Hi Guys,
> 
> I just subscribed to this list to get more information regarding the
> Debian
> Linux, which kind of lacks a lot of information resources.  Most sites are
> about RedHat Linux and as much as Debian is giving me problems, I still
> like
> to stick to this distribution instead of moving to RedHat.  I have several
> questions that I'd like to ask namely :
>   1.  Does Debian have any administrative tools akin to IBM AIX
> smitty, smit,
> wsm (Web System Management) whereby it allows me to administer and manage
> the system without having to edit files and typing in complex commands
> every
> time ?
[CHEONG, Shu Yang (Patrick)]  Have you tried linuxconf?

>   2. This is critical and I am about to start banging my head on the
> wall,
> except that I still holding on to the hope that you guys can help me out
> here.  Well, currently there is a system within my environment which is
> running RedHat 6.x and it has two ethernet adapter (3Com) installed on the
> system.  This system is running Masquarading (Sp ???), whereby there are
> two
> networks, one is running on 100.100.100.x and the other is running on
> 255.255.255.x.  This system is also acting as the gateway.
[CHEONG, Shu Yang (Patrick)]  Is the RH box acting as a gateway,
too?
> A colleague of mine also runs his system on Redhat 6.x and is able to view
> two networks on his system also having two ethernet adapters (Generic,
> dunno
> what brand they are).
> What I can't understand and which is giving me pain is that my system
> configured with Debian 2.1 cannot view the two networks.  I have two
> ethernet adapters (3Com) installed and if I configure both the cards with
> one pointing to the 100.100.100.x network and the other with the
> 255.255.255.x network, the system will not be able to ping any host out
> there (I have already configured the ifconfig and route similar to the RH
> 6.x systems).  But if I disable the 255.255.255.x network, I can ping and
> view the other systems.  If I do it the other way round, the system cannot
> detect any host whatever (Disable 100.100.100.x and enable 255.255.255.x).
> 
> I have checked the connections to the ethernet adapters and they are
> functioning.
> 
> I have updated my kernel to the 2.2.16 enabling masquarading but am still
> unable to detect any host when both the ethernet adapters are enabled.
> 
[CHEONG, Shu Yang (Patrick)]  I suggest you use the 2.2.17 kernel
instead (even the 2.2.17-preX-X which includes Alan Cox's patches) as IICR,
there were problems with the 2.2.16 kernel. Can't reccall whether the
problem was in relation to security or some other issue.

> What could be the problem here ?
> 
> I've included the ifconfig and route info for the gateway system and also
> my
> colleague's system for your info.  My system route and ifconfig
> information
> is as the ones below, but I still can't detect both networks.
> 
> $ /sbin/ifconfig
> eth0  Link encap:Ethernet  HWaddr 00:60:97:C4:FB:97
>   inet addr:202.190.130.195  Bcast:202.190.130.199
> Mask:255.255.255.248
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:12722 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:12388 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:1 txqueuelen:100
>   Interrupt:5 Base address:0xe400
> 
> eth1  Link encap:Ethernet  HWaddr 00:60:08:91:B1:C5
>   inet addr:100.100.100.150  Bcast:100.100.100.255
> Mask:255.255.255.0
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:16211 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:17041 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:712 txqueuelen:100
>   Interrupt:9 Base address:0xe800
> 
[CHEONG, Shu Yang (Patrick)]  Something wrong here...there are too
many collisions. Have you checked to ensure there are no boxes on network
sharing the same ip address? Also you mentioned that you can "see" one
network if you disable the other?! This could mean that there is a conflict
between the ethernet cards...

> loLink encap:Local Loopback
>   inet addr:127.0.0.1  Mask:255.0.0.0
>   UP LOOPBACK RUNNING  MTU:3924  Metric:1
>   RX packets:2494 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:2494 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
> 
> $
> $ /sbin/route
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse
> Iface
> tiger.first.com *   255.255.255.255 UH0

Re: network configuration

[John Pearson]

On %M 0, Peter Iannarelli wrote
> Hello Matthew:
> 
> To change the IP address, network, etc of you NIC
> to into /etc/init.d/network.
> 
> You will see everything you need there.
> 
> Peter
> 

It may also be necessary to edit /etc/networks, and perhaps /etc/hosts.


John P.
-- 
[EMAIL PROTECTED]
[EMAIL PROTECTED]
"Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark

Re: network configuration

[Peter Iannarelli]

Hello Matthew:

To change the IP address, network, etc of you NIC
to into /etc/init.d/network.

You will see everything you need there.

Peter


Matthew Wade Roberts wrote:

> When I first installed Debian, I entered incorrect information
> for the IP addresses of the network.  I need to correct
> the information now.  Is there a utility to do this similar
> to the setup program?  I've tried modifying the configuration files
> by hand, but it does not seem to work right so that I have probably
> missed a file or two.
>
> Thanks for your help,
>
> Matt
>
> --
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
begin:vcard 
n:Iannarelli;Peter
tel;fax:1+ 416 929 1056
tel;work:1+ 416 929 1885
x-mozilla-html:FALSE
url:http://www.GenXl.com
org:GenX Internet Labs.;Operations
adr:;;238a Gerrard St. East	;Toronto;Ontario;M5A 2E8;Canada
version:2.1
email;internet:[EMAIL PROTECTED]
title:Engineer
x-mozilla-cpt:;3232
fn:Peter Iannarelli
end:vcard

Re: Network configuration

[Kenneth Scharf]

True.

Not compiling network support in might cause the same problems as not
compiling in the device for the root file system, IE: not being able
to boot.  What I meant was that at some point, it is possible to make
the kernel too big and then SOMETHINGS need to be left out.  But this
is probably not a problem for the average desktop configuration.  But
for a server/firewall/router/raid/SMP monster it COULD happen. 
However you would then leave as modules ONLY stuff that was NOT
required at init time.

Then only thing I leave as a module on my system is the sound card,
and then only because it is PNP and MUST be loaded AFTER init runs
ISAPNP before the modules are loaded.




---Shaun Lipscombe <[EMAIL PROTECTED]> wrote:
>
> 
> Yes this is true for stuff that you dont use night and day, like
> iso9660 support for instance.  I would like to see a good reason for
> not compiling NIC support right in, like how much will that enlarge
> the kernel by?  100k ?
> 
> -- 
> 
> arrangements jihad Treasury Soviet Cocaine Delta Force munitions Nazi
> Legion of Doom ammunition Noriega kibo CIA Honduras Uzi
> 
> 

==
Amateur Radio, when all else fails!

http://www.qsl.net/wa2mze

Debian Gnu Linux, Live Free or .


_
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: Network configuration

[Jonathan Guthrie]

On 22 Mar 1999, Shaun Lipscombe wrote:

> Yes this is true for stuff that you dont use night and day, like
> iso9660 support for instance.  I would like to see a good reason for
> not compiling NIC support right in, like how much will that enlarge
> the kernel by?  100k ?

The total sizes of the *.o files that are in /usr/src/linux/drivers/net
that seem to be associated with my PCI ne2000 card is about 20k.  I
usually install all the drivers for stuff that I know I'm going to use and
make modules for stuff (like the floppy and CD-ROM drivers and FAT and
ISO9660 file systems) that I need occasionally, but not all the time, and
for stuff (like the IPv6 stuff) that I think I might want to play around
with at some point, but which I don't really have a good excuse for
installing now.

Also, some of the smallest kernels (and complete installations) I've ever
installed were for routers and such.  User machines, which tend to have
sound cards and joysticks, and whatnot, tend to have larger kernels, in my
experience.
-- 
Jonathan Guthrie ([EMAIL PROTECTED])
Brokersys  +281-895-8101   http://www.brokersys.com/
12703 Veterans Memorial #106, Houston, TX  77014, USA

Re: Network configuration

[Kenneth Scharf]

>Read the kernel HOWTO and compile support directly >into the kernel for
>ne2kpci.  You probably don't want the driver to be >modular, unless you
>rarely need to use your nic, and you have limited RAM >resources.

There IS a good reason for NOT compiling stuff into the kernel that is
ALWAYS used, and that is to keep the size of the thing down.  At some
point you end up with a kernel that is TOO BIG to boot, even though
almost EVERYTHING compiled in is really in use most of the time.  (Not
MY system, but an overstuffed server that is also a router and a
firewall could end up that way.)  The 'Universal kernels' used for
boot/install disks HAVE to be modular so as to be able to support ANY
scsi card or Network card present at boot time.

Now having said all that, most people should probably build everything
they use into the kernel for their desktop systems EXCEPT for the
sound card which 90% of the time needs ISAPNP to work and therefore
MUST be a module as it has to load AFTER init has configured the card
via ISAPNP.  (same would apply to pnp modem cards, network cards, etc
that can't have pnp disabled).  





==
Amateur Radio, when all else fails!

http://www.qsl.net/wa2mze

Debian Gnu Linux, Live Free or .


_
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com

[maxwell@more.net: Re: Network Configuration]

[ivan]

>Have you added lines to your /etc/resolv.conf?
>
>   ex.
>
>   nameserver  xxx.xxx.xxx.xxx
>
>where xxx.xxx.xxx.xxx is the IP of your DNS server.
>

   Yes, all the configuration files are right. I think that
the problem is with the DNS or some configuration in it, but
I don't know what kind of problem can be. Any sugestions ? 
Thanks.


>By the way, we have a machine in our subnet that recently
>was installed linux in. We have had some problems with the
>network configuration in order that the linux box doesn't
>recognize its DNS. It's possible to execute telnet from it only
>to IP addresses, and a ping to the DNS's IP doesn't work. 
>   Can this be a trouble with the linux configuration ? We are
>sure that all the configuration needed to get it working is made. 
>Or can it be a problem with the DNS ? Any sugestions will be 
>appreciated. 
>   Thanks in advance. 

Re: Network Configuration

[Erik Maxwell]

Have you added lines to your /etc/resolv.conf?

ex.

nameserver  xxx.xxx.xxx.xxx

where xxx.xxx.xxx.xxx is the IP of your DNS server.

Erik


>By the way, we have a machine in our subnet that recently
>was installed linux in. We have had some problems with the
>network configuration in order that the linux box doesn't
>recognize its DNS. It's possible to execute telnet from it only
>to IP addresses, and a ping to the DNS's IP doesn't work. 
>   Can this be a trouble with the linux configuration ? We are
>sure that all the configuration needed to get it working is made. 
>Or can it be a problem with the DNS ? Any sugestions will be 
>appreciated. 
>   Thanks in advance. 
>
>
>-- 
>Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] <
/dev/null
>
>
>

Re: Network Configuration

[ivan]

Hi, folks !!! 

By the way, we have a machine in our subnet that recently
was installed linux in. We have had some problems with the
network configuration in order that the linux box doesn't
recognize its DNS. It's possible to execute telnet from it only
to IP addresses, and a ping to the DNS's IP doesn't work. 
   Can this be a trouble with the linux configuration ? We are
sure that all the configuration needed to get it working is made. 
Or can it be a problem with the DNS ? Any sugestions will be 
appreciated. 
   Thanks in advance. 

Re: Network Configuration

[Joe Emenaker]

>How can I re-configure my network after installing linux?

Well, assuming you're talking about changing the IP address... you need to
change a couple of files:

/etc/init.d/network  - Shell script that sets up your ethernet interface.
/etc/hosts - file that holds the IP's of "well-known" hosts... itself being
one of those. :)
/etc/networks - You probably don't NEED to change this... but it can't hurt.

You'll need to reboot after you change all of this.

- Joe

Re: Network Configuration

[wtopa]

Subject: Network Configuration
Date: Tue, Dec 01, 1998 at 07:14:55AM -0800

In reply to:Brant Wells

Quoting Brant Wells([EMAIL PROTECTED]):
> 
> Howdy Y'all
> 
> How can I re-configure my network after installing linux?
> 

1. find / -iname Networking-Overview-HOWTO.gz.
2. In the same directory see NET-3-HOWTO.gz
3. Read them.
4. If/when you run into problems, _then_ send another mail.  A
   little effort on your part goes a long way.

> 
> Thanx for the help :)
> 
> Brant Wells; a linux newbie
> 
> 
> __
> Get Your Private, Free Email at http://www.hotmail.com
> 
> 
> -- 
> Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
> 
> 

-- 
Real Users find the one combination of bizarre input values that shuts
down the system for days.
___
Wayne T. Topa <[EMAIL PROTECTED]>

RE: Network Configuration

[Leandro Dutra]

> How can I re-configure my network after installing linux?

You use the ifconfig command.  Use the

man ifconfig

to learn about it.

This only configures the running system.  In order
to keep the changes even if you reboot, you need to change
the /etc/init.d/network file.



Leandro Guimaraens Faria Corcete Dutra
Amdocs Brasil Ltda

Re: Network Configuration

[csmall]

Robert D. Hilliard is rumoured to of said:
>  During the base installation, as part of configuring the network,
> the configure script asks for the netmask and the IP address for the
> network and/or the default gateway.  Where is this information stored?

You will find this information at the top of the /etc/init.d/network file;
ie

#!  /bin/sh
ifconfig lo 127.0.0.1
route add -net 127.0.0.0
IPADDR=192.168.2.17
NETMASK=255.255.255.248
NETWORK=192.168.2.16
BROADCAST=192.168.2.23
GATEWAY=none
ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK} netmask ${NETMASK}
route add -host ${IPADDR}

-- 
  / /\  | |  Craig Small VK2XLZ <[EMAIL PROTECTED]>
 |==||==|=|  Finger [EMAIL PROTECTED] for PGP key. 
  \ \/  | |  fingerprint = AD 8D D8 63 6E BF C3 C7  47 41 B1 A2 1F 46 EC 90


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Network Configuration

[Philippe Troin]

On Sun, 06 Jul 1997 19:48:11 EDT "Robert D. Hilliard" 
([EMAIL PROTECTED]) wrote:

>  During the base installation, as part of configuring the network,
> the configure script asks for the netmask and the IP address for the
> network and/or the default gateway.  Where is this information stored?

In /etc/init.d/network.

Phil.



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Network Configuration

[Shaya Potter]

It's stored in /etc/init.d/network

HTH,

Shaya

On Sun, 6 Jul 1997, Robert D. Hilliard wrote:

>  During the base installation, as part of configuring the network,
> the configure script asks for the netmask and the IP address for the
> network and/or the default gateway.  Where is this information stored?
> 
> Bob
> 
> 
> --
> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> [EMAIL PROTECTED] . 
> Trouble?  e-mail to [EMAIL PROTECTED] .
> 


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Network Configuration

[Joost Kooij]

On Sun, 6 Jul 1997, Robert D. Hilliard wrote:

>  During the base installation, as part of configuring the network,
> the configure script asks for the netmask and the IP address for the
> network and/or the default gateway.  Where is this information stored?

In the "Network Administrator's Guide" (part of the Linux Documentation
Project, can be browsed on sunsite.unc.edu or bought as a book frommm
O'Reilly and Associates.) Or in any decent book on TCP/IP.

Seriously: 
If you have an existing network, go ask the administrator.
If you don't, fill in 192.168.0.1 as IP address and default gateway,
255.255.255.0 as netmask. That'll do for the installation. Then you should
read about TCP/IP. It isn't really that hard, but too long to explain
here anyway.

Good luck and have fun,


Joost


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Re: Network Configuration

[Jens B. Jorgensen]

Jordi Inglada wrote:
> 
> >>Hello,
> >>
> >> last week, I had a problem with my ethernet card not being detected by
> >>the modconf program so I asked this list. I got lots of answers and
> >>finally my card is detected.
> >>
> >> The problem now is that I can't make it work. I mean, I can't do ftp,
> >>telnet, etc... When I try some of these, I wait and wait,... If I use
> >>nfs as the access method to the distribution, I got the message "server
> >> seems to be down or inexistent".
> >>
> >> I have configured the network, I have installed the drivers (my card is
> >>a DIGITAL depca), the card is found when rebooting at the correct
> >>address and interruption...
> >>
> >> Could somebody give me a hint about what's happenning? Maybe there's
> >>something I forgot to do. I'm a beginner in LINUX, so I would apreciate
> >>being told what to do step by step.
> >>
> > Date: Tue, 25 Mar 1997 13:30:08 +
> > From: "Oliver Elphick" <[EMAIL PROTECTED]>
> >
> > First, try the command ifconfig
> >
> > You should see something like:# ifconfig
> > loLink encap:Local Loopback
> >   inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
> >   UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
> >   RX packets:31668 errors:0 dropped:0 overruns:0
> >   TX packets:31668 errors:0 dropped:0 overruns:0
> >
> > eth0  Link encap:10Mbps Ethernet  HWaddr 00:4F:49:00:E0:5D
> >   inet addr:193.195.30.1  Bcast:193.195.30.255  Mask:255.255.255.0
> >   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >   RX packets:164771 errors:0 dropped:0 overruns:0
> >   TX packets:184328 errors:13 dropped:0 overruns:0
> >   Interrupt:11 Base address:0xef80
> >
> > #
> 
> OK, if I run ifconfig I got the same thing, but in lo, the inet address
> is the same that in eth0. Is that correct?
> 
> > If that works, try pinging other machines on your network, using their
> > IP numbers; next try their names.
> 
> I can ping my machine an doing telnet and ftp to it (with telnet and ftp
> I got _connection refused_ but I think it's OK because I've got no
> server running). But it doesn't work with the other machines in my
> network. So I can't make a query to my dns server.
> 
> I have also been told to setup routing. If I type #route add default
> eth0" nothing changes. If I add it to /etc/init.d , nothing changed
> either. My init.d file looks like:
> 
> ifconfig lo 192.168.13.1 (my gateway)
> route add -net 192.168.13.0
> IPADDR=192.168.13.114
> NETMASK=255.255.255.0
> NETWORK=192.168.13.0
> BROADCAST=192.168.13.255
> GATEWAY=192.168.13.1
> 
> ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
> route add -net ${NETWORK}
> route add default gw ${GATEWAY} metric 1
> 
> I have add to it the line route add default eth0, but it doesn't work
> either.
> 
> Any other suggestions?

Yes, actually. Where shall we start?! Your /etc/init.d/network looks
pretty screwed up. The lo ("loopback") interface should *always*
have the IP address 127.0.0.1 (I won't go into why this is so).
At any rate try changing the file to this:

ifconfig lo 127.0.0.1
route add -net 127.0.0.0
IPADDR=192.168.13.114
NETMASK=255.255.255.0
NETWORK=192.168.13.0
BROADCAST=192.168.13.255
GATEWAY=192.168.13.1
ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK}
route add default gw ${GATEWAY} metric 1

I think this will work for you. If not, post the messages which 
print out at boot.

-- 
Jens B. Jorgensen
[EMAIL PROTECTED]

Re: Network Configuration

[Jordi Inglada]

>>Hello,
>>
>> last week, I had a problem with my ethernet card not being detected by
>>the modconf program so I asked this list. I got lots of answers and
>>finally my card is detected.
>>
>> The problem now is that I can't make it work. I mean, I can't do ftp,
>>telnet, etc... When I try some of these, I wait and wait,... If I use
>>nfs as the access method to the distribution, I got the message "server
>> seems to be down or inexistent".
>>
>> I have configured the network, I have installed the drivers (my card is
>>a DIGITAL depca), the card is found when rebooting at the correct
>>address and interruption...
>>
>> Could somebody give me a hint about what's happenning? Maybe there's
>>something I forgot to do. I'm a beginner in LINUX, so I would apreciate
>>being told what to do step by step.
>>
> Date: Tue, 25 Mar 1997 13:30:08 +
> From: "Oliver Elphick" <[EMAIL PROTECTED]>
> 
> First, try the command ifconfig
> 
> You should see something like:# ifconfig
> loLink encap:Local Loopback
>   inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
>   UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
>   RX packets:31668 errors:0 dropped:0 overruns:0
>   TX packets:31668 errors:0 dropped:0 overruns:0
> 
> eth0  Link encap:10Mbps Ethernet  HWaddr 00:4F:49:00:E0:5D
>   inet addr:193.195.30.1  Bcast:193.195.30.255  Mask:255.255.255.0
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:164771 errors:0 dropped:0 overruns:0
>   TX packets:184328 errors:13 dropped:0 overruns:0
>   Interrupt:11 Base address:0xef80
> 
> #


OK, if I run ifconfig I got the same thing, but in lo, the inet address
is the same that in eth0. Is that correct?



> If that works, try pinging other machines on your network, using their
> IP numbers; next try their names.  

I can ping my machine an doing telnet and ftp to it (with telnet and ftp
I got _connection refused_ but I think it's OK because I've got no
server running). But it doesn't work with the other machines in my
network. So I can't make a query to my dns server.

I have also been told to setup routing. If I type #route add default
eth0" nothing changes. If I add it to /etc/init.d , nothing changed
either. My init.d file looks like:

ifconfig lo 192.168.13.1 (my gateway)
route add -net 192.168.13.0
IPADDR=192.168.13.114
NETMASK=255.255.255.0
NETWORK=192.168.13.0
BROADCAST=192.168.13.255
GATEWAY=192.168.13.1

ifconfig eth0 ${IPADDR} netmask ${NETMASK} broadcast ${BROADCAST}
route add -net ${NETWORK}
route add default gw ${GATEWAY} metric 1

I have add to it the line route add default eth0, but it doesn't work
either.

Any other suggestions?

Thank you.


Jordi INGLADA

Re: Network Configuration

[Oliver Elphick]

In message <[EMAIL PROTECTED]>, writes: 
  >Hello,
  >
  > last week, I had a problem with my ethernet card not being detected by
  >the modconf program so I asked this list. I got lots of answers and
  >finally my card is detected. 
  >
  > The problem now is that I can't make it work. I mean, I can't do ftp,
  >telnet, etc... When I try some of these, I wait and wait,... If I use
  >nfs as the access method to the distribution, I got the message "server
  > seems to be down or inexistent".
  >
  > I have configured the network, I have installed the drivers (my card is
  >a DIGITAL depca), the card is found when rebooting at the correct
  >address and interruption...
  >
  > Could somebody give me a hint about what's happenning? Maybe there's
  >something I forgot to do. I'm a beginner in LINUX, so I would apreciate
  >being told what to do step by step.
  >
Date: Tue, 25 Mar 1997 13:30:08 +
From: "Oliver Elphick" <[EMAIL PROTECTED]>

First, try the command ifconfig

You should see something like:# ifconfig
loLink encap:Local Loopback  
  inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
  UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
  RX packets:31668 errors:0 dropped:0 overruns:0
  TX packets:31668 errors:0 dropped:0 overruns:0

eth0  Link encap:10Mbps Ethernet  HWaddr 00:4F:49:00:E0:5D
  inet addr:193.195.30.1  Bcast:193.195.30.255  Mask:255.255.255.0
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:164771 errors:0 dropped:0 overruns:0
  TX packets:184328 errors:13 dropped:0 overruns:0
  Interrupt:11 Base address:0xef80 

# 

If you don't see lo and eth0, have a look at the boot scripts in /etc/init.d
(which are linked to /etc/rc[2345].d)

If ifconfig shows these, try doing commands to localhost (which uses
the loopback interface - that is, the machine talks to itself as if it
were another machine); for example, ftp localhost, ping localhost.

If that works, try pinging other machines on your network, using their
IP numbers; next try their names.  > Hello,
> 
>   last week, I had a problem with my ethernet card not being detected by
> the modconf program so I asked this list. I got lots of answers and
> finally my card is detected. 
> 
>   The problem now is that I can't make it work. I mean, I can't do ftp,
> telnet, etc... When I try some of these, I wait and wait,... If I use
> nfs as the access method to the distribution, I got the message "server
>  seems to be down or inexistent".
> 
>   I have configured the network, I have installed the drivers (my card is
> a DIGITAL depca), the card is found when rebooting at the correct
> address and interruption...
> 
>   Could somebody give me a hint about what's happenning? Maybe there's
> something I forgot to do. I'm a beginner in LINUX, so I would apreciate
> being told what to do step by step.
> 
>   Thanks.
> 
> 
>   Jordi INGLADA
> 
> 


Next look at how names are resolved - that is, translated to IP addresses.
Does your system use DNS or /etc/hosts; are these set up right?  If you
send a query to a nameserver, the program will wait at least 2 minutes before
giving up.

And so on...



Oliver Elphick  [EMAIL PROTECTED]
Isle of Wight  http://homepages.enterprise.net/olly

Re: Network Configuration

[David Wright]

On Tue, 25 Mar 1997, Jordi Inglada wrote:

>   The problem now is that I can't make it work. I mean, I can't do ftp,
> telnet, etc... When I try some of these, I wait and wait,... If I use
> nfs as the access method to the distribution, I got the message "server
>  seems to be down or inexistent".
> 
>   I have configured the network, I have installed the drivers (my card is
> a DIGITAL depca), the card is found when rebooting at the correct
> address and interruption...

Ouch! Depca card, eh? A couple of things to check:

It's not enough for the card to be detected. It's also rather important 
that any probing for other hardware doesn't interfere with the depca 
card. So you probably won't get it to work with an installation kernel 
which probes for everything everywhere.

The depca driver may also not work if you compile it as a module, so 
when you compile your kernel, select it as built-in.

I hope that helps. Me, I'm replacing my depca cards with 3c509 ones. 
Depcas worked with pathworks and with netbeui (just about), but they 
freeze up with PC-NFS after a couple of minutes so I'm calling it a day
(as is the Open University).
--
David Wright, Open University, Earth Science Department, Milton Keynes MK7 6AA
U.K.  email: [EMAIL PROTECTED]  tel: +44 1908 653 739  fax: +44 1908 655 151