Netgear R7000 Wireless AC router to wired LAN network

[Almighty1]

Greetings everyone:

I am basically trying to figure out how to get the following configuration working.

First I have a DSL Modem which acts as a bridge to the 75.x.x.x network, the LAN side is connected to a Cisco 10GiGE Catalyst managed switch on 100FDX Ethernet using CAT 6 cable.

The Cisco Catalyst 10GiGE managed switch routes both 75.x.x.x and 192.168.0.0/24 as I have the switch configured with the IP address of 192.168.0.100.

I then have a Netgear R7000 Wireless AC router which has a 75.x.x.x address on the WAN side and 192.168.2.1/24 on the LAN side with it handling 192.168.2.0/24 for wireless and wired clients on the LAN side of the router. I am currently using the XWRT port of ASUS-Merlin firmware for the R7000 and have used dd-wrt and OEM firmware in the past.

Now my question is, is there anyway I can get it working so 192.168.2.x clients can talk to 192.168.1.x/24. /24 just means the entire 0-255 or class C, netmask 255.255.255.0 for those who are not familiar with the terms.
It seems like one way to do it would be to give the Netgear R7000 a IP in 192.168.0.x/24 as a secondary IP on the WAN port but I am not sure how to do that exactly as I don't see a way to configure multiple IP addresses on either the LAN or WAN side. I have tried not doing anything and just physically connecting a CAT6 cable on the LAN side of the Netgear R7000 router to the Cisco 10GiGE Catalyst switch and basically what will happen is the Netgear R7000 will completely freeze up solid and the only way it will work again is the cable being disconnected. Thanks in advance for any suggestions!

 

[coxhaus]

A secondary IP address is not going to solve your problem. It will allow 2 networks on the same wire but it is not going to route between them for you.
As you know talking between networks will require a layer 3 device. You can setup the R7000 to route between networks but R7000 is not going to keep up with a 10GIG switch.This would be the same for the Netgear router. I am not sure the DSL modem can play. Is the switch running in layer 3 mode? Can you control your default gateway with policy routing or something?

A diagram would be nice?

 

[Almighty1]

Let's take the speed portion out of the question. My FreeBSD notebook is handling the routing between 192.168.0.0/24 and 192.168.1.0/24 which is also on the switch without problems since once you add the 192.168.0.2/24 ip to the WAN interface, it will add a route to 192.168.0.0 with the gateway of 192.168.0.2 and will route properly but the question is how is this done on the Wireless Router as on Windows, I have both 192.168.0.120 and 192.168.1.120 for the IP's on the same Intel 1Gbps NIC. The R7000 will be able to do 1GBps which is the common speed between all devices involved. The switch is layer 2 and layer 3 except I have it configured as 192.168.0.100 so at this point, I can only connect to it from something else that is in the 192.168.0.0/24 network and nothing else. The DSL Modem really has nothing to do with it other than it's the device in the 192.168.1.0/24 network as 192.168.1.254 which is what the Windows PC and FreeBSD box also has with 192.168.1.0/24 IP's, it was just included so you can see that the Wireless router is not directly connected to the WAN directly but rather, it goes through a switch. I do not have the FreeBSD box connected to the 192.168.2.0/24 network so that's why I cannot directly route between it, not to mention it's on a Intel 100Mbps NIC. Apologies but I'm not good at drawing diagrams.

 

[coxhaus]

It is very hard to follow without a diagram. If you want to talk between two class C networks it takes a layer 3 device. I assume your switch is not a layer 3 switch so you have a lot of horsepower going one direction. A 10 GIG NIC on FreeBSD or pfsense would solve it.
If you only want to route traffic between 2 Class C networks then create a common VLAN on the R7000 and the Netgear and route traffic with a static route on the routers. If you want to share internet across multiple WANs it is not going to happen with what you have told me.

 

[sfx2000]

It is very hard to follow without a diagram.

I agree - been following this chat...

Picture here is worth 10 posts at least... folks would like to help.

 

[Almighty1]

Not really that hard to follow since basically you just have to picture in the mind there are a few private LANs involved networks. The switch is layer 2 and layer 3. Basically, it's the R7000 that's the issue as I don't know how to assign more than one IP to the LAN port.

Port 1 of the switch is connected to the Westell B90-6100 DSL Router in bridge mode as my connectivity comes with 8 static IPs so this device does not have a IP assigned to it other than 192.168.1.254/24 which is the web interface for the DSL Router that is not user changeable.

Port 2 of the switch is connected to my Windows XP Pro SP3 Desktop on a ASUS P4C800E Motherboard with a built-in Intel Pro1000 NIC which has the public static IP of .208 on a /CIDR24 (I have .208-.215 with .1 going to the gateway which is on the other side of the public WAN), it also has the IPs of 192.168.0.120/24, 192.168.1.1.120/24, 192.168.2.120/24

Port 3 of the switch has my FreeBSD server which is a notebook with a built in 100Mbps Intel Pro100 NIC on the motherboard and PCMCIA slots so it will not take a connection faster than 100Mbps which also has the public static IP of .209/24 and secondary IPs of 192.168.0.1/24, 192.168.1.1/24 - this machine suffered a HDD crash a few years ago so it's technically offline, when it was running, it was serving as the outgoing gateway as it provided fair queue routing/traffic shaping for the other machines so for #2, it had the gateway set to .209 instead of .1, it's back to .1 because the machine is not working at the moment.

Port 4 of the switch is the Netgear R7000 which has .215 as the IP for the WAN side, and 192.168.2.1/24 for the LAN side. There are two cables, one going from the WAN to the switch and one going from the LAN side of the switch. Everything from mobile phones, tablets, Oppo BDP-105D BluRay Disc Player, Ring.com Doorbell, Ring.com Chime, LG 65EF9500 UltraHD 4K OLED TV, 2 Amazon Echo's, Roku 3 is connected wirelessly to the R7000 with the DISH Hopper connected via cable to the R7000. So basically what I want to do is assign another IP from 192.168.0.0/24 network such as 192.168.0.250/24 to the router and it will work since I am not using it to browse the web or even for fast transfers as the only thing it will be used for is to telnet/ssh to 192.168.0.100 being the Cisco Catalyst 6504-E Switch as right now, I can telnet/ssh to the switch from the machine on port #2 except that machine will not run any tftp server software for some reason which is needed to do software updates. Assuming the IP can be added, all that really needs to be done is adding a route for 192.168.0.0, netmask 255.255.255.0 to use 192.168.0.250 as the gateway on the R7000 which may or may not be needed because once you add the secondary IP to the LAN side of the R7000, everything on 192.168.0.0 netmask 255.255.255.0 will automatically use 19.2.168.0.250 for the gateway or interface by it's own as whether it's DD-WRT, Netgear OEM or XWRT ASUS-Merlin software, they are all Unix/Linux based and should all work the same.

I own and run a ISP but the wireless connections we provide uses static IPs and we don't use consumer routers as these are just NAT devices. All our WAN circuits that is 155Mbps OC-3 terminates directly into a card on the FreeBSD server just like the DSL circuits terminate there as well. I suck at drawing so drawing pictures isn't really going to get far as drawing unfortunately is not something I am good at.

 

[Almighty1]

Think I figured it out as both Cisco and HP ProCurve switches use the same commands as HP is trying to make easy converts for Cisco users at a lower price. I have both brands of switches here as these are all free evaluation units provided to me free that I can keep so it really just requires a secondary IP, not routing change is needed. The Netgear R7000, not sure what the secondary IP address would be called, I just rather do it on the Netgear R7000 because if the switch died or something and I use a non-managed switch, I would not be able to get things working.

All I did on the Cisco switch was added:
config t
vlan 1
ip address 192.168.1.100/24
ip address 192.168.2.100/24
exit
exit
wr mem

and the Cisco switch basically has the IP's:
192.168.0.100/24
192.168.1.100/24
192.168.2.100/24

On my PC which is connected to the Netgear R7000 and assigned the IP of 192.168.2.182/24, I had to add the following lines:
route add 192.168.0.0 mask 255.255.255.0 192.168.2.100
route add 192.168.1.0 mask 255.255.255.0 192.168.2.100

which produced the following results:
C:\WINDOWS\system32>ping -n 1 192.168.0.100

Pinging 192.168.0.100 with 32 bytes of data:
Reply from 192.168.0.100: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.100:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

C:\WINDOWS\system32>ping -n 1 192.168.1.100

Pinging 192.168.1.100 with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.100:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

C:\WINDOWS\system32>ping -n 1 192.168.2.100

Pinging 192.168.2.100 with 32 bytes of data:
Reply from 192.168.2.100: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.2.100:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms

Probably easier to do a static route on the R7000 for 192.168.0.0/24 and 192.168.1.0/24 to use 192.168.2.100 as the gateway.

How does one do VLAN on the R7000 using DD-WRT or the Netgear OEM firmware and how is it done on the ASUS RT68U/R as XWRT is basically the ASUS Merlin firmware ported.

 

[coxhaus]

If you have a 6504 layer 3 switch why not handle all the local processing in it. They are very fast. Your writing is still too hard to follow.
I don't know why you want to put a secondary IP address on a wireless device when there is no way it can handle DHCP for 2 networks. One broadcast domain per DHCP. DHCP is non directed traffic. It won't work. A secondary IP address is within one domain in your case. You can use multiple VLANs but not 2 IP addresses in one VLAN domain.

 

[Almighty1]

I think because I'm an Astrophysicist so I'm typing very fast. You have a good point about the local processing except remember I am doing only telnet/ssh sessions so it's not like I need it for anything else as it's about as fast as my typing goes.

I basically did the following after writing the above:
route delete 192.168.0.0
route delete 192.168.1.0

and then added the following static routes to the R7000:
192.168.0.0, netmask 255.255.255.0, gateway 192.168.2.210
192.168.1.0, netmask 255.255.255.0, gateway 192.168.2.210

although 192.168.0.0, netmask 255.255.254.0, gateway 192.168.2.210 would probably have saved a line.

Where did I say I wanted the R7000 to handle DHCP for 2 networks? I think that is where you are confused. Each network has it's own DHCP server.

192.168.0.0/24 has it's own DHCP server which is my FreeBSD machine as 192.168.0.1/24 when it's running. Besides, on the 192.168.0.0/24 network which is wired, I like assigning the IP's manually
as a static IP rather than use DHCP.
192.168.1.0/24 has it's own DHCP server as the Westell DSL Router B90-6100-60 as 192.168.1.254/24 if I change it from bridge to DHCP mode.
192.168.2.0/24 has it's own DHCP server as that is the R7000 router itself as 192.168.2.1/24 and it assigns 192.168.2.2-254 other than the hosts in the manual DHCP list.

All I wanted to do is give the R7000 secondary IP's in 192.168.0.0/24 and 192.168.1.0/24 as I can just point the gateway to any IP in 192.168.2.0/24 that can see 192.168.0.0 255.255.253.0.

You can use up to 8 IPs in a single VLAN without problems which is what I have already done and it works fine. In fact, if it was not a switch, you can put a few hundred IP's on one interface and there are no problems with that. I'm one of the FreeBSD contributors since 1993 so I know it's possible. Not sure where you get the idea that more than one IP address in a VLAN is not possible as it is in both Cisco and HP Procurve docs as on Cisco, it's basically:

interface vlan 1
ip address 192.168.0.1 255.255.255.0
ip address 192.168.1.1 255.255.255.0 secondary
ip address 192.168.2.1 255.255.255.0 secondary

and this already proves it works:

C:\WINDOWS\system32>ping  -n 1 192.168.0.100

Pinging 192.168.0.100 with 32 bytes of data:
Reply from 192.168.0.100: bytes=32 time=15ms TTL=64

Ping statistics for 192.168.0.100:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 15ms, Maximum = 15ms, Average = 15ms

C:\WINDOWS\system32>ping  -n 1 192.168.1.100

Pinging 192.168.1.100 with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time=61ms TTL=64

Ping statistics for 192.168.1.100:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 61ms, Maximum = 61ms, Average = 61ms

C:\WINDOWS\system32>ping  -n 1 192.168.2.100

Pinging 192.168.2.100 with 32 bytes of data:
Reply from 192.168.2.100: bytes=32 time=3ms TTL=64

Ping statistics for 192.168.2.100:
    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 3ms, Average = 3ms

C:\WINDOWS\system32>netstat -r
===========================================================================
Interface List
  8...14 da e9 ce 84 a6 ......Realtek PCIe GBE Family Controller
26...ac fd ce 76 e0 54 ......Microsoft Wi-Fi Direct Virtual Adapter
27...ae fd ce 76 e0 53 ......Microsoft Hosted Network Virtual Adapter
13...ac fd ce 76 e0 53 ......Intel(R) Dual Band Wireless-AC 7260
  3...00 ac 86 f7 d1 d9 ......VPN Client Adapter - VPN
19...00 ff ca 79 2d 5d ......TeamViewer VPN Adapter
12...ac fd ce 76 e0 57 ......Bluetooth Device (Personal Area Network)
  1...........................Software Loopback Interface 1
23...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.2.1    192.168.2.182     10
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      192.168.2.0    255.255.255.0         On-link     192.168.2.182    266
    192.168.2.182  255.255.255.255         On-link     192.168.2.182    266
    192.168.2.255  255.255.255.255         On-link     192.168.2.182    266
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link     192.168.2.182    266
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link     192.168.2.182    266
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination      Gateway
13    266 ::/0                     fe80::c604:15ff:fe44:db7d
  1    306 ::1/128                  On-link
23    306 2001::/32                On-link
23    306 2001:0:9d38:90d7:1004:51d:b49a:8428/128
                                    On-link
13    266 2602:244:b657:bd70::/64  On-link
13    266 2602:244:b657:bd70:ac04:9855:a2ed:79f6/128
                                    On-link
13    266 2602:244:b657:bd70:e0cd:f4bd:64b6:3a5a/128
                                    On-link
13    266 fe80::/64                On-link
23    306 fe80::/64                On-link
23    306 fe80::1004:51d:b49a:8428/128
                                    On-link
13    266 fe80::ac04:9855:a2ed:79f6/128
                                    On-link
  1    306 ff00::/8                 On-link
23    306 ff00::/8                 On-link
13    266 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None

If you noticed, 192.168.2.1 is the default route which is the R7000 router:

Besides, my question was not about DHCP but rather how to add a secondary IP on the R7000, and I was not asking about performance either so leave that out of the equation. You mentioned adding the IP to the VLAN on the R7000 but you never answered the question of how to do it on the R7000 but instead ignoring the question and then talking about something else. Remember I do not have any clients that is faster than either 867Mbps Wireless AC or 1GBbps ethernet. My objective is really to telnet/ssh to other nodes on the network that is not on the same /24 and once in a bluemoon when there are new firmware updates, transfer a locally hosted tftp server of a file that is 50MBytes in size. The other reason is because the Westell DSL Router has a Diagnostics Icon app that basically shows the stats of the Westell router based on the 192.168.1.254/24 IP. My main intention is not about speed but rather, trying to learn how to do things on the R7000 itself. This is a very small network where 99% of the time, the machines are routing via the WAN.

 

[coxhaus]

Secondary IP addresses have nothing in common with static routes. Why would you want a secondary IP address in one domain if you can't use it. Not being able to handle DHCP to me is considered not usable. Your writing is all over the place.

 

[Almighty1]

I never asked about static routes. Besides, whatever device has the secondary IPs in all the common networks in question would be able to act as the router to route traffic between the networks.

Read what you write in post #4 above, you said to create a VLAN on the R7000 but as of now, you still have not answered how to do it and ignoring the question. That is what I am asking as I know how to do the routing part since I am more familiar with real LANs that have routable IP addresses and non-routable addresses on a real router before all this SOHO routers came into the picture when WiFi became popular which is nothing more than NAT. I already have DHCP servers on each subnet so I don't need yet another one from the R7000. You value DHCP more because you have a dynamic IP for the WAN side while I have static IPs so DHCP to me is not usable to me since the only thing I need DHCP on are wireless devices. Everything else will just have assigned IP's instead as I like certain numbers for that device like 168 is good luck and always rich in chinese, 120 is my birthday, 144 is actually my alias what my business partners call me. My printer is 55 on the Wireless LAN because five sounds like fast in chinese. Like I said before, the menus on the firmware on XWRT, DD-WRT, and Netgear OEM firmware do not have anything even close to VLANs which was why I asked how it's done. My concentration is to do things on the R7000 or whatever Wi-Fi router unless these WiFi routers are really junk routers as I'm trying to learn how it's done on the WiFi NAT routers since the other things, I have learned to do in the early 1990s, a few years before Fred Van Kempen brought enhancements to the Linux networking code when there was still SLS and Slackware as far as Linux is concerned. You asked for diagrams and I have shown you screenshots, pages from the manual among other things for a visual illustration but as of now, you still have not answered what you said in post #4 on how to create a VLAN on the R7000 which is what I have been trying to get the answer to in all the former posts. I normally do WAN routing with BGP4 using ASN's so the LAN environment is not my specialty since we resell mostly dedicated connections either on a dedicated circuit or it goes on a PVC/DLCI using ATM and Frame Relay which includes ADSL connections.

 

[L&LD]

Almighty1, you should try to refrain from writing a wall of text.

 

[coxhaus]

I think your 6504 should do what you need as long as you have a route module for layer 3. I can't do the code off the top of my head anymore but we had 16 6509s. I have setup many 6509s. It can route all the VLANs you want. Feed one of them to the R7000 and one to the other router I can't remember what it was.

Without a picture I am lost. I think the 6504 is the answer now.
The more I think about it could your 6504 be 6505? It been a long time since I looked. Seems like supervisory engine took 1 slot.

 

[Almighty1]

Almighty1, you should try to refrain from writing a wall of text.

It's my style of writing and I don't have the time to get to the point in a short manner either as that takes time too. I'm already trying to read 8,000 emails a day + few hundred facebook notifications daily as I'm on a 5 year backlog too.

 

[Almighty1]

I think your 6504 should do what you need as long as you have a route module for layer 3. I can't do the code off the top of my head anymore but we had 16 6509s. I have setup many 6509s. It can route all the VLANs you want. Feed one of them to the R7000 and one to the other router I can't remember what it was.

Without a picture I am lost. I think the 6504 is the answer now.

Yes, that is one solution but I'm trying to learn how exactly the R7000 does VLANs as I haven't seen it in the menu. I know the original first WiFi router I had was a Netgear FWAG114 which was sold as a Wireless Firewall router that did have VPN but not VLAN either. Basically, what I'm trying to say is that I have never seen a WiFi router handle more than one subnet, the one it is DHCPing for. I like to eliminate the switch because I might run into a situation where someone has a regular switch like the Linksys, Netgear stuff out there and I wouldn't have the option to do the VLAN, etc like on a 6504 and remember these are cheap consumers which was why I was trying to find out how to do it on the WiFi router side because normally that's the only router available as they aren't going to go and buy Cisco or HP ProCurve switches when they are trying to be on the cheapest internet connection they can find. My network is on the LAN is really just a desktop and a notebook which is less than what most households have. Thanks for pointing out the VLAN part though. VLAN is also something I don't do much as our offices and NOC/hosting center is in Honolulu, HI and not anywhere physically I can reach. People just plug in machines on the switch there as the switch has only one IP and as long as I can access it remotely by telnet/ssh, that is all that matters since all the customers do not go past the FreeBSD server which handles all the WAN traffic with the high speed cards terminating circuits directly.

 

[coxhaus]

I have never used the R7000 but because it is a high-end router I assumed it did VLANs and multiple SSIDs. Maybe I have been using WAPs too long. The 650X will make a fantastic core layer 3 switch if you can afford the electricity. They are so fast. I also think if you stop and draw it out the answer may come to you. It is what I always did.

 

[Almighty1]

Ah, that explains it. I usually do things and remember things in my head instead of on paper and ofcourse before the web existed which is how people communicated even with Cisco Support so diagrams are not my thing as that is basically what people later used. I can't draw even if you paid me to do it. Yes, the electricity is expensive. I personally prefer Juniper routers over Cisco when it comes to the pre-made ones. There is a 4th DHCP server I forgot about, it's the one that is on the other end of my DSL connection which is a Redback SMS 1800 from what I was told, that one basically the .1 interface on the WAN side and sends the .208-.215 addresses via the DSL Modem and to the ports on the 650X since if I put the R7000 on DHCP which always happens when I factory reset the configuration when I change or update the firmware, I will always end up with a random IP in that .208-.215 which is the reason the FreeBSD machine never had the DHCP Server turned on because both the WAN DHCP server would be sending the .208-.215 and the FreeBSD machine would be sending the DHCP for 192.168.0.0/24 via the switches port and 192.168.1.0/24 is really just to communicate with the DSL modem's web interface and nothing else. What I said in the original post has slightly changed, it seems only dd-wrt and the original Netgear firmware when I first got the router would freeze if I connected a CAT6 cable between the switch and the LAN side of the R7000 which was why I was hoping to do it on the WAN side instead but since I wrote that original post, the CAT6 cable works without hanging the R7000 so it's more of doing the software configuration. It's not the drawing that is the problem since what I couldn't figure out was how to make the wired LAN see the LAN of the Wireless router as the only way they are physically connected was just from the WAN side and even now with the CAT6 cable, the default route basically says to use .1 of the WAN network so clearly by adding the 192.168.x.x addresses, it will see the other nodes on the same subnet except there doesn't seem to be a way to do this on the R7000 as this is really my 2nd wireless router in the last 16 years which was also a netgear. I suppose another way would have been to make the R7000 be part of the 192.168.0.0/24 network and just have a certain amount of IP addresses in that subnet DHCP'ed by the R7000 for the wireless clients. One would think the R7000 built in Gigabit Ethernet switch would be fast to deliver 1Gbps wire speed even though the WAN side unless it was using XWRT or Netgear OEM firmware would not be able to deliver full speed connections for anything 350Mbps and higher as it is missing the Cut Thru Forwarding (CTF) and Flow Acceleration which is something in software that the hardware manufacturer has to pay Broadcom for before it gives maximum throughput. In any case, thanks for your help about the VLAN as that was really something that was used after my time when I learned the Cisco CLI as Cisco did not even make switches yet until the 2924XL which was the first switch from Cisco I saw and used in the mid-1990s. I am sure what I want to do is probably on the CLI side of the router firmware except the routers are all based on Linux. I've been FreeBSD for the last 23 years and Linux is different in the networking department in the way things are done even though ifconfig is a common thing but the setup is still different.

 

[L&LD]

It's my style of writing and I don't have the time to get to the point in a short manner either as that takes time too. I'm already trying to read 8,000 emails a day + few hundred facebook notifications daily as I'm on a 5 year backlog too.

Just like you don't have time, others don't either. And as this is a support group that runs on a voluntary basis, you're alienating many that may otherwise help you.

Even using paragraphs helps in readability. A single 'paragraph' that covers a dozen points or so that takes 5 minutes to understand (if it is understood, even then) is getting you further behind too.

 

[Almighty1]

Just like you don't have time, others don't either. And as this is a support group that runs on a voluntary basis, you're alienating many that may otherwise help you.

Even using paragraphs helps in readability. A single 'paragraph' that covers a dozen points or so that takes 5 minutes to understand (if it is understood, even then) is getting you further behind too.

I'm providing support on many forums on a daily basis from computers to audio/video to others even when I don't have time. The point is if people don't want to help, then don't bother helping. A person's writing style is unique and when i write even on facebook comments, it's always like a book and that isn't going to change since I'm a rocket scientist, not a liberal arts major. Even though I'm a toastmaster, speaking and writing are two complete different things. My writing took a total of 3 minutes and I am reading as I type. Remember like you said, it's a voluntary support forum so those who choose to help do so on their free will. The reader can always draw their own diagram based on what I said which is explained in as much detail as one can get. If the reader still is lost, then there isn't much that can be done to remedy the situation. It is really a simple question since there was a reason I mentioned the Netgear R7000 as I want to do it on the Netgear R7000, not on the other devices in question which is more like a alternative solution as I already know that was possible. If I wanted to ask something with routers in general, I wouldn't be using snbforums for that purpose as I think of snbforums more of forums for the discussion of consumer grade Wireless Routers. For Cisco Routers, switches or basically anything commercial grade, there are specific forums elsewhere for that purpose.

 

[L&LD]

I'm providing support on many forums on a daily basis from computers to audio/video to others even when I don't have time. The point is if people don't want to help, then don't bother helping. A person's writing style is unique and when i write even on facebook comments, it's always like a book and that isn't going to change since I'm a rocket scientist, not a liberal arts major. Even though I'm a toastmaster, speaking and writing are two complete different things. My writing took a total of 3 minutes and I am reading as I type. Remember like you said, it's a voluntary support forum so those who choose to help do so on their free will. The reader can always draw their own diagram based on what I said which is explained in as much detail as one can get. If the reader still is lost, then there isn't much that can be done to remedy the situation. It is really a simple question since there was a reason I mentioned the Netgear R7000 as I want to do it on the Netgear R7000, not on the other devices in question which is more like a alternative solution as I already know that was possible. If I wanted to ask something with routers in general, I wouldn't be using snbforums for that purpose as I think of snbforums more of forums for the discussion of consumer grade Wireless Routers. For Cisco Routers, switches or basically anything commercial grade, there are specific forums elsewhere for that purpose.

Your first sentence makes no sense. Your statement about writing while reading may be why your posts are so contradictory (or at least seemingly so).

Just trying to help you get the answers you need. Helpful suggestions are all they are. But it is up to you to use them to your benefit.

Wish you well.