Running Wireless and Wired eth connections at the same time

[John Summerfield]

sam wrote:
> so john...
> 
> in your case.. when the user uses google to find an answer.. what happens
> when the user gets conflicting information from different sites.

Then a sensible user might post to the question, outline what she's 
done, the conflicting information found, the results of trying out one 
or more of the pieces of advice.

Then, seeing that the user has made a decent effort, more (and more 
capable) people will respond, and not rehash the same ground.

> 
> you see, you never ask if the user has used google, or where they got their
> information, you simply assume that the user is asking without doing any
> initial research.

The onus is on the user. If you want good advice, make sure that you can 
filter out the nonsense, and there is quite a deal of that on any list, 
as people begin to help.

heck, i spout a bit myself sometimes, most recently not realising that 
while this fails:
   /bin/echo /*/*/*/*
this does not:
   echo /*/*/*/*

A lot of people here will try to answer your problem when they should be 
asking for more information.

> 
> in the case of this situation, the solution proposed is as i stated, freely
> used/provided on a number of sites..

It doesn't mean it's the right solution. Maquerading (more properly, 
Network Address Translation (NAT)) is good when you're connecting your 
SOHO LAN to the Internet and you want the LAN protected.

If you want to run servers of any kind on both sides to serve the other 
(and this would include Windows desktops sharing files), then NAT is 
wrong. Mostly, when people configure a router, the would like avery 
machine on each side to see all on the other.


-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu

Please do not reply off-list