Re: Routing issue?

[Ryan Coleman]

As mentioned before, this is already solved.


On Nov 12, 2010, at 3:08 AM, Wojciech Puchar wrote:

>> ff02::%lo0/32 fe80::1%lo0   U   
>> lo0
>> 
>> ifconfig_em0="inet 70.89.123.5  netmask 255.255.255.248"
>> ifconfig_em1="inet 70.89.123.4 netmask 255.255.255.248"
>> defaultrouter="70.89.123.6"
>> hostname="se**.somehtingelse.biz"
>> 
>> 
>> I tried to add the gateway for link2 but it's not taking since it already 
>> exists, and I've run multiple IP'd servers before without issue.
>> 
>> I'm really lost.___
> you can't have 2 gateways.
> 
> but you may configure ipfw firewall and use it's fwd function to define 
> exactly what is routed through what, whatever your wish is.
> 
> not that long ago i had 7 links to my server doing ISP business, as there was 
> no way to get single large link that place.
> 
> no problems
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Routing issue?

[Wojciech Puchar]

ff02::%lo0/32 fe80::1%lo0   U   lo0

ifconfig_em0="inet 70.89.123.5  netmask 255.255.255.248"
ifconfig_em1="inet 70.89.123.4 netmask 255.255.255.248"
defaultrouter="70.89.123.6"
hostname="se**.somehtingelse.biz"


I tried to add the gateway for link2 but it's not taking since it already 
exists, and I've run multiple IP'd servers before without issue.

I'm really lost.___

you can't have 2 gateways.

but you may configure ipfw firewall and use it's fwd function to define 
exactly what is routed through what, whatever your wish is.


not that long ago i had 7 links to my server doing ISP business, as there 
was no way to get single large link that place.


no problems
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

{Solved} Re: Routing issue?

[Ryan Coleman]

It didn't work until I bridged the connections.

[r...@server /usr/home/ryan]# ifconfig bridge create
bridge0
[r...@server /usr/home/ryan]# ifconfig bridge0
bridge0: flags=8802 metric 0 mtu 1500
ether 0a:df:a2:b3:3e:96
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
root id 00:00:00:00:00:00 priority 0 ifcost 0 port 0
[r...@server /usr/home/ryan]# ifconfig bridge0 addm em0 addm em1 up


On Nov 11, 2010, at 10:00 PM, Gary Gatten wrote:

> What exactly isn't working? You don't have two L3 nets, but two ips on the 
> same net - nothing to route, except the default.
> 
> - Original Message -
> From: owner-freebsd-questi...@freebsd.org 
> 
> To: Free BSD Questions list 
> Sent: Thu Nov 11 21:41:40 2010
> Subject: Routing issue?
> 
> I'm trying to get the other half of my business up on my second IP.
> 
> It's not routing. This is not a multi-homed system, but two IPs in the same 
> subnet.
> 
> 
> [r...@server /usr/home/ryan]# netstat -nr 
> Routing tables
> 
> Internet:
> DestinationGatewayFlagsRefs  Use  Netif Expire
> default70.89.123.6UGS 7 1090em0
> 70.89.123.0/29 link#1 U   2  837em0
> 70.89.123.4link#2 UHS 0   25lo0
> 70.89.123.5link#1 UHS 00lo0
> 127.0.0.1  link#5 UH  0  863lo0
> 
> Internet6:
> Destination   Gateway   Flags  
> Netif Expire
> ::1   ::1   UH  
> lo0
> fe80::%lo0/64 link#5U   
> lo0
> fe80::1%lo0   link#5UHS 
> lo0
> ff01:5::/32   fe80::1%lo0   U   
> lo0
> ff02::%lo0/32 fe80::1%lo0   U   
> lo0
> 
> ifconfig_em0="inet 70.89.123.5  netmask 255.255.255.248"
> ifconfig_em1="inet 70.89.123.4 netmask 255.255.255.248"
> defaultrouter="70.89.123.6"
> hostname="se**.somehtingelse.biz"
> 
> 
> I tried to add the gateway for link2 but it's not taking since it already 
> exists, and I've run multiple IP'd servers before without issue.
> 
> I'm really lost.___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
> 
> 
> 
> 
> 
> 
> 
> 
> "This email is intended to be reviewed by only the intended recipient
> and may contain information that is privileged and/or confidential.
> If you are not the intended recipient, you are hereby notified that
> any review, use, dissemination, disclosure or copying of this email
> and its attachments, if any, is strictly prohibited.  If you have
> received this email in error, please immediately notify the sender by
> return email and delete this email from your system."
> 
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Routing issue?

[Gary Gatten]

What exactly isn't working? You don't have two L3 nets, but two ips on the same 
net - nothing to route, except the default.

- Original Message -
From: owner-freebsd-questi...@freebsd.org 
To: Free BSD Questions list 
Sent: Thu Nov 11 21:41:40 2010
Subject: Routing issue?

I'm trying to get the other half of my business up on my second IP.

It's not routing. This is not a multi-homed system, but two IPs in the same 
subnet.


[r...@server /usr/home/ryan]# netstat -nr 
Routing tables

Internet:
DestinationGatewayFlagsRefs  Use  Netif Expire
default70.89.123.6UGS 7 1090em0
70.89.123.0/29 link#1 U   2  837em0
70.89.123.4link#2 UHS 0   25lo0
70.89.123.5link#1 UHS 00lo0
127.0.0.1  link#5 UH  0  863lo0

Internet6:
Destination   Gateway   Flags  
Netif Expire
::1   ::1   UH  lo0
fe80::%lo0/64 link#5U   lo0
fe80::1%lo0   link#5UHS lo0
ff01:5::/32   fe80::1%lo0   U   lo0
ff02::%lo0/32 fe80::1%lo0   U   lo0

ifconfig_em0="inet 70.89.123.5  netmask 255.255.255.248"
ifconfig_em1="inet 70.89.123.4 netmask 255.255.255.248"
defaultrouter="70.89.123.6"
hostname="se**.somehtingelse.biz"


I tried to add the gateway for link2 but it's not taking since it already 
exists, and I've run multiple IP'd servers before without issue.

I'm really lost.___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"








"This email is intended to be reviewed by only the intended recipient
 and may contain information that is privileged and/or confidential.
 If you are not the intended recipient, you are hereby notified that
 any review, use, dissemination, disclosure or copying of this email
 and its attachments, if any, is strictly prohibited.  If you have
 received this email in error, please immediately notify the sender by
 return email and delete this email from your system."


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Routing Issue?

[Garrett Cooper]

Yousef Adnan Raffah wrote:

Hello Everyone,

I have a FreeBSD 6.1-RELEASE box that has two network cards (Dual
Homed?). Each card is on a different network, as following
(from /etc/rc.conf):

ifconfig_fxp0="inet 192.168.20.36 netmask 255.255.255.0"
ifconfig_rl0="inet 192.168.210.6 netmask 255.255.255.0"
defaultrouter="192.168.210.1"
route_servers="-net 192.168.2.0 192.168.20.1"
static_routes="net1 net2"
route_net1="-net 172.20.68.0 192.168.20.1 255.255.254.0"
route_net2="-net 192.168.2.0 192.168.20.1"

The fxp0 is connected to the outside world while the rl0 is connected to
the internal networks. I noticed whenever I ssh or try to telnet to port
25 on this box from 192.168.2.x for example, it delays the response by
something like 10 seconds, I even have a tcpdump of that!

Can someone explain what is wrong with my setup? Should I have routed
running? (I personally don't feel it is needed)

Thanks in advance for your help and guidance.

P.S. I got the above setup based on my understanding of the handbook, so
forgive me if I didn't understand it correctly :)



	I believe the actual fault is that you don't understand how networks 
are done, based on the /etc/rc.conf entries you've listed above.
	I suggest that you pick up Computer Networks: A System Approach by 
Peterson and Davie to pick up a basic idea of how networking and routing 
works, and maybe consult  
as a basis for planning out how things will be done, in particular with 
network addresses.
	Providing netstat -nr" output would be beneficial as well when 
troubleshooting issues with routing, as well as any firewall rules you 
have in place.

-Garrett
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Routing issue

[Matthew Seaman]

On Mon, Jul 19, 2004 at 12:55:45PM -0500, Web Walrus (Robert Wall) wrote:
> > > > > ifconfig_dc0 inet 1.2.3.4 netmask 255.255.255.248
> > > > > ifconfig_dc0_alias0 inet 2.3.4.5 netmask 255.255.255.248
> > > > > defaultrouter="1.2.3.1"
> > >
> > > It's not on the same network; that's the problem.  Two complete separate
> > > networks, same interface card.  The issue is that one of the networks
> > > works, and the other doesn't, depending on what network the default router
> > > happens to be on.
> >
> > In general, you're going to need a mechanism for dynamically routing
> > packets in order to make this sort of setup work.  For most setups,
> > you'ld need the co-operation of your ISP to make things work as well.
> 
> The situation is this - there are 4 servers that are on one network.  I'm
> trying to switch them over to another network, but I need to do it without
> downtime.  Therefore, I need to have both IPs completely active and
> functional simultaneously.

Right -- in which case, you've actually done everything right,

> Is there any way to determine what IP/interface a connection came in on,
> and continue to use that IP/interface for the outbound packets?  Maybe
> with static routes or something of that nature?

That should happen automatically whenever anyone connects to one or
other of those addresses.  It's setting the origin address on outgoing
connections that's usually the difficult bit, but in this case, that
shouldn't be a problem.  Really all you need to do is at some point
change the default route to point to the new gateway, and then wait
until any traffic to the old addressess dies away.  Then edit
/etc/rc.conf to make the new ip address the only one configured on the
interface and whatever else needs fiddling with similarly, a quick
reboot and you're done.

Cheers

Matthew


-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgprKTSAyFxbr.pgp
Description: PGP signature

Re: Routing issue

[Web Walrus (Robert Wall)]

> > > > ifconfig_dc0 inet 1.2.3.4 netmask 255.255.255.248
> > > > ifconfig_dc0_alias0 inet 2.3.4.5 netmask 255.255.255.248
> > > > defaultrouter="1.2.3.1"
> >
> > It's not on the same network; that's the problem.  Two complete separate
> > networks, same interface card.  The issue is that one of the networks
> > works, and the other doesn't, depending on what network the default router
> > happens to be on.
>
> In general, you're going to need a mechanism for dynamically routing
> packets in order to make this sort of setup work.  For most setups,
> you'ld need the co-operation of your ISP to make things work as well.

The situation is this - there are 4 servers that are on one network.  I'm
trying to switch them over to another network, but I need to do it without
downtime.  Therefore, I need to have both IPs completely active and
functional simultaneously.

Would the situation be any easier if I put one of the networks on a
separate NIC?

Is there any way to determine what IP/interface a connection came in on,
and continue to use that IP/interface for the outbound packets?  Maybe
with static routes or something of that nature?

The thing is, I used this exact setup (albeit on two different network
cards) on a FreeBSD 2.x box quite a ways back, for the same purpose
(switching networks), and it was working fine.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Routing issue

[Matthew Seaman]

On Mon, Jul 19, 2004 at 04:31:36AM -0500, Web Walrus (Robert Wall) wrote:
> > > ifconfig_dc0 inet 1.2.3.4 netmask 255.255.255.248
> > > ifconfig_dc0_alias0 inet 2.3.4.5 netmask 255.255.255.248
> > > defaultrouter="1.2.3.1"
> >
> > You need to change your netmask for the alias to 255.255.255.255 if it's
> > on the same network.
> 
> It's not on the same network; that's the problem.  Two complete separate
> networks, same interface card.  The issue is that one of the networks
> works, and the other doesn't, depending on what network the default router
> happens to be on.

Yes -- the OP's configuration is correct as far as it goes.  However
the problem he's facing is rather more intractable than it first
appears.

In general, you're going to need a mechanism for dynamically routing
packets in order to make this sort of setup work.  For most setups,
you'ld need the co-operation of your ISP to make things work as well.

There's two areas where you can use this dual setup profitably.

The first is failover -- should one of the connections go down, you'll
automatically switch to using the other.  About the simplest way of
doing something like that is to run a script periodically (say once
every 5 minutes) that sends a ping down the active channel, and if
there's no response, it switches the default route to the other
channel.  This means that normally all your traffic will go down one
of the connections, and there won't be any bandwidth advantages but
you will get increased resilience.

The second is 'policy based routing' -- which is a good term to google
for.  Under FreeBSD this is implemented using the ipfw(8) 'fwd'
command which lets you dynamically redirect packets down one channel
or the other.  That means you can do things like select out HTTP
traffic and send it via one channel, leaving all of the other traffic
to go by the other.  That lets you share out your bandwidth between
available channels, but doesn't give you any advantages in terms of
resilience.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgpbVdI29YXTM.pgp
Description: PGP signature

Re: Routing issue

[Kevin Stevens]

On Jul 19, 2004, at 02:12, Web Walrus (Robert Wall) wrote:
That network card has a config roughly like
ifconfig_dc0 inet 1.2.3.4 netmask 255.255.255.248
ifconfig_dc0_alias0 inet 2.3.4.5 netmask 255.255.255.248
defaultrouter="1.2.3.1"
Excuse me why I interject that it's a royal PITA when people post 
obfuscated IP information while asking IP-related questions.  It 
inevitably introduces confusion.  Ok, I feel better now...

When I have the network set up in this manner (packets coming in via 
two
external lines plugged into the same switch), I can only access the
network that is on the same network as the default router.  In the 
example
above, I can access the server by 1.2.3.4, but not by 2.3.4.5.  If I
change the defaultrouter to 2.3.4.1, I can access the server by 2.3.4.5
but not 1.2.3.4.
Access the server from where?  Let me test my understanding.  You have 
a server with one NIC and two addresses, plugged into a single switched 
network along with two ethernet connections to external ISPs, and 
you're trying to connect to the server from a remote network via the 
different addresses?

If both addresses can reach the network you are connecting from, it 
should work via either address.  Note that the RESPONSE may come to you 
from a different address, and if that confuses your application THAT 
may break.  For example, if you come in on 2.3.4.5, the reply will 
still return via 1.2.3.4 - your server can only have one default 
gateway, and if that's how it knows to reach you, that's where it will 
go.

If your two networks can't both reach your source network, then yes, it 
will break.

There are workarounds, most involve either a dynamic routing protocol 
that can assign priorites to the different paths, or introducing an 
external device (firewall, router) that basically does the same thing.  
Essentially you need more elaborate routing that takes availability 
into account.

KeS
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Routing issue

[Web Walrus (Robert Wall)]

> > ifconfig_dc0 inet 1.2.3.4 netmask 255.255.255.248
> > ifconfig_dc0_alias0 inet 2.3.4.5 netmask 255.255.255.248
> > defaultrouter="1.2.3.1"
>
> You need to change your netmask for the alias to 255.255.255.255 if it's
> on the same network.

It's not on the same network; that's the problem.  Two complete separate
networks, same interface card.  The issue is that one of the networks
works, and the other doesn't, depending on what network the default router
happens to be on.

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Routing issue

[Nelis Lamprecht]

On Mon, 2004-07-19 at 11:12, Web Walrus (Robert Wall) wrote:
> I just installed a secondary internet connection at my office, and I'm
> having a bizarre issue...
> 
> I have a network card - dc0
> 
> That network card has a config roughly like
> 
> ifconfig_dc0 inet 1.2.3.4 netmask 255.255.255.248
> ifconfig_dc0_alias0 inet 2.3.4.5 netmask 255.255.255.248
> defaultrouter="1.2.3.1"
> 

Read this page regarding adding aliases:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-virtual-hosts.html

You need to change your netmask for the alias to 255.255.255.255 if it's
on the same network.

Regards,
-- 
Nelis Lamprecht
PGP: http://www.8ball.co.za/pgpkey/nelis.asc
"Unix IS user friendly.. It's just selective about who its friends are."


signature.asc
Description: This is a digitally signed message part

Re: newbie cluele re routing issue

[Stephen D. Kingrea]

yes, it is cable/dsl. that would explain the lack of connectivity under
the linksys scenario.

i will try this again and report back. thank you for the clue

stephen d. kingrea

On 10 Jan 2003, Matt Smith wrote:

>Regarding your ISP -- is this a DSL connection?  If so, your DMZ server
>(connected to the Hub) probably needs to run PPPoE.  Is it?  Anything
>behind the linksys device does not, because the linksys device takes
>care of PPPoE for everything behind it.
>-Matt
>
>On Fri, 2003-01-10 at 14:20, Stephen D. Kingrea wrote:
>> ok, i know that i am a newbie, but perhaps what i am trying to do is
>> impossible.
>> 
>> goal: host 2 domains locally
>> equipment: linksys wireless router (4 ethernet connections--wireless not
>> running yet), freebsd 4.7 on dedicated p166, and several boxes/os's
>> connected dhcp.
>> 
>> i assigned router 1 static address (68.114.63.14), server lan address
>> (192.168.1.110). domain1.com is working.
>> 
>> i wish to alias second static address (68.114.63.34) on server for
>> domain2.com. 
>> 
>> try as i might, i cannot make this work. is it even possible?
>> 
>> linksys says: place hub between modem and router, connect server to hub
>> (placing server outside lan). that scenario renders server incapable of
>> communicating with isp's router (68.114.63.1).
>> 
>> i am beginning to wonder whether i can even accomplish this. it seems
>> simple enough, however; i just can't make it work
>> 
>> any suggestions?
>> 
>> tia
>> 
>> stephen d. kingrea
>> 
>> 
>> To Unsubscribe: send mail to [EMAIL PROTECTED]
>> with "unsubscribe freebsd-questions" in the body of the message
>-- 
>Matt Smith <[EMAIL PROTECTED]>
>
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-questions" in the body of the message
>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: newbie cluele re routing issue

[Matt Smith]

Regarding your ISP -- is this a DSL connection?  If so, your DMZ server
(connected to the Hub) probably needs to run PPPoE.  Is it?  Anything
behind the linksys device does not, because the linksys device takes
care of PPPoE for everything behind it.
-Matt

On Fri, 2003-01-10 at 14:20, Stephen D. Kingrea wrote:
> ok, i know that i am a newbie, but perhaps what i am trying to do is
> impossible.
> 
> goal: host 2 domains locally
> equipment: linksys wireless router (4 ethernet connections--wireless not
> running yet), freebsd 4.7 on dedicated p166, and several boxes/os's
> connected dhcp.
> 
> i assigned router 1 static address (68.114.63.14), server lan address
> (192.168.1.110). domain1.com is working.
> 
> i wish to alias second static address (68.114.63.34) on server for
> domain2.com. 
> 
> try as i might, i cannot make this work. is it even possible?
> 
> linksys says: place hub between modem and router, connect server to hub
> (placing server outside lan). that scenario renders server incapable of
> communicating with isp's router (68.114.63.1).
> 
> i am beginning to wonder whether i can even accomplish this. it seems
> simple enough, however; i just can't make it work
> 
> any suggestions?
> 
> tia
> 
> stephen d. kingrea
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-questions" in the body of the message
-- 
Matt Smith <[EMAIL PROTECTED]>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

newbie cluele re routing issue

[Stephen D. Kingrea]

ok, i know that i am a newbie, but perhaps what i am trying to do is
impossible.

goal: host 2 domains locally
equipment: linksys wireless router (4 ethernet connections--wireless not
running yet), freebsd 4.7 on dedicated p166, and several boxes/os's
connected dhcp.

i assigned router 1 static address (68.114.63.14), server lan address
(192.168.1.110). domain1.com is working.

i wish to alias second static address (68.114.63.34) on server for
domain2.com. 

try as i might, i cannot make this work. is it even possible?

linksys says: place hub between modem and router, connect server to hub
(placing server outside lan). that scenario renders server incapable of
communicating with isp's router (68.114.63.1).

i am beginning to wonder whether i can even accomplish this. it seems
simple enough, however; i just can't make it work

any suggestions?

tia

stephen d. kingrea


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message