On Monday, January 22, 2007 @ 8:50 PM, John Andersen wrote:

On Monday 22 January 2007 17:32, Greg Wallace wrote:

...

I just purchased a Belkin 4 port router and the built-in firewall in it is leaking like a sieve (constantly getting intrusions). I had always used Linksys, but they just don't seem to last very long in my experience. So, I'm looking for alternatives. I like IOGEAR equipment, but they don't make wired routers and I'd just as soon not go wireless right now (personal choice). In doing some browsing, I found out that Netgear and D-Link both make wired routers. Anyone had experience with either of these? Anyone have another alternative brand to recommend?

I've used Netgear and found them quite satisfactory.

I've used both their wired and wireless.

_____________________________________ John Andersen -- Well John, I went down to Fry's today and bought a Netgear 4 port router. I

<snip> tried to set it up and it couldn't even connect to my ISP, which is cable modem and assigns ip addresses automatically (so how could it fail to get the address?). So, I plugged my leaky Belkin router back in and was up and running again immediately. I guess I'll try a D-Link router next. Greg Wallace -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Kenneth Schneider wrote:

On Tue, 2007-01-23 at 15:41 -0600, Greg Wallace wrote:

...

On Monday, January 22, 2007 @ 8:50 PM, John Andersen wrote:

Snip

...

...

--

Well John, I went down to Fry's today and bought a Netgear 4 port router. I tried to set it up and it couldn't even connect to my ISP, which is cable modem and assigns ip addresses automatically (so how could it fail to get the address?). So, I plugged my leaky Belkin router back in and was up and running again immediately. I guess I'll try a D-Link router next.

Make sure they allow a mac address change.

Before you returned your router, did you make sure that it did not try to use ppoe to make the connection and not configured with just plaing DHCP? -- Joseph Loo jloo@acm.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

* Greg Wallace [01-23-07 17:19]:

Well John, I went down to Fry's today and bought a Netgear 4 port router. I tried to set it up and it couldn't even connect to my ISP, which is cable modem and assigns ip addresses automatically (so how could it fail to get the address?). So, I plugged my leaky Belkin router back in and was up and running again immediately. I guess I'll try a D-Link router next.

???? I have three in service locally and have installed over a dozen in the past year w/o any problems. It comes with *written* instructions. I know that they are for windoz but .... -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday, January 23, 2007 @ 4:22 PM, Jim Cunning wrote:

On Tuesday 23 January 2007 13:41, Greg Wallace wrote: [...]

...

Well John, I went down to Fry's today and bought a Netgear 4 port router.

...

I tried to set it up and it couldn't even connect to my ISP, which is cable modem and assigns ip addresses automatically (so how could it fail to get the address?). So, I plugged my leaky Belkin router back in and was up and running again immediately. I guess I'll try a D-Link router next.

Greg Wallace Greg,

Did you reset your cable modem? Most cable modems that I have seen learn the MAC address of the host/router connected to them and won't talk to another until the modem has been restarted.

Bingo. That was the problem. I unplugged my modem and plugged it back in and now everything is working fine.

One way to avoid this situation is to use the "Clone MAC Address" function many routers have, so they appear to have the MAC address of the/one LAN host connected to it. That way, the cable modem always see the same MAC address, regardless of the router actually attached to it.

I don't see that function in this particular router (Netgear RP614), but since I'll be using this router from now on (at least hopefully) I doubt I'll have that problem again.

Jim

Thanks!, Greg Wallace -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday, Jauary 23, 2007 @ 6:13 PM, Jim Cunning wrote:

On Tuesday 23 January 2007 15:19, Greg Wallace wrote:

...

On Tuesday, January 23, 2007 @ 4:22 PM, Jim Cunning wrote:

...

On Tuesday 23 January 2007 13:41, Greg Wallace wrote: [...] One way to avoid this situation is to use the "Clone MAC Address" function many routers have, so they appear to have the MAC address of the/one LAN host connected to it. That way, the cable modem always see the same MAC

address,

...

regardless of the router actually attached to it.

I don't see that function in this particular router (Netgear RP614), but since I'll be using this router from now on (at least hopefully) I doubt I'll have that problem again.

On page 2-16 of the Netgear RP614 v2 manual there is an illustration showing 3 choices: "Use Default MAC Address", "Use Computer MAC Address" and "Use This MAC Address" (with an entry box). The latter two choices are the clone equivalents I was referring to.

Jim

Ok. I found it. I picked "Use This Mac Address" which already had an address in it but was grayed out until I selected it. Is that the Mac Address of the modem, or of the router? Thanks, Greg Wallace -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 23 January 2007 17:07, Greg Wallace wrote:

...

Thanks, Greg Wallace

I've been doing some googling on this and I'm still a bit confused.  When you choose, for example, "Use This Mac Address", if that's not the mac address that the modem picked earlier (from, say, a different router) will it be accepted, or wouldn't you still have to re-boot the modem to get it to use that new address?  Or am I still not understanding this process?

First before you worry about this make sure your cable provider actually imposes a requirement to use a specific mac address. If they don't, and you never remember giving them a mac address before then just don't worry about it. If for some reason you must provide a mac address, turn over your old router and read the mac address off the bottom and key it in and select use THIS mac address, which means the netgear is to pretend its mac address was what you keyed in rather than what is burned in silicon inside. Really, this is very seldom necessary, unless you had a static IP or something. -- _____________________________________ John Andersen

On Tuesday 23 January 2007 21:18, Greg Wallace wrote:

I think my modem just grabs the Mac address off of the router when it's booted and connected to the router, so any of those 3 should work, meaning just leaving it as the default "Use Default Mac Address" is all I think I really needed, but maybe I'm still not understanding it correctly.  

Sounds like you are understanding it perfectly. Glad its working. Due to the nature of this list this thread will now proceed to wander off track for several days. ;-) -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

John Andersen wrote:

On Tuesday 23 January 2007 17:07, Greg Wallace wrote:

...

...

Thanks, Greg Wallace

I've been doing some googling on this and I'm still a bit confused. When you choose, for example, "Use This Mac Address", if that's not the mac address that the modem picked earlier (from, say, a different router) will it be accepted, or wouldn't you still have to re-boot the modem to get it to use that new address? Or am I still not understanding this process?

First before you worry about this make sure your cable provider actually imposes a requirement to use a specific mac address. If they don't, and you never remember giving them a mac address before then just don't worry about it.

If for some reason you must provide a mac address, turn over your old router and read the mac address off the bottom and key it in and select use THIS mac address, which means the netgear is to pretend its mac address was what you keyed in rather than what is burned in silicon inside.

Really, this is very seldom necessary, unless you had a static IP or something.

Many systems, including the one I'm on, will only work with one MAC. However, changing it only requires turning the modem off for a few minutes and then on again. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

At 11:47 AM 1/24/2007, Greg Wallace wrote:

On Wednesday, January 24, 2007 @ 6:20 AM, James Knott wrote:

<snip>

...

Many systems, including the one I'm on, will only work with one MAC. However, changing it only requires turning the modem off for a few minutes and then on again. Its more then likely the isp that requires the mac to hand out the ip address. That is the way it is here , with cox an now suddenlink who bought the cox system here in texas. When I first hooked up the cable modem I used the computer first before I had the router an I had to clone the computers nic mac address to the router so that It would work every time I changed to a new router. Been on the same netgear router for several years so not had to go thrue the mac address cloning / changing :) .

jack -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

* Greg Wallace [01-24-07 14:57]: [...]

I can hook up a new device to my modem with no problem, as long as I power cycle the modem first. Apparently, from some of the notes I'm reading, some ISPs lock you in to a single mac address, as you're describing. Not the case with my ISP or, apparently, with James Knott's.

To further obfuscate the situation, my roadrunner uses the modem's mac address. If I change modems, I have to landline roadrunner and report the new mac address from the modem. Changing routers requires nothing, not even rebooting the modem. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

* Greg Wallace [01-24-07 18:36]: [...]

Interesting. If you were using a modem like mine, would you have the worst of both worlds, or is your router somehow able to overcome the fact that the modem would normally only talk to a single router?

The modem has only one output, but that output can be attached to a switch and multiple routers from there and/or the routers daisy chained. I don't understand "modem would normally only talk to a single router?". -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

A

...

The modem has only one output, but that output can be attached to a switch and multiple routers from there and/or the routers daisy chained.

I don't understand "modem would normally only talk to a single router?".

I suspect cable modems do that, to prevent people from getting more IP addresses than they're paying for. I think that is the reasone that cox an now suddenlink does it here to keep you tied to the one or so ip's you are paying for. I too have to phone in the new mac off of a new modem when I changed them out. Have had to do that for few clients I installed new modems for. Have one client who has two modems at home an have to have both macs called in before they work.

jack -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wednesday 24 January 2007 08:47, Greg Wallace wrote:

Apparently, that's the way mine works.  I had turned the old router on and off a dozen times without re-booting the modem.  However, switching in the new router (with a new mac address) wouldn't work with out re-booting the modem.  I've been speculating as to why the modem needs to capture that mac address.

The other possibility is that the modem is really dumb about negotiation and the new router was different than the old in that respect. Most cable modems auto-negotiate not only between 10/100 and Half/Full duplex but also Crossover/Straight cabling. I've pulled cat five out of the back of a computer (which expects straight cabling) and plugged it into an uplink port of a router (which expects crossover) and had it fail exactly as you saw. A power reset on the cable modem fixed this. -- _____________________________________ John Andersen

Billie Erin Walsh wrote:

We have a wireless ISP. When we first got it set up it just wasn't as fast as it should be. One of his instructions was to clone the mac address. After that was done the service kicked butt. I'm not sure what it does but it made a huge difference in both the up and down speeds.

We did the same thing to the satellite router and made a big improvement there to [ but you still have the delay time from here to orbit and back down. ].

That simply doesn't make sense. The purpose of the MAC address is to enable devices to communicate over the local network and nothing more. Also, once you've passed through a router, the original MAC is replaced that of the router port you're going through. Cloning a MAC makes it easier to replace a device in a system that's configured to work with only one MAC, but that's all it does. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Billie Erin Walsh wrote:

James Knott wrote:

...

That simply doesn't make sense. The purpose of the MAC address is to enable devices to communicate over the local network and nothing more. Also, once you've passed through a router, the original MAC is replaced that of the router port you're going through. Cloning a MAC makes it easier to replace a device in a system that's configured to work with only one MAC, but that's all it does.

We "cloned the MAC address in the router", or at least that was the way it was explained. The owner of the ISP used to work for IBM somewhere in the tech end of things. We just followed his instructions. Other than that I have no idea what it does.

Well, I've been working with communications systems, computers and computer networks for almost 35 years ( I was working with computer networks before Ethernet was available and before the IBM PC was even though of), including a few years in tech support at IBM and it still doesn't make sense. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Billie Erin Walsh wrote:

...

James Knott wrote:

...

...

...

That simply doesn't make sense. The purpose of the MAC address is to enable devices to communicate over the local network and nothing more.

I'm just shooting in the dark here, but....................

When you "clone the MAC Address" what are you actually doing?

Our home network is connected to his network through a modem [ and a radio transceiver ]. Does the "cloning", for lack of better term, "sync" our network to his? If it does, wouldn't that give you a better [ faster ] connection?

As I said before, I don't know what it does, but it worked. We have told some other friends to do the same thing and it helped them also.

The reason for cloning the MAC is when you change hardware and the modem or cable network doesn't want to recognize the new MAC. Unless you're in such a situation, where other MACs are not recognized, there's no point in cloning. The sole purpose of the MAC, is to give the device an address on the local network, nothing more. Further, MACs are discarded and replaced with a new one at every router a packet passes through. This means that it's impossible for someone further down the internet to even know what your original MAC was, just by looking at your packets. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thu, 2007-01-25 at 12:36 -0600, Greg Wallace wrote:

On Thursday, January 25, 2007 @ 5:46 AM, Billie Erin Walsh wrote:

...

...

James Knott wrote:

...

...

...

That simply doesn't make sense. The purpose of the MAC address is to enable devices to communicate over the local network and nothing

more.

...

I'm just shooting in the dark here, but....................

...

When you "clone the MAC Address" what are you actually doing?

I thought I had all of this stuff figured out, but now I'm not so sure. However, that being said, I think that simply means you're taking the mac address of some other device and pretending to be that device. My router has place where I can select this option and, if I do, it opens up a box that has a mac address already in it, which I assume is the mac address of the router. If I wanted to, I could simply key in my computer's mac address and, in effect, pretend to be the computer. If your ISP has only authorized your computer's mac address, this would let the router step in between the computer and the ISP and the ISP wouldn't know the difference, since you have "cloned" the mac address of the computer, which is what the ISP (modem) is expecting. I probably have this all wrong, but I think that's the idea.

Actually you have it entirely correct. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thursday 25 January 2007 15:43, Billie Erin Walsh wrote:

...

Actually you have it entirely correct.

 

I asked a couple more questions. Tracie was the one actually talking to our ISP and doing the work. She said it was to clone the MAC address from the modem into the router. Something about improving communication between the two and sharing the bandwidth over the home network.

I suggest you speak to someone who might actually know something. She clearly doesn't. Its not her fault, she was looking for a job when they were looking for someone to answer the phone. Cloning a mac address is nothing more than taking the mac address from one of your machines, and pretending to be that machine when talking to the modem. This is fully explained in the manual. -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Thursday 25 January 2007 21:46, Anders Johansson wrote:

On Friday 26 January 2007 05:49, John Andersen wrote:

...

On Thursday 25 January 2007 15:43, Billie Erin Walsh wrote:

...

...

Actually you have it entirely correct.

 

I asked a couple more questions. Tracie was the one actually talking to our ISP and doing the work. She said it was to clone the MAC address from the modem into the router. Something about improving communication between the two and sharing the bandwidth over the home network.

I suggest you speak to someone who might actually know something.

Aren't you sort of missing the point that whatever was done, it did actually work.

He got it working BEFORE he talked to Tracie. Nothing she told him had any effect on the solution. Wrong is still wrong Anders. -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Friday 26 January 2007 08:51, John Andersen wrote:

On Thursday 25 January 2007 21:46, Anders Johansson wrote:

...

On Friday 26 January 2007 05:49, John Andersen wrote:

...

On Thursday 25 January 2007 15:43, Billie Erin Walsh wrote:

...

...

Actually you have it entirely correct.

 

I asked a couple more questions. Tracie was the one actually talking to our ISP and doing the work. She said it was to clone the MAC address from the modem into the router. Something about improving communication between the two and sharing the bandwidth over the home network.

I suggest you speak to someone who might actually know something.

Aren't you sort of missing the point that whatever was done, it did actually work.

He got it working BEFORE he talked to Tracie.

Um, what? Did you even read the thread?

Nothing she told him had any effect on the solution. Wrong is still wrong Anders.

Yes, and right is right. Please read the thread before you comment on it, you have clearly misunderstood everything that was said -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Friday 26 January 2007 13:27, James Knott wrote:

And aren't you missing that point that what was described is impossible? A MAC address has absolutely nothing to do with performance. Other than it systems that filter on MACs, it should make absolutely no difference what address is used.

Nevertheless, after following the advice given, the connection was faster. So the problem here is obviously not the advice given, but the recollection of it later. Now, is it really worth arguing over something that is already solved? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Friday 26 January 2007 18:56, James Knott wrote:

The problem is that someone will pass that on as a "fix". Next, people who don't know what they're doing will attempt to "fix" something and in the process, may create more problems. I have seen this sort of thing happen over the many years I have been providing support. It sometimes takes a fair bit of effort to show someone that what they "know" is in fact wrong. It's better to stop that sort of nonsense, than to allow it to continue. I can just imagine someone now calling their ISP, complaining that their service is still slow, even though they've changed the MAC. It happens!

Point taken. What I was really reacting to was comments like "I suggest you speak to someone who might actually know something", which - I still maintain - clearly missed the point of this whole thread, not to mention being fairly insulting to this person when we don't even know what was said (other than that it produced a good result) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Greg Wallace wrote:

On Thursday, January 25, 2007 @ 5:46 AM, Billie Erin Walsh wrote:

...

...

James Knott wrote:

...

...

...

That simply doesn't make sense. The purpose of the MAC address is to enable devices to communicate over the local network and nothing

more.

...

I'm just shooting in the dark here, but....................

...

When you "clone the MAC Address" what are you actually doing?

I thought I had all of this stuff figured out, but now I'm not so sure. However, that being said, I think that simply means you're taking the mac address of some other device and pretending to be that device.

That is exactly what you're doing, to avoid configuring the cable modem to recongize the new device. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday, January 23, 2007 @ 11:26 PM, Jim Cunning wrote:

On Tuesday 23 January 2007 18:07, Greg Wallace wrote: [...]

...

...

Ok. I found it. I picked "Use This Mac Address" which already had an address in it but was grayed out until I selected it. Is that the Mac Address of the modem, or of the router? I don't know. You might be able to tell by comparing that value with the MAC address displayed by 'ifconfig eth0' on your workstation (assuming you use eth0 to connect to your LAN and router. Choosing the "Default MAC Address" would definitely have used the router's MAC address on the WAN interface.

I think this means use the router's mac address.

...

...

Thanks, Greg Wallace

I've been doing some googling on this and I'm still a bit confused. When you choose, for example, "Use This Mac Address", if that's not the mac address that the modem picked earlier (from, say, a different router) will it be accepted, or wouldn't you still have to re-boot the modem to get it to use that new address? Probably the latter. Unless you have all routers that you might from time to time connect to your cable modem using the same MAC address on the WAN interface, you'll have to reset the modem on each change.

Right.

...

Or am I still not understanding this process? You're getting there. In your case, this is probably just a learning exercise

Yes. I learned a lot from this.

but not really necessary, since you were able to connect to your ISP after resetting the modem. This feature of most routers is essential, however, when an ISP requires that packets arriving at the cable modem be from some known (to them) MAC address, often one registered with them when signing up

for their service. This way it looks like the original computer NIC is still connected directly to the modem, even though there's a router between the two.

So that would be when you'd choose Use This Mac Address and key in the one provided by the ISP, right?

Jim Cunning

Greg Wallace -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Greg Wallace wrote:

On Monday, January 22, 2007 @ 8:50 PM, John Andersen wrote:

...

On Monday 22 January 2007 17:32, Greg Wallace wrote:

...

I just purchased a Belkin 4 port router and the built-in firewall in it

is

...

...

leaking like a sieve (constantly getting intrusions). I had always used Linksys, but they just don't seem to last very long in my experience.

So,

...

...

I'm looking for alternatives. I like IOGEAR equipment, but they don't

make

...

...

wired routers and I'd just as soon not go wireless right now (personal choice). In doing some browsing, I found out that Netgear and D-Link

both

...

...

make wired routers. Anyone had experience with either of these? Anyone have another alternative brand to recommend?

...

I've used Netgear and found them quite satisfactory.

...

I've used both their wired and wireless.

<snip>

...

_____________________________________ John Andersen --

Well John, I went down to Fry's today and bought a Netgear 4 port router. I tried to set it up and it couldn't even connect to my ISP, which is cable modem and assigns ip addresses automatically (so how could it fail to get the address?).

Did you remember to make the appropriate live sacrifices to the computer gods? ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday, January 23, 2007 @ 11:02 PM, John Anderson wrote:

On Tuesday 23 January 2007 12:41, Greg Wallace wrote:

...

Well John, I went down to Fry's today and bought a Netgear 4 port router. I tried to set it up and it couldn't even connect to my ISP, which is cable modem and assigns ip addresses automatically (so how could it fail to get the address?). So, I plugged my leaky Belkin router back in and was up and running again immediately. I guess I'll try a D-Link router next.

Are you SURE you plugged the WAN port into the cable modem? Did power cycle the router after plugging it in?

I submit that if Netgear couldn't even get an ip on a cable modem they would have long since gone out of business.

-- _____________________________________ John Andersen

I didn't power cycle the modem. It's working fine now. Greg W. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Monday, January 22, 2007 @ 9:02 PM, Felix Miata wrote:

On 2007/01/22 20:32 (GMT-0600) Greg Wallace apparently typed:\n

...

I just purchased a Belkin 4 port router and the built-in firewall in it is leaking like a sieve (constantly getting intrusions). I had always used

Did you try updating to the latest firmware?

Yes, even though it wasn't actually an upgrade (there have been no upgrades to the firmware on this router, so I just re-installed the one that came with the box).

...

Linksys, but they just don't seem to last very long in my experience. So,

DLink & Linksys around here come with 1 year warranties. Belkin comes with 5. Netgear comes with 3.

3 Years beats one year, so that's definitely a plus for Netgear over DLink.

...

I'm looking for alternatives. I like IOGEAR equipment, but they don't make wired routers and I'd just as soon not go wireless right now (personal choice). In doing some browsing, I found out that Netgear and D-Link both make wired routers. Anyone had experience with either of these? Anyone have another alternative brand to recommend?

"My" last router purchase was a Netgear wireless. "I" bought it by proxy about 2 weeks ago. My neighbor had been using W98 with Zone Alarm. It was heavily afflicted with the M$ popup disease. I sent him to the stores with cell phone in hand, and when he described the right one to me I said buy that one. It came with a normal wired router complement of 5 ports: 1 for the modem, and 4 for the rest of the wired network. The wireless component is disabled by default. The M$ installer, whatever it was installing, recommended an immediate firmware upgrade, which I did via one click to download, then opening the browser to open a connection to the unit to upload it.

The last 2 routers I actually bought are Netgear. I used the 4-port first about 2 years before buying the FVS318 with 8 ports to replace it. That happened nearly 2 years ago now. Or maybe it was 3 then 2. Anyway, the old is my backup in case a problem develops with the new.

Felix Miata *** http://mrmazda.no-ip.com/

John Anderson mentioned that active ftp wasn't supported on his Netgear. I really don't know the difference between the two. My assumption is that limitation wouldn't cause me any inconvenience. Thanks, Greg Wallace -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Monday 22 January 2007 21:07, Darryl Gregorash wrote:

On 2007-01-22 21:31, Greg Wallace wrote:

...

<snip>

John Anderson mentioned that active ftp wasn't supported on his Netgear. I really don't know the difference between the two. My assumption is that limitation wouldn't cause me any inconvenience.

http://slacksite.com/other/ftp.html

Some of my clients use Front Page. Earlier versions of Front Page only supported active ftp. (I have no clue if this is fixed or not in later versions). They were unable to publish their web sites using the built in Ftp engine in Front Page but were able to publish just fine when we removed the router and just used their Suse server as their router. Suse was faster too. The still use the netgear router as a wireless ap. -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 23 January 2007 04:48, Samir van de Sand wrote:

Well, if you are searching for a Wlan Router I would recommend the Linksys WRT54GL. It is an open source router and Linksys explicitly allows you to install third-party (like OpenWRT). A friend of mine has this router and he his very satisfied with it, even with the preinstalled firmware.

I'll throw out http://www.dd-wrt.com/wiki/index.php/What_is_"DD-WRT"%3F#v23_File_Versions also. Check the Features and Supported Devices. Their wiki gets better all the time with more information on price/performance, etc. You can even buy the gear from them to support the project. A dd-wrt'd router/firewall works much better than when you bought it. There are instructions for the Linksys WRT54G/S version 5,6 models with the reduced amounts of memory. They work well, I support several. Stan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday, January 23, 2007 @ 12:08 AM, Darryl Gregorash wrote:

On 2007-01-22 21:31, Greg Wallace wrote:

...

<snip>

John Anderson mentioned that active ftp wasn't supported on his Netgear. I really don't know the difference between the two. My assumption is that limitation wouldn't cause me any inconvenience.

http://slacksite.com/other/ftp.html

Excellent description. I just wonder how often you'd run into a site that didn't support passive ftp. In any even, not having active ftp capability would seem to be a small drawback, at least in my case. Greg Wallace -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 23 January 2007 10:11, Greg Wallace wrote:

...

On Tuesday, January 23, 2007 @ 12:08 AM, Darryl Gregorash wrote:

...

On 2007-01-22 21:31, Greg Wallace wrote:

...

<snip>

John Anderson mentioned that active ftp wasn't supported on his Netgear.

I

...

...

really don't know the difference between the two. My assumption is

...

...

...

limitation wouldn't cause me any inconvenience.

http://slacksite.com/other/ftp.html

Excellent description. I just wonder how often you'd run into a site

On Tuesday, January 23, 207 @ 1:27 PM, John Anderson wrote: that that

...

didn't support passive ftp. In any even, not having active ftp capability would seem to be a small drawback, at least in my case.

Greg Wallace

Actually I found the article very misleading, and in placed, just flat wrong.

In describing passive ftp it says: "The client will make both connections to the server, but one of them will be to a random high port, which would almost certainly be blocked by a firewall on the server side."

Random high ports? I think not.

Yeah, that does seem to be a misstatement in the article. In it's description of how passive ftp works, it says that the server notifies you which port to connect to, so it doesn't seem logical that it would tell you to connect to a port that is going to be firewalled.

The client will connect to a SPECIFIC port passed to it from the server, and upon which the server has started listening.

There is nothing random about it.

Right. In it's detailed description it makes this clear. It's just the summary section that seems to have it fouled up. <snip>

-- _____________________________________ John Andersen

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

The last 2 routers I actually bought are Netgear. I used the 4-port first about 2 years before buying the FVS318 with 8 ports to replace it. That happened nearly 2 years ago now. Or maybe it was 3 then 2. Anyway, the old is my backup in case a problem develops with the new. --

I vote for netgear also. been using them for years. I have the FVS318 at work an love it tooo. jack -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org