Static routes for vCenter 6

Because my provider, I need to make the static routes on type VM:

Auto eth0

iface eth0 inet static

address 8.8.8.8

subnet mask 255.255.255.255

disseminate 8.8.8.8

After courses add 5.5.5.1 dev eth0

post-up route add default gw 5.5.5.1

post-down route del 5.5.5.1 dev eth0

post-BAS route del default gw 5.5.5.1

How can I do it on vCenter Server Appliance?

SimWhite SimWhite,



VCenter server appliance is a Suse linux operating system, so if you add a static route, so that you can use a bash command perform this configuration, the link below show how to:




Route Linux add examples of commands



File/etc/sysconfig/network/road SUSE

Best regards

Joao Castro


Tags: VMware

Similar Questions

  • Static routing LRT214 does not

    Hello

    I have a hard time with a static routing on LRT214.

    My configuration:

    * LRT214 (recently purchased), acting as a gateway to the internet, local subnet is 192.168.28.0/24

    * There is a local VPN (192.168.28.98) server on the local network, serving a LAN tunnel with subnet 192.168.29.0/24. on LRT214 port forwarding is configured

    I can connect to my VPN server on the internet, and I can access the machine running on the VPN server (for example via ssh).

    However, I can not connect to any other computer on my LAN, although I tried

    adding another subnet under Configuration > network > LAN settings

    * setting up a static route under Setup > Advanced Routing (kind of route add - net 192.168.29.0/24 gw 192.168.28.98)

    of course, when I add the itinerary of statitc over any computer on the local network, I can connect via VPN tunnel to the machine, so its clearly a problem of LRT214.

    Please help, how can I configure a static route for this scenario in the user Web interface?

    The SPI Firewall, intercept traffic.

    As far as I understand, it could be that when the VPN server sends data to another machine on the local network, this happens on layer 2 (where the SPI Firewall not listening), while the return on the VPN server traffic is routed higher up in the stack, where the SPI listening and intercept.

    So, I will use the above workarounds, or put the OpenVPN server on a different subnet or VLAN, which I do anyway. I tried a basic configuration of VLAN yesterday (just put the Server full VPN with all interfaces in one VLAN separated), with InterVLAN routing enabled, but there seems to be some particularities with it (like the ping works, but not ssh). In any case, it's another story. Thanks for you support.

  • Add a static route to a RV042

    I have configured the RV042 dual WAN port for backup smart link connected to two different ISPS.  The subnet behind this is 192.168.2.xxx.  I have a second router linksys Garland with the 192.168.2.250 WAN port and subnet behind it is 192.168.20.xxx.  My problem is that I have a not able to route traffic fron 192.168.2.xxx to 192.168.20.xxx.  How can I add a static route so that clients on 192.168.2.xxx can access resources on 192.168.20.xxx?

    1. the second Linksys router must be changed of gateway (active NAT) in router mode (NAT disabled) mode. With NAT the LAN behind the second Linksys will be not accessible from the outside unless you configure port forwarding.

    2. on the RV042 set up a static route for the subnet 192.168.20.0/255.255.255.0 to the gateway IP address 1921.68.2.250 on the LAN interface.

    3. Ideally, you must configure the same static route on all clients connected to the RV042. If you don't want to do this, you must configure the firewall on all clients on the RV042 accept ICMP redirect messages. This is important because otherwise all traffic from 192.168.2. * to * 192.168.20 would be sent to the RV042 and from there to the second Linksys that is unnecessary and could create a bottleneck.

  • Static routing question

    I just took a WRT610N and configure a few static routes for my network.

    I have the router connected to a cable modem WAN and the interface of local network connected to my LAN via 192.168.0.1.

    I have three other LAN subnets in a test environment, they are:-

    172.16.0.0/24

    172.16.100.0/24

    172.16.200.0/24

    I tried to add the following to the first subnet:

    Destination = 172.16.0.0 LAN IP address

    Subnet mask = 255.255.255.0

    Gateway = 172.16.0.1

    Interface = LAN

    No matter what I try, I get a message saying route static invalid, and I can't get anything to stick.  Everyone can't see what I'm doing wrong?

    Thank you guys!

    Gary

    The IP address of the gateway in a static route is the IP address of the connected device directly on each side of the router, either on the ethernet LAN or WAN side.

    In particular you cannot route a subnet of an IP address of the gateway inside the target IP subnet. The static route example you deposited directions where to send traffic destined to 172.16.0.0/255.255.255.0. It is impossible to set the address of the gateway as 172.16.0.1 because the router doesn't know where to send the traffic to 172.16.0.1.

    In other words, the IP address of the gateway must in most cases be a 192.168.0. * IP address that you use these IP addresses in the local network of the WRT. The IP address of the gateway should be the IP address of the router on the subnet specific target within your local network.

    For example, if your second router with address 172.16.0.1/255.255.255.0 IP LAN has an IP 192.168.0.2, then the 192.168.0.2 is the IP address of the gateway for the static route to 172.16.0.0/255.255.255.0.

  • SG300-52. Prefer to send traffic to the default gateway rather than static route? Network stops if I disable ICMP redirects.

    I have 4 switches, each act as their own with a 26 subnet mask. They have static routes for every other switch. The firewall has a static route to each switch. If I unplug the LAN of the Firewall interface, traffic stops the flow of the switches. If I block the side LAN firewall, ICMP redirects, traffic stalls outside.

    So if you are connected to this switch, say that you pull an ip address of 192.168.122.20. Your front door is the 192.168.122.62 switch. If you try to access a server 192.168.127.142, the SG300 sends your traffic to 192.168.127.254 to get an ICMP redirect, rather than simply to communicate directly with 192.168.127.50.

    My network 'basic' is 192.168.127.0/24 vlan1 and the firewall is 192.168.127.254

    This is the route of one of my switches table (which has 192.168.122.0/26 and ports run on vlan122)

     Maximum Parallel Paths: 1 (1 after reset) IP Forwarding: enabled Codes: > - best, C - connected, S - static S 0.0.0.0/0 [1/1] via 192.168.127.254, 73:48:13, vlan 1 C 192.168.122.0/26 is directly connected, vlan 122 S 192.168.123.0/26 [1/1] via 192.168.127.123, 73:48:13, vlan 1 S 192.168.124.0/26 [1/1] via 192.168.127.124, 73:48:13, vlan 1 S 192.168.125.0/26 [1/1] via 192.168.127.125, 73:48:14, vlan 1 C 192.168.127.0/24 is directly connected, vlan 1 

    In any case, what gives? Why the switch would first try to send the stream to the firewall?

    EDIT: Here is the server routing table:

     [email protected]/* */:~$ ip route show default via 192.168.127.254 dev eth0 192.168.122.0/26 via 192.168.127.122 dev eth0 192.168.123.0/26 via 192.168.127.123 dev eth0 192.168.124.0/26 via 192.168.127.124 dev eth0 192.168.125.0/26 via 192.168.127.125 dev eth0 192.168.127.0/24 dev eth0 proto kernel scope link src 192.168.127.142 

    Hi Jonathan,.

    I'm sorry. I misunderstood the routing table you want to accomplish. Your concern seems relevant given that the matching rule more will be selected instead of one: page 275 http://www.cisco.com/c/dam/en/us/td/docs/switches/lan/csbms/sf30x_sg30x/...

    ... "When the routing of traffic, the next hop is decided based on the longest match on the prefix (LPM algorithm). A destination IPv4 address might match several routes in the IPv4 static routing Table. The device uses the matching route with the higher, subnet mask that is, the longest match on the prefix. "...

    So go ahead and report it to the support team so the guys can make the laboratory, confirm it and declare additional:

    http://www.Cisco.com/c/en/us/support/Web/TSD-Cisco-small-business-suppor...

    Kind regards

    Aleksandra

  • Explain SGE2000/P static routing (equal to L2 +)?

    L2 + mean?  I know these aren't L3 switches with IVR capabilities, then what is the purpose to configure static routes, if there is no functionality InterVLAN routing?

    T.I.A.,

    Chris

    Welcome to Cisco Community!

    With get them into a huge discussion, I will try to respond as quickly and directly as possible.

    Our EMS and EMS in the series switches are layer 3 switches (can also be configured as L2) so that they are able to operate as a (inter VLAN) router or gateway for all the VLANS. Once you have created the VLANS and assign an IP address, that IP address will become the GW for this VLAN. Under routing, you will not see any scholarly networks until what you assign the VLAN to a port and the port is enabled. You will then need to configure a default route to send traffic to the cloud. The router must belong to the same VLAN on the switch. So if the switch has an IP address of 172.16.30.1/24, the router will have an IP address of 172.16.30.254/24 for example. The road reads: next hop metric 172.16.30.254 0.0.0.0/0 2 (or higher).

    With respect to the static routes as a switch L2 or L3, that they would be useful when you have a device connected to another switch that is disjoint from your typical network of the local switch. In other words, let's say you have 3 (except default native VLAN 1) VLAN V10 - 30. Everything you devices belong to these VLANs, but you have a server on 30 VLAN that is not connected to this switch. You will then create a static route for the IP address of this server to the remote switch.

    VLAN30: 172.16.30.1 (local EMS)

    Server: 172.16.30.200 (on the remote switch)

    Remote switch: 192.168.20.1 (distance EMS)

    VLAN30: 172.16.30.2 (on the EMS distance)

    Static route:

    hop metric 172.16.30.2 next destination 172.16.30.200 2

    I hope that answers your question. These are really my favorite switches, because I find them very reliable and highly configurable. I love these things.

  • searching for NAT/Firewall/static routing tips

    Hello

    I am very new to vCloud network and security. I've read the documentation, but it can be confusing for me. I am attaching a schema to help provide a context for what I'm trying to achieve. Keep in mind that the IP address has been changed for security reasons. Address ranges are not accurate but for the context.

    We have an org routed with a single VM VAPP, directly connected to the VCC-Net. It is a Linux server. We have a vShield edge device. There is no rule of firewall, NAT, static routes configured. Essentially of deployment costs. The owner of the server wants to be able to connect to a Linux repo for updates/etc.

    For testing purposes, I have disabled the vShield firewall to allow all traffic through. from the Linux server, I was able to ping both addresses assigned to the border of vShield (192.168.1.1 and 10.10.16.17) but I couldn't ping 10.10.2.140. This leads me to believe the vShield Edge does not know how to route packets between 192.168.1.0/24 and 10.10.0.0/16.

    I have read and what I'm gathering is that I have to configure NAT and firewall rules to achieve. I googled everything I can, and now I'm just confused. Can someone please give me some advice?

    VShield Edge routing feature is similar to traditional router. By default, it can discover only directly attached networks and deliver packages, in this case 192.168.1.0/24 and 10.10.16.0/16 are direct networks. So if you need reach any other private network, we need to define a static route (it is not supported / configurable in vshield edges of dynamic routing since then). For Linux VM 192.168.1.10/24 join the public network, set a NAT NAT vShield edge rules and enable the appropriate firewall rules.

  • Next hop for the static route on the VPN site to site ASA?

    Hi all

    I would be grateful if someone could help me with my problem ASA/misunderstanding. I have a VPN site-to site on a SAA. I want to add a floating static route to point to the VPN on the ASA. Note that the traffic in this way is not with in subnets cryptographic ACL that is used to bring up the VPN. This VPN is used only as a backup.

    The static route with the next hop add local public address or the remote public address of the VPN? The next break maybe local ASA isp internet facing interface? I intend to do on the ASDM. I'm sorry if it's a simple question but I found no material that explains this?

    Concerning

    Ahh, ok, makes sense.

    The next hop should be the next jump to the interface that ends the VPN connection, essentially the same as your Internet connection / outside the next hop interface.

    Example of topology:

    Site B (outside interface - 1.1.1.1) - (next hop: 1.1.1.2) Internet

    The static route must tell:

    outdoor 10.2.2.2 255.255.255.255 1.1.1.2 200

    I hope this helps.

  • Different routes for interfaces VXLAN?

    Hi guys,.

    According to the NSX v2.1 Design Guide:

    The need for static routing is due to the fact that ESXi support only two TCP/IP stacks:

    -VXLAN: This is dedicated to the VMkernel VTEP interface traffic. A dedicated-default route 0.0.0.0/0 can then be configured on the stack for each ESXi pointing the gateway deployed on the local of ToR, and this allows to communicate with the VTEPs deployed in different subnets of Transport distance.

    -By default: This battery is used for all other types of traffic (vMotion, management, storage). It is typical to use a default for purposes of management route (given that the connection to the management interface of vmk0 could be from several remote IP subnets). This means that the static routing configuration is necessary to support communication inter-sous for other types of traffic.

    Sounds good, but is this special VXLAN stack added by default? Or do I need to create and configure? I configured a host with a separate management and VXLAN VMkernel interfaces. I see my traffic VXLAN hustled through the default gateway on the management network.

    I use static IP pools on the direction and the VXLAN interfaces. Does anyone know how to add this route dedicated by default under the battery VXLAN?

    Released of one of my hosts of calculation:

    vmk0 = management

    vmk1 = VXLAN

    ~ # esxcfg - road - l

    VMkernel itineraries:

    Interface of network gateway subnet mask

    172.16.100.0 255.255.255.128 subnet local vmk0

    by default 0.0.0.0 172.16.100.1 vmk0

    ~ # esxcfg - vmknic - l

    Interface Port Group/DVPort IP IP family address Netmask Broadcast MAC address MTU TSO MSS active Type

    0 IPv4 172.16.100.100 vmk0 255.255.255.128 172.16.100.127 00: 0C: true 29:ab:31:c9 1500 65535 vmk0 STATIC IPv6 fe80::20c:29ff:feab:31 0c 00 64 9:0 c: true 1500 65535 STATIC 29:ab:31:c9.

    FAVORITE

    vmk1 2 IPv4 172.16.200.100 255.255.255.128 172.16.200.127 00:50:56:64:0e:f3 1600 65535 true vmk1 STATIC IPv6 fe80::250:56ff:fe64:ef3 64 00:50:56:64:0e:f3 1600 65535 true STATIC 2.

    FAVORITE

    Kind regards

    Bobby

    VTEP interface is created by NSX during the preparation of the host.

    You can see this step the NSX Getting Started Guide - "step 3: prepare the ESXi NSX hosts" (Getting Started Guide for vSphere NSX).

    Once you have your VXLAN battery in ESXi, you can see its stack via vCenter UI (as usual).

    Or if you like CLI:

    . Directions:

    root@Lab1_ESXi1: ~ # esxcli ip network route ipv4 list n vxlan

    Interface Source network gateway subnet mask

    ------------  -------------  ------------  ---------  ------

    by default 0.0.0.0 192.168.20.1 vmk1 MANUAL

    192.168.20.0 255.255.255.0 0.0.0.0 vmk1 MANUAL

    . Ping

    root@Lab1_ESXi1: ~ # ping ++ netstack = vxlan 192.168.20.22

    PING 192.168.20.22 (192.168.20.22): 56 data bytes

    64 bytes from 192.168.20.22: icmp_seq = 0 ttl = 64 time = 0,616 ms

    Dimitri

  • Static route / network Configuration?

    I have a cable modem that connects via Ethernet (eth0) of a configuration for NAT and Firewall Linux box.  Another card (eth1) connects to a switch for my cable network (192.168.1.1/24).  I added a third adapter (eth2 - 192.168.2.1/24) which is connected to a M20 (192.168.2.2).  The server DHCP M20 has been implemented to serve the 192.168.3.1/24 network.

    Is there a configuration more simple than that?

    Problems reported with the current configuration:

    (1) I think the M20 NAT function must be disabled because the Linux machine is.  However, disable NAT causes machines on 192.168.3 bad connection to the internet.

    (2) I want the machines wirelessly on 192.168.3 to see shared windows on 192.168.1 and vice versa.  Currently they do not see each other.  If I remove M20 and plug a PC eth2 and set as 192.168.2.2, this machine can see actions on 192.168.1 and vice versa.  I think a static route must be set on the M20 so that he knows what to do with traffic to 192.168.1.  However, I don't properly because he always tells me I have an invalid route when I try to enter.

    (3) is there one another device other than on the M20 motorway which would better suit my needs (adding a wireless to my private/internal network segment)?

    Kind regards

    Case No.

    OK, I just saw the previous thread on this question pop up on the first page,

    Valet parking can be defined as an access point only?

    I'll try the posted instructions here.

  • Help! Static route between two router WRT160NL

    Hi all

    I have my internet connection to connect to my main router from Linksys WRT160NL (192.168.1.1) with 192.168.1.x.

    My 2nd Linksys router to connect to the first gateway as well.
    The 2nd router has the ip 192.168.1.100 WAN and it's a local subnet as 192.168.2.x.

    My 192.168.2.x machines can access the internet and connect to all the machines in the network 192.168.1.x.

    However, the 1.x network cannot access the machines on the network of the 2. And because of that, I can't share or print between two networks.

    I try to add static routes on my main router (192.168.1.1) with the road: 192.168.2.0 mask 255.255.255.0 and default gateway 192.168.1.100

    However, the road does not work yet.

    in any case to ensure that the 1.x network able to access the network 2.x and 2.x access 1.x file and print sharing.

    Thanks for your help!

    Gateway of the router does NAT who made the side inaccessible side LAN WAN, unless you configure port forwarding automatic or similar. If she would not make your LAN 192.168.1 would be accessible from the internet. Static routing will not change that.

    You will need to disable NAT (aka switch to router mode) on the second router. You must configure a static route on the main router then. However, most likely your network 192.168.2 * will not have Internet more because the main router will NAT for 192.168.1. * and no 192.168.2. *.

    If possible set up the second router as access point only and run a LAN.

  • Need to modernize the modem; How do I 'plan' relocation WRT54G Router for wired / wireless

    I went late to upgrade my modem, and from what I've read in the comments, do a modem/router combo doesn't seem to be the best thing to do in what concerns the issues of reliability and range.  So, I want to upgrade my modem & then use the same router/access point that I currently have.  However, I've read other users with problems by accessing the control panel after you connect to a new modem... so want to know the information that I need to have before starting this project.

    Is this to say that I'm going to basically start early and set up my home network all over again?

    I'm pretty tech-savy... but I do not enough to really launch the project & see where it takes me... I don't have the TIME!  Laughing out loud!

    Thanks for any help/advice anyone can offer!

    Jane

    Really, it depends on the type of settings that your ISP would put on the new modem. If the configuration of the new modem would be the same with the old, so there is no need for you to make any changes on the router. Simply connect the new modem, perform a powercycle by unplugging the power cord from the modem and router and it should work. However, if it is not, what you can do is to reset the router and reconfigure. The following links help you reconfigure the router after a reset.

    Setting up a Linksys router with cable Internet service

    Setting up a Linksys router for DSL Internet connection

    Setting up a router with a static IP address account

  • Connecting two routers via a static route

    I have a relatively simple configuration involving a Wireless-N Router and a wireless-B router (several years).  The N wireless router is connected to the internet (via DSL modem) and accepts several DHCP clients without problem.  Wireless - b router is connected to the Wireless-N router.  To do this, I connected the WAN port on the router wireless - b to a port on the router Wireless N ethernet (did not use the uplink). I have a PC connected to the router wireless - b, so I want him to be able to hit the internet, but also be accessible to DHCP clients on the Wireless N router.  The PC connects to the internet successfully, but it does not find clients on the network supported by the Wireless-N router.  It's about my setup:

    B 192.168.55.1 wireless router (LAN) 192.168.56.102 (WAN)

    PC 192.168.55.10 (active dhcp)

    Wireless N 192.168.56.1 (LAN) x.x.x.x (internet)

    (several clients dhcp... 192.168.56.100...)

    I've added a static route in the hope that a computer on the network of the Wireless N router would be able to hit the PC, but nothing helped. I've added a static route as such, on the Wireless-N router, which was the only way that that would enable the web interface:

    Destination LAN 192.168.55.0

    Subnet mask 255.255.255.0

    Gateway 192.168.56.102

    I tried to place the router without wireless - B gateway mode, then router and changed mode, then return.  I can connect to the web interface of the router wireless - b from the PC, and I can connect to the internet from the PC.  Also, the PC is able to reach customers on Wireless N, but the reverse is not true, i.e. clients on Wireless N can't find clients on the wireless - B network. Also, I turned on the port forwarding on the router wireless - B so that it points to the PC, in the hope he would lead all traffic to the PC, but still cannot access PC.  How to configure both routers (or both set up as access point?) so that clients on the Wireless N Router can talk to customers on the wireless router - B?  For now, all customers are on DHCP, but finally, I would like to create static entries for at least two or three of them.

    Thanks in advance

    Are Linksys routers teas? If so what model is router B? It may not supported for a DHCP client port forwarding. Even if you can get the port forwarding to work for a client on router B, it will not work for several clients.

    In addition, if you have the option in router B, disable the SPI Firewall. It is the cause of the problem, in my opinion. If you do this, you should port forward.

    Is there a reason that you connect the routers via the WAN port on the router B? You could uplink using an ethernet port on the B to an ethernet port on the N and avoid all this... You can always configure router B as a point of wireless access for specific customers.

  • Redistribution of static routes in OSPF

    Hi all

    It seems that the static routes can still live even if the designated interface went down.

    I added a description for this problem file.

    Stephen,

    I don't know why the distribution list did not work. Did you include the permit all at the end of the access list? Without it, you wouldn't get the external routes, as you journey.

    I have just re-read the documentation for the ip route, 12.2 and 12.4, ' cos I wasn't aware of the useful form of the command that Rick suggested. Here is an excerpt:

    Specifying a next digital jump which is on a directly connected interface will prevent the router to use Proxy ARP. However, if the next hop interface breaks down and the digital next hop can be reached by a recursive route, you can specify hop and the following interface (for example "ip route 0.0.0.0 0.0.0.0 Ethernet1/2 10.1.2.3") with a static route to avoid the roads pass through an unintentional interface.

    Which describes your problem exactly, I think. He comes:

    http://www.Cisco.com/en/us/products/SW/iosswrel/ps1835/products_command_reference_chapter09186a00800ca75a.html#wp1018065

    Therefore, the interface specification that force the static route to use only a local next hop.

    Kevin Dorrell

    Luxembourg

  • Static route ISA570W to Comcast gateway/modem

    In my view, that it is a question of static route.

    I want to be able to connect to the gateway/Modem Comcast (10.1.10.1) using any computer on my network. Currently, I am unable to do this, I am also unable to ping the unit of Comcast. Here's my setup.

    Comcast device (SMC8014)

    WAN IP: 50.x.x.238

    LAN IP: 10.1.10.1 (255.255.255.0)

    A single cable CAT5E for:

    ISA570W (WAN Port) - (basic out-of-the-box configuration, 1 - WAN, DMZ - 1, 8 - LAN Ports)

    WAN STATIC Port info:

    IP WAN: 50.x.x.233 bridge (255.255.254.0): 50.x.x.238

    LAN IP: 10.1.10.2 (255.255.255.0)

    DHCP enabled for bridge VLAN-1 (10.1.10.30 - 99) by default: 10.1.10.2

    A single cable CAT5E for:

    Cisco SG200 - 50 p (POE switch to serve as a connection for phones and desktop computers)

    LAN IP: 10.1.10.3 (255.255.255.0)

    For devices on my network to get an IP address from the device of the ISA, ISA is also the default gateway. I have logged on to the device of Comcast and all firewall rules and blocking are disabled.

    Here's a copy of my current routing table according to the ISA570:

    Destination address

    Subnet address Entry door Flags *. Metric Interface

    192.168.3.0

    255.255.255.0

    0.0.0.0

    U

    0

    DMZ

    10.1.10.0

    255.255.255.0

    0.0.0.0

    U

    0

    DEFAULT

    10.1.1.0

    255.255.255.0

    0.0.0.0

    U

    0

    VOICE

    192.168.25.0

    255.255.255.0

    0.0.0.0

    U

    0

    COMMENTS

    50.x.x.0

    255.255.254.0

    0.0.0.0

    U

    0

    WAN1

    127.0.0.0

    255.0.0.0

    0.0.0.0

    U

    0

    LOOPBACK

    0.0.0.0

    0.0.0.0

    50.x.x.238

    UG

    0

    WAN1

    My desktop (10.1.10.32), so I'm unable to ping or you connect the unit to comcast to 10.1.10.1.

    So according to me, that missing me something simple here, it is a solution of static route, or I'm looking for policies of NAT?

    Thanks for your help and please let me know if you need more information on my network.

    -Matthew-

    OK, a few possibilities here.

    1. Did you go through this process for the SMC8014 Bridge mode?

    2. I advise to use a different subnet on the LAN of the ISA to the 10.1.10.x interface.  The reason is that when you send a request from a subnet of 10.1.10.x behind the ISA to a subnet of 10.1.10.x, your PC and the ISA assumes that the device is on the same network and will not try to route.  Consider using the subnet of 192.168.75.x by default on ISA LAN interface.

    If you do not step 1 above, then I'm fairly certain that you will not be able to browse the internet at all.  If you can browse the internet, but just can't get the Comcast router 10.1.10.1, then chances are 1 step has already been completed.

    Shawn Eftink
    CCNA/CCDA

    Please note all useful messages and mark the correct answers to help others looking for solutions in the community.

Maybe you are looking for