|
|
Sponsored Content
Special Forums
IP Networking
Routing problem : two interfaces one gateway
Post 302920494 by gencaslan on Thursday 9th of October 2014 03:52:50 PM
10-09-2014
this is the horstbox
there are 4 blue ethernet ports. i am sorry but i have no deep knowledge in ip.
the first lan port (wan0 interface) is connected to my home network like i noticed before. if i connect with putty to the router on a shell i can ping an internet address. so the traffic seems to go over the wan0 interface and the standard gateway 192.168.2.1. thats good and ok.
but if i connect another device on lan port 2 -4 (br0) it gets no ip address from dhcp. there is no connection to my home network.
i am not sure what is the solution to this problem because of my limited knowledge to ip.
but the solution to me should be that when i connect another device to lan port 2-4 (br0) it should get acces to my home network (dhcp, internet etc).
any ideas ?
there are 4 blue ethernet ports. i am sorry but i have no deep knowledge in ip.
the first lan port (wan0 interface) is connected to my home network like i noticed before. if i connect with putty to the router on a shell i can ping an internet address. so the traffic seems to go over the wan0 interface and the standard gateway 192.168.2.1. thats good and ok.
but if i connect another device on lan port 2 -4 (br0) it gets no ip address from dhcp. there is no connection to my home network.
i am not sure what is the solution to this problem because of my limited knowledge to ip.
but the solution to me should be that when i connect another device to lan port 2-4 (br0) it should get acces to my home network (dhcp, internet etc).
any ideas ?
|
|
10 More Discussions You Might Find Interesting
1. IP Networking
Hi,
I have problems with my SCO unix network interfaces.
Intel integrated adapter was failing, so I installed new one - 3COM adapter into free PCI slot.
Installed driver using SCO Software manager - successfully
Added new Network adapter using SCO Network configuration manager - successfully... (0 Replies)
Discussion started by: vilius
0 Replies
2. SCO
Hi,
I have problems with my SCO unix network interfaces.
Intel integrated adapter was failing, so I installed new one - 3COM adapter into free PCI slot.
Installed driver using SCO Software manager - successfully
Added new Network adapter using SCO Network configuration manager - successfully... (0 Replies)
Discussion started by: vilius
0 Replies
3. Linux
My setup consists of a hardware node, which hosts several virtual machines (OpenVZ, to be precise). The hardware node has two network interfaces (<ifA>, <ifB>) connected to different subnets (<networkA>, <networkB>). I want to route the traffic of certain VEs over <ifB> while routing the other VEs... (0 Replies)
Discussion started by: bakunin
0 Replies
4. Linux
Dear Sir
I am a newbie in the world of IP telephony. I have been working with Asterisk PBX (SIP) and Cisco Call Manager (MGCP) but now I am learning on how to work GNUGK for H.323 Gatekeeper.
I am having a problem, configuring static call routing on GNUGK
in the section
... (0 Replies)
Discussion started by: mfondoum
0 Replies
5. Debian
Hello
i am configuring a debian lenny sever ,/etc/network/interfaces is modified so that eth1 takes a static IP address
then i save it wq!
then i restart the networking , /etc/init.d/networking restart .
but after reboot ,the file is reset ,note that the interfaces had by defauklt IPv6 address... (5 Replies)
Discussion started by: learn82
5 Replies
6. IP Networking
Hi gurus of unix, I haved installed my openSolaris in a HP530,
Recently I use the following command
beadm destry opensolaris1
beadm destry opensolaris2
After That I reboot my Laptop.
Well when I go to my work I try to open my wireshark tool, but the option in GUI interface does not appear!!!... (2 Replies)
Discussion started by: andresguillen
2 Replies
7. Solaris
Hi,
I have two physical interfaces on a servers.
We have connected them to differerent subnets.
1) First interface:
10.158.49.87 to newtwork 10.158.49.0, its gateway is 10.158.49.1
(It is added as default gateway)
It is existing set up. It works well
2) Second interface:
... (1 Reply)
Discussion started by: sri243
1 Replies
8. AIX
Hi .. we have two AIX 5.3 systems with a small client server app communicating over a TCP socket.
Box A has a single network interface where the server app (in Java) opens a well known port and waits for connections from Box B.
Box B has two network interfaces, X and Y. Interface X has the... (4 Replies)
Discussion started by: RonBowater
4 Replies
9. IP Networking
Dear gurus of Linux / Unix.
I have a server, which I use to monitoring traffic, the problem that I find is when I run the following command:
probe:~ # sar -n DEV 1
I see that I one second appear info in some interface and in the other second no appear, I don't know what will be the... (0 Replies)
Discussion started by: andresguillen
0 Replies
10. UNIX for Beginners Questions & Answers
Dear friends
I use RedHat 6.5, which sets the gateway in the configuration file / etc / sysconfig / network as GATEWAY = 192.168.1.26, and the gateway in the configuration file / etc / sysconfig / network-scripts / ifcfg-eth11 as GATEWAY = 192.168.1.256. The two gateways are different.... (6 Replies)
Discussion started by: tanpeng
6 Replies
LEARN ABOUT HPUX
lan
lan(7) Miscellaneous Information Manual lan(7) NAME
lan - network I/O card access information DESCRIPTION
This manual entry gives a brief description on how to access the LAN device driver at Layer 2 (Data Link Layer) of the OSI architecture. The LAN device driver controls the various LAN interface cards (e.g, Ethernet/IEEE 802.3, FDDI, Token Ring) at Layer 1 (Physical Layer). The Data Link Provider Interface (DLPI) is the supported method for accessing the LAN device driver at Layer 2. DLPI is intended for use by knowledgeable network users only. Refer to the for complete programming details. There are HP and non-HP drivers and interface cards which will provide their own DLPI module. These types of DLPI are referred to as "native" DLPI. Overview The Physical Point of Attachment (PPA) is a numerical value that uniquely identifies a particular device. The PPA value can be obtained from the and commands. The "ClassInstance" identifier in the output is the concatenation of the driver class (lan) and the PPA number. The "NamePPA" identifier in the output is a concatenation of the interface name and the PPA number. The value for a lan device is equiva- lent to the PPA number for that device. A single hardware device may have multiple "NamePPA" identifiers, which indicates multiple encapsulation methods supported for to the device. For Ethernet/IEEE 802.3 links, the "Name" is used to designate Ethernet encapsulation, and for IEEE 802.3 encapsulation. For other links (FDDI, Token Ring), only the encapsulation designation is used. Methods of transfer over the DLPI interface through the lan devices include "raw", "connectionless", and "connection-oriented" data trans- fers. WARNINGS
The and commands are deprecated. These commands will be removed in a future HP-UX release. HP recommends the use of replacement command nwmgr(1M) to perform all network interface-related tasks. AUTHOR
was developed by HP. SEE ALSO
lanscan(1M), lanadmin(1M), linkloop(1M), nwmgr(1M). 1995, Hewlett-Packard Version 2.0, November 1982, Digital Equipment Corporation, Intel Corporation, Xerox Corporation 1996, Institute of Electrical and Electronic Engineers 1996, Institute of Electrical and Electronic Engineers 1995, ANSI 1995, Institute of Electrical and Electronic Engineers 1995, Institute of Electrical and Electronic Engineers lan(7)