Skip to main content
17 events
when toggle format what by license comment
Jan 30, 2016 at 1:26 vote accept TuturuJones
Jan 30, 2016 at 1:26 comment added TuturuJones ip a del 132.248.25.125/24 dev eth0 followed by ifup eth0 did it! Thank you very much!
Jan 30, 2016 at 1:24 comment added Dariusz Bączkowski Eh my error try: ip a del 132.248.25.125/24 dev eth0.
Jan 30, 2016 at 1:19 comment added TuturuJones for that it says: RTNETLINK answers: Cannot assign requested address. Is it not, ip r del 132.248.25.0/24 dev eth0?
Jan 30, 2016 at 1:14 comment added Dariusz Bączkowski Because there is reminder of old configuration. Try this: ip a del 132.248.25.0/24 dev eth0 and then try ifup eth0.
Jan 30, 2016 at 1:11 comment added TuturuJones OK, eth1's gateway is commented out and the internal network seems to be working fine. But when I tried to ifdown eth0 it says it's not configured and when trying ifup I get the following message: RTNETLINK answers: File exists; Failed to bring up eth0
Jan 30, 2016 at 1:04 comment added Dariusz Bączkowski init.d/networking restart will not reset interfaces properly. Use ifdown/ifup commends. Put interface down, make change, get it up.
Jan 30, 2016 at 1:00 comment added TuturuJones It's actually telling me that eth0 is not configured. But it did work for eth1. Now, I have a small doubt. After commenting out the gateway on eth1, I have to do init.d/networking restart, right?
Jan 30, 2016 at 0:51 comment added Dariusz Bączkowski eth1 is not setup right now. Try ifdown eth1; ifup eth1 and the same for eth0 or reboot. It should setup IP on eth1,eth0 and add gateway.
Jan 30, 2016 at 0:44 comment added TuturuJones I'll add it in a second, since the results are too long for comments.
Jan 30, 2016 at 0:34 comment added Dariusz Bączkowski Gateway is not needed to access local network. After commenting out gateway show ip a and ip r command result.
Jan 30, 2016 at 0:31 history edited Dariusz Bączkowski CC BY-SA 3.0
typo
Jan 30, 2016 at 0:31 comment added TuturuJones It does, from 192.169.1.1 to 192.169.1.250. I did what you mentioned and I would only get a "Connect: Network is Unreachable" after doing /etc/networking restart.
Jan 30, 2016 at 0:26 review First posts
Jan 30, 2016 at 0:48
Jan 30, 2016 at 0:26 comment added Dariusz Bączkowski Yes, if internal network has also other IP ranges besides 192.169.1.*. Does it? What ranges?
Jan 30, 2016 at 0:23 comment added TuturuJones By doing that, I won't lose access to my internal network?
Jan 30, 2016 at 0:21 history answered Dariusz Bączkowski CC BY-SA 3.0