whereami: setting ip address?
so i am starting to learn whereami (because i need to use something, not because i have made a decision), and while it wonderfully detects the correct environment and changes postfix and resolv.conf and printcap and whatnot, it fails to do one vital thing: giving an IP address to eth0 and settings routes. i may well be misunderstanding whereami, but i can't figure out how to get it to interact with ifupdown... whereami is called from /etc/network/if-pre-up.d/whereami, and it works like a charm. but no matter whether it detects the lan with a static ip, wireless, dhcp, or offline, the interface brought up is still controlled by /etc/network/interfaces. do i need to use mapping in this file, should i call ifup with a mapped name from whereami.conf, should i call ifconfig from there, or am i doing something completely wrong? thanks, -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than to fix a system msg07059/pgp0.pgp Description: PGP signature
What's my dynamic IP address
As the subject says: Where do I find my IP address after I connect to my ISP with a dial-up account? I am guessing that it is somewhere in 'proc', but I haven't figured out where. -- Marc Shapiro "If you drink melomel every day, [EMAIL PROTECTED]you will live to be 150 years old, Please visit "The Meadery" at: unless your wife shoots you." http://www.bigfoot.com/~m_shapiro/ -- Dr. Ferenc Androczi, winemaker, Little Hungary Farm Winery -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: whereami: setting ip address?
Hi Martin, On Tue, Oct 15, 2002 at 11:18:41AM +0200, martin f krafft wrote: > whereami is called from /etc/network/if-pre-up.d/whereami, and it > works like a charm. but no matter whether it detects the lan with > a static ip, wireless, dhcp, or offline, the interface brought up is > still controlled by /etc/network/interfaces. > > do i need to use mapping in this file, should i call ifup with > a mapped name from whereami.conf, should i call ifconfig from there, > or am i doing something completely wrong? You are right, the integration with ifupdown is not yet perfect, and there isn't good support for using network mappings; it is on the todo list. I use ipconfig calls from within whereami.conf for the network where an ip address is not assigned automatically: +home ifconfig eth0 192.168.10.7 +home route del default +home route add default gw 192.168.10.1 Chris msg07071/pgp0.pgp Description: PGP signature
Re: whereami: setting ip address?
Hi All ! Is there any documentation about the usage of the (new) subdirectories in `/etc/network' ? Thanks in advance, Jerome Chris Halls wrote: > Hi Martin, > > On Tue, Oct 15, 2002 at 11:18:41AM +0200, martin f krafft wrote: > >>whereami is called from /etc/network/if-pre-up.d/whereami, and it >>works like a charm. but no matter whether it detects the lan with >>a static ip, wireless, dhcp, or offline, the interface brought up is >>still controlled by /etc/network/interfaces. >> >>do i need to use mapping in this file, should i call ifup with >>a mapped name from whereami.conf, should i call ifconfig from there, >>or am i doing something completely wrong? > > > You are right, the integration with ifupdown is not yet perfect, and there > isn't good support for using network mappings; it is on the todo list. I > use ipconfig calls from within whereami.conf for the network where an ip > address is not assigned automatically: > > +home ifconfig eth0 192.168.10.7 > +home route del default > +home route add default gw 192.168.10.1 > > Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: whereami: setting ip address?
Jerome BENOIT wrote: > > Hi All ! > > Is there any documentation about the usage of the (new) > subdirectories in `/etc/network' ? man interfaces -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What's my dynamic IP address
i use ifconfig ppp0 and then grep it for the IP line and cut for the address... this will only work obviously if you are using point to point protocol... try it! Shawn --- Marc Shapiro <[EMAIL PROTECTED]> wrote: > As the subject says: Where do I find my IP address after I connect to > my > ISP with a dial-up account? I am guessing that it is somewhere in > 'proc', but I haven't figured out where. > > -- > Marc Shapiro "If you drink melomel every day, > [EMAIL PROTECTED]you will live to be 150 years > old, > Please visit "The Meadery" at: unless your wife shoots you." > http://www.bigfoot.com/~m_shapiro/ -- Dr. Ferenc Androczi, > winemaker, > Little Hungary Farm Winery > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > = Shawn Lamson Debian/GNU Linux Woody Kernel 2.2.19pre17 XFree86 Version 4.1.0.1 / X Window System Jesus Loves You! __ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What's my dynamic IP address
On Tue, 1 Oct 2002 at 8:48pm, Marc Shapiro wrote: :As the subject says: Where do I find my IP address after I connect to my :ISP with a dial-up account? I am guessing that it is somewhere in :'proc', but I haven't figured out where. '/sbin/ifconfig' should report it, I think. Patrick -- Patrick Wiseman [EMAIL PROTECTED] Linux user #17943 *Google First, Ask Later* -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What's my dynamic IP address
Marc Shapiro <[EMAIL PROTECTED]> writes: > As the subject says: Where do I find my IP address after I connect to my > ISP with a dial-up account? I am guessing that it is somewhere in > 'proc', but I haven't figured out where. You should be able to find your current IP address(es) by running /sbin/ifconfig. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ "Theoretical politics is interesting. Politicking should be illegal." -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What's my dynamic IP address
--bg08WKrSYDhXBjb5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
* Marc Shapiro <[EMAIL PROTECTED]>, 2002-10-01 20:46 -0400:
> As the subject says: Where do I find my IP address after I connect to my
> ISP with a dial-up account? I am guessing that it is somewhere in
> 'proc', but I haven't figured out where.
#!/bin/sh
/sbin/ifconfig ${iface} | grep 'inet' | cut -d: -f2 | cut -d " " -f1 | grep -v 127
or, graphically,
#!/bin/sh
xmessage -center $(/sbin/ifconfig ${iface} | grep 'inet' | cut -d: -f2 | cut -d " "
-f1 | grep -v 127)
(long lines)
-Andre
--bg08WKrSYDhXBjb5
Content-Type: application/pgp-signature
Content-Disposition: inline
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9mlHFmlbrvn+0waMRAgfYAJ9LIHlLMAQCQXkHdG4ZMnf2p4TTEACghGSI
6YmP7w9+Zk2f1eO7skVSztg=
=4y6W
-END PGP SIGNATURE-
--bg08WKrSYDhXBjb5--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What's my dynamic IP address
On Tue, Oct 01, 2002 at 08:48:46PM -0400, Marc Shapiro wrote: > As the subject says: Where do I find my IP address after I connect to my > ISP with a dial-up account? I am guessing that it is somewhere in > 'proc', but I haven't figured out where. Actually, it's way easier than you suggest. Try typing /sbin/ifconfig, look for ppp0. -- Baloo msg04978/pgp0.pgp Description: PGP signature
Can't access 1 IP address on Lan
Strangest thing. Our network is 10.0.1.0/255.255.255.0 I can access any address in our network except 10.0.1.1, which is our mail server. It won't ping it or anything. Any ideas? Curtis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't access 1 IP address on Lan
route information follows: route -n DestinationGateway Genmask 10.0.1.0 0.0.0.0 255.255.255.0 0.0.0.010.0.1.2540.0.0.0 Exactly the same as on another Debian computer, but it ping 10.0.1.1 no problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't access 1 IP address on Lan
On Mon, 07 Oct 2002 15:16:33 -0700 Curtis Vaughan <[EMAIL PROTECTED]> wrote: > Our network is 10.0.1.0/255.255.255.0 > I can access any address in our network except 10.0.1.1, which is our > mail server. It won't ping it or anything. Any ideas? Please provide more information... such as the output of the following: - /sbin/route -n - /sbin/ifconfig -- Jamin W. Collins -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Can't access 1 IP address on Lan - Recap
By the way, I still can't ping one IP address from a Debian computer within my LAN. To repeat, my network setup is 10.0.1.0/255.255.255.0 eth0 information is: inet addr: 10.0.1.5 Bcast: 10.0.1.255 Mask:255.255.255.0 route information follows: route -n DestinationGateway Genmask 10.0.1.0 0.0.0.0 255.255.255.0 0.0.0.010.0.1.2540.0.0.0 This data (except IP address) is exactly the same as on another Debian computer, but it pings 10.0.1.1 no problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't access 1 IP address on Lan
I would check the route table. Sounds like you can only reach your mail server because it is probably your default route. Just a thought Cheers David On Tuesday 08 October 2002 08:16, Curtis Vaughan wrote: > Strangest thing. > > Our network is 10.0.1.0/255.255.255.0 > I can access any address in our network except 10.0.1.1, which is our > mail server. It won't ping it or anything. Any ideas? > > Curtis > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't access 1 IP address on Lan
hi ya curtis what is the output of root# route -nv root# ifconfig -v root# ipchains -L root# ping 10.0.1.1 ( a local ping of itself should always work even w/o a cable ) am assuming you didn't manually turn off ping replies on the one host am also assuming you tried swapping the cable on *.1.1 with a acalbe that worked when pinging that other machine c ya alvin you probably have a misconfigured number in one of the files - and i assume you mean you can only ping any of the 253 hosts in 10.0.1.x ( except *.0 and *.255 and *.1(broken ) On Tue, 8 Oct 2002, David Cureton wrote: > > I would check the route table. Sounds like you can only reach your mail > server because it is probably your default route. > > Just a thought > Cheers > David > > > On Tuesday 08 October 2002 08:16, Curtis Vaughan wrote: > > Strangest thing. > > > > Our network is 10.0.1.0/255.255.255.0 > > I can access any address in our network except 10.0.1.1, which is our > > mail server. It won't ping it or anything. Any ideas? > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't access 1 IP address on Lan
> hi ya curtis > > what is the output of > > root# route -nv Debian3800:~# route -nv Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 10.0.1.00.0.0.0 255.255.255.0 U 0 00 eth0 0.0.0.0 10.0.1.254 0.0.0.0 UG0 00 eth0 > root# ifconfig -v Debian3800:~# ifconfig -v eth0 Link encap:Ethernet HWaddr 00:10:A4:D2:DE:91 inet addr:10.0.1.5 Bcast:10.0.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:30267475 errors:0 dropped:0 overruns:0 frame:0 TX packets:157542 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:3128132587 (2.9 GiB) TX bytes:40244900 (38.3 MiB) Interrupt:11 Base address:0x4800 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:26119 errors:0 dropped:0 overruns:0 frame:0 TX packets:26119 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:14695650 (14.0 MiB) TX bytes:14695650 (14.0 MiB) > > root# ipchains -L Debian3800:~# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination > > root# ping 10.0.1.1 > ( a local ping of itself should always work even w/o a cable ) Debian3800:~# ping 10.0.1.1 PING 10.0.1.1 (10.0.1.1): 56 data bytes (nothing else) > > am assuming you didn't manually turn off ping replies on the one host Right. Other computers can ping it. > > am also assuming you tried swapping the cable on *.1.1 with a acalbe > that worked when pinging that other machine > > c ya > alvin > > you probably have a misconfigured number in one of the files > > - and i assume you mean you can only ping any of the 253 hosts in > 10.0.1.x ( except *.0 and *.255 and *.1(broken ) right > > > On Tue, 8 Oct 2002, David Cureton wrote: > > > > > I would check the route table. Sounds like you can only reach your mail > > server because it is probably your default route. > > > > Just a thought > > Cheers > > David > > > > > > On Tuesday 08 October 2002 08:16, Curtis Vaughan wrote: > > > Strangest thing. > > > > > > Our network is 10.0.1.0/255.255.255.0 > > > I can access any address in our network except 10.0.1.1, which is our > > > mail server. It won't ping it or anything. Any ideas? > > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't access 1 IP address on Lan
hi ya curtis do my silly question is.. where is the machine called 10.0.1.1 that does not reply to pings ?? - if you know where 10.0.1.1 is... do the same set of commands again ( route -nv, ifconfig -v, ipchains -L, etc - the 10.0.1.1 machine should be able to ping itself and should be ble to ping the local LAN and outside world i am not 100% sure... but you might wanna turn off "null ipchains" rules or at least have it pass all up .. am assuming this is NOT the firewall and if it is... you're missing all of the fw rules c ya alvin On Thu, 10 Oct 2002, Curtis wrote: > > hi ya curtis > > > > what is the output of > > > > root# route -nv > Debian3800:~# route -nv > Kernel IP routing table > Destination Gateway Genmask Flags Metric RefUse > Iface > 10.0.1.00.0.0.0 255.255.255.0 U 0 00 eth0 > 0.0.0.0 10.0.1.254 0.0.0.0 UG0 00 eth0 > > > root# ifconfig -v > Debian3800:~# ifconfig -v > eth0 Link encap:Ethernet HWaddr 00:10:A4:D2:DE:91 > inet addr:10.0.1.5 Bcast:10.0.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:30267475 errors:0 dropped:0 overruns:0 frame:0 > TX packets:157542 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:3128132587 (2.9 GiB) TX bytes:40244900 (38.3 MiB) > Interrupt:11 Base address:0x4800 > > loLink encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:26119 errors:0 dropped:0 overruns:0 frame:0 > TX packets:26119 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:14695650 (14.0 MiB) TX bytes:14695650 (14.0 MiB) > > > > > root# ipchains -L > Debian3800:~# iptables -L > Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > > > > > root# ping 10.0.1.1 > > ( a local ping of itself should always work even w/o a cable ) > Debian3800:~# ping 10.0.1.1 > PING 10.0.1.1 (10.0.1.1): 56 data bytes > (nothing else) > > > > > am assuming you didn't manually turn off ping replies on the one host > Right. Other computers can ping it. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't access 1 IP address on Lan
> hi ya curtis > > do my silly question is.. where is the machine called 10.0.1.1 > that does not reply to pings ?? It's a small office LAN. My computer that can't ping it has an IP of 10.0.1.5. It does reply to pings from ANY OTHER computer, except 10.0.1.5. > - if you know where 10.0.1.1 is... do the same set of commands > again ( route -nv, ifconfig -v, ipchains -L, etc I understood this to mean that you want me to run the route and other commands on the 10.0.1.1 computer. Well, it's an NT4 computer. Anyhow, the point is that this computer can be pinged by any computer but mine. > > - the 10.0.1.1 machine should be able to ping itself > and should be ble to ping the local LAN and outside world And it can. > > i am not 100% sure... but you might wanna turn off "null ipchains" rules > or at least have it pass all up .. > > am assuming this is NOT the firewall and if it is... you're missing > all of the fw rules Good assumption. But my firewall rules are on 10.0.1.254. So, I don't see how it could be interfering. > c ya > alvin > > > On Thu, 10 Oct 2002, Curtis wrote: > > > > hi ya curtis > > > > > > what is the output of > > > > > > root# route -nv > > Debian3800:~# route -nv > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric RefUse > > Iface > > 10.0.1.00.0.0.0 255.255.255.0 U 0 00 eth0 > > 0.0.0.0 10.0.1.254 0.0.0.0 UG0 00 eth0 > > > > > root# ifconfig -v > > Debian3800:~# ifconfig -v > > eth0 Link encap:Ethernet HWaddr 00:10:A4:D2:DE:91 > > inet addr:10.0.1.5 Bcast:10.0.1.255 Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:30267475 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:157542 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:100 > > RX bytes:3128132587 (2.9 GiB) TX bytes:40244900 (38.3 MiB) > > Interrupt:11 Base address:0x4800 > > > > loLink encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:26119 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:26119 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:14695650 (14.0 MiB) TX bytes:14695650 (14.0 MiB) > > > > > > > > root# ipchains -L > > Debian3800:~# iptables -L > > Chain INPUT (policy ACCEPT) > > target prot opt source destination > > > > Chain FORWARD (policy ACCEPT) > > target prot opt source destination > > > > Chain OUTPUT (policy ACCEPT) > > target prot opt source destination > > > > > > > > root# ping 10.0.1.1 > > > ( a local ping of itself should always work even w/o a cable ) > > Debian3800:~# ping 10.0.1.1 > > PING 10.0.1.1 (10.0.1.1): 56 data bytes > > (nothing else) > > > > > > > > am assuming you didn't manually turn off ping replies on the one host > > Right. Other computers can ping it. > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Can't access 1 IP address on Lan - Recap
> By the way, I still can't ping one IP address from a Debian computer > within my LAN. > This data (except IP address) is exactly the same as on another Debian computer, but it >pings 10.0.1.1 no problem. I would try running tcpdump and pinging 10.0.1.1 on your working machine. You should see an ARP packet and the ICMP echo packets. Next, run it from your 'broken' machine - do you see the ARP? If you don't, try running tcpdump on 10.0.1.1 and generate your pings from the broken machine. Do you see the ARP request? Other things to try on the 'broken' machine -- a different IP address. Static ARP entry for 10.0.1.1. Tony Wasson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
