Error either local is duplicate or eth0 is a garbage

Hi all,

plauria

Posts: 11
Joined: Wed Jul 23, 2014 6:57 pm

On boot: «either «local» is duplicate, or «/24″ is garbage»

Hi all,

I’m using the 0.92 version of the RP software. I am trying to give my redpitaya a static IP for use on a switch. Here is my /etc/network/interfaces file:

Code: Select all

###########################
# lo: Loopback interface  #
###########################

auto lo
iface lo inet loopback


######################################
# eth0: Wired Ethernet - 1000Base-T  #
######################################
#
# Uncomment only one: dynamic or static configuration.
#

# Dynamic (DHCP) IP address
#iface eth0 inet dhcp
# Dynamic (DHCP) IP address
#iface eth0 inet dhcp
#    udhcpc_opts -t7 -T3

# Static IP address
# Don't forget to set the static DNS IP in sd:/etc/init.d/rcS too.
iface eth0 inet static
    address 192.168.1.222 
    netmask 255.255.255.0
    gateway 0.0.0.0

The network doesn’t work, and the relevant bootup message regarding eth0 is given in the subject line.

To get it to work, I have to log into the RP using serial console, then do

Code: Select all

ifconfig eth0 down
ifconfig eth0 192.168.1.222
ifconfig eth0 up

Then it works fine. Why do I have to do this every time I boot the RP? What’s going on? I must be missing something…


Nils Roos

Posts: 1441
Joined: Sat Jun 07, 2014 12:49 pm
Location: Königswinter

Re: On boot: «either «local» is duplicate, or «/24» is garb

Post

by Nils Roos » Tue Oct 07, 2014 12:18 am

I must be missing something…

You are ! Two things, possibly:
1. You also need to put your static configuration into the /etc/network/config file

Code: Select all

...
NETWORK=static

# Static network configuration parameters (active if NETWORK=static)
IP=...
NETMASK=...
GATEWAY=...

2. Since a few commits back, the access-point («ap») configuration has become the default. If you are using the latest version from github repo, there is now a separate file /etc/network/interfaces.ap where you also need to change the settings.

The latter point has not yet been documented, unfortunately.

edit: Hmmm, just tested without the first change, I didn’t get the same messages as you did …


plauria

Posts: 11
Joined: Wed Jul 23, 2014 6:57 pm

Re: On boot: «either «local» is duplicate, or «/24» is garb

Post

by plauria » Tue Oct 07, 2014 5:48 pm

Thanks for the reply, but neither of those files exist in /etc/network. When I create them, they are gone by next boot.

I’m using a stable release; on boot it reports this version: Red Pitaya GNU/Linux/Ecosystem version 0.92-378


plauria

Posts: 11
Joined: Wed Jul 23, 2014 6:57 pm

Re: On boot: «either «local» is duplicate, or «/24» is garb

Post

by plauria » Tue Oct 07, 2014 6:05 pm

OK, I think I’ve discovered the error. Running ifup -v eth0 results in:

Code: Select all

redpitaya> ifup -fv eth0
run-parts /etc/network/if-pre-up.d
ip addr add 192.168.1.222 /24 dev eth0 label eth0
ip: either "local" is duplicate, or "/24" is garbage
ip link set eth0 up
ip route add default via 0.0.0.0 dev eth0
ip: RTNETLINK answers: File exists

There’s a typo in the `ip` command!!! There should be no space between 222 and /24! Running the commands without the space between 222 and /24 and the RP works now. :shock:

I just checked my /etc/network/interfaces file and there is a stray space at the end of the IP address! This was getting collected by ifup, and hence causing the erroneous command. This should be noted in the wiki I think!


jadalnie klasyczne ekskluzywne meble wypoczynkowe do salonu ekskluzywne meble tapicerowane ekskluzywne meble do sypialni ekskluzywne meble włoskie

Who is online

Users browsing this forum: No registered users and 4 guests

View previous topic :: View next topic  
Author Message
pneula
n00b
n00b

Joined: 16 Jan 2009
Posts: 37

PostPosted: Fri Jan 16, 2009 11:12 pm    Post subject: [SOLVED] LAN interface staying stopped Reply with quote

Dear Gentooers,

My LAN network (eth0) stopped starting a week ago and I haven’t found the reason this far, so decided to ask you all. This is the error I keep getting when trying to start using /etc/init.d/net.eth0:

Code:
Error: either «local» is duplicate, or «netmask» is a garbage.

ifconfig output for the interface:

Code:
 eth0:

Link encap:Ethernet  HWaddr 00:50:fc:2f:07:b3 

UP BROADCAST MULTICAST  MTU:1500  Metric:1

RX packets:159 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:54378 (53.1 KiB)  TX bytes:0 (0.0 B)

Interrupt:16 Base address:0xd000

Google didn’t help and I’m getting annoyed because this might be something simple if one just knows what! iptables maybe? Please advice a keen Gentoo user to get his LAN up again!

Last edited by pneula on Thu Jan 22, 2009 9:14 pm; edited 1 time in total

Back to top

View user's profile Send private message

SeaTiger
l33t
l33t

Joined: 22 Nov 2007
Posts: 603
Location: Toronto, Ontario, Canada

PostPosted: Sat Jan 17, 2009 4:17 am    Post subject: Reply with quote

Please post /etc/conf.d/net.
Back to top

View user's profile Send private message

d2_racing
Bodhisattva
Bodhisattva

Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada

PostPosted: Sat Jan 17, 2009 4:27 am    Post subject: Reply with quote

Hi, can you post your lspci ?
Back to top

View user's profile Send private message

pneula
n00b
n00b

Joined: 16 Jan 2009
Posts: 37

PostPosted: Sun Jan 18, 2009 11:32 am    Post subject: Reply with quote

Hi and thank you for your replies!

My /etc/conf.d/net hasn’t changed at all but here it is. My WAN interface is ppp0.

Code:
config_eth0=( «192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0» )

config_ppp0=(«ppp»)

link_ppp0=( «/dev/ttyUSB0» )

pppd_ppp0=(

        «460800»

        «crtscts»

        «modem»

        «noauth»

        «usepeerdns»

        «defaultroute»

        «noipdefault»

        «debug»

        «noccp»

        «nobsdcomp»

        «novj»

        «user »»

        «password »»

        «connect ‘/usr/sbin/chat -f /etc/ppp/chat-E220-pin || /usr/sbin/chat -f

/etc/ppp/chat-E220-nopin'»

)

I have tried both NICs that I have free for LAN these days, as lspci shows:

Code:

# lspci | grep Eth

00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)

This strange interface problem just simply appeared and I have no idea why! Do you get any ideas based on these infos?

Back to top

View user's profile Send private message

SeaTiger
l33t
l33t

Joined: 22 Nov 2007
Posts: 603
Location: Toronto, Ontario, Canada

PostPosted: Mon Jan 19, 2009 2:04 am    Post subject: Reply with quote

Please post /etc/udev/rules.d/70-persistent-net.rules also.
Back to top

View user's profile Send private message

pneula
n00b
n00b

Joined: 16 Jan 2009
Posts: 37

PostPosted: Mon Jan 19, 2009 7:18 pm    Post subject: Reply with quote

All right, here you go, /etc/udev/rules.d/70-persistent-net.rules:

Code:

# PCI device 0x10ec:0x8139 (8139too)

SUBSYSTEM==»net», ACTION==»add», DRIVERS==»?*», ATTR{address}==»00:50:fc:2f:07:b

3″, ATTR{type}==»1″, KERNEL==»eth*», NAME=»eth1″

# PCI device 0x1106:0x3065 (via-rhine)

SUBSYSTEM==»net», ACTION==»add», DRIVERS==»?*», ATTR{address}==»00:19:db:aa:9f:a

0″, ATTR{type}==»1″, KERNEL==»eth*», NAME=»eth0″

I must say I don’t know this file, something wrong with it?

Back to top

View user's profile Send private message

SeaTiger
l33t
l33t

Joined: 22 Nov 2007
Posts: 603
Location: Toronto, Ontario, Canada

PostPosted: Tue Jan 20, 2009 2:08 am    Post subject: Reply with quote

Try delete that file and reboot the machine.
Back to top

View user's profile Send private message

pneula
n00b
n00b

Joined: 16 Jan 2009
Posts: 37

PostPosted: Tue Jan 20, 2009 7:10 am    Post subject: Reply with quote

Yeah, tried that, did not help. =(
Back to top

View user's profile Send private message

lxg
Veteran
Veteran

Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Wed Jan 21, 2009 12:00 am    Post subject: Reply with quote

What happens if you up the device manually?

Code:

ifconfig eth0 up

ifconfig eth0 192.168.0.1 broadcast 192.168.0.255 netmask 255.255.255.0


_________________
lxg.de – codebits and tech talk

Back to top

View user's profile Send private message

pneula
n00b
n00b

Joined: 16 Jan 2009
Posts: 37

PostPosted: Wed Jan 21, 2009 5:23 am    Post subject: Reply with quote

These commands don’t give any errors! Thanks lxg, that’s already great here!

Now, ifconfig shows same still:

Code:

eth0      Link encap:Ethernet  HWaddr 00:19:db:aa:9f:a0 

          inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0

          UP BROADCAST 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)

          Interrupt:23 Base address:0xe000

I’m sorry to be so novice, but can I get it running manually? It seems that initscript can get the interface up to this point, and then something hazardous happens.

Back to top

View user's profile Send private message

lxg
Veteran
Veteran

Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Wed Jan 21, 2009 8:57 am    Post subject: Reply with quote

You’re welcome, but I forgot to ask: Can you ping something with these settings (by IP and/or domain name)? Elsewise («network unreachable») it’s worthless. If you can ping and access the net otherwise, it’s great.

According to what I found in some Google results for your error message, there seems to be an error with your routing. It appears that you have more than one route set for the device.

Quote:
Duplicate Default Gateways

If the default gateway is already assigned from DHCP, the IP command arguments format can cause one of two errors during start-up, or when bringing up an interface from the down state using the ifup command: «RTNETLINK answers: File exists» or ‘Error: either «to» is a duplicate, or «X.X.X.X» is a garbage.’, where X.X.X.X is the gateway, or a different IP address. These errors can also occur if you have another route to another network using the default gateway. Both of these errors are safe to ignore.



http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Deployment_Guide/s1-networkscripts-static-routes.html

What is the output of your route command? Is it possible that, due to the fact that you have two ethernet devices, some settings got confused?

edit: Does it help to set a default gateway for your net.eth0 in the net configuration (see /etc/conf.d/net.example)?
_________________
lxg.de – codebits and tech talk

Back to top

View user's profile Send private message

pneula
n00b
n00b

Joined: 16 Jan 2009
Posts: 37

PostPosted: Wed Jan 21, 2009 9:09 pm    Post subject: Reply with quote

Thanks, that is an interesting reference!

Answer first: I have no problems with my WAN interface ppp0, LAN only.

However, setting a default route didn’t help. I played a little again and found that the netmask really is the problem somehow: when I removed the netmask declaration from the /etc/init.d/net, I did get the interface both up and running. However, I get nothing into the routing table and cannot ping into the LAN or receive an IP address from it using DHCP. I attach route command and hope you figure something out of it! (I changed the NIC just in case…now the LAN is in eth1)

Code:

# route

Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

10.64.64.64     *               255.255.255.255 UH    0      0        0 ppp0

loopback        localhost       255.0.0.0       UG    0      0        0 lo

default         10.64.64.64     0.0.0.0         UG    4004   0        0 ppp0

Additionally still, adding route to LAN by this command does not solve the problem:

Code:

# route add -net 192.168.0.0 netmask 255.255.255.0 dev eth1

Back to top

View user's profile Send private message

pneula
n00b
n00b

Joined: 16 Jan 2009
Posts: 37

PostPosted: Wed Jan 21, 2009 9:21 pm    Post subject: Reply with quote

Oh my, this is weird.

I tried once again to bring eth1 up manually (with netmask) and I did succeed! I can ping and DHCP dealing works fine. May changing the NIC have had an impact?

Initscript still does not work!

Back to top

View user's profile Send private message

lxg
Veteran
Veteran

Joined: 12 Nov 2005
Posts: 1019
Location: Aachen, Germany

PostPosted: Wed Jan 21, 2009 9:46 pm    Post subject: Reply with quote

Hm, I’m also a bit clueless …

I understand that your ppp0 works fine, but is it possible that it messes up the routing? What happens if you shut down ppp0 and delete all routes, then set up your ethX ones? Or comment out the ppp0 config, remove net.ppp0 from all runlevels and reboot? Just to be sure that nothing in the ppp0 config (including the chat stuff) is interfering.
_________________
lxg.de – codebits and tech talk

Back to top

View user's profile Send private message

pneula
n00b
n00b

Joined: 16 Jan 2009
Posts: 37

PostPosted: Thu Jan 22, 2009 9:14 pm    Post subject: Reply with quote

Yeah, I got it working!

I tried your idea of getting rid of ppp0 but that didn’t help. Inspired by my Gentoo install at work today I then changed the /etc/conf.d/net setting for eth1by hazard and there, the initscript begun working again. I can’t explain this but everything seems to be just like before. Can you explain? See my configuration of eth1 in /etc/conf.d/net below:

Code:

config_eth1=( «192.168.0.1 netmask 255.255.255.0 brd 192.168.0.255» )

Back to top

View user's profile Send private message

Display posts from previous:   

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Debian Bug report logs —
#729882
Error: either «local» is duplicate, or «eth0» is a garbage

version graph

Reported by: Wolfgang Hotwagner <lister@feedyourhead.at>

Date: Mon, 18 Nov 2013 16:15:02 UTC

Severity: normal

Found in version openswan/1:2.6.37-3

Fixed in version 1:2.6.38-1+rm

Done: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

Bug is archived. No further changes may be made.

Toggle useless messages


Report forwarded
to debian-bugs-dist@lists.debian.org, Rene Mayrhofer <rmayr@debian.org>:
Bug#729882; Package openswan.
(Mon, 18 Nov 2013 16:15:06 GMT) (full text, mbox, link).


Acknowledgement sent
to Wolfgang Hotwagner <lister@feedyourhead.at>:
New Bug report received and forwarded. Copy sent to Rene Mayrhofer <rmayr@debian.org>.
(Mon, 18 Nov 2013 16:15:06 GMT) (full text, mbox, link).


Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

Package: openswan
Version: 1:2.6.37-3
Severity: normal

Dear Maintainer,

I do have one network-interface with multiple alias addresses:

ip addr:

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 08:00:27:d2:69:ff brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.202/24 brd 172.17.0.255 scope global eth0
    inet 172.17.0.232/24 scope global secondary eth0
    inet6 fe80::a00:27ff:fed2:69ff/64 scope link
       valid_lft forever preferred_lft forever


If i startup ipsec, i'll recieve the following error:
root@Wheezy2:~# /etc/init.d/ipsec restart
ipsec_setup: Stopping Openswan IPsec...
ipsec_setup: Starting Openswan IPsec 2.6.37-g955aaafb-dirty...
ipsec_setup: ipsec0 -> NULL mtu=0(0) -> 0
ipsec_setup: Error: either "local" is duplicate, or "eth0" is a garbage.
ipsec_setup: Error: either "local" is duplicate, or "eth0" is a garbage.


This only happens, if i use the address 172.17.0.232
If i use the main-ip(172.17.0.202) of the interface, the problem doesn't appear.


This is a big problem for me, since i want to use openswan on a heartbeat-shared-ip-address.

Thank you very much
Wolfgang Hotwagner




-- System Information:
Debian Release: 7.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=de_AT@euro, LC_CTYPE=iso_8859_1 (charmap=ISO-8859-15) (ignored: LC_ALL set to de_AT@euro)
Shell: /bin/sh linked to /bin/dash

Versions of packages openswan depends on:
ii  bind9-host [host]      1:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii  bsdmainutils           9.0.3
ii  debconf [debconf-2.0]  1.5.49
ii  host                   1:9.8.4.dfsg.P1-6+nmu2+deb7u1
ii  iproute                20120521-3+b3
ii  ipsec-tools            1:0.8.0-14
ii  libc6                  2.13-38
ii  libcurl3               7.26.0-1+wheezy5
ii  libgmp10               2:5.0.5+dfsg-2
ii  libldap-2.4-2          2.4.31-1+nmu2
ii  libpam0g               1.1.3-7.1
ii  openssl                1.0.1e-2

openswan recommends no packages.

Versions of packages openswan suggests:
pn  curl                                             <none>
pn  openswan-doc                                     <none>
pn  openswan-modules-source | openswan-modules-dkms  <none>

-- Configuration Files:
/etc/ipsec.conf changed:
version	2.0	# conforms to second version of ipsec.conf specification
config setup
	# Do not set debug options to debug configuration issues!
	# plutodebug / klipsdebug = "all", "none" or a combation from below:
	# "raw crypt parsing emitting control klips pfkey natt x509 dpd private"
	# eg:
	# plutodebug="control parsing"
	# Again: only enable plutodebug or klipsdebug when asked by a developer
	#
	# enable to get logs per-peer
	# plutoopts="--perpeerlog"
	#
	# Enable core dumps (might require system changes, like ulimit -C)
	# This is required for abrtd to work properly
	# Note: incorrect SElinux policies might prevent pluto writing the core
	dumpdir=/var/run/pluto/
	#
	# NAT-TRAVERSAL support, see README.NAT-Traversal
	nat_traversal=yes
	# exclude networks used on server side by adding %v4:!a.b.c.0/24
	# It seems that T-Mobile in the US and Rogers/Fido in Canada are
	# using 25/8 as "private" address space on their 3G network.
	# This range has not been announced via BGP (at least upto 2010-12-21)
	virtual_private=%v4:10.0.0.0/8,%v4:192.168.0.0/16,%v4:172.16.0.0/12,%v4:25.0.0.0/8,%v6:fd00::/8,%v6:fe80::/10
	# OE is now off by default. Uncomment and change to on, to enable.
	oe=off
	# which IPsec stack to use. auto will try netkey, then klips then mast
	protostack=auto
	# Use this to log to a file, or disable logging on embedded systems (like openwrt)
	#plutostderrlog=/dev/null
	interfaces="ipsec0=eth0:0"
conn %default
        keyexchange=ike
        keyingtries=0
        authby=secret
        ike=aes256-sha1;modp2048
        ikelifetime=28800s
        auth=esp
        phase2alg=aes256-sha1;modp2048
        keylife=28800s
        pfs=yes
        compress=yes
        dpddelay=10
        dpdtimeout=120
        left=172.17.0.232


-- debconf information excluded



Reply sent
to Debian FTP Masters <ftpmaster@ftp-master.debian.org>:
You have taken responsibility.
(Tue, 01 Jul 2014 11:30:54 GMT) (full text, mbox, link).


Notification sent
to Wolfgang Hotwagner <lister@feedyourhead.at>:
Bug acknowledged by developer.
(Tue, 01 Jul 2014 11:30:54 GMT) (full text, mbox, link).


Message #10 received at 729882-done@bugs.debian.org (full text, mbox, reply):

Version: 1:2.6.38-1+rm

Dear submitter,

as the package openswan has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/736557

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)



Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Wed, 30 Jul 2014 07:32:27 GMT) (full text, mbox, link).


Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Thu Feb 9 13:26:18 2023;
Machine Name:
buxtehude

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.

  • Печать

Страницы: [1]   Вниз

Тема: Наследство дяди билли или куда копать???  (Прочитано 3227 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
Pride_Winner

Прошу прощения предыдущую тему не успел поправить. Вот суть проблемы, подскажите новичку. Работало вот так Сервер с win2008 получает интернет от провайдера ppp0e через сетевую карту 1, отдает ее в локальную сеть через карточку2, которая имеет ип адреса 192.168.0.2 и 192.168.3.100. В бугалтерии стоит сервер win2003, одна карточка смотрит в локалку на 192.168.0.2 имеет ип адрес 192.168.0.116. Вторая карточка win2003 смотрит в локалку с бугалтерами имеет параметры ип 192.168.2.2, шлюз непрописан. днс 192.168.2.2. Все «чудно» работает. это настраивалось до меня и моего старшего. Севодня я заменил сервер win2008 сервером с Ubuntu. все комьпьютеры нормально получают интернет и подмены незаметили. НО в бугалтерии компьютеры подключенные к2003 серверу интернет неполучают, на самом 2003 он есть. У Ubuntu интернет приходит по eth0, ppp0 подключение, а раздаеться eth1 192.168.0.2. дописал в /etc/sysctl.conf net.ipv4.ip_forward=1 выполнил sysctl -w net.ipv4.ip_forward=«1»

iptables -v -t nat -A POSTROUTING -o ppp0 -j MASQUERADE У всех есть инет кроме пользователей сервера вин2003 Вот скришоты из вин2008 настройки сети http://yadi.sk/d/NRAXaHNc7pHAD http://yadi.sk/d/IeM3plU87pHCB http://yadi.sk/d/zdTtsVXL7pHE9 Я так понимаю мне нужно в Ubuntu сделать статические маршруты как сдесь? http://yadi.sk/d/IeM3plU87pHCB


Оффлайн
fisher74

sudo ip r add 192.168.2.0/24 gw 192.168.0.116


Оффлайн
Pride_Winner

sudo ip r add 192.168.2.0/24 gw 192.168.0.116

Простите пожалуйста совсем тупой вопрос мне нужно создать сетевой интерфейс на eth1 с ип 192.168.2.0?

sudo ip r add 192.168.2.0/24 gw 192.168.0.116[/quote] если сейчас просто выполнить то

smt@smt-web:~$ sudo ip r add 192.168.2.0/24 gw 192.168.0.116
Error: either "to" is duplicate, or "gw" is a garbage.
[/quote]


Оффлайн
fisher74


Оффлайн
Pride_Winner

smt@smt-web:~$ ip a ; ip r
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:26:55:80:83:e6 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::226:55ff:fe80:83e6/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:26:55:80:83:e7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.2/24 brd 192.168.0.255 scope global eth1
    inet 192.168.3.100/24 brd 192.168.3.255 scope global eth1:1
    inet 192.168.2.2/24 brd 192.168.2.255 scope global eth1:2
    inet6 fe80::226:55ff:fe80:83e7/64 scope link
       valid_lft forever preferred_lft forever
4: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc pfifo_fast state UNKNOWN qlen 3
    link/ppp
    inet 95.79.29.19 peer 91.144.184.70/32 scope global ppp0
default dev ppp0  scope link
default via 192.168.0.116 dev eth1  metric 100
91.144.184.70 dev ppp0  proto kernel  scope link  src 95.79.29.19
169.254.0.0/16 dev eth1  scope link  metric 1000
192.168.0.0/24 dev eth1  proto kernel  scope link  src 192.168.0.2
192.168.2.0/24 dev eth1  proto kernel  scope link  src 192.168.2.2
192.168.3.0/24 dev eth1  proto kernel  scope link  src 192.168.3.100
smt@smt-web:~$


Оффлайн
fisher74

  inet 192.168.2.2/24 brd 192.168.2.255 scope global eth1:2

Это зачем? Уберите. Тогда и с маршрутом проблемы не будет


Оффлайн
Pride_Winner

smt@smt-web:~$ sudo ip r add 192.168.2.0/24 gw 192.168.0.116
Error: either "to" is duplicate, or "gw" is a garbage.

smt@smt-web:~$ ip a ; ip r
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:26:55:80:83:e6 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::226:55ff:fe80:83e6/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:26:55:80:83:e7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.2/24 brd 192.168.0.255 scope global eth1
    inet 192.168.3.100/24 brd 192.168.3.255 scope global eth1:1
    inet6 fe80::226:55ff:fe80:83e7/64 scope link
       valid_lft forever preferred_lft forever
4: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc pfifo_fast state UNKNOWN qlen 3
    link/ppp
    inet 95.79.29.19 peer 10.86.255.126/32 scope global ppp0
default dev ppp0  scope link
10.86.255.126 dev ppp0  proto kernel  scope link  src 95.79.29.19
169.254.0.0/16 dev eth1  scope link  metric 1000
192.168.0.0/24 dev eth1  proto kernel  scope link  src 192.168.0.2
192.168.3.0/24 dev eth1  proto kernel  scope link  src 192.168.3.100


Оффлайн
fisher74

а… давайте по старинке

sudo route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.0.116


Пользователь решил продолжить мысль 12 Августа 2013, 16:52:57:


потому что надо

sudo ip r add 192.168.2.0/24 via 192.168.0.116

:)
Стыднааа….


Оффлайн
Pride_Winner

выполнилось, только эффект смогу завтра узнать, бухгалтерия свалила. заранее спасибо
вот если с вашей поправкой то

smt@smt-web:~$ sudo ip r add 192.168.2.0/24 via 192.168.0.116
RTNETLINK answers: File exists

« Последнее редактирование: 12 Августа 2013, 16:55:27 от Pride_Winner »


Оффлайн
AnrDaemon

Pride_Winner, думайте, что пишете. Два раза один и тот же маршрут вы не добавите.

Хотите получить помощь? Потрудитесь представить запрошенную информацию в полном объёме.

Прежде чем [Отправить], нажми [Просмотр] и прочти собственное сообщение. Сам-то понял, что написал?…


  • Печать

Страницы: [1]   Вверх

Понравилась статья? Поделить с друзьями:
  • Error eexist file already exists mkdir
  • Error eeprom verify
  • Error eeprom disabled
  • Error eelftpserror control channel transfer error 114690
  • Error editing value regedit