Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #174505 > unrolled thread

wheezy, cannot change the address of eth1

Back to article view | Back to linux.debian.user

Contents

  wheezy, cannot change the address of eth1 Gene Heskett <gheskett@shentel.net> - 2016-11-11 19:20 +0100
    Re: wheezy, cannot change the address of eth1 Greg Wooledge <wooledg@eeg.ccf.org> - 2016-11-11 19:40 +0100
      Re: wheezy, cannot change the address of eth1 Gene Heskett <gheskett@shentel.net> - 2016-11-12 02:00 +0100
        Re: wheezy, cannot change the address of eth1 Greg Wooledge <wooledg@eeg.ccf.org> - 2016-11-14 14:40 +0100
          Re: wheezy, cannot change the address of eth1 Gene Heskett <gheskett@shentel.net> - 2016-11-14 15:50 +0100
    Re: wheezy, cannot change the address of eth1 David Wright <deblis@lionunicorn.co.uk> - 2016-11-11 20:30 +0100
      Re: wheezy, cannot change the address of eth1 Gene Heskett <gheskett@shentel.net> - 2016-11-12 04:00 +0100
    Re: wheezy, cannot change the address of eth1 Darac Marjal <mailinglist@darac.org.uk> - 2016-11-11 22:20 +0100
      Re: wheezy, cannot change the address of eth1 Andy Smith <andy@strugglers.net> - 2016-11-12 05:50 +0100
        [SOLVED]Re: wheezy, cannot change the address of eth1 Gene Heskett <gheskett@shentel.net> - 2016-11-12 11:00 +0100

#174505 — wheezy, cannot change the address of eth1

Greetings folks;

I just bought an ethernet switch, but it is a smart switch, so I needed 
to bring up my eth1 interface at an address in the 192.168.0.xx range so 
I can talk to it.  But despite the fact that it is so specified 
in /etc/network/interfaces, no amount of stopping and restarting the 
networking makes it take effect, its stuck at the old 192.168.1.3 
address.

The output on screen for an /etc/init.d/networking restart for eth1 is:
Configuring interface eth1=eth1 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
ip addr add 192.168.0.25/255.255.255.0 broadcast 192.168.0.255 	 dev eth1 
label eth1
ip link set dev eth1   up
 ip route add default via 192.168.0.1  dev eth1 
RTNETLINK answers: File exists
Failed to bring up eth1.

I cannot change it with ifconfig either. And the manpage for ip may as 
well be in swahili, lots of unexplained terminology.

So, short of rebooting so the changed interfaces might take effect, but 
will they, what is this "File exists" error?.

Does anyone have a clue what may be wrong?

And 5 years after I had a big fight with RTNETLINK, whatever the heck 
that is, it is still keeping the cause of the error secret.

So, net experts, what do I do?

Thanks.

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 <http://geneslinuxbox.net:6309/gene>

[toc] | [next] | [standalone]

#174508

On Fri, Nov 11, 2016 at 01:13:56PM -0500, Gene Heskett wrote:
> The output on screen for an /etc/init.d/networking restart for eth1 is:
> Configuring interface eth1=eth1 (inet)
> run-parts --verbose /etc/network/if-pre-up.d
> run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
> ip addr add 192.168.0.25/255.255.255.0 broadcast 192.168.0.255 	 dev eth1 
> label eth1
> ip link set dev eth1   up
>  ip route add default via 192.168.0.1  dev eth1 
> RTNETLINK answers: File exists
> Failed to bring up eth1.

Start by showing the contents of /etc/network/interfaces.

Then find out whether a DHCP client daemon is already running.  If you
installed with DHCP (the default) and then edited /e/n/i but didn't stop
dhclient beforehand, then ifdown won't know to kill dhclient and you'll
have to kill it by hand (or reboot).

ps auxw | egrep 'dhclient|dhcpcd'
kill if necessary
ifdown eth1
edit /etc/network/interfaces if necessary
ifup eth1

If this doesn't work, then show the output of "ip addr show eth1"
and the network-relevant parts of dmesg (e.g. "dmesg | grep eth" is
often a good start).

[toc] | [prev] | [next] | [standalone]

#174560

On Friday 11 November 2016 13:38:08 Greg Wooledge wrote:

> On Fri, Nov 11, 2016 at 01:13:56PM -0500, Gene Heskett wrote:
> > The output on screen for an /etc/init.d/networking restart for eth1
> > is: Configuring interface eth1=eth1 (inet)
> > run-parts --verbose /etc/network/if-pre-up.d
> > run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> > run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
> > ip addr add 192.168.0.25/255.255.255.0 broadcast 192.168.0.255 	 dev
> > eth1 label eth1
> > ip link set dev eth1   up
> >  ip route add default via 192.168.0.1  dev eth1
> > RTNETLINK answers: File exists
> > Failed to bring up eth1.
>
> Start by showing the contents of /etc/network/interfaces.
>
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

auto lo

# The loopback network interface
iface lo inet loopback
address 127.0.0.1
netmask 255.255.255.0

auto eth0

# regular network for coyote.den
iface eth0 inet static
address 192.168.71.3
netmask 255.255.255.0
gateway 192.168.71.1

auto eth1

# to access reset to 192.168.0.1 routers/switches on the 2nd cat5 port
iface eth1 inet static
address 192.168.0.25
netmask 255.255.255.0
gateway 192.168.0.1



> Then find out whether a DHCP client daemon is already running.  If you
> installed with DHCP (the default) and then edited /e/n/i but didn't
> stop dhclient beforehand, then ifdown won't know to kill dhclient and
> you'll have to kill it by hand (or reboot).

The only dhcp running on this whole network is in a dd-wrt router, and 
out of this things class D.

> ps auxw | egrep 'dhclient|dhcpcd'

The only return is my egrep looking for it.

> kill if necessary
> ifdown eth1
> edit /etc/network/interfaces if necessary

see above.

> ifup eth1
>
> If this doesn't work, then show the output of "ip addr show eth1"
> and the network-relevant parts of dmesg (e.g. "dmesg | grep eth" is
> often a good start).

root@coyote:/etc# ifup eth1
RTNETLINK answers: File exists
Failed to bring up eth1.
root@coyote:/etc# ip addr show eth1
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN group 
default qlen 1000
    link/ether 00:1f:c6:63:07:97 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.3/24 brd 192.168.1.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet 192.168.0.253/24 brd 192.168.0.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet 192.168.0.25/24 brd 192.168.0.255 scope global secondary eth1
       valid_lft forever preferred_lft forever

From dmesg|grep eth1
root@coyote:/etc# dmesg| grep eth1
[    1.940510] forcedeth 0000:00:09.0: ifname eth1, PHY OUI 0x5043 @ 1, 
addr 00:1f:c6:63:07:97
[   29.382766] forcedeth 0000:00:09.0 eth1: MSI enabled
[   29.382987] forcedeth 0000:00:09.0 eth1: no link during initialization
[   29.383422] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[1640002.998274] forcedeth 0000:00:09.0 eth1: link up
[1640002.999087] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[1640455.806412] forcedeth 0000:00:09.0 eth1: MSI enabled
[1640749.873848] forcedeth 0000:00:09.0 eth1: MSI enabled
[1641602.825513] forcedeth 0000:00:09.0 eth1: MSI enabled

that looks like ipv6 is working, but to where? The path ends at the 
uplink input to this new router. And since anything ipv6 is probably at 
least 100 miles away, I have zero experience.  ipv6 will probably not 
arrive at the customer interface of my ISP before I miss roll call for 
good some morning.

Thanks for any additional clues, or data requests.

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 <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#174695

> > Start by showing the contents of /etc/network/interfaces.

On Fri, Nov 11, 2016 at 07:59:01PM -0500, Gene Heskett wrote:
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> auto lo
> 
> # The loopback network interface
> iface lo inet loopback
> address 127.0.0.1
> netmask 255.255.255.0
> 
> auto eth0
> 
> # regular network for coyote.den
> iface eth0 inet static
> address 192.168.71.3
> netmask 255.255.255.0
> gateway 192.168.71.1
> 
> auto eth1
> 
> # to access reset to 192.168.0.1 routers/switches on the 2nd cat5 port
> iface eth1 inet static
> address 192.168.0.25
> netmask 255.255.255.0
> gateway 192.168.0.1

Others have already pointed this out, but you have two conflicting
"gateway" lines, on two completely separate networks.  You need to
pick one.

[toc] | [prev] | [next] | [standalone]

#174697

On Monday 14 November 2016 08:38:24 Greg Wooledge wrote:

> Others have already pointed this out, but you have two conflicting
> "gateway" lines, on two completely separate networks.  You need to
> pick one.

As it turned out, bringing up an eth0:1 was the answer. It also appears 
that its default configuration seems to do exactly what I wanted it to 
do, which is to act as a hub, expanding the number of ports available by 
enabling another 8 ports in the garage on the end of that cable, and 
reducing by about 150 feet, the length of cable and a simple hub it 
presently travels thru to get 10 feet physically.

I had, with extreme difficulty, fished a piece of cat5e thru a largely 
in-accessable piece of this structure called a house, in order to get 
the network to the G0704. And I've enough jumper cables so that it, the 
r-pi, o-pi and an old dell it appears I will have to use as an X 
renderer for the r-pi's output, can all be plugged in at the same time.

I was going to use the o-pi for that, but its hdmi port is defective. So 
job one this morning is to take my movie camera out and takes a short 
film of it booting the oem os, then booting armbian, and sending that 
back to the vendor to prove its display hdwe is defective.  Its color 
alright, a mixture of pale lime green in the highlights, with a burple 
overlay over everything, extremely poor experience for these old eyes.  
Insulting even. The display from the r-pi, using the same cable and 
dvd-i adapter, is pure and perfect.

If alibaba will replace the o-pi, I might still try to use it, next 
summer maybe when I need to get rid of the Dells heat.  But till then 
the old p4 Dell will have to do.

So I will pick a path and just do it instead of wasting time discussing 
it. :)

Cheers Greg, 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 <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#174514

On Fri 11 Nov 2016 at 13:13:56 (-0500), Gene Heskett wrote:
> Greetings folks;
> 
> I just bought an ethernet switch, but it is a smart switch, so I needed 
> to bring up my eth1 interface at an address in the 192.168.0.xx range so 
> I can talk to it.  But despite the fact that it is so specified 
> in /etc/network/interfaces, no amount of stopping and restarting the 
> networking makes it take effect, its stuck at the old 192.168.1.3 
> address.
> 
> The output on screen for an /etc/init.d/networking restart for eth1 is:
> Configuring interface eth1=eth1 (inet)
> run-parts --verbose /etc/network/if-pre-up.d
> run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
> ip addr add 192.168.0.25/255.255.255.0 broadcast 192.168.0.255 	 dev eth1 
> label eth1
> ip link set dev eth1   up
>  ip route add default via 192.168.0.1  dev eth1 
> RTNETLINK answers: File exists
> Failed to bring up eth1.
> 
> I cannot change it with ifconfig either. And the manpage for ip may as 
> well be in swahili, lots of unexplained terminology.
> 
> So, short of rebooting so the changed interfaces might take effect, but 
> will they, what is this "File exists" error?.
> 
> Does anyone have a clue what may be wrong?
> 
> And 5 years after I had a big fight with RTNETLINK, whatever the heck 
> that is, it is still keeping the cause of the error secret.
> 
> So, net experts, what do I do?

Googling your error message, I think the third link tells you what it means
http://www.linuxquestions.org/questions/linux-networking-3/rtnetlink-answers-file-exists-error-when-doing-ifup-on-alias-eth1-1-on-rhel5-710766/
and the second might be a fix.
http://unix.stackexchange.com/questions/100588/using-ip-addr-instead-of-ifconfig-reports-rtnetlink-answers-file-exists-on-de

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#174561

On Friday 11 November 2016 14:17:07 David Wright wrote:

> On Fri 11 Nov 2016 at 13:13:56 (-0500), Gene Heskett wrote:
> > Greetings folks;
> >
> > I just bought an ethernet switch, but it is a smart switch, so I
> > needed to bring up my eth1 interface at an address in the
> > 192.168.0.xx range so I can talk to it.  But despite the fact that
> > it is so specified in /etc/network/interfaces, no amount of stopping
> > and restarting the networking makes it take effect, its stuck at the
> > old 192.168.1.3 address.
> >
> > The output on screen for an /etc/init.d/networking restart for eth1
> > is: Configuring interface eth1=eth1 (inet)
> > run-parts --verbose /etc/network/if-pre-up.d
> > run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> > run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
> > ip addr add 192.168.0.25/255.255.255.0 broadcast 192.168.0.255 	 dev
> > eth1 label eth1
> > ip link set dev eth1   up
> >  ip route add default via 192.168.0.1  dev eth1
> > RTNETLINK answers: File exists
> > Failed to bring up eth1.
> >
> > I cannot change it with ifconfig either. And the manpage for ip may
> > as well be in swahili, lots of unexplained terminology.
> >
> > So, short of rebooting so the changed interfaces might take effect,
> > but will they, what is this "File exists" error?.
> >
> > Does anyone have a clue what may be wrong?
> >
> > And 5 years after I had a big fight with RTNETLINK, whatever the
> > heck that is, it is still keeping the cause of the error secret.
> >
> > So, net experts, what do I do?
>
> Googling your error message, I think the third link tells you what it
> means
> http://www.linuxquestions.org/questions/linux-networking-3/rtnetlink-a
>nswers-file-exists-error-when-doing-ifup-on-alias-eth1-1-on-rhel5-71076
>6/ and the second might be a fix.
> http://unix.stackexchange.com/questions/100588/using-ip-addr-instead-o
>f-ifconfig-reports-rtnetlink-answers-file-exists-on-de
>
> Cheers,
> David.

Yes, and no. What it suggested was bringing up eth0:1, and that worked, 
and I even got past the password & logged in.  But the menu's are, shal 
we say strange. I expected it to have a facility to update its elderly 
firmware, but there's no such thing. I registered it, so I'll taze their 
LL Monday and see if I can find somebody that speaks linux.

Many thanks for the pointer, & URL, that part worked.



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 <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#174537

[Multipart message — attachments visible in raw view] — view raw

On 11/11/16 18:13, Gene Heskett wrote:
> Greetings folks;
>
> I just bought an ethernet switch, but it is a smart switch, so I needed 
> to bring up my eth1 interface at an address in the 192.168.0.xx range so 
> I can talk to it.  But despite the fact that it is so specified 
> in /etc/network/interfaces, no amount of stopping and restarting the 
> networking makes it take effect, its stuck at the old 192.168.1.3 
> address.
>
> The output on screen for an /etc/init.d/networking restart for eth1 is:
> Configuring interface eth1=eth1 (inet)
> run-parts --verbose /etc/network/if-pre-up.d
> run-parts: executing /etc/network/if-pre-up.d/wireless-tools
> run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
> ip addr add 192.168.0.25/255.255.255.0 broadcast 192.168.0.255 	 dev eth1 
> label eth1
> ip link set dev eth1   up
>  ip route add default via 192.168.0.1  dev eth1 
> RTNETLINK answers: File exists
> Failed to bring up eth1.
>
> I cannot change it with ifconfig either. And the manpage for ip may as 
> well be in swahili, lots of unexplained terminology.
>
> So, short of rebooting so the changed interfaces might take effect, but 
> will they, what is this "File exists" error?.

"File exists" is, I think, a generic translation of an error code. "ip"
is trying to create a default route and is told, by the kernel, "that
route already exists: EEXISTS". "ip" then passes "EEXISTS" to an error
code translation routing which spits out "File exists".

To cut a long story short, you can't add a default route if you already
have one (well, technically you can, but you'd need to provide more
information). You probably have a default route sending traffic over eth0.

>
> Does anyone have a clue what may be wrong?
>
> And 5 years after I had a big fight with RTNETLINK, whatever the heck 
> that is, it is still keeping the cause of the error secret.
>
> So, net experts, what do I do?
>
> Thanks.
>
> Cheers, Gene Heskett

[toc] | [prev] | [next] | [standalone]

#174564

Hello,

On Fri, Nov 11, 2016 at 09:13:26PM +0000, Darac Marjal wrote:
> To cut a long story short, you can't add a default route if you already
> have one (well, technically you can, but you'd need to provide more
> information). You probably have a default route sending traffic over eth0.

Yes, I concur. He needs to remove the "gateway" line from his eth1
stanza as he does not need another default route going out of that
interface.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [next] | [standalone]

#174577 — [SOLVED]Re: wheezy, cannot change the address of eth1

On Friday 11 November 2016 23:49:18 Andy Smith wrote:

> Hello,
>
> On Fri, Nov 11, 2016 at 09:13:26PM +0000, Darac Marjal wrote:
> > To cut a long story short, you can't add a default route if you
> > already have one (well, technically you can, but you'd need to
> > provide more information). You probably have a default route sending
> > traffic over eth0.
>
> Yes, I concur. He needs to remove the "gateway" line from his eth1
> stanza as he does not need another default route going out of that
> interface.
>
> Cheers,
> Andy

Done that, on eth0:1 now. and I can talk to it. But its slow, darned 
slow, clicking on a menu item takes 7 or 8 seconds to see the result. 

The first thing I want to do is put a newer firmware in it, 12 revisions 
newer.  I registered it with netgear, so I'll ding their LL Monday as 
while I have downloaded and unpacked the file, there is not any 
instructions about how that is done. I may have found that menu function 
but I don't want to brick it if its something else, so we'll let tech 
support tell me how.

It claims to be able to do dhcp, and my dd-wrt router has a server, but I 
also have a mac address list it restriction is not on yet so thats being 
rejected.  Attempts to put it manually on my local networks address 
block have failed, but some of their menu's may as well be in swahili 
since I have never dealt with a ""managed" switch before.  I expect the 
first thing to do after the firmware is updated, is add its MAC to 
dd-wrt's list so dhcpd works.

What I want it to be is a basic 8 port hub, plugged into a non managed 
switch via about a 60 foot cable plugged into the switch here in this 
room, and currently hooking up one machine in the garage.  The garage is 
growing more machines, probably 2 more r-pi's before I am fully hooked 
to a lathe I am cnc'ing.

So the instant problem is solved, and I thank the several people who did 
respond with helpfull links, you know who you are.

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 <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web