IWMN Forum

Off-topic :: RE: �� !!!!

��: ATIAFEDERATION
��: �� 03, 2010 3:33 pm (GMT 2)
�� : 12

�� .
_________________
TARDIS:Time And Relative Dimension(s) In Space
iwmn-20-AP-Atiafederation
Voip:2040200

Off-topic :: RE: �� !!!!

��: -Mad-
��: �� 03, 2010 3:02 pm (GMT 2)
�� : 12

�� :

�� HOOLS ANTI-MPAOK!!!!!!!!!

Translation: �� HOOLS ANTI-MPAOK!!!!!!!!!

��: �� Sprinters ��-�� !!!!!!!!!

�� :: RE: IWMN DNS

��: hatsiuli
��: �� 03, 2010 1:02 pm (GMT 2)
�� : 22

�� .
�� platanos#4, thanos#66, dide#25, kastanias#268, asteris#182, kteo#262, komninio#215, vasilis#276, atia#20, anixeos#59

��1:
�� : �� interfaces �� BB.
��: KTEO �� #4 �� #276 (�� AP �� ) - �� IRWN#24 �� #95
�� AP: veria-bb.kteo-262.iwmn-new �� 4 � �� 276
�� Interface �� : kteo-262-bb.platanos-4.iwmn-new �� kteo-262-bb.vasilis-276.iwmn-new ��
(�� .kombos-ZZ.iwmn �� IP �� )

��2:
�� AP �� :
kastanias-268-bb.papagou-10.iwmn-new. �� papagou#10 �� AP �� kastanias-268
� �� 1 �� AP �� interface �� .

��3:
�� '#' �� DNS �� 'kteo#262' �� 'kteo-262'

��4:
�� aliases (CNAMES) �� :
kteo.iwmn-new ---> kteo-262.iwmn-new ---> ap.kteo-262.iwmn-new

�� .
�� .

��: ��

Hidden:

_________________
IWMN upcoming events:
�� , routing, hatsrv
1� ��

�� :: RE: �� 478

��: chdimis
��: �� 03, 2010 10:58 am (GMT 2)
�� : 11

��
�� .
_________________
Veria Node #3
VWMN VoIP 204003

�� :: RE: �� 478

��: fakiris
��: �� 03, 2010 10:22 am (GMT 2)
�� : 11

chdimis ��:

�� 1.6 �� .��
�� celeron �� .

� C. 2,66 �� P4 1,7
.
�� . �� P4 �� 400�� .
��

�� :: RE: �� 478

��: fakiris
��: �� 03, 2010 10:21 am (GMT 2)
�� : 11

chdimis ��:

�� 1.6 �� .��
�� celeron �� .

�� !!! ��.. �� , ��

�� :: RE: �� DealExtreme Z-COM XA-622H 5.8G 128mW 802.11a

��: chdimis
��: �� 03, 2010 10:01 am (GMT 2)
�� : 6

�� .
�� .�� , ��, ��
_________________
Veria Node #3
VWMN VoIP 204003

�� :: RE: �� 478

��: chdimis
��: �� 03, 2010 9:56 am (GMT 2)
�� : 11

�� 1.6 �� .��
�� celeron �� .
_________________
Veria Node #3
VWMN VoIP 204003

Linux :: RE: static &Multinetwork routing

��: V.VASILHS
��: �� 02, 2010 8:18 pm (GMT 2)
�� : 14

�� !!!!!

��:

[color=brown]route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.204.20.32 0.0.0.0 255.255.255.240 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
10.0.0.0 10.204.20.33 255.0.0.0 UG 0 0 0 eth0
0.0.0.0 192.168.1.254 0.0.0.0 UG 100 0 0 eth1[/color]

Linux :: RE: static &Multinetwork routing

��: irwn
��: �� 02, 2010 8:11 pm (GMT 2)
�� : 14

�� wepmin �� (�� linux)

Linux :: RE: static &Multinetwork routing

��: V.VASILHS
��: �� 02, 2010 6:20 pm (GMT 2)
�� : 14

http://articles.techrepublic.com.com/5100-10878_11-1052888.html

Linux :: RE: static &Multinetwork routing

��: djantonis1
��: �� 02, 2010 6:05 pm (GMT 2)
�� : 14

V.VASILHS ��:

�� ,��
Changing static routes
Now that I�ve shown you how to display currently defined routes, you�ll need to know how to change them. This can be done easiest using the Linuxconf program under Red Hat or Linux-Mandrake and similar administration programs under other Linux variants. Some variants, however, do not have tools like Linuxconf to handle defining routes, so let�s take a look at the "old school" method, instead. To do this configuration by hand, you'll have to learn how to use the route command.

The first argument passed to route will be either add or del, which will tell route if it is adding or deleting a route from the routing table. The rest of the arguments that route uses are dependant upon which action you have chosen.

Let's take a look at creating the routing table so that we have defined the same routes, as shown in the previous example. The first thing you need to do is add the network to which you belong by using:
route add -net 192.168.10.0 netmask 255.255.255.0 dev eth0

This will add the network 192.168.10.0/255.255.255.0 to the Ethernet device eth0. This corresponds with the first line shown in the netstat output.

To add the loopback network, you would use:
route add -net 127.0.0.0 netmask 255.0.0.0 lo

This adds the network 127.0.0.0/255.0.0.0 to the Ethernet device lo, which represents the loopback (or local) network. It is not necessary to do this if you�re using Linux kernels 2.2 or higher, as those kernels will handle this automatically.

Finally, you need to add the default gateway using:
route add default gw 192.168.10.1

This creates the final entry shown by netstat and tells Linux to route all packets not destined for the 192.168.10.0 network or the loopback network to the defined gateway, in this case 192.168.10.1.

In the same way, you can delete networks using the del command with route like this:
route del -net 192.168.10.0

This will delete the routing table entry for the 192.168.10.0 network.

Multinetwork routing
So what happens if you have a more complicated network? Let's assume for a moment that you have two LANs, the first with the 10.0.0.0 network and a second with the 192.168.10.0 network. There is a firewall between the two networks, with two network cards: eth0 is attached to the 10.0.0.0 network, while eth1 is attached to the 192.168.10.0 network. This firewall needs to route packets from the 10.0.0.0 network through the 192.168.10.0 network, which will in turn forward packets to the Internet.

In this scenario, you�d set up the firewall system with two IP addresses: 10.0.0.1 on eth1 and 192.168.10.25 on eth0. The gateway to the Internet on the 192.168.10.0 network is still 192.168.10.1. On the firewall system, you would run route with the following commands:
route add -net 192.168.10.0 netmask 255.255.255.0 dev eth1
route add default gw 192.168.10.1
route add -net 10.0.0.0 netmask 255.0.0.0 dev eth0

On the router, this defines both networks: 192.168.10.0 on eth1 and 10.0.0.0 on eth0. It also assigns 192.168.10.1 as the default gateway.

On the computers in the 10.0.0.0 network, you would use route like this:
route add -net 10.0.0.0 netmask 255.0.0.0 dev eth0
route add default gw 10.0.0.1

This tells each computer that the default gateway is 10.0.0.1, which is your firewall/router.

With both the firewall and the 10.0.0.0 network set up, you should be able to route all packets from the 10.0.0.0 network to the Internet and to the 192.168.10.0 network. So what happens if you have a system in the 192.168.10.0 network you want to be able to talk to systems in the 10.0.0.0 network?

On each system in the 192.168.10.0 network, you will have to configure your routing table a little differently. Here, you would traditionally use:
route add -net 192.168.10.0 netmask 255.255.255.0 dev eth0
route add default gw 192.168.10.1

This configures the network and the default gateway. However, in this case, 192.168.10.1 knows nothing about the 10.0.0.0 network, so your packets would get lost because 192.168.10.1 has no idea where to send the packets and will attempt to send them through the default gateway. You need to add another routing statement to each system in the 192.168.10.0 network like this:
route add -net 10.0.0.0 netmask 255.0.0.0 gw 192.168.10.25

This command tells the kernel to route all packets destined for the 10.0.0.0 network to 192.168.10.25, which it defines as a gateway. So now, by using the three route commands, your kernel will know where to send packets. In this situation, a few things happen:

* Packets to 192.168.10.0 are handled without a gateway.
* Packets to 10.0.0.0 are sent to the defined gateway, 192.168.10.25.
* Packets traveling anywhere else are sent to the default gateway, 192.168.10.1.

�� .. �� ??
_________________
SSID: iwmn-289-djantonis-AP
VOIP: 2052890
DC++: 10.205.3.1 connected DJANTONIS
DJANTONIS.IWMN syntoma konta sas
djantonis.wn
(ante na er8ei k h wra na paw na meinw sto 290 ekei pianei ta panta)

��: IPs/Routing/WIND :: RE: �� pc �� 2 �� (windows/linux)

��: V.VASILHS
��: �� 02, 2010 5:51 pm (GMT 2)
�� : 2

�� chdimis ��

��:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0

#iface eth0 inet static
address 10.204.20.45
netmask 255.255.255.240
network 10.204.20.32
broadcast 10.204.20.47

auto eth1

#iface eth1 inet static
address 192.168.1.10
netmask 255.255.255.0
gateway 192.168.1.254

up route add -net 10.0.0.0 gw 10.204.20.33 netmask 255.255.255.240 dev eth0
up route del -net default netmask 0.0.0.0 dev eth0

��:

route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.204.20.32 0.0.0.0 255.255.255.240 U 1 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 1 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth1
0.0.0.0 10.204.20.33 0.0.0.0 UG 0 0 0 eth0

��:

fconfig
eth0 Link encap:Ethernet HWaddr 00:19:db:b0:68:68
inet addr:10.204.20.45 Bcast:10.204.20.47 Mask:255.255.255.240
inet6 addr: fe80::219:dbff:feb0:6868/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2955 errors:0 dropped:0 overruns:0 frame:0
TX packets:2938 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1689769 (1.6 MB) TX bytes:920529 (920.5 KB)
Interrupt:28 Base address:0xa000

eth1 Link encap:Ethernet HWaddr 00:11:6b:97:c4:6b
inet addr:192.168.1.79 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::211:6bff:fe97:c46b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:165 errors:0 dropped:0 overruns:0 frame:0
TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10161 (10.1 KB) TX bytes:12241 (12.2 KB)
Interrupt:16 Base address:0xec00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:48 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4081 (4.0 KB) TX bytes:4081 (4.0 KB)

Linux :: RE: static &Multinetwork routing

��: V.VASILHS
��: �� 02, 2010 4:35 pm (GMT 2)
�� : 14

�� ,��
Changing static routes
Now that I�ve shown you how to display currently defined routes, you�ll need to know how to change them. This can be done easiest using the Linuxconf program under Red Hat or Linux-Mandrake and similar administration programs under other Linux variants. Some variants, however, do not have tools like Linuxconf to handle defining routes, so let�s take a look at the "old school" method, instead. To do this configuration by hand, you'll have to learn how to use the route command.

The first argument passed to route will be either add or del, which will tell route if it is adding or deleting a route from the routing table. The rest of the arguments that route uses are dependant upon which action you have chosen.

Let's take a look at creating the routing table so that we have defined the same routes, as shown in the previous example. The first thing you need to do is add the network to which you belong by using:
route add -net 192.168.10.0 netmask 255.255.255.0 dev eth0

This will add the network 192.168.10.0/255.255.255.0 to the Ethernet device eth0. This corresponds with the first line shown in the netstat output.

To add the loopback network, you would use:
route add -net 127.0.0.0 netmask 255.0.0.0 lo

This adds the network 127.0.0.0/255.0.0.0 to the Ethernet device lo, which represents the loopback (or local) network. It is not necessary to do this if you�re using Linux kernels 2.2 or higher, as those kernels will handle this automatically.

Finally, you need to add the default gateway using:
route add default gw 192.168.10.1

This creates the final entry shown by netstat and tells Linux to route all packets not destined for the 192.168.10.0 network or the loopback network to the defined gateway, in this case 192.168.10.1.

In the same way, you can delete networks using the del command with route like this:
route del -net 192.168.10.0

This will delete the routing table entry for the 192.168.10.0 network.

Multinetwork routing
So what happens if you have a more complicated network? Let's assume for a moment that you have two LANs, the first with the 10.0.0.0 network and a second with the 192.168.10.0 network. There is a firewall between the two networks, with two network cards: eth0 is attached to the 10.0.0.0 network, while eth1 is attached to the 192.168.10.0 network. This firewall needs to route packets from the 10.0.0.0 network through the 192.168.10.0 network, which will in turn forward packets to the Internet.

In this scenario, you�d set up the firewall system with two IP addresses: 10.0.0.1 on eth1 and 192.168.10.25 on eth0. The gateway to the Internet on the 192.168.10.0 network is still 192.168.10.1. On the firewall system, you would run route with the following commands:
route add -net 192.168.10.0 netmask 255.255.255.0 dev eth1
route add default gw 192.168.10.1
route add -net 10.0.0.0 netmask 255.0.0.0 dev eth0

On the router, this defines both networks: 192.168.10.0 on eth1 and 10.0.0.0 on eth0. It also assigns 192.168.10.1 as the default gateway.

On the computers in the 10.0.0.0 network, you would use route like this:
route add -net 10.0.0.0 netmask 255.0.0.0 dev eth0
route add default gw 10.0.0.1

This tells each computer that the default gateway is 10.0.0.1, which is your firewall/router.

With both the firewall and the 10.0.0.0 network set up, you should be able to route all packets from the 10.0.0.0 network to the Internet and to the 192.168.10.0 network. So what happens if you have a system in the 192.168.10.0 network you want to be able to talk to systems in the 10.0.0.0 network?

On each system in the 192.168.10.0 network, you will have to configure your routing table a little differently. Here, you would traditionally use:
route add -net 192.168.10.0 netmask 255.255.255.0 dev eth0
route add default gw 192.168.10.1

This configures the network and the default gateway. However, in this case, 192.168.10.1 knows nothing about the 10.0.0.0 network, so your packets would get lost because 192.168.10.1 has no idea where to send the packets and will attempt to send them through the default gateway. You need to add another routing statement to each system in the 192.168.10.0 network like this:
route add -net 10.0.0.0 netmask 255.0.0.0 gw 192.168.10.25

This command tells the kernel to route all packets destined for the 10.0.0.0 network to 192.168.10.25, which it defines as a gateway. So now, by using the three route commands, your kernel will know where to send packets. In this situation, a few things happen:

* Packets to 192.168.10.0 are handled without a gateway.
* Packets to 10.0.0.0 are sent to the defined gateway, 192.168.10.25.
* Packets traveling anywhere else are sent to the default gateway, 192.168.10.1.

�� :: RE: �� DealExtreme Z-COM XA-622H 5.8G 128mW 802.11a

��: ��
��: �� 02, 2010 4:19 pm (GMT 2)
�� : 6

�� DX �� "Drop Shipment and Gift Service (Removes DX logo from package) " ???
_________________
www.george-tsa.blogspot.com

http://www.youtube.com/watch?v=yNSpLqmY6K0

IWMN Forum

Off-topic :: RE: �� �������� ��� ����� ����� ������!!!!

Off-topic :: RE: �� �������� ��� ����� ����� ������!!!!

��������� :: RE: IWMN DNS

�������� ���������� :: RE: �������� 478

�������� ���������� :: RE: �������� 478

�������� ���������� :: RE: �������� 478

������ �������� :: RE: ����� ��� DealExtreme Z-COM XA-622H 5.8G 128mW 802.11a

�������� ���������� :: RE: �������� 478

Linux :: RE: static &Multinetwork routing

Linux :: RE: static &Multinetwork routing

Linux :: RE: static &Multinetwork routing

Linux :: RE: static &Multinetwork routing

������: IPs/Routing/WIND :: RE: ����������� �� pc �� 2 ������ (windows/linux)

Linux :: RE: static &Multinetwork routing

������ �������� :: RE: ����� ��� DealExtreme Z-COM XA-622H 5.8G 128mW 802.11a

Off-topic :: RE: �� !!!!

Off-topic :: RE: �� !!!!

�� :: RE: IWMN DNS

�� :: RE: �� 478

�� :: RE: �� 478

�� :: RE: �� 478

�� :: RE: �� DealExtreme Z-COM XA-622H 5.8G 128mW 802.11a

�� :: RE: �� 478

��: IPs/Routing/WIND :: RE: �� pc �� 2 �� (windows/linux)

�� :: RE: �� DealExtreme Z-COM XA-622H 5.8G 128mW 802.11a