Re: Modem/Router/Router -

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2019-04-15 at 04:08 -0400, Bob Goodwin wrote:
> Initially the ISP feed was into the WAN port on my dd-wrt router a
> [a system I have been using for 13 years] and nothing was reaching
> the LAN, wired or wifi. Normally the router feeds a 16 port switch
> that connects the equipment on my wired LAN, to workaround the
> problem I have moved the ISP input from the WAN jack to one of the
> Ethernet output ports, the router is doing nothing but acting as a
> "switch" or hub, a straight through Ethernet adapter does about the
> same thing. That bypasses all the logging features that I must have
> to regulate usage ...

Sounds like a bit of diagnosis is needed.  Some first steps:

Connect a computer directly to their equipment, and tell us the
numerical IP address your computer gets assigned (e.g. run the
"ifconfig" command, tell us the "inet" address for the ethernet port). 
This IP is safe to state in public (it's isolated from everyone by
being in a NAT, and your public IP is in your mail headers, anyway). 
It's likely to be something like:  192.168.1.12

Now, connect a computer directly to your own router, and do the same
thing.

If you can't spot the right data in the ifconfig output, just copy the
whole block.  There'll be about 9 lines of data for your ethernet (or
WiFi), and another 8 for the local loopback (127.0.0.1) network.  The
ethernet (or WiFi) data is what we'd like to see.

While I can spot problems with IPv4 addresses (e.g. 192.168.1.12)
within a LAN, I'm not familiar enough with IPv6 addresses to spot
issues (e.g. fe80::8178:8ef9:4a4f:517e), but others will be.

NB:  In itself, IPv6 can be a problem (if your ISP doesn't support it,
but your LAN equipment uses it).  Your equipment can try to connect to
IPv6 addresses on the internet, expecting to be able to, but hit a
solid roadblock at your ISP.


_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux