Sponsored Content
Full Discussion: DI-524 router problem
Special Forums IP Networking DI-524 router problem Post 302280629 by otheus on Tuesday 27th of January 2009 09:54:29 AM
Old 01-27-2009
Both Windows and desktop Linux distributions typically have packet filtering ("firewall") enabled on the ethernet port, blocking access to things like port 80.

Is your router doing NAT?
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Remote Unix printing to my WinXP works with no router. How can I make it work through my router?

I set up remote printing on a clients Unix server to my Windows XP USB printer. My USB printer is connected directly to my PC (no print server and no network input on printer). With my Win XP PC connected to my cable modem (without the router), i can do lp -dhp842c /etc/hosts and it prints. I... (7 Replies)
Discussion started by: jmhohne
7 Replies

2. Slackware

Slackware router problem

I have a Slackware box that I've set up as a router for my home network. It does that and zoneminder and that's pretty much it. It's worked fine for a few years doing this until today. Today the power went out and the UPS could only keep this machine up for about 45 mins before it ran out of... (1 Reply)
Discussion started by: orsty9001
1 Replies

3. IP Networking

Upload problem with traffic shaping though a Linux router.

So I want to limit the download and upload speed of a specific ip adress in a local network. To do this I are using a bach script running in a linux OS (Ubuntu 11.04). The issue here is that the upload shaper does not work. I have tried an alternate solution aswell though that does not work as... (0 Replies)
Discussion started by: martio09
0 Replies

4. IP Networking

Dual Router (routing problem)

This is the network configuration I have: +-------------------------------------------------+ +===========+ | | | | | INTERNET |---| LINUXBOX2 | ... (4 Replies)
Discussion started by: matteo
4 Replies

5. IP Networking

Router problem or ISP problem ?

Hi everyone, I am experiencing discontinuity of Internet service, this started 1 month ago. Everything worked very well for 1 year of intensive use, but now, I have problems reaching my gateway. The gateway is not my router but a node belonging to my ISP and I share the same public IP with... (3 Replies)
Discussion started by: remic
3 Replies

6. Hardware

Netgear C3700 Modem Router Problem

I was wondering if anyone had any knowledge about how these routers work.. I bought a Netgear C3700 modem router on eBay about a month ago and couldn't get it to broadcast internet, neither wired nor wireless. When I plug it in and turn it on, all lights come on, but the internet light keeps... (2 Replies)
Discussion started by: milhan
2 Replies
MEM(4)                                                       Linux Programmer's Manual                                                      MEM(4)

NAME
mem, kmem, port - system memory, kernel memory and system ports DESCRIPTION
/dev/mem is a character device file that is an image of the main memory of the computer. It may be used, for example, to examine (and even patch) the system. Byte addresses in /dev/mem are interpreted as physical memory addresses. References to nonexistent locations cause errors to be returned. Examining and patching is likely to lead to unexpected results when read-only or write-only bits are present. Since Linux 2.6.26, and depending on the architecture, the CONFIG_STRICT_DEVMEM kernel configuration option limits the areas which can be accessed through this file. For example: on x86, RAM access is not allowed but accessing memory-mapped PCI regions is. It is typically created by: mknod -m 660 /dev/mem c 1 1 chown root:kmem /dev/mem The file /dev/kmem is the same as /dev/mem, except that the kernel virtual memory rather than physical memory is accessed. Since Linux 2.6.26, this file is available only if the CONFIG_DEVKMEM kernel configuration option is enabled. It is typically created by: mknod -m 640 /dev/kmem c 1 2 chown root:kmem /dev/kmem /dev/port is similar to /dev/mem, but the I/O ports are accessed. It is typically created by: mknod -m 660 /dev/port c 1 4 chown root:kmem /dev/port FILES
/dev/mem /dev/kmem /dev/port SEE ALSO
chown(1), mknod(1), ioperm(2) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2015-01-02 MEM(4)
All times are GMT -4. The time now is 04:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy