> [Warning: second question attached :-) ] > > Thanks for all the help and advice - sorry, I could have described the > I used to have a Linksys WRT54GX4, which was great until it stopped > working, and I had to spend hours on the phone with customer service > reps dumber than me, and the RMA replacement arrived DOA. The Linksys > had the ability to function as a switch (wrong word?) - that is, it > would pass traffic straight through to two machines on my internal > network, both of which had static, public IP addresses - one, the > server, connected via CAT5, and the other, a Windows laptop, connected > wirelessly. If your machines had static, PUBLIC > > Because of the customer-services & quality-control issues Linksys was > having, I tried switching to a Zyxel X-550 wireless router. > Unfortunately it does not seem to have the ability to cope properly with > public IP addresses on my internal network. > > So I thought that if it were an simple matter to configure my Linux > server in the way I've described, it would make the (temporary) process > of fiddling around with various bits of networking equipment easier. > > So, all that being said, do you have any technical recommendations? > Hope I have adequately described the problem... > > Thanks - > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
