Re: Default OM settings, no lan messed up
How does the default WIFI work with open/free wifi access? Would I be able to get connected to the internet with a wifi router that has dhcp working? I'd really like to get the OM functioning. Thanks ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
On Oct 14, 2008, at 7:40 AM, Rodney Myers wrote: How does the default WIFI work with open/free wifi access? Would I be able to get connected to the internet with a wifi router that has dhcp working? I'd really like to get the OM functioning. Thanks I just attempted to log onto a wide open wifi router. It did not go. Anything else I can try, to get the OM working? PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
On Tue, 14 Oct 2008 16:44:34 -0700, Rodney Myers [EMAIL PROTECTED]
wrote:
On Oct 14, 2008, at 7:40 AM, Rodney Myers wrote:
How does the default WIFI work with open/free wifi access?
Would I be able to get connected to the internet with a wifi router
that has dhcp working?
I'd really like to get the OM functioning.
Thanks
I just attempted to log onto a wide open wifi router. It did not go.
Anything else I can try, to get the OM working?
Put the following into etc/wpa_supplicant/wpa_supplicant.conf (and below
that edit /etc/network/interfaces)and try ifup eth0 manually:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# home:
network={
ssid=NEWKIRK
proto=WPA
key_mgmt=WPA-PSK
psk=118a8aa1abfc236ebb4df06e891172ccef6c72c7db0ad5540b7f4c77858378d4
priority=50
}
# Open:
network={
ssid=any
key_mgmt=NONE
priority=5
}
And alter /etc/network/interfaces to have the following:
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
(I left my own network in there as an example of working WPA to a Netgear
router - I had repeated issues with it until I used the hex key instead of
text - and yes, that's actually the right key: I wouldn't refuse any
Freerunner owner who wanted to leech my broadband, if they happened to be
down the dead-end road to my house ;)
The higher priority numbers are used first if multiples match, IE at home I
can see an unsecured network from next door, but it will always connect to
my AP. Elsewhere it will connect to whatever unsecure AP is reachable.
(In actual practice I've got three other APs defined as well, both secure
and not)
j
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
On Oct 14, 2008, at 7:13 PM, Joel Newkirk wrote:
On Tue, 14 Oct 2008 16:44:34 -0700, Rodney Myers [EMAIL PROTECTED]
wrote:
On Oct 14, 2008, at 7:40 AM, Rodney Myers wrote:
How does the default WIFI work with open/free wifi access?
Would I be able to get connected to the internet with a wifi router
that has dhcp working?
I'd really like to get the OM functioning.
Thanks
I just attempted to log onto a wide open wifi router. It did not go.
Anything else I can try, to get the OM working?
Put the following into etc/wpa_supplicant/wpa_supplicant.conf (and
below
that edit /etc/network/interfaces)and try ifup eth0 manually:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# home:
network={
ssid=NEWKIRK
proto=WPA
key_mgmt=WPA-PSK
psk=118a8aa1abfc236ebb4df06e891172ccef6c72c7db0ad5540b7f4c77858378d4
priority=50
}
# Open:
network={
ssid=any
key_mgmt=NONE
priority=5
}
And alter /etc/network/interfaces to have the following:
iface eth0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
(I left my own network in there as an example of working WPA to a
Netgear
router - I had repeated issues with it until I used the hex key
instead of
text - and yes, that's actually the right key: I wouldn't refuse any
Freerunner owner who wanted to leech my broadband, if they happened
to be
down the dead-end road to my house ;)
The higher priority numbers are used first if multiples match, IE at
home I
can see an unsecured network from next door, but it will always
connect to
my AP. Elsewhere it will connect to whatever unsecure AP is
reachable.
(In actual practice I've got three other APs defined as well, both
secure
and not)
j
Therein lies the problem. I have no shell access, and no access
through the USB port, after I edited the /etc/network/interfaces file.
I was hoping that the OM would access a wide open wifi connection, so
I could get ahead a bit.
PGP.sig
Description: This is a digitally signed message part
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
On Tue, 14 Oct 2008 20:05:53 -0700, Rodney Myers [EMAIL PROTECTED] wrote: On Oct 14, 2008, at 7:13 PM, Joel Newkirk wrote: On Tue, 14 Oct 2008 16:44:34 -0700, Rodney Myers [EMAIL PROTECTED] wrote: On Oct 14, 2008, at 7:40 AM, Rodney Myers wrote: How does the default WIFI work with open/free wifi access? Would I be able to get connected to the internet with a wifi router that has dhcp working? I'd really like to get the OM functioning. Thanks I just attempted to log onto a wide open wifi router. It did not go. Anything else I can try, to get the OM working? Put the following into etc/wpa_supplicant/wpa_supplicant.conf (and below that edit /etc/network/interfaces)and try ifup eth0 manually: [snipped configs] Therein lies the problem. I have no shell access, and no access through the USB port, after I edited the /etc/network/interfaces file. I was hoping that the OM would access a wide open wifi connection, so I could get ahead a bit. Hmmm, I would have hoped so as well. (Sorry, I hadn't realized you hadn't resolved the USBnet matter) How about a radically different approach then - if you have a card reader, stick the uSD in it and install a new base system on it (per http://wiki.openmoko.org/wiki/Booting_from_SD) and then boot the Freerunner from it. SSH into the SD-booted OS and make your changes. (I think you need to mount the internal flash manually, not sure) ***Hey Openmoko folks - I think the built-in installer should have a file dialog to install ipks we place on SD... j ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Default OM settings, no lan messed up
OS = OS X 10.5.5 I received my OM this past week. Took some time to locate an ATT sim card that would work. Yesterday, I was able to follow the instructions at; http://wiki.openmoko.org/wiki/MacOS_X ,and using the link; http://downloads.openmoko.org/releases/Om2008.9 grabbing the rootfs of Om2008.9-gta02-20080916.rootfs.jffs2 to flash the phone. Once flashed, I noticed there was no console icon anymore I was able to SSH into the OM. Once I did that, I edited changed the /etc/network/interfaces file to reflect my lan. 192.168.1.*** Before I logged out, I catted the file to make sure that I had correctly set that file. It all looked correct I then logged out of the phone restarted the phone, thinking I now would be able to ssh, without jumping through hoops. No such luck. Now, the IP address is neither the default nor anything on the 192.168.1.*** network.. Any help in getting the phone functioning again, would be greatly appreciated. Many thanks PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
On Mon, 13 Oct 2008 10:10:28 -0700, Rodney Myers [EMAIL PROTECTED] wrote: OS = OS X 10.5.5 I received my OM this past week. Took some time to locate an ATT sim card that would work. Yesterday, I was able to follow the instructions at; http://wiki.openmoko.org/wiki/MacOS_X ,and using the link; http://downloads.openmoko.org/releases/Om2008.9 grabbing the rootfs of Om2008.9-gta02-20080916.rootfs.jffs2 to flash the phone. Once flashed, I noticed there was no console icon anymore I was able to SSH into the OM. Once I did that, I edited changed the /etc/network/interfaces file to reflect my lan. 192.168.1.*** Before I logged out, I catted the file to make sure that I had correctly set that file. It all looked correct I then logged out of the phone restarted the phone, thinking I now would be able to ssh, without jumping through hoops. No such luck. Now, the IP address is neither the default nor anything on the 192.168.1.*** network.. Any help in getting the phone functioning again, would be greatly appreciated. Many thanks What is the full IP, gateway, and subnet mask you set on the FreeRunner, and on the USB network interface on your host? Does it overlap the subnet on any other interface on the host? j If you are able to set up a packet sniffer on USB network device on the host, try tapping 'installer' on the FR and see what IP the connection attempt comes from. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
On Oct 13, 2008, at 10:36 AM, Joel Newkirk wrote: On Mon, 13 Oct 2008 10:10:28 -0700, Rodney Myers [EMAIL PROTECTED] wrote: OS = OS X 10.5.5 I received my OM this past week. Took some time to locate an ATT sim card that would work. Yesterday, I was able to follow the instructions at; http://wiki.openmoko.org/wiki/MacOS_X ,and using the link; http://downloads.openmoko.org/releases/Om2008.9 grabbing the rootfs of Om2008.9-gta02-20080916.rootfs.jffs2 to flash the phone. Once flashed, I noticed there was no console icon anymore I was able to SSH into the OM. Once I did that, I edited changed the /etc/network/interfaces file to reflect my lan. 192.168.1.*** Before I logged out, I catted the file to make sure that I had correctly set that file. It all looked correct I then logged out of the phone restarted the phone, thinking I now would be able to ssh, without jumping through hoops. No such luck. Now, the IP address is neither the default nor anything on the 192.168.1.*** network.. Any help in getting the phone functioning again, would be greatly appreciated. Many thanks What is the full IP, gateway, and subnet mask you set on the FreeRunner, and on the USB network interface on your host? Does it overlap the subnet on any other interface on the host? j If you are able to set up a packet sniffer on USB network device on the host, try tapping 'installer' on the FR and see what IP the connection attempt comes from. I thought i had it setup this way address 192.168.1.20 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.101 (my MBP) My home lan is using 192.168.1.*** range. No idea on how to sniff packets, at this time. When I click on the installer it pops up a message; ERROR: Cannot access *. Please check your network When I plug the OM into the computer, it does show the MAC address, in dmesg; net_lucid_cake_driver_AJZaurusUSB: Ethernet address 40:00:ff:f7:87:5c PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: Default OM settings, no lan messed up
From: [EMAIL PROTECTED] To: community@lists.openmoko.org Date: Mon, 13 Oct 2008 11:04:34 -0700 Subject: Re: Default OM settings, no lan messed up On Oct 13, 2008, at 10:36 AM, Joel Newkirk wrote: On Mon, 13 Oct 2008 10:10:28 -0700, Rodney Myers wrote: OS = OS X 10.5.5 I received my OM this past week. Took some time to locate an ATT sim card that would work. Yesterday, I was able to follow the instructions at; http://wiki.openmoko.org/wiki/MacOS_X ,and using the link; http://downloads.openmoko.org/releases/Om2008.9 grabbing the rootfs of Om2008.9-gta02-20080916.rootfs.jffs2 to flash the phone. Once flashed, I noticed there was no console icon anymore I was able to SSH into the OM. Once I did that, I edited changed the /etc/network/interfaces file to reflect my lan. 192.168.1.*** Before I logged out, I catted the file to make sure that I had correctly set that file. It all looked correct I then logged out of the phone restarted the phone, thinking I now would be able to ssh, without jumping through hoops. No such luck. Now, the IP address is neither the default nor anything on the 192.168.1.*** network.. Any help in getting the phone functioning again, would be greatly appreciated. Many thanks What is the full IP, gateway, and subnet mask you set on the FreeRunner, and on the USB network interface on your host? Does it overlap the subnet on any other interface on the host? j If you are able to set up a packet sniffer on USB network device on the host, try tapping 'installer' on the FR and see what IP the connection attempt comes from. I thought i had it setup this way address 192.168.1.20 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.101 (my MBP) My home lan is using 192.168.1.*** range. No idea on how to sniff packets, at this time. When I click on the installer it pops up a message; ERROR: Cannot access *. Please check your network When I plug the OM into the computer, it does show the MAC address, in dmesg; net_lucid_cake_driver_AJZaurusUSB: Ethernet address 40:00:ff:f7:87:5c Using 192.168.1.x for local network with internet acess and 192.168.0.202 is my freerunner. I find no reason for this but sometimes internet acess from FR won't work, then I run firestarter (a firewall out of the ubuntu repositories) and internet works again (even if i shutdown firestarter). On freerunner (192.168.1.1 is my router, 192.168.0.200 is my host computer): auto usb0 iface usb0 inet static address 192.168.0.202 netmask 255.255.255.0 network 192.168.0.200 gateway 192.168.0.200 up echo nameserver 192.168.1.1 /etc/resolv.conf On Host (Ubuntu): auto usb0 iface usb0 inet static address 192.168.0.200 netmask 255.255.255.192 post-up /etc/network/freerunner start pre-down /etc/network/freerunner stop the /etc/network/freerunner script you can find in the wiki (USB_Networking in section Ubuntu, Debian and others) _ Werden Sie Mitglied der neuen Windows Live Messenger Familie! http://get.live.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
On Mon, 13 Oct 2008 11:04:34 -0700, Rodney Myers [EMAIL PROTECTED] wrote: On Oct 13, 2008, at 10:36 AM, Joel Newkirk wrote: On Mon, 13 Oct 2008 10:10:28 -0700, Rodney Myers [EMAIL PROTECTED] wrote: OS = OS X 10.5.5 I was able to SSH into the OM. Once I did that, I edited changed the /etc/network/interfaces file to reflect my lan. 192.168.1.*** Before I logged out, I catted the file to make sure that I had correctly set that file. It all looked correct I then logged out of the phone restarted the phone, thinking I now would be able to ssh, without jumping through hoops. No such luck. Now, the IP address is neither the default nor anything on the 192.168.1.*** network.. Any help in getting the phone functioning again, would be greatly appreciated. Many thanks What is the full IP, gateway, and subnet mask you set on the FreeRunner, and on the USB network interface on your host? Does it overlap the subnet on any other interface on the host? j If you are able to set up a packet sniffer on USB network device on the host, try tapping 'installer' on the FR and see what IP the connection attempt comes from. I thought i had it setup this way address 192.168.1.20 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.101 (my MBP) My home lan is using 192.168.1.*** range. That's the problem there. Your desktop system already has a valid working route to 192.168.1.0/24 on ethernet. When you set up another network interface with the same subnet (192.168.1.0/24) then the result is OS/kernel dependent, but almost NEVER pretty. Try setting the usb networking on the host to 192.168.1.21, subnet mask 255.255.255.248 (that's /29). You should be able to communicate with the FR again at that point. The FR will still not connect to the world though. At the minimum you'll need to change the gateway to 192.168.1.21, and deal with /etc/resolv.conf. Then you should be able to reach the internet from the FR, though your LAN (except the host itself) will be unreachable. The safest setup is to have different subnets (like 192.168.1.0/24 and 192.168.0.0/24) on each interface. If you're currently running 192.168.1.0/24 on your LAN, then the usbnet connection should use a different (non-overlapping) subnet for simplest and best functioning. The MBP will need to NAT connections from the FR - presuming it just passes them, the rest of your network (including router/gateway to the internet) will send responses to the IP of the FR, which it will have no idea how to reach since it's 'behind' the MBP from the router's point of view. To fix that you'd have to make manual routing changes on the router, or set up proxy arp on the MBP, or a few other possibilities - all far more complex than just using different subnets. The 'fix' I mentioned first works because routing decisions (IE, what interface do I use for a packet going to a.b.c.d?) are typically made by looking at the MOST RESTRICTIVE route first. So if 192.168.1.20 is technically within two subnets for the host (192.168.1.0/24 on eth0 and 192.168.1.16/29 on usb0, for example) then it will use the route with the smaller subnet. (which means the larger subnet mask number in /24 /29 format) But normally other devices on the 192.168.1.0/24 network (like another computer, or router, or network printer) will expect 192.168.1.20 to be RIGHT on the wire out their own interface, NOT on the other side of your MBP. (from their perspective the MBP is a router they need to use to reach 192.168.1.21, and they don't know that) The other possibility (which I have no idea how to implement on osX) is to bridge the ethernet or wireless interface on the host to the usb networking interface. If for whatever reason you're insistent on keeping 192.168.1.0/24 addresses on everything, you can set up the smaller /29 subnet I mentioned at the top on both the host and the FR, and set up default route and nameserver on the FR appropriately. Note that without lower-level routing tweaks the FR will NOT be able to communicate correctly with other IPs in 192.168.1.0/24, just with and through the host. No idea on how to sniff packets, at this time. I don't honestly know what's available for the Mac, but I'd be surprised if wireshark were not. That (or tshark, the text-only console variant) is what I use almost exclusively on linux and windows systems. Oh, and back to your original post for a moment, you'll need to go into Installer and install Terminal, it's not preinstalled in the image. (once Installer can communicate with the internet again, that is;) j PS: ipcalc is a handy tool... $ ipcalc -b 192.168.1.20/29 Address: 192.168.1.20 Netmask: 255.255.255.248 = 29 Wildcard: 0.0.0.7 = Network: 192.168.1.16/29 HostMin: 192.168.1.17 HostMax: 192.168.1.22 Broadcast: 192.168.1.23 Hosts/Net: 6
USB networking problems with Ubuntu host (was RE: Default OM settings, no lan messed up)
On Mon, 13 Oct 2008 19:03:54 +, Matthias Camenzind [EMAIL PROTECTED] wrote: Using 192.168.1.x for local network with internet acess and 192.168.0.202 is my freerunner. I find no reason for this but sometimes internet acess from FR won't work, then I run firestarter (a firewall out of the ubuntu repositories) and internet works again (even if i shutdown firestarter). On freerunner (192.168.1.1 is my router, 192.168.0.200 is my host computer): auto usb0 iface usb0 inet static address 192.168.0.202 netmask 255.255.255.0 network 192.168.0.200 gateway 192.168.0.200 up echo nameserver 192.168.1.1 /etc/resolv.conf On Host (Ubuntu): auto usb0 iface usb0 inet static address 192.168.0.200 netmask 255.255.255.192 post-up /etc/network/freerunner start pre-down /etc/network/freerunner stop the /etc/network/freerunner script you can find in the wiki (USB_Networking in section Ubuntu, Debian and others) Is it possible that it's not working after reboot? I'm wondering if there's a DROP rule in the FORWARD chain of the hosts's firewall. (sudo iptables -vnL FORWARD shows Policy, rules, and packet/byte counts that matched each - check it next time there's a problem BEFORE you run firestarter, as well as cat /proc/sys/net/ipv4/ip_forward which should return '1') The simple fix in this scenario would probably be just to add these two lines to the 'start' section of /etc/network/freerunner, based on what's in the wiki: iptables -I FORWARD -s 192.168.0.202 -j ACCEPT iptables -I FORWARD -d 192.168.0.202 -j ACCEPT You can add the corresponding 'iptables -D' commands in the 'stop' section to delete these rules if you like, but leaving them laying around is pretty harmless. I run Ubuntu on several workstations, three servers, and a bridge, with my FR regularly connected to three of the above. We'll make it work. j ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
The main problem is, I cannot ssh into the OM to make any changes. I cannot ping the OM, using 192.168.1.0 / 192.168.0.0 In the default setup, there is no shell icon anymore, so I am unable to see what the IP address really is. PGP.sig Description: This is a digitally signed message part ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
On Mon, Oct 13, 2008 at 4:00 PM, Rodney Myers [EMAIL PROTECTED] wrote: The main problem is, I cannot ssh into the OM to make any changes. I cannot ping the OM, using 192.168.1.0 / 192.168.0.0 In the default setup, there is no shell icon anymore, so I am unable to see what the IP address really is. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community You may have set the FR properly but it won't route properly from the desktop side. Try adding a host route on the desktop ifconfig add -host 192.168.1.20 dev usb0 You might be able to reach it then. Angus ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
On Tuesday 14 October 2008 06:14:35 Joel Newkirk wrote: PS: ipcalc is a handy tool... $ ipcalc -b 192.168.1.20/29 Address: 192.168.1.20 Netmask: 255.255.255.248 = 29 Wildcard: 0.0.0.7 = Network: 192.168.1.16/29 HostMin: 192.168.1.17 HostMax: 192.168.1.22 Broadcast: 192.168.1.23 Hosts/Net: 6 Class C, Private Internet But you'll lose those awfully useful on-demand binary skillz :) Seriously though, nice tool. Would have been really handy when I was bothering with cisco, if only to give to the people looking over my shoulder ;). I swear they sit around trying to figure out how to confuse people as much as possible. Sarton ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
On Tue, 14 Oct 2008 12:57:07 +1100, Sarton O'Brien [EMAIL PROTECTED] wrote: On Tuesday 14 October 2008 06:14:35 Joel Newkirk wrote: PS: ipcalc is a handy tool... $ ipcalc -b 192.168.1.20/29 Address: 192.168.1.20 Netmask: 255.255.255.248 = 29 Wildcard: 0.0.0.7 = Network: 192.168.1.16/29 HostMin: 192.168.1.17 HostMax: 192.168.1.22 Broadcast: 192.168.1.23 Hosts/Net: 6 Class C, Private Internet But you'll lose those awfully useful on-demand binary skillz :) Seriously though, nice tool. Would have been really handy when I was bothering with cisco, if only to give to the people looking over my shoulder ;). I swear they sit around trying to figure out how to confuse people as much as possible. Sarton sort of like riding a bicycle... My first computer I programmed via a hex keypad, 1802 machine code (no assembler, no mnemonics, just hex opcodes), so at the start of things I became (painfully) familiar with hex-dec-bin relationships, masks, and binary arithmetic. (I still see things like 'a*8' while my brain thinks 'a3') For the people over your shoulder you should omit the '-b' flag, which tells it to skip the bitwise output... ;) $ ipcalc 192.168.1.20/29 Address: 192.168.1.20 1100.10101000.0001.00010 100 Netmask: 255.255.255.248 = 29 ...1 000 Wildcard: 0.0.0.7 ...0 111 = Network: 192.168.1.16/29 1100.10101000.0001.00010 000 HostMin: 192.168.1.17 1100.10101000.0001.00010 001 HostMax: 192.168.1.22 1100.10101000.0001.00010 110 Broadcast: 192.168.1.23 1100.10101000.0001.00010 111 Hosts/Net: 6 Class C, Private Internet Seems most people who don't understand binary all the way down to their souls can't even see the dotted quads, their eyes and brains get stuck on the 'big' block of binary. For those interested in achieving understanding of netmasks it can be helpful to generate a few of these for familiar networks and look at the binary portion... The meaning of a /29 netmask for example is pretty clear above. j ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Default OM settings, no lan messed up
On Tuesday 14 October 2008 13:38:45 Joel Newkirk wrote: On Tue, 14 Oct 2008 12:57:07 +1100, Sarton O'Brien [EMAIL PROTECTED] wrote: On Tuesday 14 October 2008 06:14:35 Joel Newkirk wrote: PS: ipcalc is a handy tool... $ ipcalc -b 192.168.1.20/29 Address: 192.168.1.20 Netmask: 255.255.255.248 = 29 Wildcard: 0.0.0.7 = Network: 192.168.1.16/29 HostMin: 192.168.1.17 HostMax: 192.168.1.22 Broadcast: 192.168.1.23 Hosts/Net: 6 Class C, Private Internet But you'll lose those awfully useful on-demand binary skillz :) Seriously though, nice tool. Would have been really handy when I was bothering with cisco, if only to give to the people looking over my shoulder ;). I swear they sit around trying to figure out how to confuse people as much as possible. Sarton sort of like riding a bicycle... My first computer I programmed via a hex keypad, 1802 machine code (no assembler, no mnemonics, just hex opcodes), so at the start of things I became (painfully) familiar with hex-dec-bin relationships, masks, and binary arithmetic. (I still see things like 'a*8' while my brain thinks 'a3') I agree, though I haven't ridden that bicycle for a very long time. Although I've done some programming using hex on the z80s, I was always very fluent at deriving binary logic and determining boolean expressions by briefly looking at a diagram. So shuffling binary around in my head was never an issue, but the base 10 conversion was. Hex - binary was always easier but most likely due to the typically quad/octal nature of computing. For the people over your shoulder you should omit the '-b' flag, which tells it to skip the bitwise output... ;) $ ipcalc 192.168.1.20/29 Address: 192.168.1.20 1100.10101000.0001.00010 100 Netmask: 255.255.255.248 = 29 ...1 000 Wildcard: 0.0.0.7 ...0 111 = Network: 192.168.1.16/29 1100.10101000.0001.00010 000 HostMin: 192.168.1.17 1100.10101000.0001.00010 001 HostMax: 192.168.1.22 1100.10101000.0001.00010 110 Broadcast: 192.168.1.23 1100.10101000.0001.00010 111 Hosts/Net: 6 Class C, Private Internet Yep, this program would have saved me a lot of time ;) Seems most people who don't understand binary all the way down to their souls can't even see the dotted quads, their eyes and brains get stuck on the 'big' block of binary. You mean octal yeah? For those interested in achieving understanding of netmasks it can be helpful to generate a few of these for familiar networks and look at the binary portion... The meaning of a /29 netmask for example is pretty clear above. I second that. Anyone who doesn't completely understand what they are doing when they alter routes, IPs and netmasks should make sure to investigate further. Worst case you might light up an area of your brain that hasn't seen activity in a while :) Sarton ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
