Issue Sharing Internet with a PC

Setting up a network on my iMac to share my internet connection with my PC laptop. The connection works fine unencrypted w/o a password, but when I try to set a password (5 character, 40 bit) the PC just won't connect. Running 10.6.4 on the iMac and Windows XP on the laptop. Any suggestions on how to connect the PC with a password would be appreciated.

Can you also explain the steps you have used to share your connection?
Give an example of the type of password you are creating.
Dah•veed

Similar Messages

Sharing Internet with xbox 360

Hi, I have my Powerbook sharing internet with my Xbox 360. The connection works well and I am able to play games, but the NAT is listed as Moderate, with a Moderate NAT I am not able to do private voice chats with people. Does anyone know how I can get my NAT to Open? Also, I would like to share my media with my Xbox that is stored on a Windows XP computer. I followed all the steps given at www.xbox.com/pcsetup, but the Xbox still does not see the computer.
Any help would be appreciated, Thnx

If you are using Internet Sharing on your PowerBook you can forget trying to modify NAT settings or make nearly any other adjustments. There are very, very, very few options.
If you want to make adjustments like that you need to get a real base station.

Sharing Internet with AirPort

Hello
Okay to start my iMac here is connected directly to a DSL modem with no router through Ethernet. I saw that you can share Ethernet connections and use AirPort to create a Computer-to-Computer network and enable internet connection sharing. Would this work properly with a Windows XP computer with a wireless card in? I want to be able to get that computer on the net.

Okay to start my iMac here is connected directly to a
DSL modem with no router through Ethernet. I saw that
you can share Ethernet connections and use AirPort to
create a Computer-to-Computer network and enable
internet connection sharing.
System Preferences > Sharing > Internet
Share built-in-ethernet connection via Airport.
Would this work properly
with a Windows XP computer with a wireless card in?
Yes, but you won't be able to use a password with an XP PC therefore is not recommended.
I would recommend getting a wireless router.
iFelix

Sharing internet with Windows over AirPort

My G5 tower is connected to typical home router via ethernet. This gives it flawless internet connectivity.
To give better wireless access to mobile devices that come to that room for a visit in the far corner of the house where the G5 is located, I got a used AirPort Extreme card for the G5 and installed it, making sure to attach the antenna connector and small t-shaped external antenna (provided with original G5) plugged in the back.
When I powered the G5 back on, it immediately saw the AE card and told me to review settings and press Apply. Under Network prefs, under "Location: Automatic", I chose "Show: AirPort." An AirPort ID is shown, along with the default setting below: "By default, join 'Automatic.'" I left all other network settings as they are--I am not trying to use AirPort to connect the G5 to the main wireless router, since it already has ethernet.
I went to the "Sharing" pref and chose the third pane under it, "Internet". I configured it to read: Share your connection from built-in ethernet . . . using (checkbox on) AirPort. I clicked on the AirPort options in this same pane, and typed in a network name: "ABC wi-fi". Channel is Automatic, and--to keep things simple for now--I left encryption off. I pressed OK to close that small dialog, then hit "Start" in the Sharing/Internet pane, which makes its status message change to "Internet sharing on: sharing your built-in ethernet connection." Success! Well, no.
The AirPort icon in the menu bar was a blank quarter-pie. So I clicked on it, and saw the "open internet sharing" option. A panel appeared where I could turn airport on. I did. The grayed-out Network line of the pane then showed the name of the network I had created back in the Sharing dialog: "ABC wi-fi." And the signal level indicator shows full power, all to the right. All set? Nope! When I go to my Windows laptop and find this new network, I see two new options: One, strangely, is the "Computer Name" shown in the Sharing pref panel, and clicking on it to connect doesn't work. The other option is the network I actually named and shared, "ABC wi-fi," but when I attempt to connect to it, Windows (actually Intel PROSet/Wireless Wi-Fi Connection Utility) insists on stepping me through a series of complex security settings, when it would seem that no security should be required since I didn't enable encryption on the AirPort connection.
Giving up on those security settings, I go back to the Sharing control panel and turn sharing off. I hit the AirPort options button and turn encryption on I leave on WEP 40-bit, which requires me to type in a five character string. I do so. I click OK and restart internet sharing. Again, I am given confirmation of "Internet sharing on: sharing your built-in ethernet connection." I try to connect from Windows again, but am not even presented with the complex security options. It just says "Unable to connect," even though it can clearly see the SSID. I try the same a few more times--no luck. I go get an iPod touch and select the new G5-based network--type in the five characters required for WEP 40-bit, and jump right on. Why can't my Windows 7 laptop connect?

Good advice from rccharles, do try that, but I'm wondering if it might be related to Digitally sign communications, even though this talks about server & connecting the other way...
http://allinthehead.com/retro/218/accessing-a-windows-2003-share-from-os-x

Sharing Internet with Xbox 360 *DNS* -- Previous Posts Didn't Help!

I am running OSX 10.5.1
I want to share my laptop's wireless connection with my xbox via the ethernet port.
My router's IP address is: 192.168.1.1
My PowerBook's airport IP address is: 192.168.1.3
Under Sharing, I have set it to share my Airport with Ethernet.
*In the ethernet network panel of my PowerBook, my settings are:*
Configure: Manual
IP Address: 192.168.2.1
Subnet Masks: 255.255.255.0
Router: 192.168.1.1 (if this is left blank, the xbox can't correctly obtain an IP address, don't ask me why, and occasionally, it stops my laptop from getting internet... weird)
DNS Server: BLANK
Search Domain: BLANK
*On my xbox, I have set it to:*
IP Settings: Manual
IP Address: 192.168.2.2
Subnet Mask: 255.255.255.0
Gateway: 192.168.2.1
DNS Settings: Manual
Primary DNS Server: 192.168.2.1
Secondary DNS Server: 192.168.2.1
it gets as far as obtaining an IP address, but it fails the DNS check!!!
I am at my wit's end!!!
What can I do!?!?!?! I have tried everything.

I'm not sure I can help troubleshoot your issue specifically, but I just went through the same process it sounds like you're trying to do and I found the following link to be very helpful:
http://www.xbox360forum.com/forum/showthread.php?t=20812&highlight=share+wireles s
2.0 GHz Macbook, 80 GB HD, 2 GB RAM Mac OS X (10.4.8)

Sharing Internet with Palm Tungsten T3 via Bluetooth - possible still?

Ok...I know I'm using legacy technology with the Palm Tungsten T3 and it seems that all discussions online that I've found are out of date. Even Missing Sync's Internet Sharing product is discontinued. But I'm running 10.5 on my MacBook Pro...so I would have thought that sharing via Bluetooth PAN would work.
But could be that Bluetooth PAN is something too new for the T3 to handle. So then am I back to using Terminal to run a separate PPP server for the T3? If that's the case...I guess I can try these instructions from 2003 and 2002:
http://www.bioneural.net/2003/10/12/mac-internet-on-palm-via-bluetooth/
http://hints.macworld.com/article.php?story=20021103062212288
Message was edited by: elvinc

Hello, and Welcome to the HP Support Community!
You'll most likely need an application called Softick PPP:
http://www.softick.com/ppp/
WyreNut
I am a Volunteer here, not employed by HP.
You too can become an HP Expert! Details HERE!
If my post has helped you, click the Kudos Thumbs up!
If it solved your issue, Click the "Accept as Solution" button so others can benefit from the question you asked!

Sharing Internet with others via AirPort Extreme

Hello!!
I really hope that someone can help me with this!
I have Air Port Extreme in my Mac Pro and I recently set it up so that my girlfriend who has a laptop PC can share my internet connection. My concern is now that anyone in our building can use my connection, right? I've heard something about passwords and things like that. Something about wep passord...
Can someone tell me how I get a password so that not anybody in our building can use our connection?
I really hope to get an answer on this one!!
Cheerz!!
Mac Pro Mac OS X (10.4.8) With built in Air Port Extreme

Plug the external hard drive into one of your stationary Macs. On that Mac go to System Preferences-> Sharing preference pane and enable File Sharing.
Now you should be able to access that drive from any of your other Macs.

Sharing Internet with another Mac via Bluetooth

I'm trying to help my wireless-less iMac G5 get online. It sits about two inches away from a MacBook Pro on my desk, which connects to the household wireless network via the in-built AirPort card. I'm hoping I can share that AirPort connection via Bluetooth.
Both systems are running Leopard, although the G5 is running a vanilla 10.5.0 install since I can't update without an Internet connection. The MacBook Pro is up-to-date and then some.
On the MacBook Pro, under System Preferences -> Bluetooth -> Advanced, I've checked "Share my Internet connection with other Bluetooth devices." Under Sharing, I've turned on Internet Sharing from AirPort to Bluetooth PAN. I've also paired the devices together.
I'm trying to connect from the iMac G5 to the MacBook Pro with "Connect to Network" in the Bluetooth menu. However, it's grayed out. If I do the same from the gear menu in System Preferences -> Bluetooth, nothing occurs.
This seems like a pretty complicated process for a technology that's meant to make networking child's play.

You're making life very complicated for yourself!
1) Bluetooth is far too slow for sharing an internet connection, unless you like accessing the internet at dial-up speeds or less.
2) As the computers are so close, just run an Ethernet or Firewire cable between the two to create a network, and share the internet connection over Ethernet or Firewire.
3) You can easily update the G5 to the latest Leopard by downloading the standalone updater on the internet connected Mac from the Apple web-site, then just copy the Update to the G5 via CD, DVD, USB Disk, Firewire Cable, Ethernet Cable, external hard disk etc...

Sharing internet with Macbook from an XP machine?

I know on OS X that I can easily turn on internet connection sharing, and take my XP laptop and connect to that Wifi network, but can anyone tell me how to do this the other way around?
In other words, how do I configure XP to share a connection with an OS X machine? I tried the XP ICS thing, but it apparently will only work with other XP machines.
I know this is a Mac forum, but not many PC people know how easy internet sharing over wifi is on a Mac

Lol I just figured it out...
http://www.microsoft.com/downloads/details.aspx?FamilyID=fac8708e-3762-4e78-b372 -8404eeb7f41a&DisplayLang=en

Sharing internet with PS2?

Is it possible to share my internet connection with my Playstation 2?
Ex: My mbp is connected to an airport. -> I want to enable internet sharing so I can hook an ethernet cable into my ps2 and the other end into my mbp.
Would this allow the PS2 to use the internet?

it should be able to, i don't see why not. you should give it a try cause i would think you would have no problems doing so. you have nothing to worry about cause doing this will not hurt anything. just turn connection sharing on (and if it has the option to use the ethernet port select that) then hook the PS2 up to the ethernet

Sharing Internet with iPhone

I am at a hotel and am connected to the internet through ethernet. I have paid for one week and shared this connection with my iPhone over wi-fi. This worked for a while, but now the iPhone can not get the router and DNS fields filled in and cannot access the internet. The Mac seems to do the same when trying to access the same network (The network i created on it through sharing). What could be the reason for this sudden change?

You may need to contact the carrier and make sure the feature is still on the account, otherwise....
Settings-->General-->Reset-->Reset Network Settings

Sharing internet with iPod touch

Now, what I have is a MacBook with OS 10.5.4 installed and my Internet connection is through cable modem and it's a Ethernet Connection and I want to share my Internet through Airport with my iPod Touch.
I have followed the instruction about "Sharing your Internet connection", but it is still not work.
In my iPod touch, I can see the IP Address 168.254.13.167 and the Subnet Mask 255.255.0.0 only. The Router and DNS is blank. Also when I open the safari with iPod touch, the error message " Safari can't open the page because it can't find the server" is shown. Why is that? Please help me and sorry for my english.

Try unplugging the cable modem, wait, and then plugging it in again.
-----> I tried, but it's still not work
Is this your system: cable modem -> Airport (expess? extreme?) ---- Macbook / iPod Touch?
------> For my system, cable modem -> Macbook (Airport extreme)
Is there another router in the picture? The 168.254.13.167 IP address doesn't look like an Apple IP. It should look like 10.XX.XX.XX.
-------> what do you mean of "in the picture"
Also the System Preferences>Network>AirPort, in the Status field, is said "the AirPort has a self-assigned IP address and may not be able to connect to the Internet. "
Message was edited by: thistle1020
Message was edited by: thistle1020

Sharing internet with 2 USB ethernet adapters?

Is it possible to connect the MBA via one USB Ethernet adapter to a LAN and share it with another USB adapter? Basically internet sharing from wired to wired.

...but the only way to know for sure...is to buy a 2nd USB Ethernet adapter which is a waste of money if it doesn't work
I didn't bring it up in the previous post, but since the discussion is going to continue...I would argue that getting a second USB wired ethernet adapter is a "waste of money." Why not get a router? OSX's Internet Sharing turns the Mac into a NAT device. This is the primary function of a typical home router. For about the same price as (or only a few dollars more than) the Apple USB ethernet adapter, you can get a router which will probably provide better throughput performance than Internet Sharing, especially if the machine you're sharing to is doing a heavy download, it likely slow down your machine even if you're not doing anything on the internet. (e.g.: Your Word Processing may will slow down if the other computer starts streaming Netflix.)
You can get small routers, if portability is needed and the 4-port wired switch is not essential. (i.e.: the Macbook has built-in wireless, as does most if not all portable computers.) I got one from D-Link that is the size of a deck of cards and runs off a USB port so no AC power is needed (although an AC adapter is included.) And of course Apple has the Airport Express.
To put it another way: you got a Macbook Air, which doesn't have any wired ethernet ports, but now you want two, and will use up all of your USB ports to do so. One could argue that you got the "wrong computer" for your needs. And even then, I would argue that a router is the "correct computer" to share one wired network connection.
Or can you make the defense and show significant negatives to using a router in your use case. And you have to go beyond price because a wired router is around $50 and often goes on sale for as low as $30, the same as the Apple USB ethernet adapter. And a wireless router is in the $70 range, with sale prices going down to $50. So I argue that a router is a better value.
(edit: for that matter, I forgot to ask, what kind of network connection are you trying to share? If it's like a university or other LAN where you can obtain more than one IP address, then you don't even need a router. A simple hub/switch will do, which I've seen on sale as low as $10, and free when people throw away their old junk. Hmmm, the price of the router could now be $0 if you have a friend that is upgrading their router to 802.11n. )

Sharing Internet with AirPort - Encryption doesn't work

Hi!
With my new iMac, I try to share my internet connection but I want it to be encrypted so my neighbors can't use it! I am using a 128-bit WEP encryption with a 13-character ASCII key. However, my Windows PC can't seem to connect to the network, while it can when the network is unencrypted. It can also manage it with other encrypted networks. I'm new to Macs, so maybe someone can tell me if I'm doing something wrong? If it's important, I have a D-Link Wireless 802.11 b/g 108 Mbits USB Adapter. Thanks in advance,
Mac_swede

This will not solve why you are having your problem, but, have you tried setting up the encrypted network on the Windows PC and then tried to join it from the imac? I am not sure, but you may also need to have sharing active to allow other compters onto your network. Also, as an afterthought, for further protection, we don't have our router broadcasting the network name. So in order to join, one must know both the name of the network and the encrypted password to get in. The last thing I can think of is that on my network setup (mac os X 10.3.9) there are more than one WEP encryption setting. You may need to use the one that is compatible with the Windows PC.
I am just shooting in the wind here, so take my words with a grain of salt.
Travelrn
ibook Mac OS X (10.3.9)

Problems sharing internet with iptables and dnsmasq

I followed this exactly: http://wiki.archlinux.org/index.php/Internet_Share
And here is my dnsmasq.conf
# Configuration file for dnsmasq.
# Format is one option per line, legal options are the same
# as the long options legal on the command line. See
# "/usr/sbin/dnsmasq --help" or "man 8 dnsmasq" for details.
# The following two options make you a better netizen, since they
# tell dnsmasq to filter out queries which the public DNS cannot
# answer, and which load the servers (especially the root servers)
# uneccessarily. If you have a dial-on-demand link they also stop
# these requests from bringing up the link uneccessarily.
# Never forward plain names (without a dot or domain part)
#domain-needed
# Never forward addresses in the non-routed address spaces.
#bogus-priv
# Uncomment this to filter useless windows-originated DNS requests
# which can trigger dial-on-demand links needlessly.
# Note that (amongst other things) this blocks all SRV requests,
# so don't use it if you use eg Kerberos, SIP, XMMP or Google-talk.
# This option only affects forwarding, SRV records originating for
# dnsmasq (via srv-host= lines) are not suppressed by it.
#filterwin2k
# Change this line if you want dns to get its upstream servers from
# somewhere other that /etc/resolv.conf
#resolv-file=
# By default, dnsmasq will send queries to any of the upstream
# servers it knows about and tries to favour servers to are known
# to be up. Uncommenting this forces dnsmasq to try each query
# with each server strictly in the order they appear in
# /etc/resolv.conf
#strict-order
# If you don't want dnsmasq to read /etc/resolv.conf or any other
# file, getting its servers from this file instead (see below), then
# uncomment this.
#no-resolv
# If you don't want dnsmasq to poll /etc/resolv.conf or other resolv
# files for changes and re-read them then uncomment this.
#no-poll
# Add other name servers here, with domain specs if they are for
# non-public domains.
#server=/localnet/192.168.0.1
# Example of routing PTR queries to nameservers: this will send all
# address->name queries for 192.168.3/24 to nameserver 10.1.2.3
#server=/3.168.192.in-addr.arpa/10.1.2.3
# Add local-only domains here, queries in these domains are answered
# from /etc/hosts or DHCP only.
#local=/localnet/
# Add domains which you want to force to an IP address here.
# The example below send any host in doubleclick.net to a local
# webserver.
#address=/doubleclick.net/127.0.0.1
# --address (and --server) work with IPv6 addresses too.
#address=/www.thekelleys.org.uk/fe80::20d:60ff:fe36:f83
# You can control how dnsmasq talks to a server: this forces
# queries to 10.1.2.3 to be routed via eth1
# --server=10.1.2.3@eth1
# and this sets the source (ie local) address used to talk to
# 10.1.2.3 to 192.168.1.1 port 55 (there must be a interface with that
# IP on the machine, obviously).
# [email protected]#55
# If you want dnsmasq to change uid and gid to something other
# than root, you will need to have CONFIG_SECURITY_CAPABILITIES
# enabled in your kernel. The default uid and gid of nobody will
# be used if capability is available and this is not set.
#user=
#group=
# If you want dnsmasq to listen for DHCP and DNS requests only on
# specified interfaces (and the loopback) give the name of the
# interface (eg eth0) here.
# Repeat the line for more than one interface.
interface=eth0
# Or you can specify which interface _not_ to listen on
#except-interface=
# Or which to listen on by address (remember to include 127.0.0.1 if
# you use this.)
#listen-address=
# If you want dnsmasq to provide only DNS service on an interface,
# configure it as shown above, and then use the following line to
# disable DHCP on it.
#no-dhcp-interface=
# On systems which support it, dnsmasq binds the wildcard address,
# even when it is listening on only some interfaces. It then discards
# requests that it shouldn't reply to. This has the advantage of
# working even when interfaces come and go and change address. If you
# want dnsmasq to really bind only the interfaces it is listening on,
# uncomment this option. About the only time you may need this is when
# running another nameserver on the same machine.
bind-interfaces
# If you don't want dnsmasq to read /etc/hosts, uncomment the
# following line.
#no-hosts
# or if you want it to read another file, as well as /etc/hosts, use
# this.
#addn-hosts=/etc/banner_add_hosts
# Set this (and domain: see below) if you want to have a domain
# automatically added to simple names in a hosts-file.
#expand-hosts
# Set the domain for dnsmasq. this is optional, but if it is set, it
# does the following things.
# 1) Allows DHCP hosts to have fully qualified domain names, as long
# as the domain part matches this setting.
# 2) Sets the "domain" DHCP option thereby potentially setting the
# domain of all systems configured by DHCP
# 3) Provides the domain part for "expand-hosts"
#domain=thekelleys.org.uk
# Set a different domain for a particular subnet
#domain=wireless.thekelleys.org.uk,192.168.2.0/24
# Same idea, but range rather then subnet
#domain=reserved.thekelleys.org.uk,192.68.3.100,192.168.3.200
# Uncomment this to enable the integrated DHCP server, you need
# to supply the range of addresses available for lease and optionally
# a lease time. If you have more than one network, you will need to
# repeat this for each network on which you want to supply DHCP
# service.
#dhcp-range=192.168.20.100,192.168.20.149,12h
# This is an example of a DHCP range where the netmask is given. This
# is needed for networks we reach the dnsmasq DHCP server via a relay
# agent. If you don't know what a DHCP relay agent is, you probably
# don't need to worry about this.
dhcp-range=192.168.20.100,192.168.20.149,255.255.255.0,12h
# This is an example of a DHCP range with a network-id, so that
# some DHCP options may be set only for this network.
#dhcp-range=red,192.168.0.50,192.168.0.150
# Supply parameters for specified hosts using DHCP. There are lots
# of valid alternatives, so we will give examples of each. Note that
# IP addresses DO NOT have to be in the range given above, they just
# need to be on the same network. The order of the parameters in these
# do not matter, it's permissble to give name,adddress and MAC in any order
# Always allocate the host with ethernet address 11:22:33:44:55:66
# The IP address 192.168.0.60
dhcp-host=00:E0:B8:9C:B7:2C,192.168.20.1
# Always set the name of the host with hardware address
# 11:22:33:44:55:66 to be "fred"
#dhcp-host=11:22:33:44:55:66,fred
# Always give the host with ethernet address 11:22:33:44:55:66
# the name fred and IP address 192.168.0.60 and lease time 45 minutes
#dhcp-host=11:22:33:44:55:66,fred,192.168.0.60,45m
# Give a host with ethernet address 11:22:33:44:55:66 or
# 12:34:56:78:90:12 the IP address 192.168.0.60. Dnsmasq will assume
# that these two ethernet interfaces will never be in use at the same
# time, and give the IP address to the second, even if it is already
# in use by the first. Useful for laptops with wired and wireless
# addresses.
#dhcp-host=11:22:33:44:55:66,12:34:56:78:90:12,192.168.0.60
# Give the machine which says its name is "bert" IP address
# 192.168.0.70 and an infinite lease
#dhcp-host=bert,192.168.0.70,infinite
# Always give the host with client identifier 01:02:02:04
# the IP address 192.168.0.60
#dhcp-host=id:01:02:02:04,192.168.0.60
# Always give the host with client identifier "marjorie"
# the IP address 192.168.0.60
#dhcp-host=id:marjorie,192.168.0.60
# Enable the address given for "judge" in /etc/hosts
# to be given to a machine presenting the name "judge" when
# it asks for a DHCP lease.
#dhcp-host=judge
# Never offer DHCP service to a machine whose ethernet
# address is 11:22:33:44:55:66
#dhcp-host=11:22:33:44:55:66,ignore
# Ignore any client-id presented by the machine with ethernet
# address 11:22:33:44:55:66. This is useful to prevent a machine
# being treated differently when running under different OS's or
# between PXE boot and OS boot.
#dhcp-host=11:22:33:44:55:66,id:*
# Send extra options which are tagged as "red" to
# the machine with ethernet address 11:22:33:44:55:66
#dhcp-host=11:22:33:44:55:66,net:red
# Send extra options which are tagged as "red" to
# any machine with ethernet address starting 11:22:33:
#dhcp-host=11:22:33:*:*:*,net:red
# Ignore any clients which are specified in dhcp-host lines
# or /etc/ethers. Equivalent to ISC "deny unkown-clients".
# This relies on the special "known" tag which is set when
# a host is matched.
#dhcp-ignore=#known
# Send extra options which are tagged as "red" to any machine whose
# DHCP vendorclass string includes the substring "Linux"
#dhcp-vendorclass=red,Linux
# Send extra options which are tagged as "red" to any machine one
# of whose DHCP userclass strings includes the substring "accounts"
#dhcp-userclass=red,accounts
# Send extra options which are tagged as "red" to any machine whose
# MAC address matches the pattern.
#dhcp-mac=red,00:60:8C:*:*:*
# If this line is uncommented, dnsmasq will read /etc/ethers and act
# on the ethernet-address/IP pairs found there just as if they had
# been given as --dhcp-host options. Useful if you keep
# MAC-address/host mappings there for other purposes.
#read-ethers
# Send options to hosts which ask for a DHCP lease.
# See RFC 2132 for details of available options.
# Common options can be given to dnsmasq by name:
# run "dnsmasq --help dhcp" to get a list.
# Note that all the common settings, such as netmask and
# broadcast address, DNS server and default route, are given
# sane defaults by dnsmasq. You very likely will not need
# any dhcp-options. If you use Windows clients and Samba, there
# are some options which are recommended, they are detailed at the
# end of this section.
# Override the default route supplied by dnsmasq, which assumes the
# router is the same machine as the one running dnsmasq.
#dhcp-option=3,1.2.3.4
# Do the same thing, but using the option name
#dhcp-option=option:router,1.2.3.4
# Override the default route supplied by dnsmasq and send no default
# route at all. Note that this only works for the options sent by
# default (1, 3, 6, 12, 28) the same line will send a zero-length option
# for all other option numbers.
#dhcp-option=3
# Set the NTP time server addresses to 192.168.0.4 and 10.10.0.5
#dhcp-option=option:ntp-server,192.168.0.4,10.10.0.5
# Set the NTP time server address to be the same machine as
# is running dnsmasq
#dhcp-option=42,0.0.0.0
# Set the NIS domain name to "welly"
#dhcp-option=40,welly
# Set the default time-to-live to 50
#dhcp-option=23,50
# Set the "all subnets are local" flag
#dhcp-option=27,1
# Send the etherboot magic flag and then etherboot options (a string).
#dhcp-option=128,e4:45:74:68:00:00
#dhcp-option=129,NIC=eepro100
# Specify an option which will only be sent to the "red" network
# (see dhcp-range for the declaration of the "red" network)
# Note that the net: part must precede the option: part.
#dhcp-option = net:red, option:ntp-server, 192.168.1.1
# The following DHCP options set up dnsmasq in the same way as is specified
# for the ISC dhcpcd in
# http://www.samba.org/samba/ftp/docs/textdocs/DHCP-Server-Configuration.txt
# adapted for a typical dnsmasq installation where the host running
# dnsmasq is also the host running samba.
# you may want to uncomment some or all of them if you use
# Windows clients and Samba.
#dhcp-option=19,0 # option ip-forwarding off
#dhcp-option=44,0.0.0.0 # set netbios-over-TCP/IP nameserver(s) aka WINS server(s)
#dhcp-option=45,0.0.0.0 # netbios datagram distribution server
#dhcp-option=46,8 # netbios node type
# Send RFC-3397 DNS domain search DHCP option. WARNING: Your DHCP client
# probably doesn't support this......
#dhcp-option=option:domain-search,eng.apple.com,marketing.apple.com
# Send RFC-3442 classless static routes (note the netmask encoding)
#dhcp-option=121,192.168.1.0/24,1.2.3.4,10.0.0.0/8,5.6.7.8
# Send vendor-class specific options encapsulated in DHCP option 43.
# The meaning of the options is defined by the vendor-class so
# options are sent only when the client supplied vendor class
# matches the class given here. (A substring match is OK, so "MSFT"
# matches "MSFT" and "MSFT 5.0"). This example sets the
# mtftp address to 0.0.0.0 for PXEClients.
#dhcp-option=vendor:PXEClient,1,0.0.0.0
# Send microsoft-specific option to tell windows to release the DHCP lease
# when it shuts down. Note the "i" flag, to tell dnsmasq to send the
# value as a four-byte integer - that's what microsoft wants. See
# http://technet2.microsoft.com/WindowsServer/en/library/a70f1bb7-d2d4-49f0-96d6-4b7414ecfaae1033.mspx?mfr=true
#dhcp-option=vendor:MSFT,2,1i
# Send the Encapsulated-vendor-class ID needed by some configurations of
# Etherboot to allow is to recognise the DHCP server.
#dhcp-option=vendor:Etherboot,60,"Etherboot"
# Send options to PXELinux. Note that we need to send the options even
# though they don't appear in the parameter request list, so we need
# to use dhcp-option-force here.
# See http://syslinux.zytor.com/pxe.php#special for details.
# Magic number - needed before anything else is recognised
#dhcp-option-force=208,f1:00:74:7e
# Configuration file name
#dhcp-option-force=209,configs/common
# Path prefix
#dhcp-option-force=210,/tftpboot/pxelinux/files/
# Reboot time. (Note 'i' to send 32-bit value)
#dhcp-option-force=211,30i
# Set the boot filename for netboot/PXE. You will only need
# this is you want to boot machines over the network and you will need
# a TFTP server; either dnsmasq's built in TFTP server or an
# external one. (See below for how to enable the TFTP server.)
#dhcp-boot=pxelinux.0
# Boot for Etherboot gPXE. The idea is to send two different
# filenames, the first loads gPXE, and the second tells gPXE what to
# load. The dhcp-match sets the gpxe tag for requests from gPXE.
#dhcp-match=gpxe,175 # gPXE sends a 175 option.
#dhcp-boot=net:#gpxe,undionly.kpxe
#dhcp-boot=mybootimage
# Encapsulated options for Etherboot gPXE. All the options are
# encapsulated within option 175
#dhcp-option=encap:175, 1, 5b # priority code
#dhcp-option=encap:175, 176, 1b # no-proxydhcp
#dhcp-option=encap:175, 177, string # bus-id
#dhcp-option=encap:175, 189, 1b # BIOS drive code
#dhcp-option=encap:175, 190, user # iSCSI username
#dhcp-option=encap:175, 191, pass # iSCSI password
# Test for the architecture of a netboot client. PXE clients are
# supposed to send their architecture as option 93. (See RFC 4578)
#dhcp-match=peecees, option:client-arch, 0 #x86-32
#dhcp-match=itanics, option:client-arch, 2 #IA64
#dhcp-match=hammers, option:client-arch, 6 #x86-64
#dhcp-match=mactels, option:client-arch, 7 #EFI x86-64
# Do real PXE, rather than just booting a single file, this is an
# alternative to dhcp-boot.
#pxe-prompt="What system shall I netboot?"
# or with timeout before first available action is taken:
#pxe-prompt="Press F8 for menu.", 60
# Available boot services. for PXE.
#pxe-service=x86PC, "Boot from local disk", 0
# Loads <tftp-root>/pxelinux.0 from dnsmasq TFTP server.
#pxe-service=x86PC, "Install Linux", pxelinux
# Loads <tftp-root>/pxelinux.0 from TFTP server at 1.2.3.4.
# Beware this fails on old PXE ROMS.
#pxe-service=x86PC, "Install Linux", pxelinux, 1.2.3.4
# Use bootserver on network, found my multicast or broadcast.
#pxe-service=x86PC, "Install windows from RIS server", 1
# Use bootserver at a known IP address.
#pxe-service=x86PC, "Install windows from RIS server", 1, 1.2.3.4
# If you have multicast-FTP available,
# information for that can be passed in a similar way using options 1
# to 5. See page 19 of
# http://download.intel.com/design/archives/wfm/downloads/pxespec.pdf
# Enable dnsmasq's built-in TFTP server
#enable-tftp
# Set the root directory for files availble via FTP.
#tftp-root=/var/ftpd
# Make the TFTP server more secure: with this set, only files owned by
# the user dnsmasq is running as will be send over the net.
#tftp-secure
# Set the boot file name only when the "red" tag is set.
#dhcp-boot=net:red,pxelinux.red-net
# An example of dhcp-boot with an external TFTP server: the name and IP
# address of the server are given after the filename.
# Can fail with old PXE ROMS. Overridden by --pxe-service.
#dhcp-boot=/var/ftpd/pxelinux.0,boothost,192.168.0.3
# Set the limit on DHCP leases, the default is 150
#dhcp-lease-max=150
# The DHCP server needs somewhere on disk to keep its lease database.
# This defaults to a sane location, but if you want to change it, use
# the line below.
#dhcp-leasefile=/var/lib/misc/dnsmasq.leases
# Set the DHCP server to authoritative mode. In this mode it will barge in
# and take over the lease for any client which broadcasts on the network,
# whether it has a record of the lease or not. This avoids long timeouts
# when a machine wakes up on a new network. DO NOT enable this if there's
# the slighest chance that you might end up accidentally configuring a DHCP
# server for your campus/company accidentally. The ISC server uses
# the same option, and this URL provides more information:
# http://www.isc.org/index.pl?/sw/dhcp/authoritative.php
#dhcp-authoritative
# Run an executable when a DHCP lease is created or destroyed.
# The arguments sent to the script are "add" or "del",
# then the MAC address, the IP address and finally the hostname
# if there is one.
#dhcp-script=/bin/echo
# Set the cachesize here.
#cache-size=150
# If you want to disable negative caching, uncomment this.
#no-negcache
# Normally responses which come form /etc/hosts and the DHCP lease
# file have Time-To-Live set as zero, which conventionally means
# do not cache further. If you are happy to trade lower load on the
# server for potentially stale date, you can set a time-to-live (in
# seconds) here.
#local-ttl=
# If you want dnsmasq to detect attempts by Verisign to send queries
# to unregistered .com and .net hosts to its sitefinder service and
# have dnsmasq instead return the correct NXDOMAIN response, uncomment
# this line. You can add similar lines to do the same for other
# registries which have implemented wildcard A records.
#bogus-nxdomain=64.94.110.11
# If you want to fix up DNS results from upstream servers, use the
# alias option. This only works for IPv4.
# This alias makes a result of 1.2.3.4 appear as 5.6.7.8
#alias=1.2.3.4,5.6.7.8
# and this maps 1.2.3.x to 5.6.7.x
#alias=1.2.3.0,5.6.7.0,255.255.255.0
# and this maps 192.168.0.10->192.168.0.40 to 10.0.0.10->10.0.0.40
#alias=192.168.0.10-192.168.0.40,10.0.0.0,255.255.255.0
# Change these lines if you want dnsmasq to serve MX records.
# Return an MX record named "maildomain.com" with target
# servermachine.com and preference 50
#mx-host=maildomain.com,servermachine.com,50
# Set the default target for MX records created using the localmx option.
#mx-target=servermachine.com
# Return an MX record pointing to the mx-target for all local
# machines.
#localmx
# Return an MX record pointing to itself for all local machines.
#selfmx
# Change the following lines if you want dnsmasq to serve SRV
# records. These are useful if you want to serve ldap requests for
# Active Directory and other windows-originated DNS requests.
# See RFC 2782.
# You may add multiple srv-host lines.
# The fields are <name>,<target>,<port>,<priority>,<weight>
# If the domain part if missing from the name (so that is just has the
# service and protocol sections) then the domain given by the domain=
# config option is used. (Note that expand-hosts does not need to be
# set for this to work.)
# A SRV record sending LDAP for the example.com domain to
# ldapserver.example.com port 289
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389
# A SRV record sending LDAP for the example.com domain to
# ldapserver.example.com port 289 (using domain=)
#domain=example.com
#srv-host=_ldap._tcp,ldapserver.example.com,389
# Two SRV records for LDAP, each with different priorities
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,1
#srv-host=_ldap._tcp.example.com,ldapserver.example.com,389,2
# A SRV record indicating that there is no LDAP server for the domain
# example.com
#srv-host=_ldap._tcp.example.com
# The following line shows how to make dnsmasq serve an arbitrary PTR
# record. This is useful for DNS-SD. (Note that the
# domain-name expansion done for SRV records _does_not
# occur for PTR records.)
#ptr-record=_http._tcp.dns-sd-services,"New Employee Page._http._tcp.dns-sd-services"
# Change the following lines to enable dnsmasq to serve TXT records.
# These are used for things like SPF and zeroconf. (Note that the
# domain-name expansion done for SRV records _does_not
# occur for TXT records.)
#Example SPF.
#txt-record=example.com,"v=spf1 a -all"
#Example zeroconf
#txt-record=_http._tcp.example.com,name=value,paper=A4
# Provide an alias for a "local" DNS name. Note that this _only_ works
# for targets which are names from DHCP or /etc/hosts. Give host
# "bert" another name, bertrand
#cname=bertand,bert
# For debugging purposes, log each DNS query as it passes through
# dnsmasq.
#log-queries
# Log lots of extra information about DHCP transactions.
#log-dhcp
# Include a another lot of configuration options.
#conf-file=/etc/dnsmasq.more.conf
#conf-dir=/etc/dnsmasq.d
eth0 is set up for 192.168.20.1, netmask 255.255.255.0. I can get an IP from my client machine and ping 192.168.20.1, but cannot access the internet. resolv.conf on the client machine has a nameserver of 192.168.20.1. Also, Firefox time sout trying to access Google via it's static IP.
What should I do to grant the internet to my client machine?

http://wiki.archlinux.org/index.php/DNS_with_bind -> Did you try it too ?

Issue Sharing Internet with a PC

Similar Messages

Maybe you are looking for