Re: wheezy, cannot change the address of eth1
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>
Reply to: