diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20120522/007793.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20120522/007793.html | 187 |
1 files changed, 187 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20120522/007793.html b/zarb-ml/mageia-discuss/20120522/007793.html new file mode 100644 index 000000000..3b503db71 --- /dev/null +++ b/zarb-ml/mageia-discuss/20120522/007793.html @@ -0,0 +1,187 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-discuss] Temporarily changing IP address + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Temporarily%20changing%20IP%20address&In-Reply-To=%3Ce30a06cb2fbfa1d02fe8f11d31d27a23.squirrel%40mail.rmail.be%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="007397.html"> + <LINK REL="Next" HREF="007384.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] Temporarily changing IP address</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Temporarily%20changing%20IP%20address&In-Reply-To=%3Ce30a06cb2fbfa1d02fe8f11d31d27a23.squirrel%40mail.rmail.be%3E" + TITLE="[Mageia-discuss] Temporarily changing IP address">maarten.vanraes at gmail.com + </A><BR> + <I>Tue May 22 19:51:08 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="007397.html">[Mageia-discuss] Temporarily changing IP address +</A></li> + <LI>Next message: <A HREF="007384.html">[Mageia-discuss] Temporarily changing IP address +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7793">[ date ]</a> + <a href="thread.html#7793">[ thread ]</a> + <a href="subject.html#7793">[ subject ]</a> + <a href="author.html#7793">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>><i> -----BEGIN PGP SIGNED MESSAGE----- +</I>><i> Hash: SHA1 +</I>><i> +</I>><i> On 22/05/12 16:59, AL13N wrote: +</I>>>><i> On 22/05/12 15:08, AL13N wrote: +</I>>>>>>>><i> No :-( No difference, even though I restarted the +</I>>>>>>>><i> network service, +</I>>>>>><i> +</I>>>>>><i> Lets start from scratch. +</I>>>>>><i> +</I>>>>>><i> But first, can you tell me the ip address of the NAS and +</I>>>>>><i> your laptop's IP address for eth0. +</I>>>>>><i> +</I>>>>>><i> After making note of these, put the laptop back to it's +</I>>>>>><i> original config. (i.e. remove the manually created interface) +</I>>>>>><i> and set wlan0 not to come up on reboot. Then restart so you +</I>>>>>><i> only have an ip address on eth0. +</I>>>>>><i> +</I>>>>>><i> Then send me the info. +</I>>>>>><i> +</I>>>>>><i> Doug +</I>>>>><i> +</I>>>>><i> in fact, if we want it to be even simpler, you could add the +</I>>>>><i> ip address without a alias interface wit iproute2 +</I>>>>><i> +</I>>>>><i> []# ip addr show eth0 +</I>>>><i> +</I>>>><i> # ip addr show eth0 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> +</I>>>><i> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether +</I>>>><i> 1c:75:08:28:bd:e4 brd ff:ff:ff:ff:ff:ff inet 169.254.100.1/24 brd +</I>>>><i> 169.254.100.255 scope global eth0 inet6 +</I>>>><i> fe80::1e75:8ff:fe28:bde4/64 scope link valid_lft forever +</I>>>><i> preferred_lft forever +</I>>>><i> +</I>>>>><i> []# ip addr add www.xxx.yyy.zzz/netmask dev eth0 +</I>>>><i> +</I>>>><i> # ip addr add www.192.168.0.20/255.255.255.0 dev eth0 Error: an +</I>>>><i> inet prefix is expected rather than +</I>>>><i> "www.192.168.0.20/255.255.255.0". +</I>>>><i> +</I>>>><i> Not sure what it is expecting. +</I>>><i> +</I>>><i> hum, i meant the socalled CIDR notation: 4 parts of ip address +</I>>><i> followed by a subnet mask, +</I>>><i> +</I>>><i> in your case, i'd do: +</I>>><i> +</I>>><i> []# ip addr add 192.168.0.20/24 dev eth0 +</I>>><i> +</I>><i> Meanwhile, I played with alternatives, knowing that it must be +</I>><i> something close to what I'd already tried. So, +</I>><i> +</I>><i> # ip addr add 192.168.0.20/255.255.255.0 dev eth0 +</I>><i> # ip addr show eth0 +</I>><i> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast +</I>><i> state UP qlen 1000 +</I>><i> link/ether 1c:75:08:28:bd:e4 brd ff:ff:ff:ff:ff:ff +</I>><i> inet 169.254.100.1/24 brd 169.254.100.255 scope global eth0 +</I>><i> inet 192.168.0.20/24 scope global eth0 +</I>><i> inet6 fe80::1e75:8ff:fe28:bde4/64 scope link +</I>><i> valid_lft forever preferred_lft forever +</I>><i> +</I>><i> So now it appears to have two addresses, preferring the wrong one. +</I> + +by preferring, you mean the top one? + + +>><i> then if you do +</I>>><i> +</I>>><i> []# ip addr show eth0 +</I>>><i> +</I>>><i> again, you'd see it was there, as well as the extra route for that +</I>>><i> range: +</I>>><i> +</I>>><i> []# ip route +</I>>><i> +</I>><i> # ip route +</I>><i> default via 192.168.0.1 dev eth1 proto static +</I>><i> default via 169.254.100.100 dev eth0 metric 10 +</I>><i> default via 192.168.0.1 dev eth1 metric 10 +</I>><i> 169.254.100.0/24 dev eth0 proto kernel scope link src 169.254.100.1 +</I>><i> metric 10 +</I>><i> 192.168.0.0/24 dev eth1 proto kernel scope link src 192.168.0.101 +</I>><i> 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.20 +</I> + +whoa, 3 default routes? over different interfaces... + +you have 192.168.0.0/24 network, both reachable over eth1 and eth0, i hope +that is what you want... + + +>><i> +</I>><i> ifconfig +</I>><i> eth0 Link encap:Ethernet HWaddr 1C:75:08:28:BD:E4 +</I>><i> inet addr:169.254.100.1 Bcast:169.254.100.255 +</I>><i> Mask:255.255.255.0 +</I>><i> +</I>>>><i> +</I>>>><i> Shorewall and iptables are currently stopped. +</I>>><i> +</I>>><i> Be careful of this, in your case, it might not matter, but +</I>>><i> shorewall stop has policy DROP, (i think), allthough iptables +</I>>><i> should have policy ACCEPT. +</I>>><i> +</I>>><i> so, you'd have to stop shorewall first, then stop iptables. +</I>><i> +</I>><i> That's the order I did it. +</I>>><i> +</I>>><i> personally, i'd rather not stop the firewall, due to security +</I>>><i> reasons though. but since with this solution, you don't have any +</I>>><i> extra interface, even just restarting it would be fine. +</I>>><i> +</I>><i> Once I have a connection I'll restart them. +</I>><i> +</I>>><i> if you want to debug even further: +</I>>><i> +</I>>><i> []# tcpdump -n -i eth0 host <nas_ip> +</I>>><i> +</I>><i> Where does that write to? A log file? +</I>><i> +</I>>><i> and try to connect and then you can see what sourceip and destip +</I>>><i> are set and if a reply is coming back. +</I>>><i> +</I>><i> At the end of this, though, I can ping both the NAS on 192.168.0.200 +</I>><i> and other LAN connections. +</I>><i> +</I>><i> Last question, then, is whether this is a permanent change? +</I> +ip command is never permanent, you have to change the config files if you +want permanent changes (ie: after reboot). +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="007397.html">[Mageia-discuss] Temporarily changing IP address +</A></li> + <LI>Next message: <A HREF="007384.html">[Mageia-discuss] Temporarily changing IP address +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7793">[ date ]</a> + <a href="thread.html#7793">[ thread ]</a> + <a href="subject.html#7793">[ subject ]</a> + <a href="author.html#7793">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss +mailing list</a><br> +</body></html> |