Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] LAN, but no internet
- Date: Wed, 19 Jan 2011 15:41:30 +0900
- From: "Stephen J. Turnbull" <stephen@example.com>
- Subject: Re: [tlug] LAN, but no internet
- References: <4D357AD9.8090107@example.com> <AANLkTikWf2WMZFPHykP_+Gqg2jnLUk34Bv12w=dGnrEG@example.com> <4D35916B.9080209@example.com> <AANLkTimN2z-mJaKQtF6Rq+_exdOY1gSw7PX8neXtM7qT@example.com> <4D36518E.8000807@example.com> <4D366E61.9090002@example.com> <87fwsp78nx.fsf@example.com> <4D367F36.5060000@example.com>
Dave M G writes: > Something about how the wireless and wired networks are talking to > each other is still not clear. I think what you're missing is that in most cases routers function as gateways between logically different networks (which almost always are on separate wires[1]) and therefore are multihomed; that is, they have multiple addresses. Ie, the network looks like this, where global IPs are denoted by single-digit quads (eg, 1.1.1.1) and LAN (non-routable) IPs are denoted by Class C private IPs (eg, 192.168.1.1). Each address can be used only on the "wire" (including wireless channel) leading to it. (Strictly speaking, not quite true, but we can talk about that later if you care to.) THE INTERNET | +-------------+ | 1.1.1.1 | | ISP gateway | (far, far away) | 2.2.2.1 | +-------------+ | +-------------+ | 2.2.2.2 | | ISP modem | (in your closet) | 192.168.1.1 | +-------------+ | +-------------+ | 192.168.1.2 | | wireless | (sitting on a shelf) | 192.168.2.1 | +-------------+ | +-------------+ | 192.168.2.2 | | laptop | (on your desk) +-------------+ I don't think it is possible for a router to have the same IP address on two networks that are logically different. So you could set up "wireless" as transparent bridge with no address of its own (all packets are simply relayed to the appropriate interface), or you can set it up as a gateway, but then it must have two separate addresses: one facing the ISP's modem, and one facing the client host. It must be possible to distinguish the two logical networks by masking. Not necessarily by class, but all of the addresses on the laptop side of wireles must share a prefix of N bits for 0 < N < 32. There are some practical considerations that mean that N < 31 (ie, the smallest possible networks have 4 addresses, one of which is conventionally the network address (in practiced, simply wasted AFAIK), another is the broadcast address, leaving two host addresses. Re: your problem: try filling in the above diagram for your own network. Routers and gateways should have two IP addresses, workstations only need one. Once you've done that, you probably will be able to figure out for yourself what needs done next. If you become convinced that your wireless only has one address, you'll need to come back and ask, I suppose. Footnotes: [1] It's much easier to create a single logical network with multiple wires by bridging.
- Follow-Ups:
- Re: [tlug] LAN, but no internet
- From: Dave M G
- References:
- [tlug] Wireless router attached to a wired router
- From: Dave M G
- Re: [tlug] Wireless router attached to a wired router
- From: Marco Toldo
- Re: [tlug] Wireless router attached to a wired router
- From: Dave M G
- Re: [tlug] Wireless router attached to a wired router
- From: Hector Akamine
- [tlug] LAN, but no internet (was: Wireless router attached to a wired router)
- From: Dave M G
- Re: [tlug] LAN, but no internet
- From: Darren Cook
- Re: [tlug] LAN, but no internet
- From: Stephen J. Turnbull
- Re: [tlug] LAN, but no internet
- From: Dave M G
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] Slooooooow down: logs, smartctl, DNS? [NOT SOLVED?]
- Next by Date: Re: [tlug] LAN, but no internet
- Previous by thread: Re: [tlug] LAN, but no internet [SOLVED]: How to figure out stuff by searching
- Next by thread: Re: [tlug] LAN, but no internet
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links