Sponsored Content
Special Forums IP Networking Routing problem : two interfaces one gateway Post 302920512 by gencaslan on Thursday 9th of October 2014 06:04:35 PM
Old 10-09-2014
Quote:
Originally Posted by Corona688
If you wanted your router to route, you would have its IP address be the gateway for the things behind it.

If you don't want it to do any routing at all and just join all the ports together in a big virtual switch, make them all part of br0. Note that firewall rules still apply to traffic forwarded over a bridge.

i have a few problems. my ip knowledge is limited. and i only have a busybox linux on the horstbox-router.

so is it possible to "bridge" the interfaces per command line ? does this make sense ?
 

10 More Discussions You Might Find Interesting

1. IP Networking

Network interfaces problem

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

Network interfaces problem

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

Routing via several interfaces for hosted virtual machines

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

GNUGK-How to setup static gateway to gateway routing

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

/etc/network/interfaces problem

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

Problem when I Open my WireShark - No Interfaces Option available

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

Routing problem

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

Problem with multiple network interfaces

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

Network Interfaces Problem - Monitoring equipment

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

Inconsistency between RedHat 6.5 global gateway and single gateway leads to loss of default gateway

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
BRCTL(8)																  BRCTL(8)

NAME
brctl - ethernet bridge administration SYNOPSIS
brctl [command] DESCRIPTION
brctl is used to set up, maintain, and inspect the ethernet bridge configuration in the linux kernel. An ethernet bridge is a device commonly used to connect different networks of ethernets together, so that these ethernets will appear as one ethernet to the participants. Each of the ethernets being connected corresponds to one physical interface in the bridge. These individual ethernets are bundled into one bigger ('logical') ethernet, this bigger ethernet corresponds to the bridge network interface. INSTANCES
The command brctl addbr <name> creates a new instance of the ethernet bridge. The network interface corresponding to the bridge will be called <name>. The command brctl delbr <name> deletes the instance <name> of the ethernet bridge. The network interface corresponding to the bridge must be down before it can be deleted! The command brctl show shows all current instances of the ethernet bridge. PORTS
Each bridge has a number of ports attached to it. Network traffic coming in on any of these ports will be forwarded to the other ports transparently, so that the bridge is invisible to the rest of the network (i.e. it will not show up in traceroute(8) ). The command brctl addif <brname> <ifname> will make the interface <ifname> a port of the bridge <brname>. This means that all frames received on <ifname> will be processed as if destined for the bridge. Also, when sending frames on <brname>, <ifname> will be considered as a potential output interface. The command brctl delif <brname> <ifname> will detach the interface <ifname> from the bridge <brname>. The command brctl show <brname> will show some information on the bridge and its attached ports. AGEING
The bridge keeps track of ethernet addresses seen on each port. When it needs to forward a frame, and it happens to know on which port the destination ethernet address (specified in the frame) is located, it can 'cheat' by forwarding the frame to that port only, thus saving a lot of redundant copies and transmits. However, the ethernet address location data is not static data. Machines can move to other ports, network cards can be replaced (which changes the machine's ethernet address), etc. brctl showmacs <brname> shows a list of learned MAC addresses for this bridge. brctl setageing <brname> <time> sets the ethernet (MAC) address ageing time, in seconds. After <time> seconds of not having seen a frame coming from a certain address, the bridge will time out (delete) that address from the Forwarding DataBase (fdb). brctl setgcint <brname> <time> sets the garbage collection interval for the bridge <brname> to <time> seconds. This means that the bridge will check the forwarding database for timed out entries every <time> seconds. SPANNING TREE PROTOCOL
Multiple ethernet bridges can work together to create even larger networks of ethernets using the IEEE 802.1d spanning tree protocol. This protocol is used for finding the shortest path between two ethernets, and for eliminating loops from the topology. As this protocol is a standard, linux bridges will interwork properly with other third party bridge products. Bridges communicate with each other by sending and receiving BPDUs (Bridge Protocol Data Units). These BPDUs can be recognised by an ethernet destination address of 01:80:c2:00:00:00. The spanning tree protocol can also be turned off (for those situations where it just doesn't make sense, for example when this linux box is the only bridge on the LAN, or when you know that there are no loops in the topology.) brctl(8) can be used for configuring certain spanning tree protocol parameters. For an explanation of these parameters, see the IEEE 802.1d specification (or send me an email). The default values should be just fine. If you don't know what these parameters mean, you probably won't feel the desire to tweak them. brctl stp <bridge> <state> controls this bridge instance's participation in the spanning tree protocol. If <state> is "on" or "yes" the STP will be turned on, otherwise it will be turned off. When turned off, the bridge will not send or receive BPDUs, and will thus not partici- pate in the spanning tree protocol. If your bridge isn't the only bridge on the LAN, or if there are loops in the LAN's topology, DO NOT turn this option off. If you turn this option off, please know what you are doing. brctl setbridgeprio <bridge> <priority> sets the bridge's priority to <priority>. The priority value is an unsigned 16-bit quantity (a num- ber between 0 and 65535), and has no dimension. Lower priority values are 'better'. The bridge with the lowest priority will be elected 'root bridge'. brctl setfd <bridge> <time> sets the bridge's 'bridge forward delay' to <time> seconds. brctl sethello <bridge> <time> sets the bridge's 'bridge hello time' to <time> seconds. brctl setmaxage <bridge> <time> sets the bridge's 'maximum message age' to <time> seconds. brctl setpathcost <bridge> <port> <cost> sets the port cost of the port <port> to <cost>. This is a dimensionless metric. brctl setportprio <bridge> <port> <priority> sets the port <port>'s priority to <priority>. The priority value is an unsigned 8-bit quan- tity (a number between 0 and 255), and has no dimension. This metric is used in the designated port and root port selection algorithms. NOTES
brctl(8) replaces the older brcfg tool. SEE ALSO
ipchains(8), iptables(8) AUTHOR
Lennert Buytenhek <buytenh@gnu.org> November 7, 2001 BRCTL(8)
All times are GMT -4. The time now is 03:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy